Other than that, for web functionality, they're identical! ;-)
Then of course there's the ability to supplement authentication on the backend, detect file uploads for background processing, etc. All of which are outside the scope of FastCGI.
But you don't care for Lambda. That's fine. You do you.
https://gist.github.com/Rich-Harris/0f910048478c2a6505d1c321...
https://svelte.dev/docs/svelte-components#script-3-$-marks-a...
https://svelte.dev/docs/svelte-components#script-4-prefix-st...
"It takes all the lessons from the last decade and a half and distills them into familiar web development patterns."
That includes reactivity and state management—two concepts that weren't adequately covered by the old web.Things only get worse when you add vanilla javascript to the mix.
Or… you could use the tags most appropriate to the problem with accessibility and SEO automatically coming along for the ride.
PicoCSS is an excellent example of what can be accomplished with just a sprinkling (~10KB) of CSS over plain old HTML.
Browsers can do so much more than they used to out of the box today. We should take advantage of that rather than silo it away in one-off React-based APIs.
You may disagree that html and css are that bad. But I think it was always a mess, specially when you go beyond linked documents and add any kind of interactivity and forms. There's also inherent limitations like "select" dropdowns offering very little functionality and mostly ending up as custom components in all projects I have worked in.
This is not at all the case. I highly recommend actually looking at Svelte examples before commenting further.
That said, there are a lot of folks out there who don't know that, for example, combo boxes and accordions are possible with plain HTML.
<datalist>
<details>
<summary>
PicoCSS is a great resource for seeing what's possible with just plain HTML and ~10KB of CSS.Folks aren't against solving problems. I think the main concern is the amnesia regarding problems that had already be solved and are now be solved again only not as well.
It's a feature, not a bug. That said, I personally prefer the Svelte model. I like leveraging the client browser for effect, not just rendering everything server-side.
please build spotify using only HTML and JS language features from 1996.
Svelte's the real deal. How do I know? Because it's not a new API or paradigm. It's the old web just better.
It encourages HTML and sane CSS, not just wraps them in endless boilerplate. It compiles to efficient code rather than making you write all of it over and over again. It takes all the lessons from the last decade and a half and distills them into familiar web development patterns.
I haven't been this excited about a new web technology in a decade, so coming from an old school web dev who learned off of view source in 1996, take that into consideration.And while I prefer Svelte, Htmx is doing a lot of the same work; not new APIs; just embracing old ones without all the boilerplate.