perry

joined 8 months ago
[–] perry@aussie.zone 5 points 1 week ago

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

[–] perry@aussie.zone 14 points 1 month ago (1 children)

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.

[–] perry@aussie.zone 8 points 2 months ago* (last edited 2 months ago) (1 children)

Guess Seagate will continue getting my money then.. though via recertified options as I want the 28TB models.

What a joke.

[–] perry@aussie.zone 4 points 4 months ago

Doomwater? Missed opportunity.

[–] perry@aussie.zone 1 points 4 months ago

Yes, you probably want Geyser: https://geysermc.org/

[–] perry@aussie.zone 4 points 5 months ago

Why is blue sky in the right side column? It’s the same thing as X.

[–] perry@aussie.zone 3 points 5 months ago

This isn’t true anymore, as vendors have the ability to provide other engines within the EU.

[–] perry@aussie.zone 2 points 5 months ago

Not in the EU, at least. Time will tell if any major vendor bothers to provide a custom engine (read: their own). But important to note that this isn’t the limitation it was.

[–] perry@aussie.zone 3 points 5 months ago

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.

[–] perry@aussie.zone 4 points 6 months ago

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.

[–] perry@aussie.zone 3 points 6 months ago (1 children)

This is why I unplugged my TV from the internet some time ago. It’s been bad for a while but this is insane.

[–] perry@aussie.zone 3 points 7 months ago

Get everything migrated across to my new k3s cluster. I’ve been using larger boxes (unraid) and a couple of 1L mini PCs with proxmox to run my homelab until now.. but I work with kubernetes and terraform daily and wanted something declarative.

I’ve now got k3s setup with a handful of services migrated (Immich, Tailscale, Nextcloud etc) but there’s still a ton to go (arr suite, various databases, Plex, Tautulli etc). It’s another job entirely.

I love it but sometimes I wonder why I do this to myself 😅

view more: next ›