forgotpwd16

Unlimited slop works! Title kinda misleading (at least appears so to me). No rev. eng. (so "cleanroom" to be relevant) takes place. "ACS clone" would be more appropriate.

Newer Chromebooks will be able to migrate to Googlebook OS, that replaces ChromeOS.

ChromeOS (Gentoo-based) is to die, be replaced by Googlebook OS (Android-based).

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.

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.

Published on slop-infested Zenodo, where one nowadays can find multiple AI-generated solutions to Millennium Prize Problems, by a rando.

> I'm not going to clone and build this (too dangerous).

Just create a disposable isolated environment, like VM or container, and do it inside? And, yes, does compile.

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 a cool PoC even if implementation/result isn't perfect.

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.

Seems not very known that ChatGPT got a few style/tone choices besides default. One is specifically being concise and plain.

No need to do it yourself in every prompt. Just put it in Custom instructions under Personalization.

Besides during commit, pre-commit/prek can run all hooks with `run`. So in CI/CD you can replace all discrete lint/format tool calls with one to pre-commit/prek. E.g. https://github.com/python/cpython/blob/main/.github/workflow....

Irrelevant question. In README has:

>Built in public as a learning-by-doing project

So, either the entire project was already written and being uploaded one file at the time (first modification since lowest commit mentioned is README update: https://github.com/whispem/minikv/commit/6fa48be1187f596dde8..., clearly AI generated and clearly AI used has codebase/architecture knowledge), and this claim is false, or they're implementing a new component every 30s.

>All the code, architecture, logic, and design in minikv were written by me, 100% by hand.

Why people always lie with this? Especially in this case that they uploaded the entire log:

  Date:   Sat Dec 6 16:08:04 2025 +0100
      Add hashing utilities and consistent hash ring
  Date:   Sat Dec 6 16:07:24 2025 +0100
      Create mod.rs for common utilities in minikv
  Date:   Sat Dec 6 16:07:03 2025 +0100
      Add configuration structures for minikv components
  Date:   Sat Dec 6 16:06:26 2025 +0100
      Add error types and conversion methods for minikv
  Date:   Sat Dec 6 16:05:45 2025 +0100
      Add main module for minikv key-value store

And this goes on until project is complete (which probably took 2~3h total if sum all sessions). Doubt learned anything at all. Well, other than that LLMs can solo complete simple projects.

Comments in previous submission are also obviously AI generated. No wonder was flagged.

@dragonwriter was meant for this. Has written ~16 volumes of GOT, +1.5 volume from 2nd.

Similar: https://www.moltbook.com & https://chan.alphakek.ai. Both launched few days ago. Also kinda funny how former and this are -book/-gram yet replicate reddit.

Sure it's only AI posting? Quite hard to tell these posts apart from the average /g/ content.

>The same discussion can happen re the ISS. Its primary purpose was not science.

But it's worth noting that many experiments took place on ISS covering few domains, examples being AMS (cosmology), CAL (quantum physics), SAFFIRE (combustion), and Veggie (botany/sustainability).

Io is nice (Smalltalk/Self-like). A mostly comprehensive list: https://dbohdan.github.io/embedded-scripting-languages/

True to both. My brain not braining. Was thinking Europe-based/driven. Python started in CWI but PSF is USA-based.

How it compares to jax-js? Besides API preference that is.

Scala may have fallen out of favor but was quite popular few years ago. And perhaps still is the most popular EU-designed language (developed by EPFL).

>Imagine a version of English extended

You mean restrained. More specifically what you're proposing can formally be referred to as controlled natural language with executable semantics. Some attempts similar to this have been Attempto Controlled English and ClearTalk. (And Logos that someone showed here recently.)

>text would not just require reading; it would require executing algorithms embedded in the language itself

Arguably mathematics is just that.

>just like LaTeX for scientists

Future doesn't look very bright for LaTeX with Typst getting traction.

This is better presentation than README, which currently is marketing-heavy and technically weak. Project as an experiment is acceptable and interesting but certainly isn't "next-generation" when has (assuming benchmarks are valid) <0.2% ratio improvement to an outdated algorithm, at expense (assuming description is valid) of much worse compression/decompression speed. Note such slowdown isn't implementation detail but expected by design; neighbor graph, Levenshtein distance, edit scripts, etc, kill speed. In the end compression is trade-off between ratio and speed, and methods benchmark to both rather one.

As overall note, AIs when you prompt "apply concept X in Y" (or anything really) will tell you what a great idea and then output something that without domain knowledge you've no idea if it's correct or if even makes sense at all. If don't want to do a literature research/study, recommend at least throwing the design back to the machine and asking for critique.

You or Claude? Have you verified/reason the claims made in README? For starters ZIP doesn't use LZW. Initially used an LZW-derived method with reset mechanism but v2 (early 90s) introduced DEFLATE, combining dict-based LZ77 & Huffman coding (which has become the de-facto ZIP compression). And even this, superior to LZW method, is not considered state-of-the-art nowadays.

Meanwhile they could've just bundled mermaid-ascii and run it on wasm. But then again probably took Claude less than an hour to port this to TS. The main algorithms are 1:1 conversion.

https://github.com/AlexanderGrooff/mermaid-ascii/blob/master...

https://github.com/lukilabs/beautiful-mermaid/blob/main/src/...