![]() I used it to download a lot of stuff over the years. I'm sure there are a bunch of implementation details that seemed like a great idea as a Sophomore in college that no longer sound so clever, but the implementation is pretty sound. We chose to build a bit torrent client and I ended up continuing working on it for a year or so. Most of the groups picked games or things like that. I think the focus of the class was roadmaps and other parts of the development process for a larger project. Yes, there are probably a lot more people working on fixing bugs in the browser, but there are also a lot of people adding/modifying features and thus creating new bugs.Ī decade ago now, I wrote a bit torrent client that started as a project for a software development class. That's even worse for the browser: you have to trust several orders of magnitude more code implementing a massive set of interdependent features. If we account for complexity by using a metric like "(man-years of battle-testing)/(magnitude of attack surface)", a well-tested specialized client that hasn't had many recent bug reports is a much safer choice than anything running in a browser. ![]() If you only consider the number of man-years an application has been battle-tested, you imply that design complexity and attack surface doesn't matter. A specialized client that only implements one protocol without any connection to the "web" is far easier to reason about and debug. ![]() They also have a monstrous attack surface because they are "web-facing". ![]() Browsers are far more battle-tested than just about any other web-facing application on your computer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |