3 ms·
(gjolund: I can't reply to you directly, but consider this my reply) Because they're simple? They're relatively standard? They're compact? Because I don't have
by tomc1985 11y ago
(gjolund: I can't reply to you directly, but consider this my reply)
Because they're simple? They're relatively standard? They're compact? Because I don't have to learn a new god-damned framework for every single new assignment? When did software development become a paint-by-numbers exercise? There is a difference between spaghetti-code and engineering.
Why do you want to write all that extra code instead of just picking the right tool for the job?
Because I can do it in less lines, in less time, with no new dependencies, and -- again! -- I don't need to learn another new framework!
PS- Please understand, I know the difference between good code and bad. That's why I've automated most of my job title and am able to spend 97% of my working day helping the rest of my team solve their problems! Oh and did I mention I handle the infrastructure, enterprise integration, telemetry, and sales reporting for my company?
- Vendan 11y agojust fyi, if you don't get the "reply" link, you should be able to click the "X minutes ago" and post a reply that way.
- tomc1985 11y agothanks! That trick worked!
- codeisawesome 11y agoIt's a lot easier to learn React than what all of you think. It's especially easier to learn these frameworks when you tried to solve the problem without them and experienced the pain of not having them.
- tomc1985 11y agoAs a user of React, I disagree -- unless you are using React in a javascript runtime, in which case you're probably fine. But I resent react for all the extra cognitive load it forces me to worry about when all I really give a shit about is its shadow DOM implementation. And then, only when I've got page(s) full of data I need to update without lag.
- codeisawesome 11y agoAre you talking about ReactNative? I haven't played with that yet, but it's one reason I chose React in one of my projects (eventual plans to use our web browser components at least partially in Native).
- tomc1985 11y agoNo, more specifically, using React with Rails through the react-rails gem. I am considering ripping out all my JSX and replacing it with our React JS
- morgante 11y agoI'd like to correct some misconceptions you seem to have regarding React. > unless you are using React in a javascript runtime, in which case you're probably fine React is written in JavaScript. It runs exclusively in JavaScript. If you've somehow managed to run it outside a JavaScript runtime then I'd actually be delighted to learn about how. > all I really give a shit about is its shadow DOM implementation React doesn't have a shadow DOM.