This comes up over and over again. In my opinion it doesn’t even come down to your standing etc - I’m streaming data over HTTP, for the most part, and only I get to choose how that’s rendered. It just so happens that my renderer discards outbound requests to certain domains and drops some HTML/JS components that look bloated and or unnecessary.

Piracy? Theft? What a joke. My attention and complacency was never a component they should have relied on in the first place. This is a technical issue for me, not a moral one.

Coffeescript…

Why is documenting and making a front page to a website so hard? Checking both the blog and their website, I can’t tell what Luanti even is…

Context would be super on these kinds of posts.

And Tuxedo in Germany - just got my InfinityBook pro 14 and it’s been great.

Now it takes four engineers, three frameworks, and a CI/CD pipeline just to change a heading. It’s inordinately complex to simply publish a webpage.

Huh? I mean I get that compiling a webpage that includes JS may appear more complex than uploading some unchanged HTML/CSS files, but I’d still argue you should use a build system because what you want to write and what is best delivered to browsers is usually 2 different things.

Said build systems easily make room for JS compilation in the same way you can compile SASS to CSS and say PUG or nunjucks to HTML. You’re serving 2 separate concerns if you at all care about BOTH optimisation and devx.

Serious old grump or out of the loop vibes in this article.

Both are rubbish in my experience - both on the development side and installation side. To be honest I don’t love building any of the package formats for Linux, and prefer installing deb/rpm. Old school I guess.

This doesn’t exactly help your situation, but as a developer that builds and publishes docker images most days of my work week, I’d not suggest anyone do the same on a drive smaller than 512GB. Docker builds create layers on the fly as changes are seen and these can range from bytes to hundreds of megs at least. Casual docker development will easily chew through a few hundred gigs after a while, in my experience.

Just trying to put things in perspective: sadly, 70GB is peanuts here if you’re working with popular software stacks. Yes there needs to be some virtual image for docker desktop and due to the above, I usually have mine set at over 200GB.