zachallaun

I feel you. I've been using en-dash in my writing for decades, but finding myself removing them now for fear of being mistaken for an LLM. (They tend to use em-dash, but I don't think people are going to distinguish between – and —.)

Ton of fun! Was interesting to see how my strategy evolved as well. I started out trying to make a large pen, but quickly realized that wouldn't work, so I made a small pen and then started moving it out. This allowed me to see individual optimizations and try alternatives. Even at the end, about to hit submit, I wasn't sure my solution was optimal, but ended up with the optimal sizse-86 solution for today's challenge. Will try again tomorrow!

I'm not so sure. Both Go and Rust seem like examples of very popular ecosystems with a set of common, "blessed" tooling. (They didn't have everything from the get-go, e.g. rust-analyzer was very popular before it became part of the Rust project, but it still demonstrates that a large ecosystem can rally around a set of common tooling.)

Neat!

As someone who has contributed to a language server, I've wanted a language/editor agnostic way to interact with it, primarily for the purposes of black-box testing. I wonder if this could be useful for that?

What's the process for adding support for a new language?

I read this as "owner of _a_ Bob", as opposed to the owner of the actual company.

I think someone demonstrated in the announcement thread that, adjusting for inflation, the Pi5 is going to be cheaper at release than the Pi4.

Ultimately though, at least IMO, the Pi isn't about being cheap, it's about being capable while staying a great value. I bet there's a lot of hidden complexity in the pricing, and it's very possible that they'd have to compromise significantly more than 12.5% of the functionality/performance to get a 12.5% price reduction (to $35).

A naive approach that may still work well is to simply break up the image into fixed, predetermined regions. I don't believe this would be significantly more work for the server if it's already comparing pixel-by-pixel, and the average frame will probably contain updates only in one region. Even breaking it into 4 or 6 would, I think, be a significant payload reduction.

Ehhh, a lot of high level languages support low-level interop. Python, Ruby, etc. It's not something you usually reach for as a user, but rather as a library author.

Of course everyone wants their language to be faster, but the interop story for Elixir/Erlang is very good, all things considered.

Similar issues for me. I can load github.com and my profile, but visiting a repository (or trying to git pull a repo with the https origin) returns a 500.

day-tah-mick (think datum/atomic)

Yep! More putting it out there for other folks. I’m also a somewhat frustrated paying customer, but as I’m dealing with my own growing pains, I relate to what they’re going through. I’ve personally migrated my DB to Crunchy to somewhat mitigate the risk.