Earlier quoted context omitted.
I disagree. Web programming can be fundamentally different from application programming. Application programming tends to be far more complex, far more planned, and far slower. Applications last for years and years, and new releases might take multiple years. Whereas web programming can be extremely experimental, prototype-y, with multiple releases a day . It's also vastly faster to program. This isn't an argument ag…
"Application programming tends to be far more complex, far more planned, and far slower. Applications last for years and years, and new releases might take multiple years." Really? You can build non-web apps just as fast as web apps. There are decades of tools and programmer experience doing this daily. You can't build Autocad or Photoshop as quick as you can churn out a buggy Rails site, but that's comparing apples…
I expect the underlying point was that most popular native platforms today almost force you into best practices which does add some upfront cost.
On the web you can throw up a single page PHP script full of SQL injection vulnerabilities and Javascript spaghetti and you are off the races. There is generally no equivalent for a modern GUI system. You typically need to start with a full MVC infrastructure in order to even begin to interface with the system libraries.
When you take care to craft your website using the same best practices the differences become negligible, but a large number of developers do not care about architecture and can take shortcuts that make it feel like they are moving faster.