Debian is to be used for some legacy systems because RHEL introduced microarchitecture restrictions. Rest of their infra is on AlmaLinux (a RHEL-compatible distro ala Rocky).
Article quite a mess and, honestly, largely devoid of content. For starters, complains that SL should've continued because other community options might eventually be discontinued/change (as happened with CentOS). Like, duh. By this reasoning every effort should be duplicated to guard against the possibility that one option might disappear. In the end though all those RHEL rebuilds depend on Red Hat maintaining RHEL. The article never notes this and indirectly equalizes the effort and existence of a a genuinely independent community-driven distro (Debian, that CERN decided to move their accelerator-control computers) and RHEL rebuild (e.g., AlmaLinux, that CERN will keep the rest of infrastructure on, e.g. data centers, compute farms, etc). And here's the misguided part. If SL as still active it'll have been necessary to recompile numerous upstream RHEL source packages to remove the microarchitecture restrictions. This will've turned SL to entire new, independently maintained distro. The thing they wanted to avoid.
Well, it's not an unreasonable assumption that RHEL will continue to be maintained even if we don't go down the whole CentOS path which I won't on a public forum. But, yes, there are always dependencies. There's certainly no guarantees that any of the ~rebuilds will still be around in n years.
lo and behold, a 1000 word sample comes back in Pangram as AI generated. This should not be worth anyone's time (and maybe you have spent more time on your comment than the author did in their blogpost).
You've misunderstood something deeply. PS5 Linux doesn't exist because running Linux on PS5 is something useful or practical. Exists due to the curiosity and fun of running a free OS on a locked-down device. Maybe some nostalgia mixed in as Linux has existed in every other PS (even PSP/PS Vita).
Ok, that's indeed much different from what title implies, essentially attempting to contribute with AI code/reviews. Sony pays $$$$ for security exploits. If indeed a "slop kiddy", i.e. a noob fooling around with an LLM, found it, and if they aren't interested in homebrew scene like theflow, makes no sense not to report it and wait, as it's a bug that's now trivial to find, and can expect many others to.
SectorLISP makes an important question in its implementation: how much can strip down Lisp before stops being Lisp. Same is not done for submitted interpreter. So, although SectorLISP goal is to be a Lisp-reduced-to-its-essentials implementation, the Python-1024 goal seems to be imitating Python in most minimal code possible.
Other notable agents' LOC: Codex (Rust) ~519K, Gemini (TS) ~445K, OpenCode (TS) ~254K, Pi (TS) ~113K LOC. Pi's modular structure makes it simple to see where most of code is. Respectively core, unified API, coding agent CLI, TUI have ~3K, ~35K, ~60K, ~15K LOC. Interestingly, the just uploaded claw-code's Rust version is currently at only 28K.
edit: Claude is actually (TS) 395K. So Gemini is more bloat. Codex is arguable since is written in lower-level language.
It's related to commits actually having a parent-child structure (forming a graph) and timestamps (commit/author) being metadata. So commits 1->2->3->4 could be modified to have timestamps 1->3->2->4. I know GitHub prefers sorting with author over commit date, but don't know how topology is handled.
> It's related to commits actually having a parent-child structure (forming a graph) and timestamps (commit/author) being metadata.
Yeah, I think everyone is aware. It's just that the last couple dozen commits, to me, looked like commits had been created in chronological order, so that topological order == chronological order.
> I know GitHub prefers sorting with author over commit date, but don't know how topology is handled.
reply