3 ms·
> Do you think an app like Photoshop or 3DSMax uses a react like framework on top of whatever C++ GUI they are using? Yes I think so. Why else would they requi
by paradite 8y ago
> Do you think an app like Photoshop or 3DSMax uses a react like framework on top of whatever C++ GUI they are using?
Yes I think so. Why else would they require 1GB of space to install them and specific hardware to run them efficiently? As a matter of fact, they require rendering libraries from graphics card companies. The difference is that they use their own proprietary frameworks instead of open sourcing them.
> How many apps can boast about being as complex on the web? most of these web apps are forms.
Not a lot, but quite significant nontheless. For example google docs, office 365, Facebook, Amazon, and many cloud solutions for enterprise. I agree most of web apps out there are just fancy forms and don't really need any frameworks, but there are legitimate use cases for them.
Edit for your updated comment:
Yes, I fully agree that web developers should start from basics, not frameworks and libraries. Cheers.
- aikah 8y ago> As a matter of fact, they require rendering libraries from graphics card companies. in order to render graphics. The DOM already gives you all that for free. > For example google docs, office 365, Facebook, Amazon, and many cloud solutions for enterprise Not even VSCode uses a specific framework, which demonstrate my point. Yes, they use Monaco editor for their text editor but this is a very specific library for a specific purpose, this isn't a generic view framework like react and co.
- paradite 8y ago> Not even VSCode uses a specific framework, which demonstrate my point. Yes, they use Monaco editor for their text editor but this is a very specific library for a specific purpose, this isn't a generic view framework like react and co. I think your argument is a bit flawed here. They don't use a generic framework for VSCode not because they don't need a framework, but probably because a generic framework is not good enough for handle the complexity on their level that they need to invent their own framework. So, my point is: Simple app, fancy forms: No framework should be required, just use VanillaJS, jQuery, or d3.js. More complex apps that solves a generic problem (CRUD with heavy client side interactivity): Generic framework. Extremely complex and specialized apps: Write your own framework.
- sam0x17 8y agoAll of the above, you could implement in vanilla javascript and HTML 5 just fine. People are just getting crazy these days.
- ng12 8y agoI can tell you've never actually tried doing that, especially not with a team of 4-5 developers and constantly changing requirements. If it doesn't sound incredibly painful your webapp isn't complicated enough to warrant a framework anyways.
- sam0x17 8y agoI'm literally in charge of a team of 3 devs that does that. React complicated our stack, slowed things down both development wise and in terms of inefficient asset management, so we reverted to vanilla JS and never looked back.
- ng12 8y agoWhat kind of app is it? Is it an SPA or a mostly-HTML website with some bells and whistles? I've been through the whole gamut -- pure JS, jQuery, Backbone, Angular1, and React. I love React because it's by far the most pleasant experience for my work. You would not get me to go back to pure JS over pain of death, it's just a non-starter for the types of apps we're building.