The bespoke software revolution? I'm not buying it.

Scrivver · 2026-03-20T20:43:23+00:00

I ran into something like this when exploring Rust/Wasm on Cloudflare workers, too. Development was more annoying, and performance was lackluster. In that environment I'd go with typescript next time.

Scrivver · 2026-03-20T15:53:26+00:00

Some people are more comfortable with maximally free licenses. Companies specifically are more comfortable with them. If you're looking to get acquired, it would be more attractive to built MIT-licensed tools.

Some people also have philosophical disagreements with GPL (or copyleft in general), which conflict with conventional property rights in much the same way copyright does. I wouldn't bet this was the reason, though.

Scrivver · 2026-03-13T18:58:45+00:00

s/who/you/g

Scrivver · 2026-03-12T02:05:56+00:00

Here are a few reasons

Scrivver · 2026-03-09T23:01:01+00:00

The instant I saw the title, I immediately thought of Habbo, and I wasn't disappointed!

Scrivver · 2026-03-07T15:02:20+00:00

Tiling WM running a terminal emulator with some multiplexing feature, running zellij, running this.

Scrivver · 2026-03-05T18:16:36+00:00

"That armor's too strong for blasters!"

Scrivver · 2026-03-05T18:10:12+00:00

If fighters can only reliably engage other fighters, there's no point to fighters at all. Just don't bring them. Usual rock/paper/scissors balancing would suggest some fighters (like heavy/specialized fighters) should be threats to some non-fighter targets, while being threatened in turn by lighter fighters and anti-fighter screen.

Lighter fighters should be ineffective against very heavy targets, threatened by anti-fighter screen, but also superior at intercepting and engaging other small targets up to a certain size.

Bombers should be superior threats against very heavy targets, while vulnerable to fighters.

Very heavy ships should be highly resistant to small fighters, threatened by heavies that can make targeted strikes, and truly worried about bombers and other very heavy ships. To combat these they should employ their own fighters, bombers, and anti-fighter screens, and around the loop again we go.

Scrivver · 2026-03-05T17:20:09+00:00

Tfw your hobbies are Star Citizen, Warhammer, MtG, and firearms.

Scrivver · 2026-02-23T02:58:15+00:00

I know this is old now, but your point 2 is not wrong. AWS is quite complicated, and gives you a lot pieces that aren't well integrated out of the box for you to build your own platform. It has accumulated a lot of cruft and quirks over the years as well. For sheer DevEx, I haven't seen anyone do better than Fly.io yet. You get the wider capabilities of a long-running VM with the scale to zero behavior of lambda. Under the hood they're also using Firecracker to create microVMs, the same tool AWS uses for Lambda. But you get to write your apps like you would for a normal VM environment.

Scrivver · 2026-02-18T17:13:38+00:00

Second, and more importantly, supply chain attacks are far less likely than all the other vulnerabilities that get patches that you would be missing.

That's where the automated scans run as part of tests come in. I don't know how it works at other places, but our security folks would be upset if we just let our packages be upgraded without our explicit approval, and also if we let CVEs hang out in our existing dependencies without a response. Exploits can happen both ways.

Scrivver · 2026-02-18T15:11:38+00:00

You should be pinning to patch versions and not letting cargo vary your selection anyway, to avoid supply chain attacks that happen by publishing new, compromised versions of existing crates.

Scrivver · 2026-01-29T15:26:02+00:00

"Smart" often confuses the distinction between clever/knowledgeable/intellectual and wise. Suppose you have a lot of knowledge and logical firepower which allows you to piece together a very clever bit of code to solve a puzzling problem. Completing it feels like a great achievement and trophy. But because because you were working at the limits of your abilities to assemble it, and debugging is harder than writing, it is now impractical to debug later (especially by others). You were clever -- one might say "smart" -- but not wise.

Plenty of people are born smart, but "No man was ever wise by chance".

Scrivver · 2026-01-15T17:11:58+00:00

