pib VS Svelte

I'd say don't give anyone bad ideas, but we are too late:

https://github.com/oraoto/pib

People are weird though - so it IS also technically possible now to compile php to wasm if you really want to write some frontend code in php e.g. https://github.com/oraoto/pib - I'm not sure if that's a joke, intellectual exercise just for fun, or mad php people are really doing that for reals, I'd never use it in reality of course.

Here's an issue i opened a few weeks ago in their repository asking for help but unfortunately nobody replied yet: https://github.com/oraoto/pib/issues/65

Well, it depends on the extensions you're using. Since vscode.dev only runs locally in your browser, all extensions are limited to declarative things like snippets, themes etc. or else they have to use JavaScript or WebAssembly to run. Many extensions (I assume the ones for PHP as well) require platform-native executables, and as such can't currently run the browser. Interestingly, I found this from a quick internet search, but I don't know if any VSCode extension is making use of it yet.

Maybe something like this, then? https://github.com/oraoto/pib

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.