@ma1 They actually DON’T degrade gracefully when you factor in a11y! The native datepickers built into browsers aren’t accessible. Comboboxes need HTML attributes adjusted on what’s actively open and highlighted. Filtering must be done in JS. You actually NEED JS to pass WCAG 2 with these controls. It only degrades to a semi-working state for non-disabled users.

@molly0xfff same energy

@mook I mentioned progressive enhancement just as a nod to the argument that you can ship a JS-free version and a JS-enhanced version of a website (at least in its original form). I don’t see having JS-required sites as a bad thing anymore, since many things need JS to work (like comboboxes! and calendars! and context menus). If you’re mindful of budget and get creative, it’s possible to do one JS version better than two half-finished versions (not always of course, but often)

@berkes Eh I meant both. Modern TS is pretty good. It ships, it can be performant enough for the widest range of general programming, and the tooling is fast and mature now. To each their own, to point 8.