Front-page articles summarized hourly.
Amiga Screens: A Primer describes screens as independent, hardware-driven display areas on the original Amiga (OCS, with ECS/AGA upgrades). Screens vary in resolution and color depth, using indexed palettes and planar bitplanes to pack colors; for example, OCS supports 320×256 (32 colors, 5 bpl) or 640×256 (16 colors, 4 bpl), with HAM or EHB modes offering more. The copper co-processor allows per-scanline palette changes and copper gradients. Multiple screens can run simultaneously and overlap; Dual Playfields blends two screens with transparency. This, plus fast screen switching and screen dragging, underpins Amiga multitasking and graphics prowess.
An experimental LangGraph-based workflow with a standalone C++ CUDA harness to automatically optimize CUDA kernels. It iteratively loads or generates a workload signature and reference kernel, proposes changes, compiles via NVRTC, runs tests, compares outputs (NumPy), and ranks candidates by latency across cases, keeping the fastest validated kernel and an execution history with a timing heatmap. Implemented with a Python orchestrator and a C++/CUDA runtime using CUDA Driver API; results are stored per-run. Requires Windows with RTX GPU, Python 3.12+, CUDA toolkit/driver, CMake, Visual Studio; OpenAI API key. Optional Nsight/NVIDIA-guidance flags.
This is a Financial Times security verification page reporting a 403 CG000 error (Request ID a4096a291f94173e). It instructs enabling JavaScript and cookies and visiting help.ft.com for assistance; it references Terms, Privacy, Cookie Policy, Manage Cookies, and FT’s copyright and Editorial Code of Practice.
Apple Silicon Macs can run local LLMs. RAM guidance: 1–3B on any Mac; 7–8B with 8GB; 14B with 16GB; 70B with 64GB+. Free tools: Ollama (CLI) and LM Studio (GUI). Local models offer low latency, privacy, and no ongoing cost, but aren’t frontier cloud models. Practical uses: local autocomplete, transcription, and file search inside apps; frontier cloud handles hard reasoning. Balance: cloud for the 5% frontier tasks, local models for the 95% of typing tasks. Example: TypeTab uses a 1B model fine-tuned on your prose on-device.
Ferri Benedetti argues that in AI-driven change, tech work needs humanists. Prioritize humanities—philosophy, literature, linguistics, math, history, anthropology—and language study to think deeply, form opinions, and explain them. Pure technical skills aren’t enough; professionals must learn fast, design for humans, question AI outputs, and map whole systems including human factors. Language and culture broaden problem-solving and prevent “meat proxy” roles. Become a flexible, well-read “humanist in tech” who can read proposals, detect bullshit, and articulate robust, defendable positions.
An interactive 2.5D painting 'The Last Day' by Opus 5.5, set in Hell Creek 66 million years ago. Across seven movements from evening valley to Chicxulub impact, the piece uses Neon Reed Pulse music and interactive camera controls (drag to look, pinch/scroll to zoom, timeline navigation) to immerse viewers. It's an artistic interpretation of the dinosaur extinction—birds survived; captions softened and timescales dramatized, not a scientific simulation. The project also promotes Get Amplified video lessons, the 1000x Lab, and private consulting, and requires JavaScript/WebGL2.
DAWO.community is an open initiative to build a digitally autonomous Dutch government workplace using replaceable, inspectable building blocks instead of a single product. It aims to enhance digital autonomy, collaboration, security, innovation, and verifiability, with AI, DAWO-NixOS, cloud infrastructure, and open collaboration tools. All events, news, blog, and forum content are public on the member portal, where participation includes conversations, code, pilots, and events. Supporters include Codeberg, code.overheid.nl, and LinkedIn; the project is built with the NL Design System.
Jared Norman critiques David Heinemeier Hansson's Rails World 2026 keynote, arguing his vision abandons traditional Rails in favor of AI-driven development. DHH proclaims retirement from professional programming, embraces LLMs for code, endorses Rust for backend, and rewrites Hey as six native apps, with CLI-driven interfaces. Norman notes Rails content was minimal and questions who will drive Rails’ future, pitting Hanami and Mosscap against Rails. He warns that the claim of '100x programmers' is dubious, and that the idea of code-free horizons risks unstable architectures. Overall, he doubts Rails has a clear path or leadership.
Mac Mini M6 achieves a stable 600MHz emulated Pentium II in 86Box 6.0 (Win98 SE with a Voodoo 3); 650MHz overclock causes audio underruns, so 600MHz is the ceiling. Compared with the M4’s 500MHz, the M6 offers a strong single‑core lead, with two fast host cores ~4.7GHz total and ~26% package use, delivering 100% emulation speed with no dropouts for Cinebench 2000/3DMark. CB2000: 9.28 at 600MHz vs 7.73 at 500MHz. This places retro emulation near Pentium III territory, for under €1,600.
jev-code-reviewer reframes PR reviews by classifying each change into P0/P1/P2 and presenting diffs in natural language, with P0 shown by default. It runs locally as a CLI + agent skill plus a Chrome extension and does not post data to GitHub. It’s designed to review the user's own coding-agent PRs. Setup requires Node.js 22+, and a local server at 127.0.0.1:4731; keys live at ~/.config/jev-reviewer/credentials.json. It analyzes the first 12 change units by default (configurable up to 100) and supports policy customization. MIT licensed.
Part 2 of SAFA Team's Avast CVE-2025-13032 exploit on Windows 11 describes abusing a double-fetch bug in Avast's kernel driver to trigger a paged-pool overflow. The researchers heap-spray I/O Ring RegBuffers, corrupt a RegBuffers entry to obtain an arbitrary kernel read/write primitive, then leak a kernel _EPROCESS address via an MDL attached to a user buffer. They steal the SYSTEM token to gain SYSTEM privileges, repair pool state to avoid a crash, and ensure teardown safety. Avast users should update; Part 1 covers discovery and sandbox escape.
Robert O'Callahan resigns from Google, citing AI progress as too rapid and potentially harmful; he believes AI demands urgent regulation and ethical restraint. He will continue maintaining Pernosco and rr, and plans to explore how AI agents debug code and to pursue hobby projects, ensuring his work remains pro-human. He identifies as a Christian and Auckland Chinese Presbyterian Church elder; living in New Zealand; despite leaving, he'll engage with AI safety discussions, and aims to influence outcomes from outside Google.
TypeSafe AI’s Jev is a System One model that returns structured answers in a single forward pass with attached probabilities. It operates non-autoregressively and uses RLCD to aim for epistemically honest probabilities, not free text. Jev targets classification-style tasks in production—fast, low-cost, and easily plumbed into existing pipelines—by avoiding generation. The author plans an experiment (PR acceptance at submission) to compare Jev with a Random Forest (calibrated and uncalibrated) and a frontier LLM, focusing on ROC-AUC, Brier, ECE, latency, and cost. He argues calibration, not accuracy, is the real bottleneck and offers practical team guidance.
The content shows a page trying to establish a secure connection but asking the user to enable JavaScript to continue, plus a request ID.
Describes adding a Parquet writer to Haskell Dataframe. Use writeParquet (defaults) or writeParquetWithOptions for fine control. Explains Parquet internals (row groups, column chunks, data pages, and definition/repetition levels) and how options like pageSize, rowGroupSize, batchRows, and compression influence layout. The writer uses memory buffers (MutableByteArray) and a core loop that processes the dataframe into a Parquet file with per-column buffers and metadata. Current limits: Snappy/Uncompressed, plain encoding, single-threaded; future work includes more codecs, multithreading, optional stats/bloom filters, and a two-pass memory strategy.
GitLab.com is experiencing 503 service disruptions. Investigations began around 23:02–23:04 UTC; by 23:27 UTC the cause had been identified and mitigation is underway. The incident involves Google Compute Engine components, with several items (website, API, Git operations, CI/CD, registries, runners) listed, most shown as operational. The status page offers updates and subscription options via email, webhook, Teams, RSS, Slack, and iCalendar.
Patch introduces a leased handoff for coding-agent questions to survive disconnects. Only one connected author device can own a question at a time; if a device goes offline, its claim expires after 45 seconds and the question becomes available again. Questions now queue with their session and wait for the author's coding agent rather than assuming online. A short lease token lets any connected device claim work atomically; original session provides context. Updates include making anchor movement conservative and surfacing the answering device in UI, with a Reconnecting state when leases lapse. Files changed: agentQuestions.ts, project-anchor.ts, agent-question-status.tsx.
Made by Johno Whitaker using FastHTML