Leo_Verto

It's a shame it had to come to this but I can see why Element had to make this choice.

To me it feels like they've ended up in a position similar to Docker Inc. where they've spent years of work and tons of resources building the standards and reference implementations, but missed out on the juicy integration and support contracts.

Docker has turned into the OCI standard and most Kubernetes deployment don't even run containerd anymore. The company has massively rate limited Docker hub and recently increased the pricing again, which has had much bigger impact for end users than this pivot by Element.

I really hope this works out as a funding source for future Matrix development, I don't see how its ecosystem can continue to be developed and healthy without Element.

Like it or not, containers are here to stay. They just make way too much sense as an atomic unit for delivering applicstions and really aren't that complicated.

Kubernetes is a whole nother beast though and while it introduces a ton of overhead, it can be useful at a certain organisational scale as an API definition for delivering services to other teams.

You probably should avoid working for a German company practising domain driven design in Java.

I've seen code that named classes and variables much worse than that.

Besides the report on mirror damage this telegram also appears to contain observations of "periodic comet Curmumov-Gerasimenko", which had been discovered a year earlier, and happens to be the one ESA's Rosetta mission visited in 2016.

That's because there's a floor to HDD prices regardless of size.

If you want maximum storage per unit of currency spent, you'll be looking at 16-20TB drives which go for 15-16€ per TB in my area.

By comparison, 4TB drives tend to go for 20€+ per TB.

But I agree that SSDs have moved much more rapidly and am looking forward to them finally surpassing HDDs on the price front too.

The fact that it's a purely functional programming language with lazy evaluation is really powerful but steepens the learning curve for devs who haven't worked with functional languages.

The stdlib is also pretty sparse, missing some commonly required functions.

The author didn't even remove ChatGPTs disclaimer in the last paragraph. Other articles on the site however seem human-written.

Organic Maps really nails the use case for a minimalistic, no-nonsense mapping app with great UX design. Whereas OsmAnd tries to accommodate all use cases with full configurability, which results in a mess of nested options menus, OM goes for reasonable defaults and short menu paths.

Unfortunately that minimalism comes with some downsides. While OM has a great metro map, it doesn't show bus lines (which would probably blot the map size quite a bit), making it unfortunately unusable for my use case.