Ryan DeBeasi @ryan@mastodon.xyz

HTML, CSS and our vanishing industry entry points, If we make it so that you have to understand programming to even start, then we take something open and enabling, and place it back in the hands of those who are already privileged. 💯 true. https://rachelandrew.co.uk/archives/2019/01/30/html-css-and-our-vanishing-industry-entry-points/

That said, it doesn't have to be all-or-nothing. At one point the speaker drew a parallel to vegetarianism, and I actually think it's a great comparison.

You can have an impact on your health, the planet, and the suffering of animals without becoming a full vegan. There's a spectrum between flexitarian -> pescetarian -> vegetarian -> vegan where you're at least having a positive impact the further you move to the right. Maybe FLOSS can be thought of the same way.

"Rendering on the Web" by Jason Miller and Addy Osmani https://developers.google.com/web/updates/2019/02/rendering-on-the-web

This is a good read on the state-of-the-art in Server Side Rendering vs Client Side Rendering vs everything in between. Interesting to see that they are explicitly discouraging SSR Hydration. It was a promising technology, but it looks like in the real world it doesn't actually give many performance gains, and leads to an "uncanny valley" where sites look interactive but aren't.

Hooo YES "Google Play Store now open for Progressive Web Apps 😱" https://medium.com/@firt/google-play-store-now-open-for-progressive-web-apps-ec6f3c6ff3cc

since there are so many weird ux titles anyway can I just be a 'ux bassist' and then include all equipment purchases in tax?

🎶 I'm bringing blogging back!🎶

"Migrating from macOS to Ubuntu"

https://tiffanybbrown.com/2019/01/migrating-from-macos-to-ubuntu/index.html

"CSS doesn’t suck" Andy Bell is remind us how amazing and flexible CSS is. Let's start celebrating. https://andy-bell.design/wrote/css-doesnt-suck/

Crayola had a line of tech-themed crayons in 1997 called "Techno-Brite"

Moving CSS into JS adds a barrier preventing people not already deep in JS land from styling stuff. Doing CSS the classical way means you lose the advantages of JS infrastructure (dependency management, avoiding a global namespace). For authors of generic components, both suck.

I'm hitting a bit of a wall here https://github.com/codemirror/codemirror.next/issues/40#issuecomment-450885805

The Elements of UI Engineering - a great list of "problems" you need to solve on a UI level, with the advice to try to solve them without the constraints of the library / framework first https://overreacted.io/the-elements-of-ui-engineering/

I've heard some folks on the Chrome team say they were looking for proposals for new Layered APIs (basically JS libraries bundled in the browser) so I just wrote up a suggestion for an emoji picker: https://github.com/drufball/layered-apis/issues/39

If this were accepted, it would mean that every chat/social media app wouldn't need to bundle their own emoji picker, but could instead just rely on the browser to give them an <emoji-picker> element. It would also be available as an open-source JavaScript library.