Not to mention the creation of a single point of failure for a critical service...

Right, but in this case the critical service isn't providing "health" for users, it's extracting profit from them (from the transactions) for the shareholders. THAT'S the critical service this company cybernetically fulfills.

I liked M. Waldrop's book: The Dream Machine

https://press.stripe.com/the-dream-machine

Would it be possible to install duckdb extensions in python using packages instead of dialing back home to the extension service? Lots of companies block direct connections to that service but allow packages via JFrog's Artifactory.

Interestingly this is better in terms of precision but as an interface for math is still behind good old paper and pencil.

The interface is still 30+ years old...

With Draw.io embedding Mermaid diagrams and plug-ins available for VSCode and other IDEs, why is this so special?

Hi! I'm Akshatha from the Product team at Mermaid Chart :)

While Draw.io's integration with Mermaid and the availability of plug-ins for VSCode and other IDEs are great, they primarily support programmatic editing of diagrams. What sets Mermaid Chart apart is its bi-directional editing capability. You can edit the code to update the diagram and make changes directly to the diagram, which will automatically reflect in the code.

Currently, this two-way editing functionality is available for class diagrams and flowcharts, but we're excited to expand it to other popular diagram types in the future. Stay tuned!

Competition is good for innovation and choice is good for everyone. Does it need to be special?

And they still have soldered RAM and no option to add an SSD... who is this for?

There is so much our software needs to improve to reach the level of sophistication of even plants :-)

https://inquisitivebiologist.com/2018/11/12/book-review-the-...

https://en.wikipedia.org/wiki/Stigmergy

Oh the irony: https://futurism.com/the-byte/ceos-easily-replaced-with-ai

How does it compare with N.Wirth's?

https://onlinebooks.library.upenn.edu/webbin/book/lookupid?k...

Wirth's book does not implement a "real" programming language. Whatever your thoughts on Oberon and Pascal-like SHOUTCASE languages, it's largely irrelevant. Oberon is arguably a "real" language (and operating system), but Wirth's book does not cover the implementation of Oberon. It covers the implementation of Oberon0, an inarguably toy subset of Oberon. (Actually, "subset" is not even correct.) The example code has also diverged from the book, with Wirth abandoning the strategy described in the book for avoiding redundant initialization of the module static base, among other things.

Aside from that, I encourage everyone who cites Compiler Construction to actually work through the first 10% of the book and then count the number of errata.

The book is a very hands on tutorial whereas Wirths is basic literature for the general case.

While they teach similar content, they have a different approach.

There are literally thousands of compiler design books out there, I don't really see anything particularly comparable between this book and Wirth's

Similar to studying OS concepts using Silberschatz' Operating System Concept and Tanenbaum's Operating Systems Design and Implementation. The former only explains the theoritical ideas, while the latter is the documentation of an implementation.

This story is missing the impact that Tom Lord's TLA had on the git design.

Previously: <https://news.ycombinator.com/item?id=32155067#32157109>