3 ms·

Or we can use our own component system, which we created ourselves at least 10 years ago, and not use React at all. When you are into programming, like we are,

Or we can use our own component system, which we created ourselves at least 10 years ago, and not use React at all. When you are into programming, like we are, you think of these things long before some big company tells you what to do.

pault 8y ago
I am into programming, like you are. I also would rather benefit from the thousands and thousands of developer hours that have gone into the react core, and not have to train every new team member on a crufty ten year old bespoke codebase. I do try to keep my external dependencies low, but core utilities are not worth rewriting from scratch.
- sureaboutthis 8y ago
  >a crufty ten year old bespoke codebase. Anything you want to show up to us, bring it on, and our code will run rings around anything you can give us while spitting in its face. We are high performance. Don't think that we wrote the first run 10 years ago that we haven't modified and improved and left it as is all this time. If you think you need react to do your job, then you can't work for us. We are professional programmers.
  - dang 8y ago
    I appreciate that you've mostly stuck to being civil with this account, but please don't cross into flamewar like this. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
abiox 8y ago
sadly we aren't all as smart and worthy as you are, and don't have a decade old react-like hanging around. some of us even prefer the idea of using an open source library for the various benefits of doing so.
dan1234 8y ago
If you'd shared that system 10 years ago maybe we'd all be using that instead of React! Where I work, we use React because it's easier to find new hires (because they want to work with React) and quicker to get them up to speed on a project (because they already know the framework). It's also easier to integrate and extend any 3rd party components, as we're already familiar with the boilerplate.

pault 8y ago

I am into programming, like you are. I also would rather benefit from the thousands and thousands of developer hours that have gone into the react core, and not have to train every new team member on a crufty ten year old bespoke codebase. I do try to keep my external dependencies low, but core utilities are not worth rewriting from scratch.

sureaboutthis 8y ago
>a crufty ten year old bespoke codebase. Anything you want to show up to us, bring it on, and our code will run rings around anything you can give us while spitting in its face. We are high performance. Don't think that we wrote the first run 10 years ago that we haven't modified and improved and left it as is all this time. If you think you need react to do your job, then you can't work for us. We are professional programmers.
- dang 8y ago
  I appreciate that you've mostly stuck to being civil with this account, but please don't cross into flamewar like this. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html

abiox 8y ago

sadly we aren't all as smart and worthy as you are, and don't have a decade old react-like hanging around. some of us even prefer the idea of using an open source library for the various benefits of doing so.

dan1234 8y ago

If you'd shared that system 10 years ago maybe we'd all be using that instead of React! Where I work, we use React because it's easier to find new hires (because they want to work with React) and quicker to get them up to speed on a project (because they already know the framework). It's also easier to integrate and extend any 3rd party components, as we're already familiar with the boilerplate.