Deno solves this, it's not a JavaScript Issue, it's a Node.JS / NPM issue.

How does Deno solve this? Genuine question by the way. I'm not trying to be snarky.

It provides a runtime, that sandboxes your application and requires you to give explicit permissions for file system operations and network requests.

This limits the attack surface, when it comes to installing malicious dependencies, that npm happily installs for you.

So yes, I was wrong and my previous comment a hyperbole. A big problem is npm, and not JavaScript.

My point about the staggering amount of dependencies still holds though.

Of course, this only works so long as the sandbox is secure.

There have been attempts to do this kind of sandboxing before. Java and .NET both used to have it. Both dropped it because it turns out that properly sandboxing stuff is hard.

We moved a 8y/old React app to preact in a few lines of code, barely anything was needed.

I think the signals integrations are great added value to the "classic React" formula.

Light weight bundles too, can't recommend it enough.

You can find screenshots here: https://dev.to/9zemian5/tired-of-writing-sql-just-to-explore... (might be outdated, didn't test the tool)

On my part, I would like to see sqlite support and screenshots on the mainpage, also not a big fan of running an unknown command on my data.

Since you run locally, any value of having the frontend loaded from a website instead of just opening it in localhost ?

Hi, yes, the dev.to post is a bit outdated.

> I would like to see sqlite support Indeed, it is something I'm planing to add, but following all the feedback I got so far this will have to wait (landing page needs some work, plus a lot of people are having concerns regarding CLI tool not being open sourced)

> any value of having the frontend loaded from a website instead of just opening it in localhost ? I want the CLI package to be as small as possible, and including 600kb React bundle in it is the exact oposite of small. Moreover, the idea in the future is for you to be able to connect to any host (be it cloud, localhost or selfhosted) from the same page (for example I have company self hosted server and a local server for my local databases).

My strategy for this kind of situation is to avoid direct rejection. Instead of saying stuff like "it's unnescessary" or "you are wrong", I push for trying first without.

I would say:

> Once we have a working MVP without websockets we can talk again to think about using websocket.

Most times, once something is working, they then stop to care, or we have other priorities then.

100% agree, I felt very put off by the tone, I think HTMX pull it off by not taking itself too seriously and also having good insights.

I wish the homepage talked more about how nue approach the problems rather than how better than other framework it is.

Nice one, thank you for sharing !

What I love most is how well "out of the box" sublime work for me. Even on a fresh install it's very usable without doing anything, I usually install about 3 extensions (not counting specific language syntax support).

Integrated LSP would be nice to have, but most of the time I don't use it and I like to be able to turn it of and have the simple autocomplete that is very predictable and unintrusive.

And performance, I know Zed showed some benchmarks on how fast it is, I still had some hang up from time to time with it and some crash, I can't suffer jankiness in my editor, it stress me out.

Thanks for the work done on Sublime.

I think the best thing about Sublime's LSP plugin is that you have everything off by default and then only turn it on on a per-project basis. I actually have an example of that in the article. Do a search on the article for "eslint" and you'll find the section where I show ESLint being disabled and Biome being enabled

I thought it was a wordle variant, but was gladly surprised it feels more like playing sudoku. Everything is based on deduction and you don't need to have a good english vocabulary !

Yeah, I really love this keyboard, if only it was still alive, didn't find a successor

This use allow to update SELECT operations, but UPDATE / DELETE still have to be done on the old underlying schema right ?

No way to trigger a DELETE from a view right ? How would you approach this ?

Views can be updatable though there are caveats, but deletes and updats can be done via a function or stored procedure, meaning there's no direct access by the app to the underlying schema. If it's done well it means that the calling code in the app won't have to change (or at least be minimised) even as the schema changes. The speed and security benefits are a nice by-product.

You can even do things like prevent the app from deleting things unless the functions are used and prevent poor development practices in the process.