4 ms·

There is a lot of anger in response to my comment, but it is all legitimate points too. Here are the facts as I know them: 1. Poor software can be written usin

There is a lot of anger in response to my comment, but it is all legitimate points too. Here are the facts as I know them: 1. Poor software can be written using either web or native technology. 2. It is possible to write fast, responsive applications that run in the browser (up to a certain level of complexity.) I know because this is what I do for a living, and I am pretty good at it. Sadly, many web developers are not very good at it or simply don't care enough about preventing a slow, clunky experience. 3. Some cutting-edge web tech (WebGL is the best example I can think of) is not yet ready for prime time. I love proof-of-concepts that demonstrate the possibilities of canvas, but commercial software should not be relying it yet. 4. The barrier of entry is lower for web. The double edge of this sword is web applications are more likely to be built by inexperienced amateurs. These are real problems, but they do not indicate that small applications will inherently run slowly in a browser. That is caused by poor design and architecture.

clarry 12y ago
> 2. It is possible to write fast, responsive applications that run in the browser (up to a certain level of complexity.) I know because this is what I do for a living, and I am pretty good at it. But if I tried your web application and found it to be slow, would you blame my computer, my OS, my browser, me, or something else? I don't want to be angry but it gets frustrating when things doesn't work. Things that -- at this day and age -- should be completely a non-problem for pretty much any PC system. Things that ran fine on grandma's old toaster when implemented the way they were fifteen years ago. And I get attacked a lot for complaining about it. Some people just don't see a problem with it when displaying some text and a handful of pictures requires millions of lines of code and a few hundred million bytes of RAM.. code that can completely bog down a 64bit CPU running at nearly 2GHz. I'm the victim, blame me. I'm the slave, no freedom for me.. I admit, I am grumpy, perhaps even angry. But it's not directed at you personally; I have no hard feelings against anyone here. Sorry if it came across that way :-)
- protonfish 12y ago
  If you tried my app and found it slow, I'd blame myself. Then I would find the reason it sucked and fix it. I have never found a performance problem in a web app that could not be traced to a mistake and be corrected to work fast. I am as frustrated with this situation as anyone else, even more so because it is my career. The amount lousy work being done makes it appear that the web application platform is to blame, when it is all the lousy developers' fault. Another major problem I didn't mention before is JavaScript libraries. These are a disease that has only one cure: more JavaScript libraries! Pointless JS bloat destroys an app's performance and is in high fashion right now (especially with the recent ubiquity of front-end frameworks.) The use of Angular and Bootstrap should be considered computer crime.

clarry 12y ago

> 2. It is possible to write fast, responsive applications that run in the browser (up to a certain level of complexity.) I know because this is what I do for a living, and I am pretty good at it. But if I tried your web application and found it to be slow, would you blame my computer, my OS, my browser, me, or something else? I don't want to be angry but it gets frustrating when things doesn't work. Things that -- at this day and age -- should be completely a non-problem for pretty much any PC system. Things that ran fine on grandma's old toaster when implemented the way they were fifteen years ago. And I get attacked a lot for complaining about it. Some people just don't see a problem with it when displaying some text and a handful of pictures requires millions of lines of code and a few hundred million bytes of RAM.. code that can completely bog down a 64bit CPU running at nearly 2GHz. I'm the victim, blame me. I'm the slave, no freedom for me.. I admit, I am grumpy, perhaps even angry. But it's not directed at you personally; I have no hard feelings against anyone here. Sorry if it came across that way :-)

protonfish 12y ago
If you tried my app and found it slow, I'd blame myself. Then I would find the reason it sucked and fix it. I have never found a performance problem in a web app that could not be traced to a mistake and be corrected to work fast. I am as frustrated with this situation as anyone else, even more so because it is my career. The amount lousy work being done makes it appear that the web application platform is to blame, when it is all the lousy developers' fault. Another major problem I didn't mention before is JavaScript libraries. These are a disease that has only one cure: more JavaScript libraries! Pointless JS bloat destroys an app's performance and is in high fashion right now (especially with the recent ubiquity of front-end frameworks.) The use of Angular and Bootstrap should be considered computer crime.