home.social

#laptops — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #laptops, aggregated by home.social.

  1. What will be closing end of 2026, early 2027:

    - #OriginPC
    - #Maingear
    - #FalconNorthwest
    - #iBuyPower
    - #CyberPowerPC
    - #NZXT

    What will dissapear or reduce operations (output or only high-end products) in 2027/2028:

    - #ASRock
    - #MSI
    - #Gigabyte
    - #Zotac
    - #TeamGroup
    - #PowerColor
    - #Palit
    - #Corsair

    #PC will become a luxury. Laptops will become the new entry point.

    #Technology #Computer #Computers #Laptop #Laptops #PCHardware #Hardware #PCGaming #PCGames

  2. What will be closing end of 2026, early 2027:

    - #OriginPC
    - #Maingear
    - #FalconNorthwest
    - #iBuyPower
    - #CyberPowerPC
    - #NZXT

    What will dissapear or reduce operations (output or only high-end products) in 2027/2028:

    - #ASRock
    - #MSI
    - #Gigabyte
    - #Zotac
    - #TeamGroup
    - #PowerColor
    - #Palit
    - #Corsair

    #PC will become a luxury. Laptops will become the new entry point.

    #Technology #Computer #Computers #Laptop #Laptops #PCHardware #Hardware #PCGaming #PCGames

  3. What will be closing end of 2026, early 2027:

    - #OriginPC
    - #Maingear
    - #FalconNorthwest
    - #iBuyPower
    - #CyberPowerPC
    - #NZXT

    What will dissapear or reduce operations (output or only high-end products) in 2027/2028:

    - #ASRock
    - #MSI
    - #Gigabyte
    - #Zotac
    - #TeamGroup
    - #PowerColor
    - #Palit
    - #Corsair

    #PC will become a luxury. Laptops will become the new entry point.

    #Technology #Computer #Computers #Laptop #Laptops #PCHardware #Hardware #PCGaming #PCGames

  4. What will be closing end of 2026, early 2027:

    - #OriginPC
    - #Maingear
    - #FalconNorthwest
    - #iBuyPower
    - #CyberPowerPC
    - #NZXT

    What will dissapear or reduce operations (output or only high-end products) in 2027/2028:

    - #ASRock
    - #MSI
    - #Gigabyte
    - #Zotac
    - #TeamGroup
    - #PowerColor
    - #Palit
    - #Corsair

    #PC will become a luxury. Laptops will become the new entry point.

    #Technology #Computer #Computers #Laptop #Laptops #PCHardware #Hardware #PCGaming #PCGames

  5. What will be closing end of 2026, early 2027:

    - #OriginPC
    - #Maingear
    - #FalconNorthwest
    - #iBuyPower
    - #CyberPowerPC
    - #NZXT

    What will dissapear or reduce operations (output or only high-end products) in 2027/2028:

    - #ASRock
    - #MSI
    - #Gigabyte
    - #Zotac
    - #TeamGroup
    - #PowerColor
    - #Palit
    - #Corsair

    #PC will become a luxury. Laptops will become the new entry point.

    #Technology #Computer #Computers #Laptop #Laptops #PCHardware #Hardware #PCGaming #PCGames

  6. Hersteller #HP liefert schon längere Zeit ein fehlerhaftes #BIOS über #Windows #Update aus. Einige teure #Laptops wie das ZBook Ultra G1a und das EliteBook X zeigen BSODs und Boot-Probleme. winfuture.de/news,158901.html?

  7. Hersteller #HP liefert schon längere Zeit ein fehlerhaftes #BIOS über #Windows #Update aus. Einige teure #Laptops wie das ZBook Ultra G1a und das EliteBook X zeigen BSODs und Boot-Probleme. winfuture.de/news,158901.html?

  8. Hersteller #HP liefert schon längere Zeit ein fehlerhaftes #BIOS über #Windows #Update aus. Einige teure #Laptops wie das ZBook Ultra G1a und das EliteBook X zeigen BSODs und Boot-Probleme. winfuture.de/news,158901.html?

  9. Hersteller #HP liefert schon längere Zeit ein fehlerhaftes #BIOS über #Windows #Update aus. Einige teure #Laptops wie das ZBook Ultra G1a und das EliteBook X zeigen BSODs und Boot-Probleme. winfuture.de/news,158901.html?

  10. Hersteller #HP liefert schon längere Zeit ein fehlerhaftes #BIOS über #Windows #Update aus. Einige teure #Laptops wie das ZBook Ultra G1a und das EliteBook X zeigen BSODs und Boot-Probleme. winfuture.de/news,158901.html?

  11. Linux 7.1 RC5 released!

    Linux 7.1 RC5 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.

    The official announcement from the kernel mailing list says:

    To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.

    I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.

    So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.

    End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.

    Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".

    So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".

    Why not try out this awesome pre-release of Linux 7.1?

    #Computer #Computers #Kernel #Laptop #Laptops #Linux #LinuxKernel #news #Tech #Technology #update
  12. Linux 7.1 RC5 released!

    Linux 7.1 RC5 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.

    The official announcement from the kernel mailing list says:

    To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.

    I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.

    So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.

    End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.

    Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".

    So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".

    Why not try out this awesome pre-release of Linux 7.1?

    #Computer #Computers #Kernel #Laptop #Laptops #Linux #LinuxKernel #news #Tech #Technology #update
  13. Linux 7.1 RC5 released!

    Linux 7.1 RC5 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.

    The official announcement from the kernel mailing list says:

    To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.

    I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.

    So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.

    End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.

    Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".

    So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".

    Why not try out this awesome pre-release of Linux 7.1?

    #Computer #Computers #Kernel #Laptop #Laptops #Linux #LinuxKernel #news #Tech #Technology #update
  14. Linux 7.1 RC5 released!

    Linux 7.1 RC5 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.

    The official announcement from the kernel mailing list says:

    To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.

    I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.

    So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.

    End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.

    Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".

    So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".

    Why not try out this awesome pre-release of Linux 7.1?

    #Computer #Computers #Kernel #Laptop #Laptops #Linux #LinuxKernel #news #Tech #Technology #update
  15. Linux 7.1 RC5 released!

    Linux 7.1 RC5 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.

    The official announcement from the kernel mailing list says:

    To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.

    I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.

    So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.

    End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.

    Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".

    So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".

    Why not try out this awesome pre-release of Linux 7.1?

    #Computer #Computers #Kernel #Laptop #Laptops #Linux #LinuxKernel #news #Tech #Technology #update