@dopey_kun Ah, I've just been forced to use usePathname and useParams to do that trick like how Anilist does /anime/[id]/[title]/ to auto rewrite the title.
I mean, it's quite a trick to figure out that I needed to do the page as a layout under [id]/layout and do the redirecting in /[title]/page :ablobcatreachflip: but it definitely improves performance.
@anianimalsmoe I had to go to Anilist to check the behavior. I didn't realize that you could actually just put whatever in that title part of the url, and it'd still work.
“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.
@Crell Yes! “Tech management will sacrifice technological progress – performance, design, and general product effectiveness – if it disempowers labour.”
@assertchris I believe the core point that what wins is what most commoditizes cheap labor, regardless of its technical quality, is valid, and the examples cited fit that point.
I admittedly can speak more of Laravel and Drupal personally. "Make amateurs able to do things halfway decent without knowing what they're doing" is a core design principle of both systems. Which in turn drives down labor costs and quality.
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've been working with React Native for about two years now and have really been trying to give it the benefit of the doubt. I'm done with that. RN is garbage.
I've been having too much fun clipping things on YouTube to share with my colleagues. Here's a clip with @slightlyoff on questions you should ask yourself when considering React:
Has anyone here got opinions about Preact vs React?
Specifically, I'm weighing up migrating a large-ish codebase to Preact instead of upgrading React, and I'd be interested to hear from anyone who a) has done this, b) has decided not to do this, c) can think of solid reasons to stick with React.
I can't see much benefit to choosing React over Preact, but is there anything I'm overlooking?
@developit I've already tried it and it seems to work perfectly! We're using a handful of React-based libraries (eg. react-router) that seem to work equally well with Preact, so no incompatibilities I can see.
I've written up an RFC to propose switching, so this was really a last attempt to catch anything I might have overlooked (and because I'm interested to hear from anyone who's already gone down this path). I'm taking the lack of anyone saying "don't do it!" as a good sign! :)
About every time I think about an architectural problem in a #react application, I think: "This could easily be solved using a context!". Then I remember that the context API does not work with react server components and I'm lost.
The next step is tooting about it. And after that, I realize that most of my #react bubble is still on X (formerly known as twix) and that I'm talking into a void here.
For nearly a decade I was a strong fan of using jQuery and Backbone to enhance server generated html.
What led me to abandon that and embrace #React was not reactive development, it wasn’t the performance of dom diffing, it wasn’t any of the things that were inherent to React… it was JSX and pluggable, composable components.
Now, after two years working in a large scale react SPA with federated microfrontends… I’m finding that I miss the simplicity of Backbone and jQuery.
@ketmorco it really is. Web components almost fit my needs, but the limitation of attributes being exclusively strings is a real hinderance to the kind of composition I want to perform
@rick once its all setup, react eliminates a LOT of mental overhead in terms of everything one needs to know about the browser. Getting closer to the metal, as it were, takes a lot more general knowledge that is hard to expect from less experienced devs. Leaning in hard on React and styled components lets teams iterate REALLY fast, so it’s clear why it’s so attractive.
But wow, has that come with a performance cost to the user.
Created 65 tickets to migrate from class components to functional , some are small and should be relatively easy others are 2000+ mono components that render whole pages. Legacy #React is such a trip (I’m sure I’m also responsible for similar code in a past life)
"This reminds me of a hammer I had with a broken handle. Instead of replacing the handle, I attached the hammer to a helmet and whenever I want to drive a nail, I would wear the hammer and swing my head. But sometimes I miss and hit my head against the wall instead. So to fix that, I added some padding to my forehead and now it doesn’t hurt at all.
I’ll be speaking at App.js Conf 2024 in May, in Kraków. Super excited to be back in Kraków as a speaker this time. See you there? https://appjs.co/#speakers
@h_thoreson if you want to make web UI in python, check out streamlit. it’s just for prototypes & dashboards, but it nails its' use cases nearly perfectly https://streamlit.io/
