In 45 minutes I made a #kotlin#javalin application from scratch, which uses #webjars to include #htmx from a #maven pom file. It uses static #HTML files for the first load, and then renders HTML from #jte templates for #SSR of the parts of the pages that need that kind of interaction. There's no #springboot (or any #spring at all) and no #SPA like #angular or #react.
Now because simply setting up a project says close to nothing about its real world viability, next step is an actual usecase ( :
We are excited about React Compiler, aren't we? I just remembered that my first OSS library in JavaScript was a JS-to-JS compiler! Funny how things come around.
“React and the component model standardises the software developer and reduces their individual bargaining power excluding them from a proportional share in the gains”. An amazing write-up by @baldur about the de-skilling of developers to reduce their ability to fight back against their employers.
This article uses #React as it's main example, but it applies to #Laravel, #Tailwind, even #Drupal just a much. I say that as a recovering Drupal dev who used to use the standardization argument.
Greedy management is the reason we can't have nice things.
My friend is looking into contributing to open source but doesn't know where to start. They have experience in Python, C# (Unity), Swift, and React. Does anyone have some pointers or projects they could look into to get started?
Hearing about all the changes in #React19 is giving me anxiety. I've been working on #React apps at my past four or five jobs now, but I just have no interest in relearning #ReactJS for the upteenth time, and I'm worried that is going to impact my ability to get another job if I ever decide to go back to work.