I'm helping a friend of mine writing a long essay exposing the abusive, monopolistic and anti-consumer practices of Microsoft. First, we've created some sort of table of contents with the different topics we want to cover and now we're gathering sources for each of these topics.
Microsoft is a huge corporation with a big influence on media and although if you dig enough you can find useful sources, they've also made an extremely good job at hiding bad press from search engines.
We've scrolled through Hacker News, other links aggregators and sites like TechRights and we've found a good amount of articles against Microsoft. But we're sure there has to be more. So that's kinda why we're asking.
Bullet points for the sections we've thought of (suggestions are welcome too):
* The Microsoft Monopoly
* Microsoft and the web
* Internet Explorer
* Microsoft Edge
* Microsoft Windows Monopoly
* Microsoft and the Governments
* Education
* Healthcare
* Microsoft Gaming Empire
* Windows Backdoors (not sure where this section belongs)
* Work with the NSA
* Microsoft loves Open Source (microsoft infiltration in foss)
* Microsoft and the OSI
* Github
* Github Copilot
* VSCode
* War on GPL
* Microsoft loves Linux and BSD?
* Embrace, extend, extinguish
* Our lord, Bill Gates
* The media empire
* Twitter censorship
* Bill Gates the philanthropist
* Big Pharma
* Bill and Jeffrey Epstein
Edit: typos and removed the pun "Kill Bill Gates" because it seemed inappropriate.
There probably is some shell extension that could add this in context menu. In Windows you use mklink or New-Item commands. Links are not really popular in Windows environment, I would say an absolute majority do not even know about them or never think about them. Shortcuts are the ones that people generally use.
I can accept a compromise of slightly more verbose and standardized syntax for interactive use when compared with unix/linux and ability to easily automate pretty much everything you can in Windows / Microsoft ecosystem. I am not a professional coder, but I thoroughly enjoy scripting in PowerShell for work and private tasks.
True, that's just how Windows programs work. Executables probably will never be available from shell as they can be from Linux without manual tinkering. Start menu is essentially the alternative here. For those couple programs I need to be easily lauched from terminal, adding paths to PATH variable does not seem too much of an problem.