Sussman Explains the End of SICP

Re:Sussman Explains the End of SICP by fouronnes3 on Saturday February 04, 2023 @05:05PM (#34658887)

I've heard a joke some time ago that I can't stop thinking about: every program is either a compiler or a database. I still haven't found any counterexample.

[ Parent | on HN ]

Re:Sussman Explains the End of SICP by thefaux on Saturday February 04, 2023 @05:23PM (#34659044)

> every program is either a compiler or a database

or both!

[ Parent | on HN ]

Re:Sussman Explains the End of SICP by amelius on Saturday February 04, 2023 @05:42PM (#34659218)

Or it's just a CRUD website.

[ Parent | on HN ]

Re:Sussman Explains the End of SICP by consilient on Sunday February 05, 2023 @06:22AM (#34663961)

That's a user input to SQL compiler

[ Parent | on HN ]

Re:Sussman Explains the End of SICP by karmakaze on Saturday February 04, 2023 @05:21PM (#34659036)

A load balancer? Operating system kernel?

[ Parent | on HN ]

Re:Sussman Explains the End of SICP by sfink on Saturday February 04, 2023 @07:32PM (#34660155)

A load balancer is a compiler. Instruction scheduling and register allocation are probably the most similar tasks.

An OS kernel is a database, or rather a DBMS. Query planning fits well.

Arguably, a load balancer is a primitive query planner. Perhaps DBMSes are compilers?

[ Parent | on HN ]

Re:Sussman Explains the End of SICP by karmakaze on Saturday February 04, 2023 @09:41PM (#34661153)

It seems that these arguments can also be applied in reverse, so it's quite a loose interpretation, but I do see the logic in them.

[ Parent | on HN ]