Just to be explicit, if you skipped over that link when it crossed your feed, you need to go back and click it right now. Here it is again:


@sir The sentiment is good, but so many of the details are wrong it hurts. With his document example, selecting two at a time would prevent the software from deleting both documents. And with his OS kernel example, there have been a bunch of kernels in the past 25 years! None of them have really seen much popularity, but they're there.

Outside of the few errors though it's a pretty great manifesto.

Excellent read and certainly addresses a lot of concerns.

cc @don_gato

mini rant, swearing 

mini rant, swearing 

A couple of years ago this guy wrote some excellent stuff about Clojure programming, but what he's doing now, it's just... counterproductive.

@VikingKong I disagree with every amount of sincerity and emphasis I can muster


have you got a tl;dr of your counter-criticisms?

(I was tempted to just write "I am interested in your theory and would like to subscribe to your newsletter" but I'm feeling good enough today to keep the snark somewhat in check.)



just like the article says, i still use my dos accounting app in 2020 :)

@sir No proposed solutions though.
IMO impossible unless metrics for complexity are defined for the project or you have a PM not overly budget constrained.

@sir According to CoreBoot developers, what BIOS does for so long is just waiting — an artificial delay to make it look like it "thoroughly checks" the hardware…
Same, I guess, is true for the other proprietary s/w.

Why? — Because of the management, pressing to squeeze a month's work into a week. And also the bandwagon effect, making the "industry-standard" tech. popular for libre s/w as well.

What do? — IDK, take stance?…

@sir P.S. Another factor is that the shittiest languages (e.g. JS) are the easiest to "pick up" for complete newbies, at the expense of virtually impossible optimization and huge rate of technical debt.
IDK whether a strict regulations will change the incentives.

I used to work for a company that did good work, with every piece of software being as lean and fast as possible... except for the installer.

Having an installer take only 2 seconds was perceived as "unprofessional" by some clients, so my boss added an artificial delay after every decompressed file, so the install would take at least a couple minutes.



@jon_valdes @sir So "normal" → "professional" in their opinion? Non-technical people making technical decisions, I hope they're increasingly irrelevant…

@amiloradovsky @sir well, it was a comparative thing. "So this thing costs as much as 3D Studio Max, which takes 40 minutes to install... but this thing installs in 2 seconds? I've been ripped off!"

@sir That post sure struck a cord. I don't know what happened to pride in craftsmanship in the software development industry, but I sure do miss it.

@sir The general thrust of the argument is bang on. I agree totally that inefficiency and bloat should not be tolerated.

Where we diverge a bit is what should be considered "bloat", and I'm not sure even he knows precisely.

> An Android system with no apps takes up almost 6 GB. Just think for a second about how obscenely HUGE that number is. What’s in there, HD movies? I guess it’s basically code: kernel, drivers. Some string and resources too, sure, but those can’t be big.

He has no idea what's in there, so he just takes a guess and builds an argument around it?

The mistake a lot of people make when they pine romantically for the days of old, efficient computing, is that to some degree they're unwittingly dreaming of the days when everyone was an able-bodied American English-speaker. Everything's easy when you have 128 glyphs, one typeface, one text direction, no composition, no accessibility features, etc.

Google Noto ALONE is well over 1GB. There's no way to get around that.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!