jgrpf

DbGate might fit your needs: https://dbgate.org/

It even has a demo: https://demo.dbgate.org/

With framework maintainers providing paid support, extending services or an ecosystem with commercial components it somewhat makes sense even if not outright obvious or intentional.

I've had a couple of cases case where a bug was not fixed in time or fixed at all which results in writing workarounds or forking which is far from an ideal solution and further reduces the advantages of using a framework.

React might have stabilized in the meantime but a couple of years ago the upgrade pain definitely was there.

I switched some years ago and never looked back. What I really like about Vue is that I can use it with a build system or just add it with a script tag for a bit of progressive enhancement over a form. I think it is simpler and decreased my bug count. I'm mainly a backend developer though.

Some JS seems to hijack the native scroll behaviour. The same on Manjaro Linux Firefox 89.0.1.

But it does break a lot of times and still contains a lot of inconsistencies.

But that's a problem: it maintains backwards compatability with a LOT of well known problems/inconsistencies while introducing more features/inconsistencies for which you can just hope they don't mess up this time. It's a bit of good and a lot of bad from both worlds. I'm just so glad I don't have to use PHP anymore and no amount of a swine's make up will change this.

This analogy doesn't work. You can still use a lot of these legacy mistakes today.

A lot of people are scammed though by Shamans and the like. And often times they do not leave that much happier but emotionally dependant and sometimes even broke. I've seen it plenty of times and think it's absolutely immoral.

A couple of programs substitue that with ctrl+[hjkl].

We use it on all our projects though it really needs improved/additional m:n handling.

I like wuzz. An ncurses interfaces for HTTP requests that allows me to save my configuration. It's super lightweight and all I need.

https://github.com/asciimoo/wuzz

This is totally possible. You can create a sub component, register and use it in the same file as the parent component. Though not really recommended you can even do this:

  ...
  components: {
    "inline": {
      template: `
        <h1>My inline subcomponent</h1>
      `
    }
  }
  ...

Though rather focused on todos, I use Taskwarrior with taskd deployed to a VPS. On mobile I use it inside Termux. For code snippets I wrote an interactive CLI that supports shell hooks which pushes changes into a Git repository automatically. Quite a nice combination for my shell-centric workflow.

But writing React without JSX is really not that great in my opinion whereas writing Vue without any preprocessor is totally fine. I know there's the option to use a JSX browser compiler but it's not recommended for production.

Apart from anecdotal experience telling me that fresh JS devs have a much easier time with Vue than React, I love to still have the option to use it through a simple embed without a build system but can switch to a Webpack/any module bundler if the requirements demand it.

The JS ecosystem really has a problem with bloat in my opinion and Vue trumps React in the regard (react eject anyone?).