LWN: Comments on "25 Years of Linux — so far" https://lwn.net/Articles/698042/ This is a special feed containing comments posted to the individual LWN article titled "25 Years of Linux — so far". en-us Fri, 17 Oct 2025 08:08:46 +0000 Fri, 17 Oct 2025 08:08:46 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net 25 Years of Linux and the World Wide Web. https://lwn.net/Articles/699750/ https://lwn.net/Articles/699750/ anselm <p> Which would have been a bit silly given that one could write a basic Gopher server in half an afternoon and it would take perhaps three screens' worth of code. </p> <p> I think one of the main advantages of the WWW over Gopher – at least with the advent of the likes of NCSA Mosaic – was that it made page-embedded hyperlinks and graphics a thing (although technically you could argue that these were features of HTML and it would have been perfectly possible to serve HTML over Gopher, which later versions of the Gopher protocol in fact allowed). Other drawbacks of Gopher included not having an equivalent to URLs, and only a very limited selection of allowable content types. In the end, Gopher was really too primitive to win. </p> Wed, 07 Sep 2016 08:48:10 +0000 25 Years of Linux — so far https://lwn.net/Articles/699731/ https://lwn.net/Articles/699731/ mathstuf <div class="FormattedComment"> Huh. And now we have plugins which do that (ignore front-page, skipping JS completely or block subsets based on URLs, etc.). Indeed it does make for some…interesting renders, but on the whole, I like it better.<br> </div> Wed, 07 Sep 2016 01:16:55 +0000 25 Years of Linux — so far https://lwn.net/Articles/699727/ https://lwn.net/Articles/699727/ flussence <div class="FormattedComment"> Well, it was missing most of CSS 3. And it didn't live to see HTML 5 finally standardise the parsing of tag soup. And I think I had to file a bug about it sending malformed *HTTP headers* once.<br> <p> It's pretty dire on today's web, I'll admit (even NetSurf's doing better). But it was pretty good back when Opera couldn't put CSS opacity and text anti-aliasing on a page at the same time, Firefox injected parts of its browser UI into the page's own DOM, and IE... existed...<br> <p> <p> </div> Wed, 07 Sep 2016 01:12:47 +0000 25 Years of Linux and the World Wide Web. https://lwn.net/Articles/699722/ https://lwn.net/Articles/699722/ chfisher <div class="FormattedComment"> Part of the reason the WWW took off instead of Gopher is that CERN gave the WWW stuff away for free, whereas the Univ of Minnesota (authors of Gopher) attempted to monetize it by selling Gopher server licenses. Oops<br> </div> Tue, 06 Sep 2016 21:49:21 +0000 25 Years of Linux — so far https://lwn.net/Articles/699711/ https://lwn.net/Articles/699711/ zlynx <div class="FormattedComment"> As I recall it, KHTML got that speed by simply ignoring large chunks of HTML and CSS specs that would have slowed it down. KHTML's page rendering was often -- interesting.<br> </div> Tue, 06 Sep 2016 19:45:36 +0000 25 Years of Linux — so far https://lwn.net/Articles/699690/ https://lwn.net/Articles/699690/ flussence <div class="FormattedComment"> KHTML doesn't get anywhere near as much credit as it deserves. I'll sorely miss having a browser that had an option for middle-click autoscrolling, *and* could do said scrolling at 60fps. On a uniprocessor machine ten years ago!<br> <p> (Okay, maybe Opera could've done the same at the time, but I couldn't stand that non-native UI.)<br> </div> Tue, 06 Sep 2016 17:06:16 +0000 25 Years of Linux and the World Wide Web. https://lwn.net/Articles/699686/ https://lwn.net/Articles/699686/ zlynx <div class="FormattedComment"> A lot of the other "wonderful" hypertext ideas require either a single big server or cooperation between web servers.<br> <p> Bidirectional links with consistent metadata don't just happen.<br> <p> But with HTTP I can just create a link to anyone's web page. Whether they like it or not. And they can rename that web page whether I like it or not.<br> <p> Other, better systems require far too many coordinated moving parts which is why they fail.<br> </div> Tue, 06 Sep 2016 16:40:41 +0000 25 Years of Linux and the World Wide Web. https://lwn.net/Articles/699597/ https://lwn.net/Articles/699597/ anselm <p> The World Wide Web is to distributed information retrieval systems essentially what MS-DOS (and its successors) are to operating systems. It works reasonably well for what it set out to do, it is very widespread, many people seem to like it, and by now, even though its shortcomings are well-known and there have been additions to the additions that were made to attempt to mitigate them, it is quite impossible to get rid of. It managed to get where it is now not because it was technically excellent or otherwise compelling but mostly because it was there at the right time when somebody (or somebodies) important was looking for something like it, and the other stuff that existed (remember Gopher?) for whatever reason wasn't interesting enough. </p> <p> I remember attending a conference in the 1990s where a guy from a university in, I think, Austria gave a long talk which essentially amounted to whining that everyone was using this terrible WWW and nobody was interested in the much more clever and powerful system that his research group had invented. Didn't make a big impact, though. </p> Tue, 06 Sep 2016 09:58:20 +0000 25 Years of Linux and the World Wide Web. https://lwn.net/Articles/699552/ https://lwn.net/Articles/699552/ tialaramex <div class="FormattedComment"> Exactly, Tim _shipped something that worked_<br> <p> I was studying and later working at a major hypermedia lab in the 1990s. Without a doubt some of the research work was on things that the World Wide Web still doesn't really do today. But unlike our research work, Tim's half-arsed "Web" had users out in the wild. A research project would scope out a small problem, solve some of it, and write up a paper. If you were lucky some of the code making it work lasted beyond the time taken to get published, and if you were _very_ lucky that code was actually available from an FTP site somewhere. But by the time I arrived even as an undergraduate, there were more pages on Tim's World Wide Web than in any of these research systems, and by the time I became a postgrad they were writing up the new research systems _on_ Tim's World Wide Web, and at that point it becomes obvious that you're basically just wanking. Even if Tim's system was much worse in a whole variety of ways than the prototype research projects (it was), Tim's system existed and the prototypes were just prototypes. By the time I ceased to be a postgraduate student Tim had an office in the building where I had studied and his name was highlighted above all the clever people who'd been designing "better" hypermedia systems while the World Wide Web was taking over the world.<br> </div> Tue, 06 Sep 2016 00:10:17 +0000 25 Years of Linux and the World Wide Web. https://lwn.net/Articles/699548/ https://lwn.net/Articles/699548/ nix <blockquote> Tim Berners Lee's only real invention with the Web was the hyperlink. </blockquote> Ted Nelson (the coiner of the term 'hypertext') was talking about unbreakable bidirectional hyperlinks (and not just point-to-point hyperlinks, but links to and from *regions*, with optional annotations and other attributes) decades before. <p> But Tim actually got it working on a large scale. :) Mon, 05 Sep 2016 21:33:12 +0000 25 Years of Linux — so far https://lwn.net/Articles/699384/ https://lwn.net/Articles/699384/ pboddie <blockquote>The community was singularly unsuccessful at creating a proper web browser for Linux until the collapse of Netscape jump-started the development of the tool we now call Firefox.</blockquote> <p>That's rather unfair on those who developed KHTML - the basis of the decent-enough Konqueror - which then evolved to become WebKit, making possible the tools we now call Chrome, Chromium and (if it is still around because I don't follow Apple) Safari.</p> Sun, 04 Sep 2016 14:10:29 +0000 25 Years of Linux — so far https://lwn.net/Articles/699102/ https://lwn.net/Articles/699102/ Wol <div class="FormattedComment"> Plus infinity!!!<br> <p> Sorry for the noise, but yes, she did an awesome job!<br> <p> Cheers,<br> Wol<br> </div> Fri, 02 Sep 2016 11:28:36 +0000 25 Years of Linux — so far https://lwn.net/Articles/699023/ https://lwn.net/Articles/699023/ geek <div class="FormattedComment"> yes, indeed! who could have imagined the great job Pamela did on groklaw?<br> </div> Thu, 01 Sep 2016 22:38:18 +0000 25 Years of Linux and the World Wide Web. https://lwn.net/Articles/698900/ https://lwn.net/Articles/698900/ Wol <div class="FormattedComment"> <font class="QuotedText">&gt; I shudder to think where we would be without these two inventions of August of 91.</font><br> <p> In a similar place to where we are now?<br> <p> Tim Berners Lee's only real invention with the Web was the hyperlink. That's not to decry his hard work - but he basically built on what was already there.<br> <p> And instead of Linux we would have the BSDs. That world nearly happened ... <br> <p> Really, it's the people that matter, not the inventions. Linus, with his excellent project management skills and readiness to accept contributions from anyone, and TBL with his open Scientific "giving" frame of mind.<br> <p> Oh - and the lack, back then, of all these attempts to stifle creativity by patenting mathematics (software).<br> <p> Cheers,<br> Wol<br> </div> Thu, 01 Sep 2016 05:06:47 +0000 employer/employee copyright https://lwn.net/Articles/698578/ https://lwn.net/Articles/698578/ giraffedata I believe those are exactly the points I made. We made up copyright law and arbitrarily decided that by default it belongs to the employer (I see "naturally" could be taken another way; I just meant that with the law in place and no further action, the employer has the copyright), so for the employee to have it, the employer has to do something to give it up. <p> That's the opposite of the impression a reader would get from the phrasing, "employees should demand to keep their copyrights in Linux." The word "keep" implies that the copyright starts off belonging to the employee and the employee should insist on keeping it that way. If we want to give the correct impression (unless, again, we're trying to make a political point about truly natural rights being different from the ones created by law), a better wording would be, "employees should demand to own the copyright in their work on Linux." Tue, 30 Aug 2016 02:27:21 +0000 employer/employee copyright https://lwn.net/Articles/698449/ https://lwn.net/Articles/698449/ pabs <div class="FormattedComment"> I don't think there is anything "natural" about copyright, nor about employers owning it. As well as copyright transfers, the "employer owns copyright" rule can be overridden by the employment contract in at least the US and the UK:<br> <p> <a href="http://www.copyright.gov/title17/92chap2.html#201">http://www.copyright.gov/title17/92chap2.html#201</a><br> <a href="https://www.gov.uk/guidance/ownership-of-copyright-works#works-created-for-an-employer">https://www.gov.uk/guidance/ownership-of-copyright-works#...</a><br> <p> <p> </div> Mon, 29 Aug 2016 10:08:01 +0000 employer/employee copyright https://lwn.net/Articles/698397/ https://lwn.net/Articles/698397/ giraffedata <blockquote> ... reasons that Linux developers should demand to keep their copyrights in Linux instead of giving them to their employers. </blockquote> <p> Maybe you're trying to make a political point with this wording, but it's misleading. In the US, when someone pays someone else to write code, the copyright naturally belongs to the employer and the employer would have to give it to the developer for the developer to have it. Copyrights are man-made rights and the people who created them defined who's rights they would be. Sun, 28 Aug 2016 02:42:12 +0000 25 Years of Linux — so far https://lwn.net/Articles/698343/ https://lwn.net/Articles/698343/ halla <div class="FormattedComment"> Yes... We're currently having a Krita sprint in Deventer, and one of the contributors who is doing a ton of great coding work... She just realized she was one year old when Krita started :-). But it's good to have a good age spread, in this project we've had twelve year old people contributing code, while I'm definitely getting geezerish! <br> </div> Fri, 26 Aug 2016 19:15:00 +0000 25 Years of Linux — so far https://lwn.net/Articles/698341/ https://lwn.net/Articles/698341/ sjj <div class="FormattedComment"> It is kind of trippy to work with people for whom Linux and the Internet have *always* existed.<br> </div> Fri, 26 Aug 2016 18:20:38 +0000 25 Years of Linux — so far https://lwn.net/Articles/698308/ https://lwn.net/Articles/698308/ robbe <div class="FormattedComment"> <font class="QuotedText">&gt; As we have seen with projects like OpenSSL or GnuPG, it's not just </font><br> <font class="QuotedText">&gt; the obscure projects that fall by the wayside; important </font><br> <font class="QuotedText">&gt; infrastructure can also go without support.</font><br> <p> I don’t think the amount of resources poured into these projects is that much lower than it was 10 or 20 years ago. It’s just that /many/ more people, companies, and projects rely on them.<br> <p> This is not the only place where the „crumbling infrastructure“ problem exists.<br> </div> Fri, 26 Aug 2016 11:55:36 +0000 25 Years of Linux and the World Wide Web. https://lwn.net/Articles/698243/ https://lwn.net/Articles/698243/ mattrose <div class="FormattedComment"> About two weeks ago, the 25th anniversary of Tim Berners-Lee's announcement of the WWW happened. I would argue that though nobody knew it at the time, the events of August of 1991 was to change the world for the better more than any other single month in history. I shudder to think where we would be without these two inventions of August of 91.<br> </div> Thu, 25 Aug 2016 15:08:51 +0000 25 Years of Linux — so far https://lwn.net/Articles/698231/ https://lwn.net/Articles/698231/ JFlorian <div class="FormattedComment"> That sounds like a great suggestion for a future series of articles. I'd love to learn more about such endeavors. Important history is being made here (IMHO) and who better to capture that for future generations than our beloved LWN.<br> </div> Thu, 25 Aug 2016 13:17:57 +0000 25 Years of Linux — so far https://lwn.net/Articles/698207/ https://lwn.net/Articles/698207/ gnu <div class="FormattedComment"> Excellent point, jdub! There are so many of them who can't be found via `git blame' but worked tirelessly on various projects.<br> </div> Thu, 25 Aug 2016 08:08:51 +0000 25 Years of Linux — so far https://lwn.net/Articles/698196/ https://lwn.net/Articles/698196/ jdub <div class="FormattedComment"> <font class="QuotedText">&gt; In general, a lot of the outcomes that people feared have not come to be.</font><br> <p> In an otherwise excellent piece, I felt that this section skipped an important point: Many of those outcomes did not come to pass thanks to the non-technical contributions of some pretty surprising people.<br> <p> Activists and researchers, lawyers and managers… there are so many people who found this world through shared politics, principles, and social connections, or were simply reassigned to a new job and got excited. Some of them have contributed more than they'll ever let on (corporate politics), did invaluable work we couldn't fully understand (pro bono legal expertise), or simply gave their staff time to get involved and do things right (enlightened management).<br> <p> If you have ever worked on a major FLOSS project, you'll know people like this. You won't find them in git blame, you may not even find them in mailing list archives, but their contributions are still felt today.<br> </div> Thu, 25 Aug 2016 04:01:14 +0000 25 Years of Linux — so far https://lwn.net/Articles/698195/ https://lwn.net/Articles/698195/ pabs <div class="FormattedComment"> There are other funding models for open source and we are starting to see some organisations move towards them but it would be interesting to see how a Linus crowd-funding campaign could go.<br> <p> Thanks for highlighting the reasons that Linux developers should demand to keep their copyrights in Linux instead of giving them to their employers. Anyone who is doing that might want to talk to SFC about having their copyrights in Linux enforced.<br> <p> <a href="https://sfconservancy.org/copyleft-compliance/">https://sfconservancy.org/copyleft-compliance/</a><br> </div> Thu, 25 Aug 2016 03:17:02 +0000 25 Years of Linux — so far https://lwn.net/Articles/698190/ https://lwn.net/Articles/698190/ felixfix <div class="FormattedComment"> I patched a binary card deck ... once. Only got one bit wrong out of 960. Took a while to find it. Ugh.<br> </div> Thu, 25 Aug 2016 01:43:36 +0000 25 Years of Linux — so far https://lwn.net/Articles/698187/ https://lwn.net/Articles/698187/ neilbrown <div class="FormattedComment"> <font class="QuotedText">&gt; each of which had its own problems and none of which could be fixed by its users. </font><br> <p> ... excepting those of us driven enough to create binary patches... It was fun to do that *once*.<br> <p> </div> Thu, 25 Aug 2016 00:52:08 +0000 12 Years of Linux ONLY — so far (for me) https://lwn.net/Articles/698182/ https://lwn.net/Articles/698182/ pr1268 <p>Well, then that means it's been twelve years since I kicked MS Windows to the curb, wiped the drive, and went Linux only. (I had been dual-booting since about 1998 or so.)</p> <p>I think it's a nifty coincidence that I made this &quot;major lifestyle change&quot; on the anniversary of Linus' newsgroup posting. ;-)</p> Wed, 24 Aug 2016 22:44:45 +0000 25 Years of Linux — so far https://lwn.net/Articles/698179/ https://lwn.net/Articles/698179/ Depereo <div class="FormattedComment"> It's still exciting, and I'm looking forward to Rust on RISC-V, and Microsoft naming a kernel release "Hurr durr I'ma sheep".<br> <p> I wasn't working on the kernel 25 years ago (maybe working on learning my multiplication tables), but GNU/Linux is still a passion project for me. If I get paid to work with the tools and systems that excite and motivate me, all the better - I hope that I can still do meaningful and useful work (that makes its way upstream) without having to do it afterhours.<br> <p> A quarter-century of growth and success is a very impressive achievement for a software project, and as I get more and more experience I appreciate the challenges it has overcome more and more.<br> </div> Wed, 24 Aug 2016 22:24:00 +0000