throwaway60320

8 ms·

1.
by throwaway60320 3y ago
How would you put this if it was a fact and not "biased"?
2.
by throwaway60320 3y ago
They did. Read the ToS.
3.
by throwaway60320 3y ago
Yeah, I agree. I live in an EU country where firing people is normal... It's also the country with lowest unemployment rate in EU.
4.
by throwaway60320 3y ago
Yes, that's what they're doing. And Russia/Belarus too, before the war. Also, not just EU companies - the EU branches of US companies I worked for had 1/2 of the teams in Ukraine/Russia/Belarus.
5.
by throwaway60320 3y ago
What do you mean, never gave consent for? I helped a friend put their photos on there, and they most definitely did consent to practically anything.
6.
by throwaway60320 3y ago
Sorry but this sounds like they just didn't know how to write React and didn't take the time to learn it. You can write React and have 2 runtime dependencies in total - react and react-dom. Or you can go for preact and have exactl
7.
by throwaway60320 3y ago
(P)React is the best way to do it in a maintainable, easy-to-reuse, easy-to-understand, extendable fashion, indeed. Show me something better and I'll jump on it. I don't care about resumes, I own my consultancy. I care about quick
8.
by throwaway60320 3y ago
Why though? It's much easier to do a simple API (or use a pre-made one like this one) from the web and the app. And no need to change the backend code on design updates. I just don't get what you're chasing after. All this se
9.
by throwaway60320 3y ago
Sure, you do you. I spent 10 years working with jQuery and am very thankful to leave that very far behind me. BTW: jQuery is 85.1 kB minified and 29.7 kB gzipped. Preact (same API/dev experience as React, minimal performance impact) is
10.
by throwaway60320 3y ago
So the user would have to submit the form and be met with 10s of errors? I'd rather tell them immediately.
11.
by throwaway60320 3y ago
Yeah until a manager comes and says "well great, it works, now let's do a mobile app like that"
12.
by throwaway60320 3y ago
Check out XState, it's really great! But it's not that necessary in my case, my forms are usually not complex statecharts, just a lot of individual and largely decoupled complex form controls - multiselects with rules, map pins, t
13.
by throwaway60320 3y ago
It's not simple. I made multi-page forms with dozens fields where your suggestion would lead to intangible mess of spaghetti code - I know because I worked with the web way before React. Even with the best coding standards and a team o
14.
by throwaway60320 3y ago
Of course you have to validate on the server. That's a given, always. But you want to provide better UX to the user. Htmx is not simpler than React. I can't deploy that without a server that knows everything about the frontend. Re
15.
by throwaway60320 3y ago
It's really not that simple. What about complex validation rules? Do you really think it's user friendly to require them to send the whole form just to tell them "sorry no" 10 times over until they get it right? What abo