How I fork the CI pipelines and the source codes
Shutting Down Clear Linux OS
31–40 of 121 posts
Re: Shutting Down Clear Linux OS
#32Knowing which projects/languages/frameworks to invest time into and which to skip (even if they produce useful subprojects) is a superpower these days.
Some are easy to see to avoid (ie Google, https://killedbygoogle.com), whereas others like this one are a bit more unexpected though make sense (to me) in hindsight.
Re: Shutting Down Clear Linux OS
#33What optimizations did they do that had the biggest effect? can they be brought into the mainline linux kernel and distros?
Mostly it's just compiling everything correctly and getting the most juice out of transparent hugepages.
Yeah, but there is something else here too... I used cachy for a heartbeat and it advertises the same benefits; it just felt slower (notably on boot) Maybe it was just all the graphical load screens.
There's something clear had that made it feel modern, familiar and boring (which might not be for everyone) 90% of my tasks were in vscode devcontainers so kept things simple and out of the system for the most part.
Re: Shutting Down Clear Linux OS
#34[dead]
Re: Shutting Down Clear Linux OS
#35Knowing which projects/languages/frameworks to invest time into and which to skip (even if they produce useful subprojects) is a superpower these days.
Debian, FreeBSD.. the longstanding community software is immune from these kinds of rug pulls.
Yes, but you pay a real cost for those choices too. A management plane that is non deterministic, imperative, and full of highly mutable state, not to mention basic stuff like the package manager metadata and cache not being shareable, and package installs all having to be serialized because they all call shell scripts as root. These limitations constrain even tools like dagger from providing a first class interface to apt like there is for apk because any deb could have rm -rf / as the postinstall script.
A lot of normal users don’t feel these pain points or tolerate them by sidestepping the whole affair with containers or VM images. But if you’re in a position where these things have an impact it can be extremely motivating to seek out others who are willing to experiment with different ways of doing things.
Re: Shutting Down Clear Linux OS
#36Earlier quoted context omitted.
Mostly it's just compiling everything correctly and getting the most juice out of transparent hugepages.
I could be wrong but I think they used icc (Intel's c compiler) for most/everything?
I don't think they build any part of it with icc, the world's worst compiler. They do not even offer icc as a package.
Re: Shutting Down Clear Linux OS
#37Earlier quoted context omitted.
Mass firings
Is this a guess, or have you heard something?
Intel Job Losses Mount as 4,000 layoffs are reported across multiple sites
https://www.pcgamer.com/hardware/processors/intel-job-losses...
Re: Shutting Down Clear Linux OS
#38Earlier quoted context omitted.
Mostly it's just compiling everything correctly and getting the most juice out of transparent hugepages.
Yeah, but there is something else here too... I used cachy for a heartbeat and it advertises the same benefits; it just felt slower (notably on boot) Maybe it was just all the graphical load screens. There's something clear had that made it feel modern, familiar and boring (which might not be for everyone) 90% of my tasks were in vscode devcontainers so kept things simple and out of the system for the most part.
Sounds like bloat removal and minimalism.
Re: Shutting Down Clear Linux OS
#39Always found clear linux very interesting and wanted to give it a try but totally expected this.
Re: Shutting Down Clear Linux OS
#40Knowing which projects/languages/frameworks to invest time into and which to skip (even if they produce useful subprojects) is a superpower these days.
Always bet against Intel whenever it's something software?
Intel will probably be somebody’s subsidiary for less than $150B sometime within the next 3 years, pending DOJ approval.
Company is absolutely cooked.