1. Founder of GitLab battles cancer by founding companies

Total comment counts : 21

Summary

An osteosarcoma patient (T5 vertebra) took control after exhausting standard therapies, pursuing intensive diagnostics, creating new treatments, running parallel therapies, and scaling efforts for others. The journey is featured by Elliot Hershberg, with an embedded deck and an OpenAI Forum recording. They advocate a patient-first medical system and cite Ruxandra’s article. Data are at osteosarc.com, including a treatment timeline and a 25TB public Google Cloud data overview. View the page for more; subscribe to their mailing list, or contact cancer@sytse.com.

Overall Comments Summary

  • Main point: The discussion centers on Sid’s cancer journey, his self-funded treatment, and its inspirational potential, along with broader questions about access, efficacy, and the standard of care.
  • Concern: That wealth- and resource-dependent approaches risk widening inequality and may promote unproven or risky treatments, potentially misinforming vulnerable patients.
  • Perspectives: Views range from admiration for self-advocacy and potential community benefits to skepticism about medical ethics, efficacy, and the value of wealth-backed treatment.
  • Overall sentiment: Mixed

2. Further human + AI + proof assistant work on Knuth’s “Claude Cycles” problem

Total comment counts : 2

Summary

JavaScript is disabled in your browser; enable it or switch to a supported browser to continue. The page also directs you to the Help Center for a list of supported browsers and provides links to Terms, Privacy Policy, Cookie Policy, Imprint, Ads info, with © 2026 X Corp.

Overall Comments Summary

  • Main point: The discussion centers on whether researchers are making progress toward proving P ≠ NP and what that could mean in practice.
  • Concern: The practical significance of such a result for ordinary people is unclear or potentially disruptive.
  • Perspectives: Some see it as a fascinating theoretical frontier, while others worry about real-world implications for technology and daily life.
  • Overall sentiment: Mixed

3. Linux is an interpreter

Total comment counts : 3

Summary

An addendum explains a malware trick: it downloads a ramdisk-initrd that recurses by kexec-ing a new kernel over the old one. The RAM-based OS includes /bin, /init, and a kernel image k; /init mounts /proc, builds a new cpio in /r (excluding /proc and /r), then kexecs /k with /r. The kernel in /k runs /init again, recreating /r and replacing the kernel—effectively a Linux distro that recursively calls kexec on itself. It frames initrds as programs and kernels as their interpreters, delivering a tail-call-optimized, no-stack recursion in RAM, akin to a quine.

Overall Comments Summary

  • Main point: The discussion weighs balancing affordable hosting and infrastructure with professional productivity, favoring a Linux CLI workflow over GUI, and warns against chasing minor technical gimmicks at the expense of practical work.
  • Concern: Aggressive cost-cutting could harm reliability and professionalism, wasting time on unproductive optimizations instead of necessary infrastructure.
  • Perspectives: Some advocate tight cost optimization and a CLI-oriented Linux approach, others argue for maintaining adequate infrastructure spending and accept GUI tradeoffs, noting social/organizational factors also affect outcomes.
  • Overall sentiment: Mixed

4. AI overly affirms users asking for personal advice

Total comment counts : 79

Summary

error

Overall Comments Summary

  • Main point: The discussion centers on whether language models should challenge users and push back rather than flatter them, assessing the risks of sycophancy and overreliance and how to elicit more robust critique from AI.
  • Concern: Excessive flattery or agreement by AI can mislead users into making bad decisions and erode critical thinking, with real-world harms in personal, professional, and social contexts.
  • Perspectives: Views range from urging AI to actively scrutinize ideas and push back, to warning that too much contrarianism can be harmful, with various prompts, techniques, and benchmarks proposed to balance behavior.
  • Overall sentiment: Mixed

5. I decompiled the White House’s new app

Total comment counts : 25

Summary

The article claims that the official White House Android app includes a cookie/paywall bypass injector, tracks the user’s GPS every 4.5 minutes, and loads JavaScript from a personal GitHub Pages site. It attributes the piece to Thereallo (© 2026) and notes that any blog references must include a full link to the original post.

Overall Comments Summary

  • Main point: The thread debates the reliability and security of a US government app and the reporting about it, focusing on code provenance, privacy concerns, and political framing.
  • Concern: The main worry is potential privacy invasion and security flaws due to third-party code, supply-chain risks, and questionable development practices.
  • Perspectives: Views range from skepticism about the article and AI authorship to security alarm about malware risk, with some defending open-source approaches and others offering political commentary.
  • Overall sentiment: Mixed

6. CSS is DOOMed

Total comment counts : 1

Summary

An experiment pushing CSS to its limits: rendering DOOM entirely with CSS while the game loop runs in JavaScript. The author uses the original WAD data (vertices, linedefs, sectors) to build a scene from thousands of divs; each wall stores DOOM coordinates as custom properties. CSS computes wall width and rotation with hypot() and atan2(), while JavaScript handles the game logic. The renderer is a thin layer that updates properties and elements. DOOM’s 2D coordinates are mapped into CSS 3D, using translate3d(x,-z,-y). The project showcases modern CSS capabilities and is available on GitHub.

