5 ms·

According to Wikipedia, a browser is an "application for accessing information on the World Wide Web (...) retrieves the necessary content from a web server and

• thedirt0115 7y ago
  Probably because they think that most of the hard work that goes into building a browser -- like parsing sloppy html, handling CSS correctly, a JS engine, etc -- were not done by the author. To me this feels like like getting a free cheeseburger, adding a leaf of spinach to it, and then saying you built a cheeseburger. But hey, maybe you want a cheeseburger with spinach, and you don't care whether other people think they "built" the cheeseburger or not.
  • Isamu 7y ago
    >the hard work that goes into building a browser ... is a gigantic amount of work, indeed. >like getting a free cheeseburger, adding a leaf of spinach to it If that cheeseburger was the size of an office building, and your spinach leaf was particularly small.
• deleted 7y ago
  [deleted]
• djsumdog 7y ago
  I guess technically he built a browser. There are many browsers out there that just use Gecko, WebKit, Blink, etc. under the hood. Hell, Edge just switched from their own Titan engine to Chromium/Blink. Building a control around a render is still neat, but it's not baking the thing from scratch. I think part of the pushback in these comments is that as devs and hackers, a lot of us want to see new rendering engines. Even if they're basic or just render web data differently, it'd be a good change from the narrowing and limited web rendering landscape that's out there.