Recent observations from users on the social platform X have uncovered performance issues tied to the Windows 11 Start Menu, revealing that the component
  • 7rokhym
    10·
    3 days ago

    My work PC has W11. Microsoft ruined the start menu. I removed all the icons off the Start menu as it is simply useless and has zero practical functional except to shutdown the PC because Shutdown can’t be found with search.

  • hperrinEnglish
    9·
    3 days ago

    Lolwut? They made the Start Menu with JavaScript? Who are they, me?

    • pastermil@sh.itjust.works
      4·
      3 days ago

      To be fair, a lot of graphical toolkits in the UNIX ecosystem use JS as well. One profilic example would be the GNOME JavaScript.

      Nevertheless, they all don’t do this terribly with performance.

  • RejZoR@lemmy.mlEnglish
    13·
    3 days ago

    When Ai vibe coders are in charge of projects… They have no fucking clue what they are doing, but Ai yo! Start menu is slow? We have no fucking clue how to fix it.

  • i_am_not_a_robot@discuss.tchncs.de
    121·
    3 days ago

    The start menu being React Native is irrelevant. If it were React in an Edge web view that would be a different story.

    Opening the start menu should cause a spike in CPU usage. You want the CPU to open the menu ASAP instead of dragging out the process so the CPU usage is more flat.

    But everything in Windows these days is wasting time stealing your data, loading ads or other unnecessary data from cloud services, and interacting with “AI.” Performance is one of the lowest priorities, somewhere between software quality and privacy. Since mid Windows 10, Microsoft consistently replaces things with modernized, but worse, versions and never returns to finish making the new version as good as the previous version that evolved over decades. It’s a really expensive way to ruin a product. They could make a React Native start menu where people wouldn’t complain about the performance. They probably did and people are only noticing now because of a recent regression.

    • hperrinEnglish
      6·
      3 days ago

      Back when I wrote my own start menu replacement (for Windows XP), it worked by turning itself transparent and not responding to mouse input. When you clicked the start button, it would turn itself back to opaque and start responding to mouse input. This meant it opened in maybe 32 milliseconds if it was being particularly slow and took two frames to open instead of one.

  • Hawk@lemmy.dbzer0.comEnglish
    2·
    3 days ago

    I still cannot use search in the start menu, no idea why. It simply does not allow me to type.