4 ms·
>When people tried to write big enough applications with JavaScript, they found out, that it was a mess. I have written huge, complex, graphics-intensive appl
by rhapsodic 8y ago
>When people tried to write big enough applications with JavaScript, they found out, that it was a mess.
I have written huge, complex, graphics-intensive applications with Javascript, and that was not my experience at all. So maybe it's not the language, but the person using it that is responsible for the mess.
> It's similar to WinAPI. Sure, you can write C with WinAPI and it's enough for simple applications.
That is a very far-fetched comparison, in my view.
- ricardobeat 8y agoDo you use any framework, library or specific patterns in your apps?
- rhapsodic 8y ago>Do you use any framework, library or specific patterns in your apps? Yes, but my team takes the same approach that Facebook or Google takes. We don't try to shoehorn in some general framework made for some other application by someone else. We make our own, that serves our own particular needs. We are the architects and the builders of our software.
- abiox 8y ago> So maybe it's not the language, but the person using it oh. it would seem this is more about you feeling impressed with yourself, rather than making substantive arguments.
- rhapsodic 8y ago>oh. it would seem this is more about you feeling impressed with yourself, rather than making substantive arguments. That is my argument. It's simple logic. If I can get good results without React, I've proven that React is not necessary to get good results.
- abiox 8y agothat seems like a trivially true statement, if not an outright tautology.