Live data from Hacker News

React created roadblocks in our enterprise app

medium.com

21–30 of 298 posts

Re: React created roadblocks in our enterprise app

#21

Technology problems are usually just human problems behind a mask. In this case, the real problem was a poorly skilled team with bad leadership, and React just exacerbated the problems by giving the team enough rope to hang itself.

Well said. It was frustrating how little he talked about the actual problems with the codebase, instead choosing to handwave and blame it all on React. The dig on the React team in particular was bizarre:

> React’s team enjoy experimenting with new ideas, but this is killing the ecosystem! They should be brave and take the blame for it!

Have to make a lot of assumptions with this sort of thing, but I can't imagine that attitude results in high quality engineering work.

Re: React created roadblocks in our enterprise app

#24
post #4

AngularJS was indeed a bit of a pain when we switched to Angular 2+ and beyond, but it was so worth it. I chose it because of the skillset that our current (small) team has. There's no way our 'designer' (more an HTML/CSS guy) could have wrapped his head around JSX, the way it mixes scripts with layout markup. The way Angular separates concerns for us is great. And the components are extremely flexible and reactive a…

JSX always seemed like a red flag to me. It was redesigning something that already exists to make it so that it uses non native browser functionality? Also the portability looked like an issue from it. I don't understand the use case for it. Vue and apparently Angular use basic browser friendly components.

Why does it really matter if the code you write is browser friendly or not? Everything is transpiled to browser code anyways, that includes Vue and Angular and JSX.

None of the code you write is ever really touched by a browser anymore. At the very least it's minified.

Re: React created roadblocks in our enterprise app

#25
I mean, this feels like a classic example of not choosing the best technology for the situation. Picking a more opinionated (or more batteries included) framework likely would have streamlined a lot of the problems he described. That doesn't reflect badly on React - certainly there are teams that could have used it to implement a project of this size - but it reflects badly on the author.

> I will not encourage using it for enterprise applications.

Almost like large-scale projects have different requirements and the tools generally used on large scale projects (like .Net) have adapted to reflect those requirements.

Re: React created roadblocks in our enterprise app

#27

Technology problems are usually just human problems behind a mask. In this case, the real problem was a poorly skilled team with bad leadership, and React just exacerbated the problems by giving the team enough rope to hang itself.

> ... the real problem was a poorly skilled team with bad leadership...

Given this kind of team and leadership, why does that still make React the best choice for them?

Re: React created roadblocks in our enterprise app

#29
Just reading the initial scope of the requirements. This project was guaranteed to fail, no matter what tech stack was utilized.

There's no future proofing in Software Development. As soon as an application is deployed to prod, it's obsolete. It must be on constant maintenance/upgrade schedule. And, the replacement project must be scoped out quickly.

Re: React created roadblocks in our enterprise app

#30

Technology problems are usually just human problems behind a mask. In this case, the real problem was a poorly skilled team with bad leadership, and React just exacerbated the problems by giving the team enough rope to hang itself.

At some point one has to see the trend of all these people hanging themselves with this one platform and maybe there's something to the platform, ecosystem, or community that is lending itself to the hangings.
Post reply on HN