4 ms·

I built an private side project app that was in use at of the major brokers. I built it in react redux, because I thought it would raise "my" value. I've had

I built an private side project app that was in use at of the major brokers. I built it in react redux, because I thought it would raise "my" value. I've had to rebuild that shit more times than I care to admit. Imho for a small dev shop picking react is a stupid choice. For a small dev shop picking node in the backend is IMHO also a stupid choice. I could go on with the list, but I'm going to stop knowing that I will already have upset enough people. We've basically recreated the PHP problem. For whomever doesn't remember, before the first decent php frameworks like codeigniter(let's not talk about stuff like laravel) pretty much everyone built their own framework. After a couple of years when zend started to get traction they would integrate components from there. The main issue wasn't all the security issues or the usual PHP complaints you hear. The main was the same you have in the javascript community: > No two projects are the same If you have time and money to waste for people to constantly update your tooling fine. But I don't. Hell just keeping up to date with airbnbs linting style guide was a major PITA. EDIT: no I don't think the constant rewrites of redux and react router components, async connect, history etc. can be blamed on someone not having "enough experience in react". there's even a plugin to do regression tests on dependency updates. paying 100k for glorified javascript plumber jobs is unacceptable to me.

joshwcomeau 9y ago
I think a key thing you're missing is that you're new to React/Redux. Of course you won't be as productive with something you're just starting to learn (rebuilding something multiple times is natural when you're still figuring it out, but that goes away). That's not to say that everyone running Angular or Backbone or whatever should ditch their current stack and rebuild in React. But, a new dev shop would be wise to pick React, because most people who become experienced with it are very productive.
- deleted 9y ago
  [deleted]
- pdimitar 9y ago
  Flawed feedback. I trained myself in Elixir for a few weekends and once things started to click in my head (I was always an OOP / imperative programming guy so learning functional programming took me some trying) then I was able to do a mini-project that had real value... in 2 working days. I didn't have to deal with dependencies for more than 10 seconds (not an exaggeration), I didn't have to transpile, I didn't have to include shims / polyfills, I didn't have to explicitly include 2-3 CLI "task runners", etc. weird crap from the JS ecosystem that everybody in there thinks is normal for some reason. You can't just expect people to worship your tech stack and blame them for "not being experienced enough". Hell, if you put enough labor, you can get solid experience on a custom-tailored banking system written in COBOL, or custom-programmed FPGA CPU units. You can become an expert manual tailor, too. But that's not the point. IMO the point is -- are you able to immerse yourself in the tech stack you're proclaiming and be useful in business terms no more than 1-2 weeks later? If no, then your stack isn't worth investing into, especially after your stack is known to change trends as if it's some kind of a glamour fashion empire.
mahyarm 9y ago
If react/njs is a mistake for web side projects, what would be a good alternative?
- chrisco255 9y ago
  It's not a mistake. It's a great framework. Most of the complaints I hear about React come from folks who dislike JavaScript. JS is a great language for a side project. Make sure you learn fundamentals of JS. If you want an easy way to build a static web application with React, use Next.js. It's dead simple, no config, the folder structure acts as your router. https://github.com/zeit/next.js/ https://github.com/zeit/next.js/
- Double_a_92 9y ago
  Just HTML and CSS, with some occasional JS to make things nicer?

joshwcomeau 9y ago

I think a key thing you're missing is that you're new to React/Redux. Of course you won't be as productive with something you're just starting to learn (rebuilding something multiple times is natural when you're still figuring it out, but that goes away). That's not to say that everyone running Angular or Backbone or whatever should ditch their current stack and rebuild in React. But, a new dev shop would be wise to pick React, because most people who become experienced with it are very productive.

deleted 9y ago
[deleted]
pdimitar 9y ago
Flawed feedback. I trained myself in Elixir for a few weekends and once things started to click in my head (I was always an OOP / imperative programming guy so learning functional programming took me some trying) then I was able to do a mini-project that had real value... in 2 working days. I didn't have to deal with dependencies for more than 10 seconds (not an exaggeration), I didn't have to transpile, I didn't have to include shims / polyfills, I didn't have to explicitly include 2-3 CLI "task runners", etc. weird crap from the JS ecosystem that everybody in there thinks is normal for some reason. You can't just expect people to worship your tech stack and blame them for "not being experienced enough". Hell, if you put enough labor, you can get solid experience on a custom-tailored banking system written in COBOL, or custom-programmed FPGA CPU units. You can become an expert manual tailor, too. But that's not the point. IMO the point is -- are you able to immerse yourself in the tech stack you're proclaiming and be useful in business terms no more than 1-2 weeks later? If no, then your stack isn't worth investing into, especially after your stack is known to change trends as if it's some kind of a glamour fashion empire.

mahyarm 9y ago

If react/njs is a mistake for web side projects, what would be a good alternative?

chrisco255 9y ago
It's not a mistake. It's a great framework. Most of the complaints I hear about React come from folks who dislike JavaScript. JS is a great language for a side project. Make sure you learn fundamentals of JS. If you want an easy way to build a static web application with React, use Next.js. It's dead simple, no config, the folder structure acts as your router. https://github.com/zeit/next.js/ https://github.com/zeit/next.js/
Double_a_92 9y ago
Just HTML and CSS, with some occasional JS to make things nicer?