News for hackers. Stuff that matters.
Re:The death of web development education by johnnyanmac on Thursday October 01, 2026 @10:38PM (#49929333)
That's not accidental, anymore than human language itself is accidental. APIs are designed very intentionally, and a good API's parameters have architectural reasons behind what they include (or exclude).

Even your example has unintentional complexity. A 'duplicate'? What's that? Do we compare the memory it points to? Through use of a custom comparator function?by an id or tag? APIs and entire languages are designed around how we define such seemingly simple terms.

Ultimately a language, be it a programming language or human one, is about communication. I find there to be value in knowing how to communicate effectively, even if employers increasingly disregard the value of such knowledge. Without it, we'll quickly find out why it's fundamentall quickly.

Re:The death of web development education by _aavaa_ on Friday October 02, 2026 @07:22AM (#49932256)
“Computer add a filter that removes all duplicate entries from this data structure. Two entries are duplicates if they every value in their rows are identical.”

This is the same thing as pressing the power button on my computer; I want the thing turned on, I don’t want to have to know about memory training.

Re:The death of web development education by johnnyanmac on Friday October 02, 2026 @01:50PM (#49936418)
>I don’t want to have to know about memory training.

And then we wonder why apps are getting so much slower and bloated. That's fine if you don't want to think that low level, but someone needs to worry about performance. And others will need different needs for defining a duplicate in their different use cases.

Re:The death of web development education by _aavaa_ on Friday October 02, 2026 @10:15PM (#49940791)
I don’t think that lack of knowledge about memory training is a hill to die on when it comes to causes of app bloat.

The people who need to most think about performance are those making the frameworks and languages. Why are bloated electron apps so easy to make but building native cross-platform apps with similar ergonomics hard? Why are people choosing electron?

Re:The death of web development education by johnnyanmac on Friday October 02, 2026 @10:39PM (#49940933)
>The people who need to most think about performance are those making the frameworks and languages.

Yes. I am not a web dev, but I tend to fall into that category in my domain.

>Why are bloated electron apps so easy to make but building native cross-platform apps with similar ergonomics hard?

If you want to be blunt, it's political. Each OS wants to ultimately build its own moat, so there's less incentive to come together and make a standardized solution. Then Linux is a less centralized OS that makes theoretical cross platform support even harder. Cross platform applications get made despite that friction to fill the obvious demand.

The why's of which cross platform framework wins is hard to say. It only becomes obvious that whoever breaks out tends to win more, and it gets a massive flood of support, funding, and clients. So it snowballs up. Those who don't simply struggle to stay relevant.

Electron likely wins in the market aspect that bloat isn't enough friction to turn off a modern consumer with a modernish (10 years or younger) desktop. And it especially doesn't matter to phones (which tend to skew newer).

Re:The death of web development education by _aavaa_ on Friday October 02, 2026 @11:32PM (#49941159)
Then based on your own analysis, at least the electron bloat angle (that many people, at least many developers, hate and wish was native) has nothing to do with the low level knowledge of the developer. And I would argue that a good deal of other areas of slow software will have the same conclusion, i.e. the slowness is not due to lack of knowledge.