frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Outages reported at Bank of America, Chase, U.S. Bank, Wells Fargo and Zelle

https://apnews.com/article/bank-outage-chase-wells-fargo-truist-50fee2693c22f597fa6ca51a97ef2cda
477•samk3nny•2h ago•362 comments

Grazing sheep in fields with solar arrays

https://news.cornell.edu/stories/2026/10/sheep-grazing-solar-fields-offers-farmers-economic-ecolo...
144•PaulHoule•3h ago•110 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
224•burntsushi•4h ago•49 comments

Launch HN: Axonnic (YC F26) – Sleeves that track fingers and estimate force

13•arshpatankar•33m ago•3 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
174•geerlingguy•4h ago•100 comments

Squircles

https://linebender.org/wiki/curves/squircle/
37•raphlinus•13h ago•12 comments

Nations Must Die

https://marvindanig.com/blog/nations-must-die/
7•marvindanig•24m ago•0 comments

Aristotle Expands into Rust

https://www.harmonic.fun/news/aristotle-rust-verification/
66•maufl•3h ago•37 comments

The Secret ThinkPad Powerbutton Code to Bring Dead Laptops Back to Life (2007)

https://masnick.com/posts/the-secret-thinkpad-powerbutton-code-to-bring-dead-laptops-back-to-life/
270•sammatilda•9h ago•107 comments

OpenAI: Strengthening the fight against online child sexual abuse

https://openai.com/index/strengthening-online-child-safety/
57•rossant•2h ago•90 comments

How to Intercept HTTP/3 Traffic: QUIC and Qpack

https://interceptsuite.com/blog/intercept-http3-traffic-quic-qpack-explained/
19•anof-cyber•1h ago•0 comments

Michael Mann's 'Heat' Copyright Fight Turns on a Deal with Himself

https://copyrightlately.com/michael-mann-heat-copyright-termination/
51•speckx•3h ago•16 comments

Giant Roadside Attractions Face Mounting Costs and an Uncertain Future

https://www.nytimes.com/2026/11/08/world/canada/roadside-attractions-giant-dinosaur.html
23•bookofjoe•6d ago•17 comments

Software is breaking down at a systemic level

https://www.breck-mckye.com/blog/2026/11/software-is-breaking-down-at-a-systemic-level/
252•zero_shift•2h ago•143 comments

Rust changed me as a developer

https://blog.startifact.com/posts/how-rust-changed-me/
8•speckx•46m ago•0 comments

Many of Amazon’s Black Friday and Cyber Monday “deals” offered no savings

http://groundworkcollaborative.org/news/amazons-decoy-deals-groundwork-investigation-reveals-near...
711•DeepLogin•7h ago•444 comments

How to make almost anything

https://pub.cba.mit.edu/863.26/site/
796•o4c•15h ago•132 comments

The origins of the placenta

https://www.caltech.edu/about/news/uncovering-the-hidden-origins-of-the-placenta
12•gmays•3d ago•2 comments

Jolt – Clojure that speaks C

https://jolt-lang.net/
58•michaelsbradley•4h ago•16 comments

Microsoft blames monster email outage on software defect introduced in July fix

https://www.theregister.com/saas/2026/11/16/microsoft-blames-monster-email-outage-on-software-def...
102•Bender•7h ago•70 comments

Nvidia was in trouble before the Jensen Huang mess

https://www.wired.com/story/nvidia-was-already-in-trouble-before-the-jensen-huang-mess/
192•Brajeshwar•5h ago•194 comments

OOS – an open operating system for the Rigol Scopes

https://www.eevblog.com/forum/testgear/oos-an-open-operating-system-for-the-rigol-scopes/
118•qwezxcrty•2d ago•35 comments

Smallest possible nopert polyhedra: the Septopert

https://github.com/tom7/noperts/blob/main/septopert.md
43•RebelPotato•2d ago•4 comments

Comcast's "fiber-powered Wi-Fi" is cable, AT&T says in false advertising case

https://arstechnica.com/tech-policy/2026/11/comcast-falsely-advertises-cable-internet-as-fiber-po...
7•jaredwiener•15m ago•0 comments

First phase of embedded assessments at OpenAI

https://openai.com/index/our-first-phase-of-embedded-assessments/
24•dvaplima•4h ago•8 comments

Coffeehouses and the Rise of Science [pdf]

https://www.monirbounadi.com/Bounadi_JMP.pdf
165•Michelangelo11•9h ago•98 comments

Interpreting claims that a theorem is correct because it was checked in Lean

https://xenaproject.wordpress.com/2026/11/12/and-the-proof-is-checked-in-lean/
267•matt_d•13h ago•116 comments

A 512 KiB binary message teaching chess without a shared language

https://artemlegotin.com/golden-board/
40•legotin•6h ago•12 comments

Researchers track whole body movement with just a smartwatch

https://news.cornell.edu/stories/2026/11/researchers-track-whole-body-movement-just-smartwatch
189•PaulHoule•3d ago•65 comments

Caltech professor no longer grades homework's because everyone uses AI

https://www.businessinsider.com/ai-math-class-university-homework-caltech-careers-2026-11
9•ishanz•15m ago•1 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.