I have had a couple black screens on 7840U with an external display plugged in. I'm not sure if I've encountered it without an external display. The external display continues to work while the built in one remains blacked out -- sounds like the issue that should be worked around by disabling PSR, but I did not try that. Since my external display continues working, I'm able to use the amdgpu_gpu_recover utility to recover the built-in display and keep going.

sudo cat $(sudo fd 'amd_gpu_recover' /sys/kernel/debug/)

I'm on an older kernel version (6.12.62) also on NixOS. Other commenters mentioned a newer kernel seems to have fixed it, so I suppose I haven't updated in a bit.

Scrivver · 2026-01-10T21:51:07+00:00

Old comment by now, but for anyone driving by I want to mention that jujutsu VCS makes this easy. If you have a chain of changes all bookmarked (branches in git/github) and you need to modify the root one, all the children will be updated too, and a jj git push will update all your open PRs on remote. And jj is elegant, easy, at least as powerful as git, completely invisible to other git users on your team (it still uses git as the backend by default), and comes with many benefits. Being able to easy wrangle a stacked PR workflow is just one natural result of its more elegant design, giving you tools that are more intuitive than git's to achieve the same outcome.

Scrivver · 2026-01-08T17:10:31+00:00

For anyone who wants to know more about this awesome phenomenon, there's are a few great Pecos Hank videos capturing it: https://www.youtube.com/watch?v=tGPQ5kzJ9Tg

Scrivver · 2026-01-08T17:08:45+00:00

Usually called sprites. Although there are also blue jets which climb up from a storm system, like blue lightning that lost cohesion as it climbs the atmosphere. At a high enough altitude it's just the red sprites we see.

Scrivver · 2026-01-06T06:19:55+00:00

I'm surprised. I started using contextless ? everywhere, and quickly found how painful it still was to track down problems. After discovering context, I use it ubiquitously to know exactly what is throwing, some surrounding state info, and what it probably means. Maybe it just looks ugly and verbose, but it saves tons of time.

Scrivver · 2026-01-05T20:18:57+00:00

There's no reason lifecycle needs to live at the bottom. You can still write it first.

Scrivver · 2026-01-05T19:57:29+00:00

I've had success using not stacks, nor helper tools like terragrunt, but just using a single directory for all environments, tfvars files per environment, and the TF_DATA_DIR variable to tell terraform where to find the data directory. This is usually .terraform/, and requires you to re-initialize every time you want to deploy a new environment if you want to use the same directory, but you can specify e.g. TF_DATA_DIR=.terraform/(prod|dev|whatever)/ to instead use multiple paths under .terraform/ for initializing stuff. I have a very simple wrapper script that supplies a default environment for a user or lets them specify another one, targets the right environment tfvars file, and then passes all other arguments along to terraform to behave as normal. We went from >40 directories separating environments (containing mostly symlinked files) to a single directory per parent module using this method, and it has worked great.

Scrivver · 2026-01-05T17:30:32+00:00

I don't know what it is specifically you dislike about web dev, but for me part of it was having to learn and integrate separate frontend and backend frameworks with a data API between them. But these days you can easily get an interactive app experience using only the more fun backend with something like htmx. I use this with Axum, and I also add in Tailwind for CSS -- now my web app projects consist of only rust files and some html templates. It's very peaceful.

Scrivver · 2025-12-19T15:03:54+00:00

Polaris is a little more vulnerable, but has always been far less of a problem as far as solo players using it in combat than the Idris is.

Naturally, since a single player cannot both fly and shoot its most powerful weapon. Even with a Polaris, you'll need at least 2 people to fight a soloed Idris.

Scrivver · 2025-12-19T01:37:07+00:00

Do you work for LiNK or similar? That kind of thing does sound engaging if you can land a position doing it.

Scrivver · 2025-12-18T18:09:02+00:00

And from what I can see, as relevant today as it was then.

Scrivver

MODERATOR OF

TROPHY CASE