6 ms·

> First, we lost compatibility with a couple of tools that we really wanted to use. One of them was storybook, that is a super-nice preview system. We had to de

by jklm 5y ago

> First, we lost compatibility with a couple of tools that we really wanted to use. One of them was storybook, that is a super-nice preview system. We had to develop our own frankenstein to do the same. > Our choice does not need anyone to learn anything, and one can create a widget in no time! As someone who made the mistake of writing their own internal framework, I tip my hat to you. You just created your own framework that people now have to learn. And best of all, the documentation is always going to be less detailed than what you'd get with popular frameworks.

taeric 5y ago
I've found most applications people make on any framework are ultimately things to be learned by new folks. That is, picking a framework doesn't really help in this angle. It is true that simple apps can usually keep up with trends and documentation of a chosen framework. But, all too often, the choices in how to use a framework pile up and are lost to the tribal knowledge of a team. This was worse when libraries are pulled in easily to scratch itches for each part of the application without care to the whole.
soperj 5y ago
We actually have our documentation as a sandbox for the framework. So it gets updated as you build new pieces.
throwawayboise 5y ago
Does it really matter? In 5 years none of the popular frameworks are going to be the same. React will be "legacy" (if it isn't already) and something else will be the hotness.
- serverholic 5y ago
  React was released in 2013 and it's been the top framework for awhile now. There's a strong possibility that React will still be one of the top frameworks if not the top framework in 5 years still.
  - sudo_bang_bang 5y ago
    The Lindy Effect is real.
- DangitBobby 5y ago
  Doubt. React is here to stay. This is about as grounded in reality as people 5 years saying Ruby on Rails and Django would be gone today.
  - vanusa 5y ago
    Gone, no. But both seem to have distinctly ebbed since their peak (especially Rails).
- midrus 5y ago
  As much as I don't like React, it is here to stay. But even if it weren't, it would still be a better idea to use something existing than writing your own framework. It is documented, well tested, easy to integrate with other tools, has devtools, and lot of developers already know it (and will still know it several decades from now). Writing your own framework is almost never a good idea. It is only a good idea for the one writing it because we like tech and we like to show how good we're at building things ourselves. Business wise is the worst mistake ever... unless you're Figma or something like that building something radically special, I don't see how this is a good idea. You have the first example of this problem in the post itself: "...We did lost something with this choice. First, we lost compatibility with a couple of tools that we really wanted to use. One of them was storybook, that is a super-nice preview system. We had to develop our own frankenstein to do the same...." The more your project grows, the more of that you will get. Then one day the people that took this decision leaves the company. And then the new joiners are stuck with an undocumented, failing, spaghetti frankestein mess they have to work on day to day. And finally...those "few simple" components, will evolve...and sooner than later they won't be neither few neither simple anymore.
1ark 5y ago
Anecdotally documentation in JS framework world is quite bad or missing. So maybe not much of an argument? Compare React documentation to Flutter for example. Also you do not have to update your framework more than necessary. Often times there's a dependency that needs to be updated that requires everything else to be updated and you spend a lot of extra time with that instead of just fixing whatever bug you were supposed to fix. Tradeoffs to both approaches of course.
- trs8080 5y ago
  > Anecdotally documentation in JS framework world is quite bad or missing. So maybe not much of an argument? Compare React documentation to Flutter for example. can you give some examples of poor documentation? most frontend JS frameworks (react included) have friendly, comprehensive documentation. - https://beta.reactjs.org/learn https://beta.reactjs.org/learn - https://redux.js.org/introduction/getting-started https://redux.js.org/introduction/getting-started - https://svelte.dev/docs https://svelte.dev/docs - https://vuejs.org/v2/guide/ https://vuejs.org/v2/guide/

by jklm 5y ago

taeric 5y ago

I've found most applications people make on any framework are ultimately things to be learned by new folks. That is, picking a framework doesn't really help in this angle. It is true that simple apps can usually keep up with trends and documentation of a chosen framework. But, all too often, the choices in how to use a framework pile up and are lost to the tribal knowledge of a team. This was worse when libraries are pulled in easily to scratch itches for each part of the application without care to the whole.

soperj 5y ago

We actually have our documentation as a sandbox for the framework. So it gets updated as you build new pieces.

throwawayboise 5y ago

Does it really matter? In 5 years none of the popular frameworks are going to be the same. React will be "legacy" (if it isn't already) and something else will be the hotness.

serverholic 5y ago
React was released in 2013 and it's been the top framework for awhile now. There's a strong possibility that React will still be one of the top frameworks if not the top framework in 5 years still.
- sudo_bang_bang 5y ago
  The Lindy Effect is real.
DangitBobby 5y ago
Doubt. React is here to stay. This is about as grounded in reality as people 5 years saying Ruby on Rails and Django would be gone today.
- vanusa 5y ago
  Gone, no. But both seem to have distinctly ebbed since their peak (especially Rails).
midrus 5y ago
As much as I don't like React, it is here to stay. But even if it weren't, it would still be a better idea to use something existing than writing your own framework. It is documented, well tested, easy to integrate with other tools, has devtools, and lot of developers already know it (and will still know it several decades from now). Writing your own framework is almost never a good idea. It is only a good idea for the one writing it because we like tech and we like to show how good we're at building things ourselves. Business wise is the worst mistake ever... unless you're Figma or something like that building something radically special, I don't see how this is a good idea. You have the first example of this problem in the post itself: "...We did lost something with this choice. First, we lost compatibility with a couple of tools that we really wanted to use. One of them was storybook, that is a super-nice preview system. We had to develop our own frankenstein to do the same...." The more your project grows, the more of that you will get. Then one day the people that took this decision leaves the company. And then the new joiners are stuck with an undocumented, failing, spaghetti frankestein mess they have to work on day to day. And finally...those "few simple" components, will evolve...and sooner than later they won't be neither few neither simple anymore.

1ark 5y ago

Anecdotally documentation in JS framework world is quite bad or missing. So maybe not much of an argument? Compare React documentation to Flutter for example. Also you do not have to update your framework more than necessary. Often times there's a dependency that needs to be updated that requires everything else to be updated and you spend a lot of extra time with that instead of just fixing whatever bug you were supposed to fix. Tradeoffs to both approaches of course.

trs8080 5y ago
> Anecdotally documentation in JS framework world is quite bad or missing. So maybe not much of an argument? Compare React documentation to Flutter for example. can you give some examples of poor documentation? most frontend JS frameworks (react included) have friendly, comprehensive documentation. - https://beta.reactjs.org/learn https://beta.reactjs.org/learn - https://redux.js.org/introduction/getting-started https://redux.js.org/introduction/getting-started - https://svelte.dev/docs https://svelte.dev/docs - https://vuejs.org/v2/guide/ https://vuejs.org/v2/guide/