exidex

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

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

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

People are biased by definition

Larger types are supported, there is A notion of tearing. According to JVM spec even long and double could tear, not sure about practical implications though

I have converged on a workflow that is just what I was doing before, but use LLMs just for boring or tedios parts. General guidelines are: only single agent at a time, small targeted queries, understand what you are building, if something would seem like a fun task, do it yourself. I use LLMs for bug hunting, to trace the flow, to build quick visualizatios (paste csv, ask to generate visualization), to search in the code of the dependencies using github mcp, to write 100 line scripts (deno + ts + zx was a game changer for me). Even "dumber" opensource models are good for this kind workflow, more tokens per second is generally more benefitial than plain intelligence. I would use LLMs more or less, sometimes even full vibecoding if the task is something like quick tooling web app and the flow is just firing of the next LLM query every 30 seconds. But, depending on the type of task or domain that you work in, YMMV

Not sure why people praise Minecraft for this. This is huge feat of Wayland, and was possible because devs took time to consider use cases outside of current norm, and why it took so long to migrate the ecosystem. People liked to bitch about the "Gnome blocking/not implementing essential protocols" part, but even that partially made this possible

"The bottom line" is the new "Its not just X, its Y"

My choice is to not do a PhD and just invest as much or as little effort in the topic as you like

That is only because there is no viable platform to build similar gui-based tooling on

This is the idea I had in mind since initial wasm release but wasm wasn't ready then but now it is. Glad to see somebody is working on this. If executed properly this could be the last windows manager that people will ever need

I was more thinking in terms of creating a benchmark which would optimized during training. For regular projects, I agree, you have to count that anyway

Now you have to count defects

Add that to a long list of side projects I would like to do "at some point"

Pantograph[0] seems to be a more recent attempt to implement the same idea. It is still not a general editor but generalizing it to ranges of tree selections looks promising

[0]: https://pantographeditor.github.io/Pantograph/

And I am sure that people have been complaining about the hand gymnastics you have to do to press those shortcuts since around that time as well

There are certainly different possibilities of where the line would be drawn. I am not that familiar with vim internals, but I don't consider file management to be part of vim editing model. And we are only talking about editing model (e.g. b being beginning of a word), not the whole editor (plugin system, ui, lsp and treesitter integration, etc). Though it is true that some parts are more tightly related to "vim". There some cases were Neovim already wants to disconnect itself from vim legacy like allowing to scroll viewport without moving the cursor

By "recreating everything" I was also referring to the ecosystem around the editor

I didn't really spent time thinking about it, because from reading their issue tracker, I very much doubt neovim would consider something like that. Partially because of how much of it is already vim specific and it would be very difficult to abstract that away, but mostly because of ideology.

You can already to a lot in Neovim with plugins, including recreating Helix, Ki, whatever. But the problem is that the vim state machine is always present underneath it, resulting in unwanted behaviors or impossibility to implement some things. I would envision it to pretty much allow to listen on raw keyboard and mouse events. However cursed it sounds, it should be possible to fully implement vscode or any other editing model in neovim

It's a shame that editors are build around the editing model, so much time has been wasted by recreating everything. Neovim is a perfect editor in many aspects but editing model is not one of them, in my opinion. Helix or even Ki would not be needed if Neovim allowed to completely replace the vim part of it with plugins

To some extend that is true for any opinionated piece of software. But that is a beauty of opensource don't use it if it doesn't match your idea of how that software should look like

Having been in the community for some time, it is just how the authors are, very enthusiastic about the wording. They like to come up with some wild terms explaining different behaviors and reasoning behind those behaviors, like "positional coherence" or "behavioral asymmetry", and the term "kimmunity" to reference to ki editor community. On a surface level, sure, it looks LLM generated, but I would be very surprised if they used LLM to generate that sentence. I choose to look at the actual meaning of the content and what they are trying to do differently

Have you tried Ki Editor[0]? It seems to be more into direction that you are looking for. It is not as mature as the rest of the editors but the editing model is definitely an improvement from ux perspective

[0]: https://ki-editor.org/

What a grim future, just chat with a bot without ever seeing the code

There is https://github.com/SixArm/usv which is exactly that, but with special unicode characters

> I couldn't find the SWR hooks though.

What do you have in mind?

> Also, the interface isn't pretty atm.

Agreed, creating pretty UIs is not my strongest suit if I am completely honest, and could use a help with that. But I have been polishing it up steadily, though sometimes it is an uphill battle with iced-rs.

> The Video could probably show more practical examples than Game of Life

Also agreed. Game of Life demo was supposed to show the interactivity of a view and was easy to implement but at some point I would like to add something more usable as a builtin plugin. For the code example I think it would be better to have that in documentation which is the next on my TODO list

All in all, good points

They said it is waiting for some feature from project Valhalla. Not sure which one though