hambes

Tailored suits fit better than off-the-rack street clothes? That is not an argument for suits, it's an argument for tailoring.

or just tax wealth and profit instead of income and tools. these are neither new ideas nor are they specific to the proposed llm-based worker replacement

does anyone have resources on how to build surface-to-satellite missiles at home? seems we'll need those at some point

I am not scientist enough to judge this, so please someone enlighten me: most categories i've read through that find a shift do so with an increase of about 0.1-0.2 standard deviations. that does not sound significant to me. is that enough to make the claims this study makes?

the article mentions three types of stakeholders: contributors, debuggers and incident responders. it entirely fails to mentions consumers, who mostly care about backwards compatibility of changes, and thus about the type of a change. once the type is established, e.g. a change is breakimg, the consumer next cares about the scope to make downstream adjustments.

the part about broken promises regarding breaking changes is _kind of_ fair, but only assuming tooling isn't able to track reverts. accidental breakages occure with every approach and better to have an approximation than no information at all.

I've always wanted to do this, but can't get over the linux tty only supporting 256 colors. If I could get that higher and maybe add unicode support, I'd love to go tty only.

then the military would also act life-saving, since they are defending the attacked country

because approval processes take time which i can use to keep working

I agree that a `gh stack` command is not needed, but this feels to me like just a better UI feature for a good git workflow. It literally is about making multiple smaller PRs that build on top of each other.

for one thing the ingress nginx is retiring[1], so they're probably revsiting alternatives, maybe even the service meshes for the new gateway api.

1: https://kubernetes.io/blog/2026/01/29/ingress-nginx-statemen...

yes, i do realize that. thank you for expanding on my point.

demand for AI is not high, which is the current problem of the industry and the reason that AI companies are trying to shoehorn their technology into products everywhere.

these companies and the author of the article are trying to increase capacity for something that barely anyone wants in the software they use, which makes it all the more wasteful.

it is difficult to comprehend for me that soneone spends all this time thinking through and calculating how to harness as much energy as possible and then wants to use it for large language models instead of something useful, like food production, communication, transport or any other way of satisfying actual human material needs. what weird priorities.

I've been doing a similar thing using GhostSCAD[1], which is a relatively thin wrapper around OpenSCAD in Go. Not as typesafe, but my language of choice.

[1]: https://github.com/ljanyst/ghostscad

is that first sentence entirely broken or am i having a temporary lapse in cognition?

To add to the very short "valodating the result" section, let me recommend `git range-diff`.

Range diff takes two commit ranges and compares thor commits pairwise, wich is perfect for rebases, since after the rebase all commits still exist and should be mostly identical, just at some other place in the history.

Use it like `git range-diff main..origin/mybranch main..mybranch` to compare the local, rebased branch with the upstream branch.

This let's you easily verify that eitger mothing changed or that any conflicts were resolved well.

sure, let's build more energy sources with finite fuel supply and negative environmental impact while there's better options available <.<

Why would I need claude code for remote programming, if I could just use ssh and tmux?

thank you!

As someone who is not deep into linux desktop history: Can you please elaborate on the missing accessibility features in wayland or direct me to resources on that?

I've been using wayland for a while now and am very happy with it, but my accessibility needs are pretty basic.

Maybe, but that is a different issue.

The use of generative AI for art is being rightfully criticised because it steals from artists. Generative AI for source code learns from developers - who mostly publish their source with licenses that allow this.

The quality suffers in both cases and I would personally criticise generative AI in source code as well, but the ethical argument is only against profiting from artists' work eithout their consent.

That's awesome. I like the explicit nature of go and usually the verbosity is worth the benefits. But finding ways to improve upon it without losing the explicitness is great.

Because when Ferret7446 says "neutral", they mean "anything that doesn't harm them". Centrism is a lie.

probably not relevant to you, since it is yet another tool for managing your development environment, but maybe have a look at devenv (https://devenv.sh). it's main purpose is managing the development environment, but it has integration for pre-commit (or even prek iirc) that let's pre-commit do it's thing, but takes over the dependency management.

read the article, it recommends devenv or pre-commit as tools that do thr setup for you

zero delay on commit, but then an entire CI run and feedback loop just to fix a linter or formatting issue

maybe, because i really don't have the problem you're describing.

yes, formatters run on every commit. not only during rebase, but also every commit beforehand. if that is done consistently, the formatter does not cause merge conflicts.

merge conflicts during rebases due to variable name changes occur without commit hooks, too.

I would argue that if the pre-commit hooks come in the way of rebasing, either the commit hooks are doing way too much (which is one of the points of the article) or you are creating broken commits during rebasing. If any of the commits you are rebasing is e.g. breaking formatting rules, they shouldn't have been committed that way in the first place.

This is the first time I ever got ruby. Reading it always felt like magic to me and I think it's still too much, if I really want to understand the abstractions, which unfortunately I do. But the understanding of blocks and especially instance_eval has helped a lot.

you're telling me my depth perception is not creating a 3D model of the world in my brain?