'Lean or purple drank is a polysubstance drink used as a recreational drug. It is prepared by mixing prescription-grade cough or cold syrup containing an opioid drug '

proving that one of the hardest problem in CS - 'naming things' still keeps on keeping on.

[1]https://www.tomshardware.com/tech-industry/semiconductors/ym...

So Open source it may be , however there are still pressure points that can be used. I believe this is one of the main reasons RISCV foundation moved to Europe.

They will probably market the ARM inclusion similarly - as something that the package provides.

As far as POWER i think only Raptor[1] does direct marketingof the power(hehe) and capabilities

[1]https://www.raptorcs.com/

The architecture might be non-standard and not very widespread however for what it does and workloads that are suited to it. I dont think any ARM design comes close , maybe Fujitsu's A64FX.

[1]https://github.com/chipsalliance/chisel

Still early innings but i bet this plays out the same way - not everyone will have the time sink to vibecode all the software workflows they require.Maintainance iwse and security wise holes will still remain for the personaly non tech user. Devs and orgs will probably limit the usage to a helper sidecar rather than the hyped 100% LLM generated apps. Reminds me about the hype

With wayland they seem not to be even entertaing this optionality - with wayland itself being not yet feature complete to standalone.And the attempts to bridge like xwayland coming way after the fact and pushing a oneway path with no coexisting situation.

As a result introducinga whole lot of friction and surprises in UI functionality. So yeah at a time when the presentation layer should be a boring afterthough, it is too timeconsuming in part of a Linux setup and daily usage.

They want to sell a technically brillant protocol that is single vendor propriety/patent restricted.

Their bet should have been of open protocol and captalizing on fist mover advantage to drive their business side witha large partner like ericsson/cisco etc.

Of course theres also the soveriegnity angle knowing what went on with another swiss company CryptoAG.

Too much friction and limiting the potential - thats why i reiterate. The SailFishOS is a delight technically and aesthetically - the business side though needs a major overhaul.

Just thinking out loud , they could partner with someone likee huawei to preload for EU/rest of world customers that cannot use HarmonyOS outside CH. Or even one of the other smaller OEM with access to the deep tech ecosystem to give a prebuild/preloaded f;agship at a cost competitive price. Or do a Apple and auction search/maps defaults to keep BOM costs down and aim for widespread adoption.

The market is there , product is loved and ppeople have proved they are willing to take some pain adopting the product.But still the execution to serve that market is shambolic to say the least.

Were Haiku mor mature/stable would have been a nice fit for the OS for the LLM/Ai personal use cases.

[1] https://arstechnica.com/information-technology/2018/07/the-b...

As i recall there were some similar situations in regards to licences for distro builders regarding graphicsdrivers and even mp3 decoders wherer there was a song and dance the end user had to go through to legally install them during/after setup.

Or better yet to make a truly api compatible re-implementation to use with the license that they want to use, since what they have done i surmise would fall under a derivative work.So they havent really accomplised what they wanted - and instead introduced an unacceptable amount of risk to whoever uses the library going forward.

Kinda reminds me of what the Inderner Archive did during the pandemic with the digital lending library.Pushing the boundaries to test them and establish precedence. in any case let see how it plays out.

Bikeshedding to eventually come full circle to understand why those decisions were made.

In a world where the large OEMs and bigcorps are increasinly locking down firmware , bootloaders , kernels and the internet. I would think a reappraisal of more enforcement that benefits the USER is paramount.

Instead we have devs looking to tear down the few user protections FLOSS provides and usher in a locked down hacker unfiendly future.

[1] https://licensecheck.io/blog/lgpl-dynamic-linking

Also a few years bcak theer was the csae of SAP(?) i tthink where they did a reimplementation indipendently via the design documents.

Those two were upheld on litigation and bear out to this day.

This case however is neither a clean room implementation nor relicensable.

A good example if the author had wanted to be correct would have been the sudo rewrite , which ubuntu is doing with their sudo-rs in rust.Not bug for bug compatible as they have already deviated from some usablility choices but more valid than this.