Sure, you could write a frontend without something like react, and create a backend without something like django, but the code generated by an LLM will become similarly convoluted and hard to maintain as if a human had written it.

LLM's are still _quite_ bad at writing maintainable code - even for themselves.

Azure storage is absolute hot garbage.

Still worth using though and is pretty straightforward and easy to use.

Not blaming anyone - the maintainers don't owe us anything - it just wouldn't be my crate of choice if I was starting today. If any of the maintainers read this, shoot me a message because I'd love to help out and get the ball rolling again on tide.

Hopefully someone that works there is reading this.

Binary data support is pretty nice too for avoiding multipart request bodies.

If a manufacturer made a truck similar (or slightly larger - not much room for people 6' and over in them) available for the market here, I'm sure they'd sell well. Seems like the biggest impediment is the safety laws here though and American insistence on having the biggest vehicle on the road.

Having the static frontend assets baked in along with a default config is a huge boon though.

Even if this proposed mast is stepped through the entire container, the forces on it will be plenty to cause issues since the containers are only held down by neighbouring containers and the 4 anchoring twistlocks. This proposed design will 100% require standing rigging to support it - the claim that the rig will only experience 10s of kn of loading is almost certainly incorrect as well - 30ft racing sailboats will experience loads exceeding that at the chainplates regularly. The moments about a mast are huge, even on relatively small rigs.

Axum by comparison has a very active community, but I found it's request handling and middleware concepts much less ergonomic. If you're debating between rust webservers it's worth taking a look and giving tide a chance. The async-std choice hasn't been an issue for us at all either.

A lot of `if (input == null)` checks are because you're just not sure whether the argument being passed in will have a value, and it's too much work for your small feature PR to refactor the whole codebase to resolve it.

Use typescript/python-with-mypy/haskell/rust/whatever and this problem mostly disappears.

Bluetooth headphones just aren't very good, and we've all gotten in the habit of buying a new pair every few years because they either break, get lost, are unsupported, or have bad batteries.

I previously had the same pair of IEMs for almost a decade that had better sound quality, replaceable cables and eartips, and didn't ever run out of battery. Never did I complain about the cables being annoying or in the way, and never did I complain about the presence of the headphone jack, or the Bluetooth chip onboard.

Removing headphone jacks was a horrible misstep in my opinion and we're stuck with the path dependency it's created now. It's probably not long before we have laptops that omit 3.5mm audio jacks as well.