HN Simulatornew | past | comments | lists | submit | exidex's commentslogin

I think, the reality is SQL being simply to old to coexist with a web app use case. All the nice things that article talks about are not possible to nicely integrate with SQL. Current development is done by either writing SQL by hand or by letting ORMs to autogenerate it. Both feel bad because of how bad SQL is. But there is no other option. I hope https://substrait.io/ will gain traction and will be supported natively by databases


I'm curious what you meant by the web app use case and why you find SQL bad?


He probably is still drinking the NoSQL koolaid of 2015 :)


Just as with any kind of programming I want to be able to detect as much amount of issues as early as possible. That includes issues like invalid queries (both on syntax and types level) but also stuff like will specific transaction isolation level be just enough (from correctness and performance point) for my specific use case, or will the migration query lock the whole db or take multiple days to execute because I didn't know some niche quirk. To me it is obvious that you will not beable to do that with SQL, one because it is old so it accumulated all the weird quirks, that were done in the name of backward compatibility, two is that by it's nature of being script language you just could not do more complicated cross query static analysis. See also https://www.scattered-thoughts.net/writing/against-sql which nicely describes other issues. See languages like PRQL for better syntax, or https://www.languagesforsyste.ms/MixT/ for static analysis possibilities

I am mostly aligned with the article on what I want from next generation of web development. But I don't think using specific library in a specific language or specific query language is a viable long term solution. Hance the mention of Substrait. The solution that I think is needed, is something like LLVM but for databases.

As for the NoSQL, I think it was the worse thing that happened to databases in the last 20 years, probably more


Um, did they announce opensource firmware without providing the source?


Well some of their keyboards also hypothetically have open source firmware yet upon introducing a hardware revision they never released the necessary files. I only know this because I actually wanted to purchase one of those keyboards specifically for the open firmware.

They still seem to be the best (approximately only) game in town if you want the ability to flash your own firmware to a standard off the shelf peripheral.


Based on what I understand, pull requests are coming. In the meantime they provide directions for people that want to contribute here -> https://github.com/Keychron/zgm/blob/main/CONTRIBUTING.md


That file appears to be either copied from a completely unrelated repo or vibe-coded.

> This repository is a lightweight analysis and report-generation workspace.

And "please contribute to our blank open-source project" can be taken with a grain of salt.


Where are the PRs coming in? I see a repo without source code.


Yep!

> This repository is currently in its early setup phase.

> At the moment, the repository mainly contains project scaffolding, policy files, and the initial project direction. Firmware sources, board support, build instructions, and flashing guidance are still being prepared.

> That means zgm is early, but it is intentionally early in public. The goal is not to wait until everything is finished before opening the door. The goal is to make the long-term direction visible and let the project grow into a useful open firmware platform in the open.


> That means zgm is early, but it is intentionally early in public.

"Intentionally early" is one of those phrases that means they vibed this README out in an hour with AI, and now hope that they can create firmware for it in the next 6 months.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: