frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Anthropic hits $2T in Nasdaq debut

https://www.reuters.com/business/finance/anthropics-historic-debut-put-ais-promise-peril-wall-st-...
732•wslh•5h ago•1330 comments

Pancreatic cancer halted by virus injection in three patients

https://www.newscientist.com/article/2528235-pancreatic-cancer-halted-by-virus-injection-in-three...
350•cybermango•5h ago•46 comments

Claude solves two open problems in the physics of black holes

https://www.anthropic.com/research/claude-black-hole-physics
311•cybermango•5h ago•137 comments

Synology Security Advisory

https://www.synology.com/en-uk/security/advisory/Synology_SA_26_21
18•choult•19m ago•3 comments

The 98% Slot Machine: How Paid Advertising Became an Extraction Tax

https://globalcommercegraph.com/writing/the-ninety-eight-percent-slot-machine
131•dev1one1•3h ago•68 comments

Garage Door Spam

https://blog.harrison.page/garage-door-spam/
691•harrisonpage•3d ago•284 comments

Should governments slow frontier AI? Jacob Coxon and Robin Hanson debate [video]

https://www.youtube.com/watch?v=lwfewYL7X0o
50•sandslash•3h ago•82 comments

Show HN: Cornhole News – A Hacker News inspired site for news across the Midwest

https://cornholenews.news
160•cornholemedia•6h ago•83 comments

Someone reported java4shell bug in September 2026

https://github.com/openjdk/jdk/pull/32781
318•notmine1337•10h ago•85 comments

UK government forced to admit it issued Apple a secret encryption order

https://macanorak.com/uk-government-forced-to-admit-it-issued-apple-a-secret-encryption-order/
414•Terretta•6h ago•181 comments

Rebuilding my local voice assistant pipeline

https://blog.platypush.tech/article/Rewriting-my-voice-assistant-pipeline
19•todsacerdoti•1h ago•1 comments

Reverse-Engineering Kevin J. Lang's Lost OCaml Code in Apache DataSketches

https://www.tisonkun.io/posts/ai-repair-program/
19•tison•3d ago•0 comments

Launch HN: Onlook (YC W25) – An open-source developer tool for designers

https://github.com/onlook-dev/onlook/
72•D_R_Farrell•5h ago•64 comments

Pete warden on local AI, open models, voice interfaces, the future of hardware

https://thedataexchange.media/pete-warden-moonshine/
194•datascientist•6h ago•171 comments

Making 8-page foldable zines from a single A4 sheet in the browser

https://krthr.co/paper-folds-and-whats-new-in-fanzines-app/
212•krthr•9h ago•48 comments

Nintendo takes Picofly firmware down from GitHub [video]

https://www.youtube.com/watch?v=-TLCGUpoD6c
236•cowlevel•1d ago•89 comments

Ruby2ßhell: Pre-authentication RCE on stock Rails

https://verialabs.com/ruby2shell/
363•jdns•17h ago•154 comments

How the European Commission rolled out Matrix to more than 40k staff

https://element.io/blog/how-the-european-commission-rolled-out-matrix-to-more-than-40-000-staff/
626•liotier•11h ago•302 comments

How to CAD Almost Anything

https://ocw.mit.edu/courses/res-16-002-how-to-cad-almost-anything-january-iap-2024/
7•o4c•2d ago•1 comments

An Oregon library ditched Dewey Decimal and got people excited about books again

https://www.fastcompany.com/91597520/oregon-library-ditched-dewey-decimal-wayfinding-system
171•bookofjoe•2d ago•121 comments

What's New in PHP 8.6

https://www.php.net/releases/8.6/en.php
260•netol•13h ago•125 comments

Adding Fortran Support to LLDB (GSoC 2026)

https://blog.llvm.org/posts/2026-09-07-gsoc-add-fortran-support-to-lldb/
22•JDevlieghere•3d ago•5 comments

Do not buy RAM, compress

https://curiousbits.nl/blog/do-not-buy-ram-compress/
216•Ecno92•13h ago•184 comments

Unblockable communication with gravity

https://www.science.org/doi/10.1126/sciadv.aee0802
128•rbanffy•10h ago•41 comments

How to Make the Ink Used to Write Hamlet and the Declaration of Independence

https://lithub.com/how-to-make-the-ink-used-to-write-hamlet-the-declaration-of-independence-and-b...
60•ohjeez•7h ago•28 comments

Distributed, high-performance blob storage on SQLite

https://zerodha.tech/blog/high-performance-distributed-blob-storage/
241•ghostfoxgod•13h ago•66 comments

Everything you need to survive and rebuild society

https://lastbook.org/
326•tejohnso•7h ago•175 comments

Cooling buildings is overtaking heating them as an energy need, IEA says

https://maccus.fr/en/cooling-overtaking-heating/
142•robtherobber•7h ago•94 comments

Fuck Your AI Safeguards

https://ounapuu.ee/posts/2026/11/19/unsafeguards/
419•speckx•6h ago•169 comments

AI Came for the Coders. Understanding Why Tells Us Who's Next

https://www.robertpeake.com/archives/104254-ai-came-for-the-coders-understanding-why-tells-us-who...
20•speckx•4h ago•15 comments
Open in hackernews

Anatomy of a SQL Engine

