4 ms·

> The answer: “It’s the web; use existing web technologies.” was—and still is—a good answer. That's a terrible answer. Oh, I just need to cobble together a bun

> The answer: “It’s the web; use existing web technologies.” was—and still is—a good answer. That's a terrible answer. Oh, I just need to cobble together a bunch of shitty libraries that pale in comparison to what's available on native platforms just to build a simple app that will equally pale in comparison to apps on actual native platforms? Yeah, I think I'll pass. Web technology sucks and it's holding us all back. I'd rather see a new web that is built as a platform for actual applications instead of "documents".

sehr 12y ago
What a refreshing and well thought out viewpoint. I especially like the delivery of it, a perfect way to convince others!
- WorldWideWayne 12y ago
  I'm not evangelizing here and I don't have to because what I want is going to happen eventually anyway.
  - sehr 12y ago
    Then there is no point to you comment whatsoever is there?
    - WorldWideWayne 12y ago
      Are you the Internet police or something? Why don't you take a look at your own comment history, asshole :) Are you evangelizing every time you disagree with an article?
  - sehr 12y ago
    Then there is no point to you comment whatsoever is there?
EdSharkey 12y ago
Yes, but developer experience is only one aspect for you to consider. Have you considered the ease of deployment/availability/potential audience size of web apps versus your native platforms? We're all just trying to make successful products, after all. And any app of significant complexity will require at least some level of craft (which I suspect is part of your gripe - no craft required, ecosystem too large.) Also, consider that any platform like HTML5 that includes Gamepad, Audio Data, Canvas/GL, Mouse Lock, and Socket API's has evolved far beyond simple document display. The cruelest retort I can give on HN is none at all. It must be crushing to see one's story meet the front page of HN, only to receive few/no comments, right? If you're this passionate and worked up on the subject, please give the silent treatment a go.
- WorldWideWayne 12y ago
  > Have you considered the ease of deployment/availability/potential audience size of web apps versus your native platforms? Sure. Do you think that a new system that is better than HTML/CSS/JS couldn't be built with that in mind? Native systems all already have hooks for easy deployment and updates and the potential audience is everybody since you need a native system to run a browser and a browser is nothing special. What we need are standards for applications. Not documents that you can script. > Also, consider that any platform like HTML5 that includes Gamepad, Audio Data, Canvas/GL, Mouse Lock, and Socket API's has evolved far beyond simple document display. HTML is still very, very deeply rooted in document display and browsers. That's why native apps perform better and are more popular for anything but simple data entry. Even for simple data entry, as a user I prefer native. > If you're this passionate and worked up on the subject, please give the silent treatment a go. I guess three sentences including a curse-word and a bit of sarcasm counts as "passionately worked up" these days :)

sehr 12y ago

What a refreshing and well thought out viewpoint. I especially like the delivery of it, a perfect way to convince others!

WorldWideWayne 12y ago
I'm not evangelizing here and I don't have to because what I want is going to happen eventually anyway.
- sehr 12y ago
  Then there is no point to you comment whatsoever is there?
  - WorldWideWayne 12y ago
    Are you the Internet police or something? Why don't you take a look at your own comment history, asshole :) Are you evangelizing every time you disagree with an article?
- sehr 12y ago
  Then there is no point to you comment whatsoever is there?

EdSharkey 12y ago

Yes, but developer experience is only one aspect for you to consider. Have you considered the ease of deployment/availability/potential audience size of web apps versus your native platforms? We're all just trying to make successful products, after all. And any app of significant complexity will require at least some level of craft (which I suspect is part of your gripe - no craft required, ecosystem too large.) Also, consider that any platform like HTML5 that includes Gamepad, Audio Data, Canvas/GL, Mouse Lock, and Socket API's has evolved far beyond simple document display. The cruelest retort I can give on HN is none at all. It must be crushing to see one's story meet the front page of HN, only to receive few/no comments, right? If you're this passionate and worked up on the subject, please give the silent treatment a go.

WorldWideWayne 12y ago
> Have you considered the ease of deployment/availability/potential audience size of web apps versus your native platforms? Sure. Do you think that a new system that is better than HTML/CSS/JS couldn't be built with that in mind? Native systems all already have hooks for easy deployment and updates and the potential audience is everybody since you need a native system to run a browser and a browser is nothing special. What we need are standards for applications. Not documents that you can script. > Also, consider that any platform like HTML5 that includes Gamepad, Audio Data, Canvas/GL, Mouse Lock, and Socket API's has evolved far beyond simple document display. HTML is still very, very deeply rooted in document display and browsers. That's why native apps perform better and are more popular for anything but simple data entry. Even for simple data entry, as a user I prefer native. > If you're this passionate and worked up on the subject, please give the silent treatment a go. I guess three sentences including a curse-word and a bit of sarcasm counts as "passionately worked up" these days :)