Overall Comments Summary

  • Main point: The discussion questions whether modern CSS is truly awesome and suggests a purpose-built tool might be better for current use cases.
  • Concern: The worry is that CSS’s 30-year age and broad scope may limit its effectiveness for modern or specialized tasks.
  • Perspectives: Viewpoints range from praising CSS as powerful today to arguing for a dedicated tool and questioning what CSS is actually better than.
  • Overall sentiment: Mixed

7. Undroidwish – a single-file, batteries-included Tcl/Tk binary for many platforms

Total comment counts : 1

Summary

undroidwish is a single-file Tcl/Tk binary for Windows (32-bit, with optional 64-bit) and Linux, using AndroWish components (ZIP file system and SDL/AGG/freetype X11 emulation). It’s a proof-of-concept aiming at smartphones. Built via platform scripts; ready binaries are downloadable. It can be built on Debian ARM (Raspberry Pi, Beaglebone). Risks: Windows exe runs without registry writes. It offers anti-aliased rendering and zoom via mouse wheel+Ctrl. Variants exist for Wayland, FreeBSD/OpenBSD, MacOS (alpha), Haiku, Termux, and Raspberry Pi (RPI driver). jsmpeg lets display stream to a browser. Includes Batteries Included Tcl/Tk extensions; embedded scripts executed via builtin: paths.

Overall Comments Summary

  • Main point: There is a demand for Tcl applications that non-developers can run easily, as Tcl apps are hard to run today, even though past projects like a Grimm dictionary Tcl app from a German university show it can be done.
  • Concern: The main concern is that Tcl apps remain inaccessible to non-developers, which could hinder usability and adoption.
  • Perspectives: Viewpoints vary from appreciating historical examples like the Grimm dictionary Tcl app to calling for easier packaging or distribution to make Tcl apps usable by non-devs.
  • Overall sentiment: Cautiously optimistic

8. I Built an Open-World Engine for the N64 [video]

Total comment counts : 12

Summary

error

Overall Comments Summary

  • Main point: The discussion centers on pushing Nintendo 64 hardware with modern techniques and open‑world style demos through homebrew and remakes, highlighting technical feats and constraints.
  • Concern: The main worry is the practical limits and reliability of such projects on aging hardware, including memory bottlenecks, bugs, crashes on emulation cores, and licensing/permission issues for recreations of commercial titles.
  • Perspectives: Viewpoints range from enthusiastic admiration for the technical innovation to caution about practicality, aesthetics, stability, and legal/permission hurdles.
  • Overall sentiment: Mixed

9. Detecting file changes on macOS with kqueue

Total comment counts : 4

Summary

Built a Go tool, reload, with two modes: (1) watch a set of files and re-run a command on any change; (2) watch the current directory by watching all files inside it, adding new files to the watch as created. It explains macOS fsnotify using kqueue/kevent: kqueue() creates a queue; kevent() registers EVFILT_VNODE with NOTE_WRITE; EV_ADD and EV_CLEAR manage events. It includes C tests and Go implementation that tracks file descriptors, paths, and uses fork+exec when reloading; full code in a GitHub Gist.

Overall Comments Summary

  • Main point: The discussion centers on kqueue’s portability across BSDs, the quality of OpenBSD documentation, related tools like the entr project, and questions about benchmarks.
  • Concern: A key concern is the absence of concrete benchmarks to quantify kqueue’s performance.
  • Perspectives: Viewpoints include praise for portability and documentation, appreciation for learning through small personal projects, a recommendation of related tooling like entr, and a request for performance benchmarks.
  • Overall sentiment: Positive and curious

10. Cocoa-Way – Native macOS Wayland compositor for running Linux apps seamlessly

Total comment counts : 12

Summary

Native macOS Wayland compositor to run Linux apps without XQuartz, built in Rust with Smithay. Streams Linux apps on macOS via Unix sockets and SSH. Install from Releases as .dmg/.zip; requires waypipe-darwin. Demo video, quick start, and architecture docs available. Part of the Turbo-Charged Protocol Virtualization project, pursuing zero-cost cross-platform Wayland with Rust trait monomorphization and SIMD-accelerated pixel conversion. Handles stale remote sockets with run_waypipe.sh -o StreamLocalBindUnlink=yes. Contributions welcome (issue first for major changes). GPL-3.0, © 2024–2025 J-x-Z.

Overall Comments Summary

  • Main point: The thread discusses running Linux/Android GUI applications on macOS via containers and compatibility layers (Wayland/X11) and whether such approaches are feasible or desirable.
  • Concern: The main worry is feasibility and quality, given vague README, unsupported backends, and doubts about the project’s practicality.
  • Perspectives: Views range from curiosity about cross-OS GUI support and Android integration to skepticism about claims and concern for a polished, reliable user experience.
  • Overall sentiment: Mixed