https://www.dolthub.com/blog/2025-04-25-sql-engine-anatomy/
168•ingve•1y ago

Comments

jimbokun•1y ago
Very nice write up enumerating all the stages of SQL query execution. Interesting even if you don’t care about the DoIt database specifically.
Austizzle•1y ago
Man, this title tripped me up for a minute because I pronounce it with the letters like Ess-Queue-Ell

So the "A" in "A ess-queue-ell" engine felt like it should have been an "An" until I realized it was meant to be pronounced like "sequel"

perching_aix•1y ago
Not necessarily, I see native speakers completely ignore this a lot.

Have you ever considered pronouncing it as squirrel by the way?

kreetx•1y ago
Many (most?) non-native English speakers do pronounce it as ess-queue-ell, especially in their own languages, so yes, the use of "a" instead of "an" does look off from that perspective.
SloopJon•1y ago
When I read SQL for Dummies almost thirty years ago, it made a point of distinguishing "sequel" as a historical predecessor to standard "SQL." As I recall, the author even asserted that SQL is not an acronym/initialism for structured query language. I felt funny saying sequel for the next decade or so, because I wasn't an old timer experienced with this pre-SQL technology.

Now I usually say sequel because everyone else does. That and it rolls off the tongue better than S-Q-L.

jtolmar•1y ago
I prefer "ess queue ell" these days, but the first DBA I ever worked with pronounced it "squirrel".
gopalv•1y ago
This is a great write up about a pull-style volcano SQL engine.

The IR I've used is the Calcite implementation, this looks very concept adjacent enough that it makes sense on the first read.

> tmp2/test-branch> explain plan select count() from xy join uv on x = u;

One of the helpful things we did was to build a graphviz dot export for the explains plans, which saved us days and years of work when trying to explain an optimization problem between the physical and logical layers.

My version would end up displayed as SVG like this

https://web.archive.org/web/20190724161156/http://people.apa...

But the calcite logical plans also have that dot export modes.

https://issues.apache.org/jira/browse/CALCITE-4197

th0ma5•1y ago
This is really great!!
gavinray•1y ago
Calcite also has a relatively-unknown web tool for plan visualization that lets you step through execution.

It's a method from "RuleMatchVisualizer":

https://github.com/apache/calcite/blob/36f6dddd894b8b79edeb5...

Here's a screenshot of what the webpage looks like, for anyone curious:

https://github.com/GavinRay97/GraphQLCalcite/blob/92b18a850d...

ignoreusernames•1y ago
I recommend anyone who works with databases to write a simple engine. It's a lot simpler than you may think and it's a great exercise. If using python, sqlglot (https://github.com/tobymao/sqlglot) let's you skip all the parsing and it even does some simple optimizations. From the parsed query tree it's pretty straightforward to build a logical plan and execute that. You can even use python's builtin ast module to convert sql expressions into python ones (so no need for a custom interpreter!)
Abde-Notte•1y ago
Second this - building even a simple engine gives real insight into query planning and execution. Once parsing is handled, the core ideas are a lot more approachable than they seem.
albert_e•1y ago
Sorry for slight digression.

In a larger system we are building we need a text-to-sql capability for some structured data retrieval.

Is there a way one could utilize this library (sqlglot) to build a multi-dialect sql generator -- that is not currently solved by directly relying on a LLM that is better at code generation in general?

LtdJorge•1y ago
This is a SQL to X library, though. I don’t think it’s what you need.
gavinray•1y ago
You can use an LLM to generate query-builder expressions from popular libraries in whatever language.

For example, on the JVM there is jOOQ, which allows you to write something like:

  select(field("foo"), avg("bar")).from(table("todos"))
And then it will render dialect-specific SQL. It has very advanced emulation functionality for things like JSON aggregations and working around quirks of dialects.

Alternatively, you can ask an LLM to generate a specific dialect of SQL, and then use jOOQ to parse it to an AST, and then render it as a different dialect, like:

    val parser= DSL.using(SQLDialect.POSTGRES).parser()
    val parsedQuery = parser.parseQuery(postgresQuery)
    val renderedMySQL = DSL.using(SQLDialect.MYSQL).renderInlined(parsedQuery)
    println(renderedMySQL)
Unsure if functionality like this exists in other Query Builder libraries for other languages.
KyleBrandt•1y ago
Using dolthub's go-mysql-server for Grafana's upcoming SQL expressions feature (private preview in Grafana 12, but in the OSS version with a feature toggle).

GMS lets you provide your own table and database implementations, so we use GMS to perform SQL queries against Grafana's dataframes - so users can join or manipulate different data source queires, but we don't have to insert the data into SQL to do this thanks to GMS.

genai-analyst•1y ago
another digression here... sorry... i see you're trying to diy text-to-sql—at some point you're gonna hit a bunch of hiccups. like, the model writes a query that “almost” works but joins the wrong tables, or it assumes column names that don’t exist, or it returns the wrong agg because it misread the intent. and retries won’t always save you—it’ll just confidently hallucinate again.

we’ve been through all of that at wobby.ai we ended up building a system where the data team defines guardrails and reusable query templates, so the agent doesn’t just make stuff up. it can still handle user prompts, but within a safe structure. if you want to save yourself from debugging this stuff endlessly, might be worth checking out wobby.ai.