NextJS VS Remix created some drama, an exciting article about Web Components, some internet artefacts, Radix Vue, Yarn and more.
This post caused drama in Dev News. Those are fascinating points from Kent. However, Lee responded quickly.
https://www.epicweb.dev/why-i-wont-use-nextjs
And a response from Lee Robinson.
https://leerob.io/blog/using-nextjs
Nevermind above, and take a look at changes for the latest Next.JS
https://nextjs.org/blog/next-14
https://remix.run/blog/remix-heart-vite
https://astro.build/blog/astro-340/
Does anyone use Web Components?
https://jakelazaroff.com/words/web-components-will-outlive-your-javascript-framework/
Component library for Vue.
https://yarnpkg.com/blog/release/4.0
Here is a fun page about the first spam email, first smiley, first mp3 and so on: https://neal.fun/internet-artifacts/
There is no way to animate an element that has been removed. Current solutions are hacky as you have to keep time in CSS animation and the same in JS with setTimeout. Not nice. The new proposal would make it simpler.
https://chriscoyier.net/2023/10/30/exit-animations/
https://jwdallas.com/posts/namingcssvariables/
https://www.kirupa.com/web/changing_colors_svg_css_javascript.htm
It’s getting complicated…
https://danielcwilson.com/posts/mathematicss-rem-mod/
“…close look at how different performance tools audit and report on performance metrics, such as core web vitals. Different tools rely on different types of data that are capable of producing different results when measuring different performance metrics.”
https://www.smashingmagazine.com/2023/10/answering-questions-interpreting-page-speed-reports/
Because, Why not?
https://www.asepbagja.com/programming/making-music-with-google-sheets/
“To conclude, the core problem isn't that browsers are bad — it's more that browsers are not browser enough.”