(2/2)

A system where the faction with the most absolute and unquestioned loyalty wins fights and slaughters their intellectual betters.

This reeks of a bourgeois fear of the masses rising up to demand what’s rightfully theirs, of thinly veiled elitism and misunderstanding of the basics of class relations. No, it's not blue vs white collars but people living off others' toil and the toilers.

Who are these “intellectual betters”? Capitalist apologists? Corporate technocrats? The same people whose “brilliance” built a world teetering on ecological collapse? Spare us the melodrama. Revolutions don’t thrive on blind loyalty; they’re built on solidarity and the shared understanding that the status quo is unsustainable.

Your argument boils down to a defense of complacency: ballots over barricades, submission over struggle. You seem more afraid of the risks of change than the certainty of suffering under capitalism. But history teaches us that systemic change demands courage—not the cowardice of hoping billionaires and their henchmen will play nice. Keep clutching those ballots; the rest of us will be busy building a world where they aren’t needed to decide who gets to live with dignity.

Akkoma's bubble feature should be ported to other software

Notesnook ftw

Good luck to AI-based legal "solutions" startups, hope they and their customers are generously insured to cover for the fallout of such blatantly ignorant stupidity that completely discards our current subject matter expertise, which clearly shows that the error rate is too high, while you're either right about the law or you're not.

if you want even more frictionless experience and save a few megs of ram check out wezterm, it does a pretty good job of integrating multiplexing into terminal. also it's very extensible as it's configurable with lua.

on a side note, I had some stability issues with vscode-neovim where it'd crash it in worst cases.

it's a feature not a bug, still simpler than chaining 10 iterators where half of them also requires a callback parameter. Clojure even disallows nested % iteratees.

Yes even for technical writing it's absolute shit. I once stumbled upon a book about postgresql with repetitive summaries and generally a very algorithmic, article-like pattern on literally every page.

I mean, libraries access is good. But lack of tail call optimization support is not something you'd want in a functional programming language runtime. Luckily here Clojure somehow manages to fare better than Scala.

This. Y'all should checkout Saintdrew's discussion on crops

also just plain readability. Indentation-based scoping is horrible for larger codebases. Maybe if it was a purely-functional language like Haskell where this sort of scoping works better and all effects are tightly contained. But most larger codebases tend to use python in OO way and that can get messy pretty quickly. Damn, if python had a piping operator like elixir that'd be of a lot of help, actually. Plus there is so much legacy code in a language that had e.g. ternaries long before adding something seemingly so fundamental as switch-case.

tbh the biggest upside of competitive programming sites was when I finally learned some Scala so that I can feel smug about my elegant one-line solutions dabs in a very specific way that makes my arms resemble a lambda /s

still not your keys