0x6c6f6c

I think they've likely dropped the focus entirely while they work to catch up. Just running open source projects alone has administrative overhead and headcount dedicated to communciations and oversight. May be something they trimmed in the name of focus or gains.

I'm not happy about it, but I can see why they would. I want to incorporate some of these things locally myself.

Given these two are both comparable to the Cloudflare developer stack that I often think of as alternatives, this makes the decision to let Deno die feel at least a bit more calculated.

Time can be an issue connecting to Wi-Fi. Devices who've lost track of time often can't properly negotiate access to then get NTP updates to their time. Perhaps this could be solved, but it's a common problem for devices left for the batteries to go dry.

It is a bit sensationalist to say this is reviving it though, which makes this sound like some wild issue.

It is default behavior based on implicit environment setup. But I think the title could use updating because it is misleading without that.

Perhaps "creates CLAUDE.md for claude-code users by default" instead.

What are you using for OCR locally? This is something I've been considering trying for some time with old journals.

Comparing self-hosted immich and a truly E2EE hosted platform like Ente is really odd. There are massively different trade-offs and target customers between these.

Ente is a private hosted photo storage and sharing platform. Only trusted devices that can decrypt /encrypt would even be able to perform the kind of work to tag photos for face recognition, and in this category I'm not aware of any hosted alyermative that actually does this, and they do a _pretty good job_ considering the limitations of E2EE.

Immich, Google Photos, Apple Photos- these platforms don't have to work around the fact all user data is opaque ciphertext. I imagine you could extend the capabilities of machine learning to a trusted node (similar to what you can do with Ente Desktop, but with more capable models), but they still have to work around any of that metadata being visible to them as well.

This takes somewhat trivial problems and makes them entirely non-trivial to solve. Self hosted platforms that don't provide an E2EE story have significantly less headache to deal with, especially since most people justify it by "it's running on my server so it's okay". And I get that, you can generally work around this issue with disk-level encryption and you're all good. It's just not the same product at all.

That's a somewhat reaching use of the word "natively".

It's being run through the equivalent of a virtual machine. So it's really quite similar to the layers used to abstract away platform specifics like Wine / Proton does for Windows compatibility. Instead of DXVK you have WebGL.

There is no comparison when running a TypeScript project with Bun vs with Node. Or when mixing ESM and CJS. Or when setting up unit testing.

Node and its ecosystem was considerably behind in multiple regards.

Bun does zero work in relation to TypeScript's type system. Since it's a strict superset, it is "simply" stripping types to execute the resulting JavaScript. That is effectively what it boils down to.

TypeScript is the most complex type system in existence. I am unsurprised it is difficult to port, but I am still a bit surprised by the length of the project thus far.

Microtransactions. In a non-joking sense. People pay for outfits or gear to wear to the rave. Or they can work for it in game. Maybe a bit like EVE Online where you can pay monthly to play but if you make enough in-game you can buy a months subscription.

Honestly Claude straight up ignores my input sometimes, preferring to instead run commands for output and processing that and burning through a series of tokens when thinking hard about whether to ignore me.

Like today, I told Claude exactly the name of the folder it had mistaken (it was supposed to be prod, not production), and it disregarded my input to then examine the directory itself. Small example of the kind of things it's been doing lately but that's top of mind.

And if you were a smaller team then you don't even need K8s. Just ECS or Cloud Run have simple abstractions for horizontally scalable services and sidecars support.

I like TEA but don't fully grasp how it scales for apps that may have reusable components or sufficiently complex pages. Is there an agreed-upon way(s) to deal with this? I know state is a big NO so it seems a bit at odds, but also does this essentially mean all Elm apps are just a global Redux and React app with no effects? Curious about more details to what you enjoy and how you like to work in Elm. Links also perfectly fine too.

What are some of the alternatives that are worthwhile for this?

Many people do use GitHub for this. There are even Android app stores hinged around searching and installing release APKs.

The social connectivity and discoverability in github is a big reason many people use it. Can't say how many, but it is.