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.
> most Kubernetes deployment don't even run containerd anymore
I assume you mean moby, which was used via dockershim in Kubernetes until support was removed in v1.24.
I can't find a reliable source, but I believe containerd, followed by CRI-O and alternatives, are the common choices of container runtime for Kubernetes.
It was called plain docker originally, the Moby rebrand came much later and not everyone is even aware that it happened, because plain docker was already much less relevant when they did it (vs k8s, which was already becoming the default by then).
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.
I also didn't realize it could be used for all syscalls, but storage access and networking seem to be the biggest use case for it.
Depending on the exact setup, storage IOPS can be increased by up to 100% versus the older asynchronous IO kernel API [1], only beaten by pure user-space implementations that aren't as feature-complete.
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.
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 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.
does it really though? what part do they struggle with?
> The stdlib is also pretty sparse, missing some commonly required functions.
This seems to be the general curse of template languages. For some reason, their authors have this near-religious belief in removing every "unneeded" feature, which in practice results in having to write 10 incomprehensible lines of code to do something that could be easily done in one line of readable code in a proper PL.
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.
OSM Public Transport schemes support for buses and trams is not implemented yet, and it's not an easy task. Any volunteers to lead the development are welcome!
I use both Organic Maps and OsmAnd, I see both your descriptions as features:
- Organic Maps is minimalistic, easy, great for what it does.
- OsmAnd does everything. Whenever I want to do something more advanced that is not in Organic Maps (typically I like the GPX stuff for hiking, or the ski maps, etc), I turn to OsmAnd.
Same here. Although I also keep both around from the perspective of an OpenStreetMap contributor and mapper. OrganicMaps is a bit spartan at times, but it has its place.
OsmAnd, while a bit harder to use (but not that much), is much better than Organic Maps: it can show satellite imagery from both Google and Microsoft (and download it for offline use!), has a 3D map view, supports coloring slopes, has a bunch of specialized functionality for hiking, cycling, skiing, maritime navigation, can record trails, can route according to vehicle dimensions and in general can do everything (except for things that require access to Google's data like routing based on live traffic data and showing data like opening hours that businesses put in Google Maps).
OSMand definitely has more features, but whether that makes it better depends on the use case. I like it in principle and try it every once in a while but could never really warm up to it, and every time I just end up going back to Organic Maps.
I love OSMand but I can't figure out why it announces speed bumps when I'm in walking and biking mode but not when in car mode :) But it's still the best navigation app I've used.
I agree, including other guided transit (trams, urban gondolas...) on the metro layer would greatly improve public transit routing.
But bus routes are a harder problem to integrate, especially in larger cities. In Paris, there are more than 200 bus routes (more than 1000 including the greater suburbs), map readability would take a probably big hit if they were displayed on the map, or at least it would require a lot of care to do it right. A some larger cities also have a night service for busses, with routes differing from the day busses, handling those properly is also an issue.
That's actually one of the few areas where I really like the way OsmAnd approached the UI. When you tap a bus stop, it shows you which bus lines stop there, and only after you tap one of the lines do you actually see the route for that particular line, and it has buttons to focus the next and previous stops.
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.