I'm surprised about the negativity in the comments. I'm happy someone is testing alternative approache. If they're wrong, they just wasted a bit of their own capital. If they are right - we might all benefit. You've got to treat technology as means to an end, not a religion that requires conformity.
People got so stuck on JS for decades that they've forgot that HyperText in HTML is there for a reason. It was always supposed to be more than just UI descriptor markup.
It is JS who is out of place in web. A little script in form of DHTML that grew into becoming a cancer that it is now.
It doesn't matter if we get rid of The Agile. If you make The Agile go away, there will be something else, equally horrible.
The internal incentives in hierarchical organizations is to balloon the management, which suffocates the bottom of the pyramid. That's just how the world works, for most people, not just SWE. The Agile is horrible because corporate management makes everything horrible.
If you don't like it work in a small, carefully selected startup, or make your own company. Otherwise just accept that you're just a corporate drone and you have to endure the shitty corporate system to pay your bills. At least you get paid decently, because there's not that many people to replace you like in other professions.
I disagree. Merge conflicts are just a fact of life, and line-granularity has good usability properties (displaying and editing). `git` has issues, but I don't see merge conflict granularity being an issue, especially when project enforce consistent&automatic formatting.
I agree however that while Pijul is technically very interesting, it doesn't seem to have any killer features that would overcome the cost of switching to a niche version control.
To contrast tech workers against working class, and redirect resentment. It's not billionaires that turned the system against working class. It's the nerds at Google that make six figures, duh.
Is it? Because AFAICT people censorship themselves online all the time for the fear of repercussion. It's like being on tape 27/7 where anyone that doesn't like you can watch your old tapes and loook for problems.
At very least some free tier for NAT64 gateways, or shared DNS64/NAT64 alike https://nat64.net/public-providers for Amazon users would be nice. I'm fine with ipv6-only connectivity for a lot of hosts, but once in a while they need to download some software / updates from github.com which is still ipv4-only. Paying fixed extra cost for every subnet just for 100MB/mo download per host is meh.
Large part of biggest crimes I've seen in software comes down to picking some allegedly good property and optimizing for it irrespective of costs and limitations it involves. Encapsulation, modularity, flexibility, readability, purity, testability - you name it. Some dubious, some reasonable - no matter what, it usually involves costs and drawbacks.
I have 99 big problems developing software, and not being able to read it from start to end ain't one.
I'm a bit jealous for people advocating such things, being able to work on software tiny enough to even be able to think this is practical. Literate programming could work for tiny software that can be approximately flattened to a 1d "story": "beginning -> end" with only minor detours.
Most of projects I worked with was large enough that things are optimized precisely for not having to understand large parts that were abstracted away (and the problem is to try to do it without introducing too much complexity).
Love both Tailscale and Xe's writing as well, and indeed, all these (rather irrelevant) images are just breaking the flow of reading/skimming the content. I guess I'll just watch the video instead.