Building a robust frontend using progressive enhancement
1–10 of 168 posts
Re: Building a robust frontend using progressive enhancement
#2This is very good advice.
Re: Building a robust frontend using progressive enhancement
#3> If you use a JavaScript framework you should:
>
> be able to justify with evidence, how using JavaScript would benefit users
Steady on, guys.
Re: Building a robust frontend using progressive enhancement
#4I wish the whole internet followed this advice.
Re: Building a robust frontend using progressive enhancement
#5Good advice, but
> - users of assistive technology would be unaware of changes in context, for example when moving to a new page
> - it would fail to handle focus when moving between pages
> - the user would be unable to navigate using the back or forward buttons in their browser
> - users would be unable to recover from an error, for example if there is an interruption to their network connection
These aren’t strictly true, are they? You can achieve these things in an SPA, even if many (most?) don’t bother
Re: Building a robust frontend using progressive enhancement
#6When even governments knows the web better than the tech industry by and large itself.
I despise React, ended up with Svelte+Typescript and now I realise that could do it all mostly with HTMX + templating with bit of alpine.js if at all.
Re: Building a robust frontend using progressive enhancement
#7This advise may have been correct for old-school SPAs, but most if not all points should be fixed in the current generation. E.g. first page load is static or SSR, and then the page is hydrated as a accessible SPA including url manipulation. Also automatic a no-js fallbacks are provided with many.
Re: Building a robust frontend using progressive enhancement
#8User first programming rather than work inflating bloated frameworks mainly used to justify further dev work. Which one do engineers choose
Re: Building a robust frontend using progressive enhancement
#9OMG it feels so good to not be the lone voice in the woods. I would say about 3/4 of my frustrations as a user are from sites that should have simply been built with HTML + CSS and minimal Javascript. The front end community most days feels like a jobs program.
Re: Building a robust frontend using progressive enhancement
#10When even governments knows the web better than the tech industry by and large itself. I despise React, ended up with Svelte+Typescript and now I realise that could do it all mostly with HTMX + templating with bit of alpine.js if at all.
Despise React's unnecessary complexity and non-standard-compliant non-separation-of-concerns squeeze-it-all-in-js approach as well.
Svelte(kit) is still the most W3C compliant of the major frameworks out there. Also, it's not even a runtime-framework but a compiler, meaning you're left with nothing but the necessary HTML, JS & CSS just relevant for your page.