4 ms·
I think things just move too fast in the web world in the past few years... Yes, a common component plugin standard so you can reuse it in both React and Angul
by eranation 9y ago
I think things just move too fast in the web world in the past few years...
Yes, a common component plugin standard so you can reuse it in both React and Angular would be nice (Web Components?) but remember not that long ago, we were debating between EmberJS, BackboneJs and jQuery UI. And Gulp vs Grunt, and UMD vs CommonJS, Bower vs NPM. React and Angular4 are very, very new relatively, and they evolve pretty fast, with breaking changes. A company betting on building a CRUD / UI builder needs to go into market in a few months or it's already behind.
Take a look at react studio (see comment here). They are a great tool probably, but they are focused on one popular library at the moment. The change is so rapid that by the time you create an automation tool, it's generating code that will be "obsolete" in terms of people who would like to maintain it (would you go work for a startup where you need to maintain backboneJS or jQuery UI all day?). The alternative is to generate code that doesn't try to be "latest and greatest" at all, and not really care (see wix code post earlier today)... but not sure it's a great bet as well.
I think back in the day, there were just less options to choose from when building apps, and they evolved slower. This is why in the desktop days we had a lot more robust UI builder, app builders (Every IDE has top notch visual destkop UI editor, but also good old Magic, MS Access, FileMaker etc...).
I do think this is begging to be changed. And I'm sure a few people have this in mind as well. But it will always be one step behind of the latest web frameworks.
However you do have some solutions
1. Java - JHipster uses yeoman to generate Spring Boot + Angular apps including basic CRUD UI
2. Rails - rails scaffolding do basic CRUD nicely
3. Node.JS - http://loopback.io http://loopback.io
I'm sure there are more. And I'm sure there will be more. But in the end all the above do is give you a jumpstart, if all your app is doing is just CRUD, then your barrier to competition is already low, whether it's automated, outsourced or done by Stanford grads getting 200K a year.
But I do think that eventually your idea of shared components should be a thing. Just need to get google and facebook in the same room and agree... weirder things happened... companies agreed on standards before...
- davidjnelson 9y agoThat's an extremely good point. The solution to this would be that the output is plugin based. It could spit out react, angular, next framework, framework after that etc. Edit: Thinking some more about this. I think the future proofing is the hardest aspect. If you were able to leverage a custom compiler to transform react or angular components to a future framework, that would get you there. Also, Jhipster looks really great _if_ you happen to be using java.
- nwellinghoff 9y agoJhipster looks really great. Are people primarily using it to just bootstrap a project or actually using for the duration of a projects full lifecycle?