Slashdot Mirror


Linus Torvalds Says Linux Kernel v5.0 'Should Be Meaningless' (betanews.com)

An anonymous reader shares a report: Following the release of Linux kernel 4.16, Linus Torvalds has said that the next kernel will be version 5.0. Or maybe it won't, because version numbers are meaningless. The announcement -- of sorts -- came in Torvalds' message over the weekend about the first release candidate for version 4.17. He warns that it is not "shaping up to be a particularly big release" and questions whether it even matters what version number is slapped on the final release. He says that "v5.0 will happen some day. And it should be meaningless. You have been warned." That's not to say that Linux kernel v5.0 -- or whatever it ends up being called -- will not be significant. With the removal of old architecture and other bits of tidying up, with v4.17 RC1 there were more lines of code removed than added: something described as "probably a first. Ever. In the history of the universe. Or at least kernel releases."

165 comments

  1. Follow the Mozilla model by Anonymous Coward · · Score: 1

    And release a new major version every six weeks. Also get rid of kernel modules in favour of webextentions, because cloud.

    1. Re:Follow the Mozilla model by Tarlus · · Score: 1

      Snaps snaps snaps!

      --
      /* No Comment */
  2. Legacy free kernel by Anonymous Coward · · Score: 0

    They should make a legacy-free branch so the kernel isn't a 100MB d/l.

  3. Version numbers are meaningless? by Anonymous Coward · · Score: 0

    WTF Torvalds? Is the kernel somehow behind the rest of the world in terms of software development?

    That's like 20% a serious question. Why not go semantic? Or by calendar date?

    captcha: cypress, which is apparently just as meaningful a label for a kernel version as 5.0.

    1. Re:Version numbers are meaningless? by Junta · · Score: 1

      Think there's a difference in interupreting the sense of 'should'.

      He is saying 'should' as in 'I expect it should be meaningless' as in 'As it stands, I don't see a forseeably different reason to bump the version number, but it's going to happen anyway to keep the numbers small'.

      It all boils down to there originally being meaning, and the kernel suffering greatly as a result of how they went (spending years of drift from stability that would be herculean to overcome as it sat in unstable.

      Then they decided that they had no 'casual' users at all, and so they could treat every little release as a combination fix/feature release, and the cadence of efforts would not tangle each other up. The 'casual' users are sheltered from the details by RedHat, Debian, SuSE, or Ubuntu, all of which do work to understand the real nature of a kernel and do backports as appropriate.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    2. Re:Version numbers are meaningless? by Carewolf · · Score: 1

      Well, they are not going to break backwards compatibility as that would break Linux, so the major version would be forever stuck at 2, and they no longer differentiates between adding features or adding bug-fixes (they are the same), so the two other numbers in the semantic versioning would also be somewhat meaningless.

  4. It should by Anonymous Coward · · Score: 4, Insightful

    0.0.xx releases should be bugfixes. 0.xx releases should be minor feature updates. X.00 releases should be releases that break, or significantly change, the ABI, or that add major functionality.

    1. Re:It should by Junta · · Score: 1

      The problem for the kernel is it has exceedingly broad scope and as such has hit difficulties with the 'major functionality' criteria.

      Some major networknig addition that only matters for telcos lands in a kernel and that drives a bump, even though 90% of the users don't even use it? There a new DM module for a nice enterprise storage that does nothing for a phone user?

      When they did do the major functions are held back dance, some 'major things' that were quick got held up for years waiting for other 'major things' that were not so quick.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    2. Re:It should by aardvarkjoe · · Score: 2

      0.0.xx releases should be bugfixes. 0.xx releases should be minor feature updates. X.00 releases should be releases that break, or significantly change, the ABI, or that add major functionality.

      That's one way to do version numbers. That's how the Linux kernel used to do things. And Linus found that it didn't work very well for the kernel, so he changed to a different approach.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    3. Re:It should by skullandbones99 · · Score: 1

      We already have:

      0.0.xx releases which are stable releases from the linux-stable repository, these include bug fixes. However, only LTS (Long Term Support) kernels have on-going support.

      0.xx releases are the cumulative releases. Each release is unique. Each release is generally compatible with the previous release. However, note the kernel has config options with allows the kernel to be conditionally built which allows sub-systems to be configured in and out. Therefore, the kernel version only identifies the codebase, it does not identify what is in the kernel.

      X.00 releases are rare due to the kernel being in continuous update. This makes the point that X.00 releases are arbitrary because the kernel evolves rather than revolves. There are few step changes in the kernel and generally multiple APIs for the same sub-system can co-exist via build CONFIG options. This allows a sub-system to have an experimental new API, current API, mature but deprecated API all available concurrently which reduces the occurrences of incompatibility between kernel releases because the appropriate solution can be selected and built for your system.

      We might as well only have x.yy where x is the serial number of the version and yy is the bug fix state of the stable release. In other words, the current major number is redundant. Perhaps we can have a year prefix ?

    4. Re:It should by ceoyoyo · · Score: 1

      Fair enough, but the jump between .17 and .0 seems odd unless there's some reason. Why not .18? Or .9 to .0 like everyone used to do it?

    5. Re:It should by aardvarkjoe · · Score: 1

      Fair enough, but the jump between .17 and .0 seems odd unless there's some reason. Why not .18? Or .9 to .0 like everyone used to do it?

      Linus's "meaningless" quote addresses his motivations: he doesn't want there to have to be a reason. He wants to discourage people from treating a "5.0" release any differently than they would treat a "4.17" release, because with the current kernel development model, every version increment is essentially equal.

      --

      How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
    6. Re:It should by AvitarX · · Score: 1

      Just drop the first digit then.

      Didn't Solaris or something do that?

      As a user, I'd think it makes sense to bump the first digit for the long-term supported ones. I'd be able to know 5.0.x was going to have the x incrememnted with bugfixes longer than anything until 6.0.x

      The number is no longer then about features, but still provides useful information.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    7. Re:It should by AmiMoJo · · Score: 1

      Key thing is to pick one and stick with it. Windows 10 is all very well, but what are they gonna do when they are on V94, huh?

      I seem to recall that the API uses bytes for major and minor versions, so Windows 256 is gonna be a problem.

      Pretty short sighted if you ask me. All my version numbers are uint64s representing the number of nanoseconds since 02:14 on August 29th, 1997.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    8. Re:It should by Xenna · · Score: 1

      So Linus basically invented semantic versioning and now that it's become religion he's dropping it.

      Cheeky bugger ;-)

    9. Re: It should by dunkelfalke · · Score: 1

      Windows 10 was supposed to be the last Windows version.

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    10. Re:It should by ceoyoyo · · Score: 0

      I understand that. My point is that when he makes jumps as I described, he's inviting people to assume there's a reason. Presumably Linux has influence over the version numbering.

      If you go from 4.9 to 5.0, that's just a .1 bump. If you go from 4.17 to 5.0, it implies there's a reason why you changed the big number instead of the little one.

    11. Re:It should by Anonymous Coward · · Score: 0

      Didn't Windows essentially copy Ubuntu's numbering?, and release cadence. E.g. currently we're on Windows 1709, and it will be followed by 1803 or something.

      Although in the terminal the "ver" command gives something else. If there's a byte for major and a byte for minor, then these are frozen to the 10.0 number and for the real versions numbers they use something else!
      1709 is the user facing version is winver but another version number is : 16299.371
      In the console it's 10.0.16299.371 and in winver the 10.0. prefix is left out.

      If they can afford a 16299 or a 371 there's no need to worry about a 256 or 255. It's smaller than either.

    12. Re:It should by jwhyche · · Score: 2

      Well then he should just drop the numbering plan all together. We should name kernel releases after porn stars. Cindy, Tammy, Candy....

      --
      I read at +2. If your post doesn't reach that level I will not see or respond to it.
    13. Re:It should by bakes · · Score: 1

      Good plan, although unlike numerics with this system not everyone knows in which order they come.

      --
      Ho! Haha! Guard! Turn! Parry! Dodge! Spin! Ha! Thrust!
    14. Re: It should by Anonymous Coward · · Score: 0

      Unix epoch timestamps.

      I vote we move to using Unix Epoch Timestamps for version numbers.

      It will be calculated based on the last commit time to the repo.

    15. Re: It should by Anonymous Coward · · Score: 0

      Alphabetical...

      Amber, Barbie, Candy, Denise, Ember, Francine, Ginger, Heidi, Ivanka, Julie, Kimberly, Lamborgini, Melissa, Nadia, Orgasm, Priscilla, Quinoa, Rebecca, Sandy, Tequilla, Uvula, Vanessa, Wendy, Xaiya, Yellow, Zimber

    16. Re:It should by q4Fry · · Score: 1

      Cheeky bugger ;-)

      You might even say he's a git.

    17. Re:It should by Anonymous Coward · · Score: 0

      Linux' ABI changes all of the time. They assume you recompile. I'm not sure version 200.x would help any more than arbitrary version changes.

  5. What's in a number, what's in a name? by Opportunist · · Score: 2

    People put way to much emphasis on labels. While you might expect to break more compatibility on a major number than on a minor, i.e. I'd probably be more wary to install a 5.0 than a 4.22, it's been shown time and time again that it doesn't really matter. Why the urge to have a major number anyway? I'd be calling it 5.0 if something huge changed.

    With most software it's mostly a marketing game. We change major numbers so we can charge you again. But with the transition to SaaS, this practice will even change for CSS, why FOSS felt the urge to play the game in the first place is beyond me.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    1. Re:What's in a number, what's in a name? by the_saint1138 · · Score: 5, Insightful

      Many version numbers in software are meaningful.

      If anyone depends on your software, then using major/minor/patch version numbers to distinguish which changes are backwards incompatible, feature additions, and bug fixes is very helpful to those downstream. See https://semver.org/

    2. Re:What's in a number, what's in a name? by Major+Blud · · Score: 1

      Indeed. It's rumored that Microsoft skipped Windows 9 because of potential compatibility issues.
      https://www.informationweek.co...?

      --
      If you post as Anonymous Coward, don't expect a reply.
    3. Re:What's in a number, what's in a name? by nine-times · · Score: 1

      Yeah, I don't think software version numbers are necessarily (or should be) meaningless. However, I think it's true that version numbers are arbitrary. Maybe that's what Torvalds meant.

      It may not seem like much of a distinction, but the point is that developers can number their software any way that they like. The actual numbers are not objectively an indicator of anything. If the developer has no reason for the number they've chosen, then the version number has no meaning. However, if they have a reason, then that reason becomes the meaning of the new version number.

    4. Re:What's in a number, what's in a name? by Opportunist · · Score: 1

      That's no rumor, that's the reason. Many install scripts (and other programs) didn't bother looking for "Windows 95 || Windows 98" but were just looking for "Windows 9", because whether it's 5 or 8 after the 9 didn't matter. That's all that could have happened after the 9.

      All these programs and scripts would break in Windows 9.

      Another reason was that MS learned that people wisened up and knew that only every OTHER version of Windows was actually usable, so they tried to trick people into thinking that 10 is the usable one. Didn't work so well, people knew that 9 would have been the usable one (after Win 7 and the tiled atrocity Win 8 was, Win 9 would have been the "good" one).

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    5. Re:What's in a number, what's in a name? by Junta · · Score: 1

      He simply meant that for the linux kernel, the version numbers after 2.6 are meaningless except to say x is newer than y. It's just how they chose to do it. He is not making some grand statement about version numbers in general, it's just the particular approach they do for the kernel.

      The kernel is well enough known, does a lot of different things, and wrapped by other organizations that it can be one of the 'special snowflakes' and not really be a big part of the whole 'versioning' philosophy.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    6. Re:What's in a number, what's in a name? by Junta · · Score: 1

      Versions are a way of conveying information. For simplistic and/or obscure projects, adherence to general rules of thumb help people know how to interact with your software.

      For the kernel, well, they are special and for them torturing themselves over whether a particular interval has something that *means* x or y or z changes in an x.y.z version is a waste of time. For them, the direct technical stakeholders have a much more nuanced understanding of how it develops than any version number could possibly convey. For the lay man, there is no kernel version, there is 'RedHat 7' or 'Ubuntu 17.10', the kernel version is some obscure detail they don't bother with.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    7. Re:What's in a number, what's in a name? by Anonymous Coward · · Score: 0

      Why would the naming of it being 10 vs 9 mean the every other version doesn't apply? Windows version have rarely had a consistent naming convention.

    8. Re:What's in a number, what's in a name? by jawtheshark · · Score: 1
      ... that and OS X (ten) envy.

      I personally think the (very improbably) reason that in German "Windows Nine" would sound like "Windows NEIN!" or, well, "Windows NO!", and thus causing failure in the German market was the best explanation ;-)

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    9. Re:What's in a number, what's in a name? by AmiMoJo · · Score: 1

      A company I worked at had to change version numbering from two decimal places to one, because another company stripped tailing zeros when displaying our firmware version and people thought that V2.9 was older than V2.52... Because 9 is less than 52.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    10. Re:What's in a number, what's in a name? by Opportunist · · Score: 1

      This would've been the moment for me where version 2.91 follows 2.89, with the patchnotes reading "2.90: Patch skipped because company (name) is too stupid to display it correctly".

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    11. Re:What's in a number, what's in a name? by Anonymous Coward · · Score: 0

      I just shrugged, Windows 8.1 was version 9. And with Windows X, it's Windows 8.2.

      8.1 -> 8 + 1 = 9
      8.2 -> 8 + 2 = 10

    12. Re: What's in a number, what's in a name? by dunkelfalke · · Score: 1

      Germans simply would say Windows neun.

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    13. Re: What's in a number, what's in a name? by jawtheshark · · Score: 1

      I know. I actually know German. It ruins the joke though.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    14. Re: What's in a number, what's in a name? by Anonymous Coward · · Score: 0
    15. Re: What's in a number, what's in a name? by jawtheshark · · Score: 1

      I always have to watch those with sound disabled, because I understand German and the subtitle/sound mismatch makes it hard to follow.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    16. Re:What's in a number, what's in a name? by r3jjs · · Score: 1

      I *DO* this!

      Its for a rather small open source project with less than 100 users, but yea, I screwed up on the version number code and now its kind of a baked in mis-feature.

  6. Linux 5.0: SystemD Strikes Back by Anonymous Coward · · Score: 0

    systemD is pissed and it's not going to take it anymore

  7. Re:I can haz frist post! by Anonymous Coward · · Score: 5, Insightful

    Once Linus is no longer maintaining the kernel (or has died), you will miss him more than you miss Steve Jobs.

  8. nonsense by Anonymous Coward · · Score: 1

    I still have high hopes that 5.0 brings windows subsystem support

    1. Re:nonsense by Anonymous Coward · · Score: 1

      Doesn't SystemD do this?

    2. Re:nonsense by Anonymous Coward · · Score: 0

      touche!

    3. Re:nonsense by iggymanz · · Score: 1

      I heard there was talk to make it run Linux well too after that

  9. Its more meaningful to use the year.month.day by Anonymous Coward · · Score: 1

    2018.4.17 would be a much more useful over version numbers as consumers would know how old their IoT devices actually are.

    Year of linux desktop should be more like 1995.4.17 for gnome, kde, xfce to indicate how far behind they are when comparined to windows and macs.

    1. Re:Its more meaningful to use the year.month.day by AvitarX · · Score: 1

      Do you add another .x for bugfixes and keep the old release date?

      It seems using strictly dates could get real messy.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    2. Re: Its more meaningful to use the year.month.day by Anonymous Coward · · Score: 0

      Call that a minor release with is own separate year.month.date.

    3. Re: Its more meaningful to use the year.month.day by AvitarX · · Score: 1

      Sure, but then one needs a look up table to know what's what.

      20180101 is the Long Term Release.
      20180515 is the new update
      20180613 is the bug/security update to 20180101 with none of the features of 20180515

      etc. etc.

      That sounds like a mess.

      there are 3 numbers, the meaningless first, the feature explaining second (the 2 combined really), and the fix number for that.

      if they just went to a single number, it would be hard to keep it sorted out as a user. am I downloading 4.17.0 equivalent, or 4.16.2 equivalent?

      the date alone doesn't help.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  10. Headline fail by QuietLagoon · · Score: 1

    It is not the kernel that is meaningless, but the concept of version numbers that he says is meaningless.

    1. Re:Headline fail by Anonymous Coward · · Score: 0

      Nah that headline is completely correct.

  11. Everybody Does It by Anonymous Coward · · Score: 0

    Everybody avoid the x.0 versions, which are suspected of having bugs. Now even Linus says a x.0 version is meaningless. Poor x.0 versions. Their social isolation must be killing them.

  12. Version numbers are not meaningless by Anonymous Coward · · Score: 1

    Version numbers are a very broadly understood proxy for communicating risks associated with change to your users.

    The fact some have elected to fuck up version numbers for financial gain and politics shows version numbers are in fact not meaningless. As a user I would much prefer Linus et al stop playing games with version numbering. Often people working a project develop a project centric mindset that does not extent to the thinking or value propositions of users.

    You think everyone has the time to rummage through change histories to understand the level of risk associated with updating any of a zillion different packages? We don't. There is no benefit to anyone in needlessly trying to make the situation worse.

  13. Not meaningless by Anonymous Coward · · Score: 0

    Linux 5.0 will be evidence that Sun Microsystems marketers have joined the kernel team.

    1. Re:not meaningless by Anonymous Coward · · Score: 0

      WhaaaaT? You don't want marshmellow finger in your brain?! Weirdo.

    2. Re:not meaningless by Anonymous Coward · · Score: 0

      While linux can also stay on 4.47, 4.89 etc. naming scheme forever it might also get confusing, or just mental noise from a big number.
      Is 4.5 newer or older than 4.47?, is 4.51 slightly newer than 4.5?, what is 4.101?

      It's good that Linux Torvalds is also able to bypass a superfluous debate or explanation about this.

  14. Look, we all know where this is going by johannesg · · Score: 3, Funny

    As demonstrated by both Apple (with their OS X, but no OS XI) and Microsoft (with their Windows 10, but no Windows 11), ten is just the highest number an OS can have. Linus is just preparing for the day when Linux, too, reaches its final version number.

    1. Re:Look, we all know where this is going by Anonymous Coward · · Score: 0

      LinuX

      One OS to rule them all.

    2. Re:Look, we all know where this is going by Anonymous Coward · · Score: 0
    3. Re:Look, we all know where this is going by Anonymous Coward · · Score: 0

      ten is just the highest number an OS can have

      Are you deliberately trying to set up a Spinal Tap reference or what?

    4. Re:Look, we all know where this is going by thegarbz · · Score: 1

      This is Linus we are talking about. If there's one person in the world who realises he also has toes it's him. Apple and Microsoft may only be able to count to 10 but I expect Linux will go up to 20.

    5. Re:Look, we all know where this is going by jwhyche · · Score: 2

      21 if he is in the shower.....

      --
      I read at +2. If your post doesn't reach that level I will not see or respond to it.
    6. Re:Look, we all know where this is going by Anonymous Coward · · Score: 0

      5.0 isn't even it's final form hwuahahahahaha!

  15. self-contradictory by Anonymous Coward · · Score: 0

    If it was meaningless, he wouldn't want to do it.

    What he really means is please don't yell at me. I should have the right to do this.

  16. semantic versioning by ooloorie · · Score: 5, Insightful

    This is how Semantic Versioning ought to work:

    Given a version number MAJOR.MINOR.PATCH, increment the:

    MAJOR version when you make incompatible API changes,
    MINOR version when you add functionality in a backwards-compatible manner, and
    PATCH version when you make backwards-compatible bug fixes.
    Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

    So, while Linux kernel version numbers may be meaningless, it would perhaps be better if they were actually meaningful.

    1. Re:semantic versioning by amorsen · · Score: 2

      It's the kernel. You can't do incompatible API changes. Does that mean Linux should be on version 1.387.4?

      --
      Finally! A year of moderation! Ready for 2019?
    2. Re:semantic versioning by Anonymous Coward · · Score: 2, Insightful

      Linux kernel historically has had no API/ABI stability at all and Linus actively opposes any such concept. For a good reason too, we wouln't want to end up like Windows with their backwards compatibility baggage. On the other hand that means it's really hard to support hardware in any other way than having it in the kernel itself - just ask nVidia how their closed driver efforts are going when a new kernel/x.org versions arrive.

    3. Re:semantic versioning by drinkypoo · · Score: 1

      Historically, major versions are for major feature set changes. They don't have to break backwards compatibility. Sometimes they even correspond to complete rewrites, and it's hard to argue that's not useful.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    4. Re:semantic versioning by ooloorie · · Score: 1

      It's the kernel. You can't do incompatible API changes. Does that mean Linux should be on version 1.387.4?

      Sure you can, happens all the time, both with Linux and with other kernels. For Linux, those changes have simply been so haphazard that the rest of the Linux ecosystem assumes little and tries to compensate for them.

    5. Re:semantic versioning by Anonymous Coward · · Score: 0

      It can be arged that no project should do incompatible API changes, either. If your want to break APIs a simpler and clearer way is to think of a new name and start fresh.

    6. Re:semantic versioning by Anonymous Coward · · Score: 0

      Erm, hey chief? Are you 100% sure that you meant to include ABI in your statement? Because I could find some Linus stuff on LKML that would seem to indicate otherwise ...

    7. Re:semantic versioning by Anonymous Coward · · Score: 0

      Userspace ABIs don't generally change ("We don't break userspace!!11"), but in-kernel ones change all the time.

    8. Re:semantic versioning by Anonymous Coward · · Score: 0

      Linux kernel historically has had no API/ABI stability at all and Linus actively opposes any such concept

      The user space API/ABI is fixed and you can bet Linus will be pissed at any attempt to break backwards compatibility without very good reason. Breaking changes on internal APIs however are fair game and necessary to improve the kernel.

      we wouln't want to end up like Windows with their backwards compatibility baggage.

      Windows isn't backwards compatible with kernel internal APIs either, they just tend to be fixed for one or more Windows releases. Half the cheap hardware I have lying around requires Windows XP and the manufacturers would rather get annother $30 for each replacement than write Windows Vista/7/8/10 drivers for free.

    9. Re:semantic versioning by amorsen · · Score: 2

      This is completely wrong. The Linux kernel API/ABI is utterly stable. You can install one of the first distributions, switch the kernel to 4.x, and things will work just fine.

      You may have to enable a.out support though.

      --
      Finally! A year of moderation! Ready for 2019?
    10. Re:semantic versioning by thegarbz · · Score: 1

      it would perhaps be better if they were actually meaningful.

      It is meaningful in its meaninglessness. The semantic versioning system assumes that you make software in a way that breaks functionality frequently or that you roll out bug fixes at a different cadence to feature improvements. The Linux kernel hasn't been maintained like that in a long time.

    11. Re:semantic versioning by Anonymous Coward · · Score: 0

      It's not wrong, it's inaccurate. GP means the in-kernel APIs being without stability guarantees and that is correct. You can't take an out-of-tree module written for kernel 2.x and expect it to work with 4.x. It might, but probably won't. This is the reason of the GP's example - nVidia binary blob often breaks between kernel releases because it's building out-of-tree modules that consume in-kernel APIs.

      You are talking about userspace API/ABI and those are indeed stable, though I doubt getting an old distro being driven by a modern kernel is as simple as you describe.

    12. Re:semantic versioning by ooloorie · · Score: 1

      The semantic versioning system assumes that you make software in a way that breaks functionality frequently

      Where does it assume that?

      or that you roll out bug fixes at a different cadence to feature improvements

      And the problem with that is...?

      The Linux kernel hasn't been maintained like that in a long time.

      Indeed! Probably because Linus thinks that a lot of standard software engineering "is meaningless".

    13. Re:semantic versioning by Anonymous Coward · · Score: 0

      They are actually meaningless as in "we drop Power4 support, we enable GCN support by default and this will be the first release that will let you mine unpatched with newer AMD hardware". Linus does not want to be forced to meaningful version numbers in future, but he's clearly aware that it's easier to remeber "5.0" as "the modern linux", instead of "4.17".

    14. Re:semantic versioning by thegarbz · · Score: 1

      Where does it assume that?

      Right in the major version number.

      And the problem with that is...?

      Version numbering ceases making sense when you classify it according to bug fix / feature improvement but don't have a development cadence that incorporates standard fixes and maintenance fixes. When every fix involves both bux fixes and feature improvements then the entire premise of the versioning system you promote falls apart. You may as well just Start at 1.0 and then increase the decimal point at every commit. Which version of Linux are you running? 1.123512345 or the 1.123512358?

      Indeed! Probably because Linus thinks that a lot of standard software engineering "is meaningless".

      And? To be clear you are proposing changing the approach taken by one of the worlds most expensive and longest ongoing software projects. When Linus says something it no longer is an appeal to authority fallacy, it is the actual authority. You are going to have to come up with a much better justification than *it doesn't follow this system* in light of its current success.

    15. Re:semantic versioning by ooloorie · · Score: 1

      Right in the major version number.

      Where in the major version number does it say that you "break functionality frequently"? Lots of software projects increment their major version number very infrequently.

      And? To be clear you are proposing changing the approach taken by one of the worlds most expensive and longest ongoing software projects.

      No, I'm simply saying that people should remember that version numbers are not meaningless, it is only Linux kernel version numbers that are meaningless because Linus happens to choose meaningless version numbers.

    16. Re:semantic versioning by thegarbz · · Score: 1

      Where in the major version number does it say that you "break functionality frequently"?

      Dunno I was quoting you with your incompatible API changes. Maybe you were wrong.

      No, I'm simply saying that people should remember that version numbers are not meaningless

      They aren't. They form a logical sequence of releases. But the specific versioning system you proposed is meaningless to the development process of the Linux kernel. Maybe you don't understand Linus's comment because you don't understand the kernel development. I tried to explain it to you but you either didn't read it or willfully ignored it choosing instead to just repeat your original reply without addressing any subsequent part of the discussion. To quote an unlikely president: "SAD."

    17. Re:semantic versioning by ooloorie · · Score: 1

      Dunno I was quoting you with your incompatible API changes. Maybe you were wrong.

      I simply stated that version numbers are meaningful and that major version number changes indicate API changes. How does that imply that a project "breaks functionality frequently"?

      But the specific versioning system you proposed is meaningless to the development process of the Linux kernel.

      I wasn't making a comment about the Linux kernel, I was making a comment about version numbers in general.

      I tried to explain it to you but you either didn't read it or willfully ignored it

      You responded to points that you imagined, not to points that I actually made. Learn to read.

  17. "Go" semantic? That is/was the whole point of vers by Anonymous Coward · · Score: 0

    The entire damn point of version numbers is, always was, and likely always will be, that they *tell* you useful information about the changes!

    Those changes are
    * Build number: Unique identification. Optional.
    * Bug fix version: No new features. Just bugs fixed. Optional.
    * Minor version: Format-compatible feature additions. Files, packets, plugin APIs, etc are all guaranteed to work.
    * Major version: Big, feature-breaking changes. Compatibility might be available, but it might require importing, etc.
    * Series: This is the same as the number in movie titles. Usually it means a complete rewrite and an entirely new thing. An example would be, when Opera switched the engine. It could have been called "Opera II 1.0". Sometimes confusing, and obviously optional. Usually a new name is chosen.

    I don't know when the meme of calling that "semantic" came up, but it is like calling a day that does not have a solar eclipse a "sunlit" day. (Or like saying a(-)theist instead of just "normal", for you Europeans.)

    This is how I learned it in the late 80s and 90s, this is how it still is ... in sane land (the tiny leftover enclave).

  18. It matters in other contexts by Anonymous Coward · · Score: 0

    For the software I work on, it matters a lot: Consider Version number A.B.C.D:

    A: Major Version: Breaks backwards comparability from previous version. Don't deploy without careful integration testing.
    B: Minor Version: Introduces a new feature. Functional tests are enough.
    C: Hotfix: Fixes a bug. Unit tests OK.
    D: Build number: Used to allow the automatic deploy scripts to fetch the right version out of the CI. Not strictly needed.

    See http://semver.org.

    For our software, it's essential. It is what signals to my colleagues how closely they need to monitor a version I am working on... or when they will be able to deploy a feature that depends on a feature in my software... and so on.

    But for a Kernel, which is doing a rolling release, which is dropping support for something or other every other week, this makes no sense. You have to pick the label that makes sense for you.

  19. Version numbers are NOT meaningless by EmagGeek · · Score: 1

    At least, they are not supposed to be. Version numbering, particularly decimal-delimited versioning, was originally intended to communicate concisely the level of risk involved with the change from the prior version, with each field, progressing left to right, representing less risk.

    For example:

    2.4.12 -> 2.4.13 ~= Little risk involving a low degree of time and expense managing integration failures and customer blowback. Often these changes can be rolled out in production with little or even no integration testing beforehand

    2.4.x -> 2.5.x ~= Moderate risk involving a significant degree of time and expense, customers should plan on offline integration testing on a snapshot before deployment

    2.x.x -> 3.x.x =~ Major risk involving significant changes in process or procedure, significant changes in data handling. May require significant software retooling by the customer, and certainly requires significant integration testing, software development, or capital outlay before deployment.

    Today, this helpful, informative approach has morphed into a marketing tool... sad!

  20. Yeah by SurenEnfiajyan · · Score: 1

    Considering how poor QA and regression testing Linux kernel gets even x.y.z is meaningless unless we are talking about the kernels maintained by Red Hat and Google.

    1. Re:Yeah by Anonymous Coward · · Score: 0

      > kernel maintained by google is well tested
      Hahahahahahahaaha, that's a good one.
      Have you looked at their code?
      And their "commit messages" are simply the best.
      "fixed something"
      "fixed indention" on a commit that actually fixes a bug.
      The only thing they do is backport patches from upstream and maintain their proprietary drivers.
      Sometimes they fix things in stupid ways because they don't understand the code and upstream didn't do it yet.

    2. Re:Yeah by SurenEnfiajyan · · Score: 1

      "fixed something"
      "fixed indention" on a commit that actually fixes a bug.

      At least they fix things which are mostly not fixed in the mainline kernel.

      The only thing they do is backport patches from upstream and maintain their proprietary drivers.
      Sometimes they fix things in stupid ways because they don't understand the code and upstream didn't do it yet.

      Don't worry, even core Linux developers don't understand what they are doing which has many unpleasant effects. Examples? The broken IO since 3.x (see bug 12309). revoke() is still not there which means that file descriptors and network sockets cannot be forcibly closed and without unmounting them it leads to stale mount points, which can then cause oopses and even kernel panics (bug 14505), the fix requires rewriting the half of the kernel, but who is gonna do that? In many BSD's this feature is implemented. Broken thread priority. There's also no concept of backward compatibility. And so on... This is what happens when there's no interest towards consumers. And Google is in process of switching to its homegrown Zircon.

  21. Interesting Linux dropping old hardware support by Anonymous Coward · · Score: 0

    When you think of Linux desktop, you tend to think of end users installing it on older hardware to eek out a few more months or years of use. Sort of disappointed to read some older hardware won't be supported anymore. Given that Linux desktop isn't exactly setting the world on fire in users. I wonder why you would do this to users of older hardware? I get Linux needs to start streamlining and losing some bulk because its losing the efficiency battle with Windows as well as Chrome OS and Mac OS.

    1. Re:Interesting Linux dropping old hardware support by zekica · · Score: 1

      The architectures removed are not used in mainstream computers - they are mainly used in signal processing or other embedded CPUs with low number of users.

    2. Re:Interesting Linux dropping old hardware support by SurenEnfiajyan · · Score: 1

      Unfortunately and mildly saying, Linux is a second class citizen on the desktop (initially Torvalds wanted to be so but it failed), more than 97% of the investments are going to servers, embedded and HPC (high performance computing). Nobody cares. Except maybe Google who has enough resources to create an alternative desktop OS.

    3. Re:Interesting Linux dropping old hardware support by iggymanz · · Score: 1

      you're being silly. the discontinued CPU aren't what are used in PC, look them up and in what kind of devices they are used.

    4. Re:Interesting Linux dropping old hardware support by Eravnrekaree · · Score: 1

      What good should do is merge android and chrome browser as app platforms, and allow apps to be installed in a container inside chrome, the app would be installed into a sandbox and could have access to its own files and nothing else, unless the user manually shares files with it, apps would of course be distributed as Webassembly and use DOM APIs, WebGL, HTML5 Video, etc, JIT for native speed. Apps could be installed through an app store. This is different from an extension becuase a Chrome app would not have any access to web pages, its not a browser extension. This would allow developers to target chrome as their primary platform, allowing apps to run on Windows. Linux, Android, Apple, etc etc. It would allow apps to be installed on the hard drive (within sandbox) and used without internet access and documents to be stored locally (inside a sandbox directory). An app could be started even from command like with google-chrome app://appname. This is better than YAIOS (Yet Another Incompatible OS) by allowing a common app platform between current OSs. 99% of the code is already in the browser for all this

    5. Re:Interesting Linux dropping old hardware support by Anonymous Coward · · Score: 0

      The main reason I don't really like this idea is this story : install Firefox 59, on Windows (so everything from hardware H264 decoding to WebGL ought to work, maybe). Try to run Google Earth, it tells you to fuck off and download Chrome.
      This reminds me of Microsoft UWP that's "Universal Windows P-something" that only runs in Windows 10, not 7 or 8 or Wine or gasp, non-Windows platforms.

      Adobe Flash was one of the high points of "run anywhere universal binary". It was better than HTML5 for video games etc., because it ran the same on any browser (tho limited to supported platforms, so linux on x86 and solaris on sparc etc,. not linux on sparc nor solaris on x86..). The common theme with the others? Flash is universal but only runs on Flash.

      Now don't get me wrong I think I like your idea, even for vid games (perfect for graphical adventures like in the 1990s CD-ROM days, etc.)
      I just would like it if it ran on Firefox (or Edge, even if I will never use it). Feature request : if you're making some super duper web app even just a traditional on-line one please make sure it'll run on Firefox 60 ESR. If Firefox 60 ESR doesn't support bluetooth fish rods or quadroscopic cameras, that's too bad, but maybe requiring those things can wait for a year.

      Too bad FirefoxOS was not successful - a few months late on FirefoxOS 2.x, and the cancelled ZTE 5" phone launch killed it permanently. There also was no 7" low end tablet : a large omission, for a system that targeted non-smartphone users / first time touch screen users and people who can't afford to buy 3G service.
      Then, not building a DESKTOP version after the former were done, which millions people might have used on junky ARM netbooks and old computers!

  22. Moving away from point releases by IGnatius+T+Foobar · · Score: 2

    Isn't the whole world moving away from point releases? Perhaps the Linux kernel still needs development and stable tracks, but the whole idea of a "major release" followed by a bunch of "point releases" is an artifact of the days when software came in a box with a CD in it, or (for us old greybeards) on a magnetic tape. Rolling releases with whole numbers (like 50123 rather than 5.0.123) are where it's all going now.

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
    1. Re:Moving away from point releases by Njovich · · Score: 0

      Isn't the whole world moving away from point releases?

      Not really. I would say that atrocities such as Semver have made point releases more popular than ever. You aren't wrong about rolling releases with whole numbers being popular too though.

    2. Re:Moving away from point releases by Anonymous Coward · · Score: 0

      Chrome and later Firefox's versions are the ultimate atrocity. They took years to get to 1.0 and then 2.0, they go from 57 to 58 to 59 in a few months, but is there the same type of testing? Are there enough new features to release a major version?

    3. Re:Moving away from point releases by Anonymous Coward · · Score: 0

      Point releases are still needed because unlike most crapware being sold these days the linux kernel actually has several long term support versions that need to keep track of the patch number. The major version number is kind of pointless for the kernel at this point though.

  23. It could by Anonymous Coward · · Score: 0

    That's fine, but the version numbers should mean *something* I think bumping the major when the ABI breaks would be helpful.

    Otherwise bump the version yearly, or when some arbitrary goal is met, or something.

  24. That's the problem right there! by Anonymous Coward · · Score: 0

    It has become a jack of all trades. Spaghetti code's structural mother.

    It should be cut into modules and aspects which actually can progress like that.
    This would also make custom kernels easier.
    But of course it would require proper stable APIs. The one thing Linux never managed to have, and where it was misdesigned from the very start according to Linus, from what I've been told.

    Of course, while microkernels are apparently the obvious better choice, as they are everyone's theoretical wet dream, everyone who tried them realized that the waste due to the tight intetfaces between modues is too big, and that they hence will always be too inefficient.

    1. Re:That's the problem right there! by Junta · · Score: 1

      Interestingly enough, it's more like a 'master of all trades'. The reality is that while there are some unique needs for a phone versus a desktop versus embedded networking equipment versus a server, they also have a lot in common (the general concept of organizing codes into 'processes' and 'threads'). Also, we are deeply in a world where purpose-built hardware has to a large extent given way to generics (nowadays it's more likely your cell phone signal is handled by SDR on servers in the tower than a hardware raidio).

      From various people I've talked to, academically it seems that by all rights the kernel *should* have to be carved up to be productive in managing the project. In actual practice however, it seems to work better than one would think it should work.

      I don't think it would make custom kernels easier, but it could greatly alleviate the complexity associated with installing third party drivers. On the other hand this might be viewed as a feature. Because out-of-tree drivers were so challenging to do, almost all the significant companies ultimately relented and enabled open source drivers for their equipment rather than fight the nightmare of supporting binary kernel modules. If Linux from the get go had very long lived and very stable driver ABI, we wouldn't have nearly as ubiquitous open source driver support as we do.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    2. Re:That's the problem right there! by Anonymous Coward · · Score: 0

      When it comes to programming, there are very few "trades". Most of programming has very little to do with knowledge or experience and mostly to do with abstract thinking and reasoning. Anyone can practice these on their own with no access to anything but their own thoughts. Reasoning skills and metacognition are nearly perfectly correlated. There seems to be a circular dependency and strengthening one strengthens the other. Shows up as an exponential progression in ability up to some individual human limit.

      According to psychology, masters in cognitively hard disciples tend to have little experience, to the point that there's an inverse relation between experience and mastery. Master programmers are seemingly masters at all technical aspects of programming or become a master in weeks or months. Once you've mastered reasoning, all forms of reasoning are easy to pick up. Masters also tend to be bored quickly, leading to them jumping around, mastering new subjects. The more you master, the easier it becomes to master something new.

      This only applies to the reasoning aspect. There are merits to experience in that someone with experience can do something quickly, as long as it's something they've been trained to do and assuming they do the right thing. Programming is littered with people using the wrong tool, not knowing what they don't know. Part of the definition of metacognition is knowing what you don't know.

  25. Re:He's Right by hduff · · Score: 2

    Linux itself is quite meaningless. Tacking on a version number doesn't change much.

    Give me a proper Windows system any day.

    The problem there is that a Windows system that is secure and stable is difficult to find. Soon , the windows OS itself will be a subscription product, locking you in to a new version of the walled garden.

    --
    "I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
  26. Re: He's Right by Anonymous Coward · · Score: 0

    You are so increadibly dumb and incompetent it literally hurts me.

  27. The numbers are not meaningless by Waffle+Iron · · Score: 1

    In particular, a legitimate "5.0" release really needs to be a "GT" version, and should include sport suspension, an aero package, 21-inch wheels, and Brembo brakes.

    1. Re:The numbers are not meaningless by Anonymous Coward · · Score: 0

      aero kits don't age well.

  28. Re:He's Right by DontBeAMoran · · Score: 2

    Windows is great for games.
    macOS is great for desktops.
    Linux is great for servers.

    --
    #DeleteFacebook
  29. Good opertunity for positive press by Anonymous Coward · · Score: 1

    Version numbers are pretty meaningless, but it does mean you can generate some news. Write up a big press release about all the changes since version 4.0, stick in some stats about how many computers are running linux and you might get into the mainstream press.

  30. Re:He's Right by bjwest · · Score: 1

    macOS is great for desktops.

    For those who can afford it I guess it's OK, but I can (and do) build a system much more powerful and install Linux on it for the price of a Mac desktop. Probably closer to half the price of a Mac, but I haven't priced one lately.

    --

    --- Keep the choice with the user..
  31. He should increase it to version 26.0 by Anonymous Coward · · Score: 0

    The first release on or after September 17th should be 26.0 this year and increasing every year thereafter. So the first 2019 release on or after September 17th would be version 27.0.

    1. Re: He should increase it to version 26.0 by Anonymous Coward · · Score: 0

      Actually, Increase those numbers by 1.

    2. Re: He should increase it to version 26.0 by Anonymous Coward · · Score: 0

      Actually, increment them by 5 +-(0,5-3)

  32. Skip 5.0. Go straight to 6.0 by Anonymous Coward · · Score: 0

    Linus should do that, just because he's Linus. No reason necessary. He's the decider. If he says it, everyone will line up behind to to agree. Anyone who disagrees he will call a perkeleen vittupää. Because he can.

  33. Here is my version by Provocateur · · Score: 1

    Five dot oh: complete with systemd.

    The red pill: Back to the way it once was. Meaning less trouble.

    --
    WARNING: Smartphones have side effects--most of them undocumented.
  34. Numbers are fine. by bjwest · · Score: 1

    Keep them going in an ever increasing direction, and any numbering scheme will be fine. Just don't go with the Asinine Asshole method Ubuntu's doing (and Android). Numbers are easy to remember and keep in order, artsy-fartsy naming conventions are harder to keep up with.

    --

    --- Keep the choice with the user..
  35. Re:He's Right by Joce640k · · Score: 1

    And ... Linux for servers was a solved problem a decade ago.

    I guess this is the real reason why incrementing the Linux version number is irrelevant.

    --
    No sig today...
  36. Linus already not that "active" ... by drnb · · Score: 1

    Once Linus is no longer maintaining the kernel (or has died), you will miss him more than you miss Steve Jobs.

    Why? Hadn't Linus dropped off the top contributor list long ago? We are already well past the point where Linux development is done, or guided, by hobbyists; development is now dominated, and guided, by corporations.

    Linus is more of an administrator in the development process, approving changes more than making changes. The corporations could easily supply someone for that role too.

    Linus would be missed as a spokesperson, a figurehead, an occasional source of humor (ex. comments when irritated), but for day-to-day work he is completely replaceable. And being completely replaceable means he did his job correctly and his project will be healthy without him.

    1. Re:Linus already not that "active" ... by dabadab · · Score: 2

      Hadn't Linus dropped off the top contributor list long ago?

      Yes. And Steve Jobs was never the Employee of the Month at the Foxconn factory where the iPhones are actually made. But that doesn't matter.
      It's still Linus who ultimately decides what is and what is not accepted into the kernel (either directly or by delegating it to people he personally trusts) and makes the major decision regarding where the kernel is headed and that's the thing that actually matters not writing a few hundred lines of code to support a new wi-fi chip.

      --
      Real life is overrated.
    2. Re:Linus already not that "active" ... by drnb · · Score: 1

      So he's largely delegating on the kernel administrative side too. Again, he seems easily replaced for non-spokesperson non-figurehead roles. Which, again, indicates he did his job well.

    3. Re: Linus already not that "active" ... by Anonymous Coward · · Score: 0

      yeah but it cannot be linux as he hold and defend that trademark

    4. Re: Linus already not that "active" ... by drnb · · Score: 1

      yeah but it cannot be linux as he hold and defend that trademark

      An heir will sell the trademark to Microsoft of Oracle. :-)

  37. not meaningless by Anonymous Coward · · Score: 1

    Version numbers are coherent. You instantly know where in the chain of evolution you are.

    I despise projects that use names instead... "marshmellow finger", "Toxic lake"... what does that even mean? That is not information I want to have to store in my brain.

    Version 5.0. I know exactly what that means and I am grateful for the simplicity.

  38. Re:He's Right by Joce640k · · Score: 2

    macOS is great for desktops.

    For those who can afford it I guess it's OK

    I don't see what's so special about it. As soon as you step outside of web/email/basic use then there's suddenly a great big hole compared to windows. Even basic stuff like text editors and FTP programs are completely lacking (show me the Mac equivalents of Notepad++ or WinSCP...)

    My guess is that Macbooks mostly sell because they look pretty compared to the $500 Windows laptops you see in most stores.

    My answer to that is to try spending $1500 on a windows laptop. You might find something equally pretty but a whole lot better built and much more useful.

    --
    No sig today...
  39. Major versions should break broken APIs by technosaurus · · Score: 2

    Now that there are really long term support versions, breaking compatibility in a major version is really not that big of a deal. Fix the memory manager so mmaped files can be unloaded on a low memory condition and generate a page fault as needed. Make the various compressed memory and file subsystems compatible with each other when using the same compression format (rather than de+re-compressing on each copy) simplify the video/gpu systems. Currently, if you run code deduplication software you will fill the disk. Simple things like struct definitions and syscall numbers vary unnecessarily across architectures. Each individual chunk of code is top notch, but overall it is shit.

  40. Actually it is time for microkernels by drnb · · Score: 1

    Of course, while microkernels are apparently the obvious better choice, as they are everyone's theoretical wet dream, everyone who tried them realized that the waste due to the tight intetfaces between modues is too big, and that they hence will always be too inefficient.

    With computer power so far beyond user demands, with so many layers in the software stack and/or application implemented with convenience rather than performance in mind, or implementation speed rather than execution speed if you prefer, the reduced performance of the light interfaces is rather insignificant overall. Greater reliability and security would outweigh such minor overall performance costs.

    1. Re:Actually it is time for microkernels by Junta · · Score: 1

      Certainly in some software and especially desktop software, the efficiency of communication between parts of the kernel is down in the noise. However there continue to be exceedingly latency sensitive scenarios where the developers have done the hard work to minimize every last little hit to performance. Of course this is taking the claim that micro kernel necessarily means a compromise on performnace at face value, which is not necessarily true.

      The Linux kernel is one of those things that seem to work better in practice than in theory in terms of reliability and security. Nothing is perfect, but their track record isn't too shabby and I'm not sure if a microkernel would fare better on the security half of things. Now one can rightfully argue that as a 'driver model' it's a very hostile environment for third-party modules and makes it impossible to have a distinct cadence for each component. For the former that bites people frequently, but the latter, in practice, works out better than it has any right to.

      --
      XML is like violence. If it doesn't solve the problem, use more.
  41. Re:"Go" semantic? That is/was the whole point of v by ConceptJunkie · · Score: 1

    Congratulations, AC. Your logical attitude will win you a one-way trip to the re-education camps. I'm sure I'll see you there. But I don't see what any of this has to do with Linux.

    --
    You are in a maze of twisty little passages, all alike.
  42. They are meaningful by Anonymous Coward · · Score: 0

    If they're odd numbered, then they are beta.

  43. Re: He's Right by Anonymous Coward · · Score: 0

    My windows laptop turned off has never crashed. Actually, I think it has blue screened a few time in standby. Lol.

  44. Re: He's Right by Anonymous Coward · · Score: 0

    Home Brew negro! Do you even lift

  45. Re:"Go" semantic? That is/was the whole point of v by Anonymous Coward · · Score: 0

    Congratulations, AC. Your logical attitude will win you a one-way trip to the re-education camps. I'm sure I'll see you there. But I don't see what any of this has to do with Linux.

    Same AC here. Thanks. The tie-in is that GPP mentioned the diminishing enclave of sane-land, and the whole topic was on the naming of things. Why debate the merits of one naming/versioning scheme over another? Why, because there is power in the use of language. Expectations and even norms come from using one term or number and not another. I mentioned George Orwell (Eric Arthur Blair) because he really understood this. It's what 1984's Newspeak was all about.

    It reminded me of all the other silly controversies we see all the time, mostly because people cannot act like adults. The whole LGBT thing is a prime example. It's filled with frothing-at-the-mouth types who think anyone disagreeing with them is pure evil. So there is one orthodoxy and many heresies. It's like we learned nothing from the Dark Ages. At least with kernel version numbering, the posts are a lot more reasonable. The posters are acknowledging the utility of having reasons for their stances. That much is refreshing.

  46. Re: "Go" semantic? That is/was the whole point of by Anonymous Coward · · Score: 0

    I hate them too. So so much. Changing normal to cis because that are a abnormal walking freakshow. Iâ(TM)ve never met a lesbian that didnâ(TM)t hate men, or themselves. A lesbian trying so hard and failing to mimic men, of who they hate so much. And a lesbian that did not to extreme violence on each other. They are dishonest and liars to their core being. And are extremely selfish to the point of having children, just so they can raise them corrupted to hate society and men and hate most of all the women âbreedersâ(TM).

    Almost all lesbians could disappear and would not be missed and would not have any impact on the world.

  47. Re:I can haz frist post! by Anonymous Coward · · Score: 0

    Doubtful. Saint Steve’s rotting cock is still the most amazing thing to shove in your ass. Even an iPhone X doesn’t feel as good when sliding up your poop shoot.

  48. Linux kernel lifecycle by satsuke · · Score: 1

    He's right, when we went from 0.98/1.0 to 2.0 kernel, there were entire suits of new hardware supported, kernel modules, many new features, to say nothing of breaking existing functionality for many things.

    20 years later and the major releases are functionally changing things only kernel programmers would care about.

    Not to diminish those contributions, but by this point it's more slow roll evolution and iteration.

  49. Re:He's Right by DontBeAMoran · · Score: 1
    --
    #DeleteFacebook
  50. Re:He's Right by Anonymous Coward · · Score: 0

    Linux itself is quite meaningless. Tacking on a version number doesn't change much.

    Give me a proper Windows system any day.

    I see someone is familiar with APK's work
    What is he at now, version Eleventy9^42!!!OMGWFTBBQ

  51. Re:He's Right by iggymanz · · Score: 0

    no, windows laptops are flimsy, mac laptops are robust and have incredible battery life. don't have to fart around with driver downloading either.

    windows and its hardware are an inferior world, I'm in both for laptops as my mac book pro is supplied by employer but at home my family and I have wintel laptops

  52. Re:He's Right by Tarlus · · Score: 1

    Even basic stuff like text editors and FTP programs are completely lacking (show me the Mac equivalents of Notepad++ or WinSCP...)

    Depending on what you mean by "equivalent"... Equally functional, or looks/feels the same?

    In either case, a lazy search in Google gives plenty of results.

    Atom or Sublime Text are popular text editors. Most developers I work with use one or the other. Notepadd++ is a useful program but I use it more for viewing and searching XML and JSON files, or things like firewall config files.

    FileZilla is cross platform and has been around for many years.

    Or you can always use vim or emacs and sftp in the terminal. Those are fast and reliable and are built in.

    --
    /* No Comment */
  53. No, The Windows/AppleOS model by Anonymous Coward · · Score: 0

    Linux X or as it will eventually be called, Linu(x^2)

  54. Legacy hardware by Anonymous Coward · · Score: 0

    "With the removal of old architecture and other bits of tidying up, with v4.17 RC1 there were more lines of code removed than added: something described as 'probably a first'."

    Does the Linux Foundation realize that a big feature of Linux is to be able to run on legacy hardware? Nothing in the kernel announcement explains that "obsolete" means "non-existent". If "obsolete" means "our bean counters don't care about your hardware any more", then the Linux Foundation runs the risk of forking Linux. Does systemd ring a bell?

    1. Re:Legacy hardware by Anonymous Coward · · Score: 0

      If you look at the list of CPU architectures : seem to be all unheard of, except "tile" which was the chips from Tilera I think.
      Perhaps we can find a slashdot user who worked on them (or perhaps they're the proverbial slashdot user who left long ago)
      Maybe it's companies that folded two years after launching their CPU, etc.
      Maybe there are very few users, or there are very few users and they use an RTOS/custom OS/no OS instead of running linux.
      Maybe the actual hardware mostly runs linux 2.6.16 etc. and five people in the world updated theirs, or run their stuff on FPGA or simulator.

  55. Re: He's Right by Anonymous Coward · · Score: 0

    It depends ... my MacBook Air 1st gen from 7 years ago still works great albeit having a rather tiny 256GB SSD drive.

    It drop it so many times I lost count until the corners are bent (drop from a high standing table) .... any yet it still works without a glitch.... only that Batt life is now half of what it used to be.

    Iâ(TM)ve gone through 3 windows laptops in that same timeframe. 2 Lenovos Thinkpads and Sony.

    But I heard the latest MacBooks are not as good as the ones from before which would really suck :(

  56. Re:He's Right by Anonymous Coward · · Score: 0

    Dell XPS 13/15 want to have a word with you. Compare apples to apples (pun intended) and not MacBook Pros to cheap Windows laptops.

  57. Enterprise vs Experimenters by Anonymous Coward · · Score: 0

    Version 5 tells Enterprise users to hold off for a while.
    Version 5 tells Experimenters to salivate.
    Maybe Linus wants some breathing room in the near future.

  58. Re:He's Right by iggymanz · · Score: 1

    we have a choice at work between those or mac books so we see the lifetime of hundreds. those Dell have MUCH more reliability problems

  59. Re:I can haz frist post! by Anonymous Coward · · Score: 1

    Once Linus is no longer maintaining the kernel (or has died), you will miss him more than you miss Steve Jobs.

    Steve Jobs would be alive today if only his doctors could have opened him up to fix him!

  60. Re:I can haz frist post! by Anonymous Coward · · Score: 0

    How would your mother feel if she knew you'd posted this?

  61. Deleting Code by scdeimos · · Score: 1

    Deleting code is my favourite software development activity, ever. Especially when all the tests are still green afterward.

    1. Re:Deleting Code by Anonymous Coward · · Score: 0

      Mod parent up. Deleting code usually means you are Doing It Right.

  62. Re:Why doesn't Linus bring on more POC? by Anonymous Coward · · Score: 0

    You know what the worst thing about shitheads like you who pollute every thread is?

    You're *boring*, *boring*, *boring*, same shit day after day, don't you ever get *bored* with posting it?

    No, you think you're being witty and clever *even though the same shit gets posted a million times*.

    Sad.

  63. Up next by easyTree · · Score: 1

    We go for three levels deep whilst reporting one of Linus' burps.

  64. What's wrong with semantic versioning? by Anonymous Coward · · Score: 0

    I like semantic versioning. It makes sense. I want it. It should be used for all software products.

    Rapidly incrementing integers (e.g. Chrome, Firefox) quickly lose all meaning. Humans need meaning.

    In short, I think you are wrong. Prove me wrong if you can.

  65. Version magnitude is meaningless by Anonymous Coward · · Score: 0

    Versioning is absolutely necessary and meaningful.

    But version magnitude (i.e. 5.0 vs. 4.0) is meaningless to Mr. Torvalds.

    He needs to get on the Oracle bandwagon and just do Linux 18.2 (as in 2018, second release) already. Then the perceived meaning of the first component (i.e. "5" of "5.0") is eradicated ("18" in "2018" just means the year, not that it's hugely better than 4.0).

  66. Fucking worthelsss "Journalists" again! by gerald.edward.butler · · Score: 0

    What the fuck! What is it with completely misleading, sensational "headlines". I've seen this troped all over the place. These so-called "journalist" should be taken out and have a bullet put in their brain pan. The world would be a better place if they were removed from it.

  67. Why bother by Anonymous Coward · · Score: 0

    Just start versioning it like browsers then.

  68. Re:I can haz frist post! by Anonymous Coward · · Score: 0

    She's be shocked he didn't know the difference between "shoot" and "chute".

  69. Re:"Go" semantic? That is/was the whole point of v by Anonymous Coward · · Score: 0

    Kernels generally should never have breaking changes in userland. Internally, kernels are already making breaking changes. Most "breaking" changes around kernel changes are not caused by the kernel, but by the frameworks an libraries that make use of new features in the new kernel.

  70. LINUX by razibraj · · Score: 1

    The present android operating system is derived from Linux.

  71. Re:"Go" semantic? That is/was the whole point of v by JustNiz · · Score: 1

    > It's filled with frothing-at-the-mouth types who think anyone disagreeing with them is pure evil.

    What you're describing is not coming from LGBT its coming from so-called liberalism, It just so happens that many (if not most) LGBTs are also liberals.