Well all they needed to do was erase the screen with white and draw on it, but their app's internal logic meant that they erased it more than once.
I was capturing QuickDraw library calls - the low level graphics primitives, to figure out where the graphics time in apps was going and found out sometimes excel did it 9 times
Of course users didn't see it more than once, but our hardware made all that wasted time run faster
It's more likely that one dev wrote the draw-cell code.
Another dev who's fixing a bug, realizes if they call a certain function either directly or indirectly, their particular bug gets fixed.
Oh, and as a side effect, the cell gets erased (again).
A few more fixes/new features added like this and the code is inadvertently erasing the same cell multiple times.
It takes a certain type of dev to step through in a debugger and Notice the app is doing way too much work and then to untangle the mess of code without causing regressions.
Will never understand why some people prefer mailing lists to do development, it always feels like the most convoluted way to hold a discussion, especially if there are multiple topics at the same time.
It probably doesn't really change that much in this scenario but with a forum or any other topics-based platform you can at least just close and ignore these things without it affecting everyone else.
A good mailclient allows a skilled user a much more efficient communication than most forums.
> It probably doesn't really change that much in this scenario but with a forum or any other topics-based platform you can at least just close and ignore these things without it affecting everyone else.
True, external moderation is a benefit of centralized platforms, but a mailclient allows personalized moderation, which allows with a well organized list to only filter out anything you are not interested in. Usenet had the benefit of both, a centralized platform with moderation, and powerful clients for further personalization. Too bad it died for most usages.
Usenet is probably better, but to a rough approximation, nobody has access to a usenet feed anymore.
Mailing lists allow people to use threads if they want (assuming nobody thrashes the threads headers by using terrible email software from Microsoft/Google), and also allows people to read from the firehose if the want. And there's plenty of threaded web views of mailing lists available for lurkers.
I remember when it was popular, computers had limited storage and bandwidth, and you had to "sip" usenet articles because it was a giant firehose of data, mostly hand-typed text. (excepting alt.binaries.*)
You can still use it. Eternal September provides free access to everything but binaries. There's a number of relatively active groups and some that'll get a post or two a month
Show me a forum or topics based platform that handle threads as good as proper mail clients? Don’t mistake the poor HTML view for how managing threads with thousands of replies look like.
Local filtering is the key to ignoring threads you are not interested in. Depending on the client with 2 or 3 keystrokes you are ignoring the whole thread or this particular sub branch of it and automatically jumping to the next interesting, unread message.
Because ther don't have to keep switching from discussion client to discussion client or whatever tools the use for each project they are involved with, at the same time being distracted by adverts, geegaws, random emojis and other kinds of nonsense.
They are simply more efficient and more importantly censoring is done by the user themselves, not by politically motivated admins who ban discussions based on their ideologies and whims.
This is the reason behind essentially every reply I've ever seen to this question.
"I like it this way because it's always been this way and once you change your entire email workflow and customize your email client, it's almost as good as PHPbb"
Forums are built for threads and are immediately visible and accessible for everyone, not just people who want to spend their limited time dicking with email clients.
Mailing lists are the proto-discord: knowledge locked away from the public behind a special frontend and elitist attitudes. It's only better because the list is technically visible, but only in the worst, most low-effort way possible. You dump a raw txt copy of the entire thread unstructured onto the user and make it their problem to figure out. After all, your email client makes it easy to read, so why should you care about what anyone else needs?
I understand it is out of fashion, but technologically more advanced are systems that use well defined interfaces and allow pieces to be exchanged easily. After all, we’re communicating over a number of open protocols here. A forum merges all elements into one silo. I prefer web over AOL/Compuserve. If you want a forum-like interface, there’s no technical reason why this couldn’t be done on top of a mailing list. In fact, Discourse and others attempted it.
This discussion has been happening since forever. And also the idea that it serves anyone to complain how others are obviously doing it wrong, without even attempting to understand why they’re doing it a certain way. And then be irritated when the response is negative, and labeling others as elitist for using and providing open platforms over decades and not silos.
If you don’t know, feel free to ask. And then suggest (or provide!) improvements that factor in current requirements and goals instead of dismissing them as stupid.
Life advice: if you want anybody to change what they do, you need to first understand why they’re doing it, and then offer suggestions based on that understanding that improve it with them. Otherwise you’re going to continue to recreate your own victim position, and an “elite” position that you will never belong to.
I think it's unsurprising that the people maintaining the tangled plumbing of the clunky, customizable, fiercely independent operating system most popular with highly-opinionated power-users prefer the clunky, customizable, open format that's a little inconvenient for non power-users but allows them to set up their own personal bespoke client.
You like forums for the same reason - because you grew up with them.
Today's preteens will be pining for Discord in the 2050s era of AI Neuralink vibe-telepathy. They'll say once you change your entire workflow and customize your client, phpBB is almost as good as Roblox chat or TikTok comments.
maybe the old tools are prevailing for a good reason.
I prefer people to email me because half of the time they figure out their problems while writing them.
it's not an absolute rule but people who don't do their homework gravitate towards calls and messaging because they just don't prepare their questions.
asynchronous communication puts the burden on the sender, where it belongs.
This could be read as reductive, presumptuous, ignorant, and insulting.
At the same time, it's often technically true, but for a good reason that you neglected to mention:
Those old tools tend to be very capable email clients, not web apps with their awkward attempts to simplify complex conversation structure. A good email client can handle large, high-traffic, frequently branching, long-lived threads with ease. All the web forums I've ever used fail miserably here.
The people who are tasked with participating in large scale discussion groups (like the LKML) know this through experience. They prefer email because it works better. It makes their lives easier. It helps them to be more efficient, which is absolutely necessary given the sheer volume of messaging that they handle.
Yes, a specialized tool is required to get these benefits, just as a specialized tool is required to make web server output easily readable. Thankfully, these tools have existed for decades.
Many "new" tools are basically the old tools with a few additions like emojis and pictures.
I do think upvoting was one "technology" that did make discussion forums different than mailing lists, but that put them under control of someone and had different drawbacks. hn is a good example, reddit is one devolving example
It’s an open format and with basic tools, you can create a very good pipeline to consume the information. There’s no ceiling on the convenience and automation. Gmail and other webmail client are not a representation of good email workflow.
Fortunately my "defenses" worked on this one, though CSS only doesn't seem to have been enough. I don't care if they want to make the user feel like they're living in a blingee gif by default, I just desperately want pages to respect prefers-reduced-motion
If those are referenced in the linked article, I'll be honest I didn't read it. That website succeeds whole handedly in its job of being too annoying to read.
To be honest I don't know of any, I just didn't want to be outright dismissive of it. If you just use it for a header to have some kind of small animation that grabs the reader's attention I guess it's fine. Just don't use it for the main text body.
That's a long-term challenge for the next CEO to figure out.
Unlike CTC or CTC, radio and streaming ad campaigns are notoriously hard to track and attribute, and hence trend to brand-awareness. Advertisers won't see the effect of rising fraudulent streams immediately.
Don't stop Facebook from completely making up video numbers. Seems like it's a good way to rug pull a bunch of workers and force them to accept lower rates.
If someone doesn't know what .gitkeep is they should be able to derive from the name that it's some special file intended for git.
If they then google it they will immediately find out what it's for.
Yes, git itself has no concept of it but it's common enough that there's plenty documentation on the internet.
Yes, because relying on google-fu is the way to ensure your build environment is consistent. /s
.gitkeep is explicitly not intended for git, because git doesn't recognize it at all.
Having the .gitignore, which is actually recognized by the git tools, means you can rely on the .gitignore functionality, including ensuring that things other than the .gitignore cannot be added to the repo.
I feel like I'm having a stroke trying to read this, what does it mean??
reply