“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.
Once again I get foiled by switching languages. :blobcatfacepalm2:
In Javascript, you have to compare strings with ===, not ==, or else you'll run into type coercion problems, because Javascript thinks 1 == "1" is a totally fine thing to be true. (it's not)
But in Kotlin, === compares identity not equality for strings. But in the JVM, string values are aggressively cached, so === actually does what you want most of the time. Unless your strings come from weird places, like JNI code. Then you get awful non-deterministic behavior that's incredibly hard to debug, but it totally goes away when you use the correct comparison operator == for strings.
sigh I'm not really as good at this whole programming thing as I should be by now.
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.
> [HTMX] can get you 80% there with radically less complexity. No extra dependencies, no build step, no advanced tooling (now re-written in Rust!), no complicated state management, no “double data” problem, no hydration mismatch… Just write your HTTP server and return HTML!
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.
I scrapped 2 months worth of work on a headless front end application for Siren, and went server-side with PHP. In doing so, I literally built the entire interface in 3 days.
Accepting almost* everything in #webdev eventually falls but agreeing w/ @chriscoyier here.
"Technologies do tend to come and go.... But when tech gets big enough, it tends to not go. #WordPress is huge, and it’s been huge every second of my entire web dev career. To me it echos social media in a way. In the middle days of Facebook, it’s demise was often predicted.... But it didn’t, and it’s demise is no longer predicted. It’s too big to fail. So too is #React."
Google provides a tool called PageSpeed Insights which gives a website some metrics to assess how well it is put together and how fast it loads. There are a lot of technical details but in general green scores are good, orange not great and red is bad.
I tried to ensure the tests were similar for each platform by choosing a page that shows a list of posts, like https://mastodon.social/explore.
The rest don’t seem to have prioritized performance or chose a software architecture that cannot be made to perform well on these metrics. It will be very interesting to see how that affects the cost of running large instances and the longevity of the platforms. Time will tell.