• 16 Posts
  • 18 Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle







  • from the comments of the article that got the most upvotes

    Embrace, Extend, Extinguish

    Microsoft’s Copilot push isn’t strategy, it’s the old embrace, extend, extinguish play dressed up in “AI” robes. GitHub was acquired to embrace developers. Copilot is the extend phase: saturating every workflow with unasked-for AI noise, from issues to pull requests to editors. The extinguish part is already visible - trust in GitHub is collapsing, and the very maintainers who underpin Microsoft’s ecosystem are moving to other platforms.

    On earnings calls, this is presented as “momentum”. In reality, it’s forced adoption: a hostile takeover of developer experience. When customers explicitly ask for an off switch and leadership ignores them, that’s not innovation - it’s managerial negligence. Any competent operator knows that coercion isn’t growth, it’s decay.

    GitHub’s competitive advantage was never a Copilot sidebar, it was trust and network effects. Those are finite assets, and they’re being burned for vanity metrics. The result? A platform that once symbolised collaboration now feels like adware, and developers - the same ones whose code powers Azure and every Microsoft AI demo - are signalling they’re done.

    Shareholders should be asking a simple question: what is the long-term value of poisoning the well you drink from? Copilot may inflate short-term KPIs, but the cost is strategic: erosion of goodwill, flight of open-source projects, and reputational damage that no amount of AI rebranding can fix.

    I agree with the first paragraph, this is just another M$ EEE. Utilizing source codes on github to train their AI to be smarter in coding. So they can promote vibe coding to people with a little or no experience in coding.






















  • My laptop did not go to sleep

    Some people have similar experiences regarding sleep issue, including system just went blank on wake up.

    From my experiences on Linux Mint in two different laptops, the sleep issue related to Linux system cache. By default, many Linuxes use these settings, vm.dirty_ratio and vm.dirty_background_ratio are about 5 to 20 percent of the available system memory. This is fine if your system has less than 4GB of memory installed, but if your system has 8GB or more of memory, this can cause problems later on.

    So I have this “can’t wake up” issue on my two differents laptop, the first laptop has 8 GB of memory and the second laptop has 16 GB. And both laptops are running on Linux Mint.

    In search of a solution, I came across this conversation https://lkml.org/lkml/2013/10/25/39

    I also found some possible system cache related issues on various distros.

    So I tried what Linus suggested, and I use lower values than suggested. And it worked!, the “can’t wake up” issue on both laptops just gone in instant!