It’s one of those ideas that sounds utterly bonkers and will probably come true even if in a limited way. Why not have a fresh heart ready?

I found it easier just to drop social networks entirely.

I don’t need it so much to seek an alternative.

I really feel for Dan Bricklin. He should have been richly rewarded for his innovation.

He was, for a time, until others made even better products. It would've been terrible if he had exclusive IP over the idea of "digital spreadsheet".

64K was huge when the Commodore 64 came along.

I barely used or remember the ZX-81 my folks had with it's amazing 1KB of memory. It had a 16K expansion module you could plug into the back, which apparently made a big difference, but also didn't have the greatest connection. You could easily dislodge it typing on the keyboard. I do remember my father coming up with various ways to try to secure it.

The ZX Spectrum that followed, with its huge 48K of RAM was night and day. The programs were so much more complicated.

Even echo on linux these days takes 38K of disk space and a baseline of 13K of memory to execute, before whatever is required to hold the message you're repeating.

Fixing the 16K RAM pack makes an apperance in the Micro Men film:

https://youtu.be/XXBxV6-zamM?t=1694

RAM was so tight on those 8-bit machines that many games used tricks like hiding things inside the viewable area of the screen to eck out just a little bit more.

Not sure why the down votes, this is true. If you only had 16, 32, or 48K then 64K seemed like a lot.

Hell, the RAM size was so important that they named machines after it.

Use it or lose it folks.

Hard to believe people are asking this question in 2026.

Quality is something that takes dedicated focus and lots of work. Therefore it’s a job, not an afterthought or latest priority for someone whose primary focus is not quality.

So why would you outsource it to another team that isn't doing the actual work?

QA is actual work. Building the thing is actual work. Each is not "the" work, which is the task of the whole company.

QA perspective and focus is just different from the one of the team building the thing. It's precisely because of their detached perspective that they can do their work properly.

Team doing the work should do QA so they only produce quality.

But on other hand those people can not often be trusted. As such you need a team that does checks again. Or alternatively they might have misunderstood something and thus produced incorrect system. Or there is some other fault in their thought process or reality. And system operates differently in more real scenario.

Like the majority of slop articles, the author is advertising his services.

I knew a guy who had a dog that ate cigarette butts.

Age verification isn’t misleading is it?

and then they all break out into song and dance.

If you reaaaly dont liiike it, dun dudun dun!

Lock the taskbar. lock the taskbar! (ref: z0r . de / 2090)

Man, I love 20+ year old memes. The early Internet was a better place.

The problem Deno faces is that nodejs is “good enough”.

Pray you never have a “good enough” competitor.

I felt it should have aimed to be a 100% drop in replacement for nodejs then innovated on top of that.

Tried moving a monorepo off Node once. The runtime swap was the easy part. What killed us was the 50-odd package.json files with node-specific stuff baked in. Conditional exports, postinstall scripts, engine constraints, pnpm overrides. Bun got this right by just eating all of that as-is. Deno asking you to throw out package.json on day one was basically asking you to rewrite your entire build config before you even got to try it.