Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "microsoft fans"
-
"Anything that can be done in GUI is better than in terminal"
Yes it's wrong and stupid. Let Microsoft fans disagree.16 -
Whoever designed UEFI, FUCK YOU!! Giving the OS control over every fucking thing in the hardware instead of letting the BIOS do that separately, WHO IN THEIR RIGHT FUCKING MIND THOUGHT THAT THAT WAS A GOOD IDEA?!!
And same goes to fucking you Microsoft! How difficult is it to do a fucking ACPI shutdown and do it properly?! How fucking difficult is it to not make the fans spin like jet engines because why the fuck not?! And yes the fucking PC is dust-free and bloat-free so I don't want to see any fucking Wintard comment that.
You know where else I saw the inability to power down? In Linux 4.20-rc2. A kernel that is within active development, and rc2 at that!! A kernel branch that's designed to be unstable, for testing purposes. Meanwhile the stable branch of MS Windows does the same. Also designed to be unstable because fuck QA?! Filthy fucking motherfuckers!!27 -
Ok seriously is Microsoft mining Bitcoin on my computer? If I leave it idle for >5 minutes it starts using intense amounts of CPU and I have no clue why (doesn't show up in task manager, all the processes added up in taskmgr are like 15% max). It's super annoying since I have a razer and high cpu turns on BOTH VERY LOUD FANS.
I checked for malware and stopped any update or useless background tasks (cortana, indexing, etc) and it has not helped one bit. If I click the screen or move the mouse it subsides immediately.
(No, I won't get a mac--I have two and they lacks compatibility with the software I need as well as the specs for what I usually work with)13 -
Would just like to give kudos to 343 for there work at bring halo to PC. They are actually being developers and not doing a rushed port with minimal tweaking...
It's great to see some Devs take pride in their work and not see it just as a quick job to rake in the money from fans...
Never thought I would give good credit to a Microsoft owned thing...
(I'm an Xbox gamer so i suppose I can't hate too much?)6 -
I HATE SURFACES SO FRICKING MUCH. OK, sure they're decent when they work. But the problem is that half the time our Surfaces here DON'T work. From not connecting to the network, to only one external screen working when docked, to shutting down due to overheating because Microsoft didn't put fans in them, to the battery getting too hot and bulging.... So. Many. Problems. It finally culminated this past weekend when I had to set up a Laptop 3. It already had a local AD profile set up, so I needed to reset it and let it autoprovision. Should be easy. Generally a half-hour or so job. I perform the reset, and it begins reinstalling Windows. Halfway through, it BSOD's with a NO_BOOT_MEDIA error. Great, now it's stuck in a boot loop. Tried several things to fix it. Nothing worked. Oh well, I may as well just do a clean install of Windows. I plug a flash drive into my PC, download the Media Creation Tool, and try to create an image. It goes through the lengthy process of downloading Windows, then begins creating the media. At 68% it just errors out with no explanation. Hmm. Strange. I try again. Same issue. Well, it's 5:15 on a Friday evening. I'm not staying at work. But the user needs this laptop Monday morning. Fine, I'll take it home and work on it over the weekend. At home, I use my personal PC to create a bootable USB drive. No hitches this time. I plug it into the laptop and boot from it. However, once I hit the Windows installation screen the keyboard stops working. The trackpad doesn't work. The touchscreen doesn't work. Weird, none of the other Surfaces had this issue. Fine, I'll use an external keyboard. Except Microsoft is brilliant and only put one USB-A port on the machine. BRILLIANT. Fortunately I have a USB hub so I plug that in. Now I can use a USB keyboard to proceed through Windows installation. However, when I get to the network connection stage no wireless networks come up. At this point I'm beginning to realize that the drivers which work fine when navigating the UEFI somehow don't work during Windows installation. Oh well. I proceed through setup and then install the drivers. But of course the machine hasn't autoprovisioned because it had no internet connection during setup. OK fine, I decide to reset it again. Surely that BSOD was just a fluke. Nope. Happens again. I again proceed through Windows installation and install the drivers. I decide to try a fresh installation *without* resetting first, thinking maybe whatever bug is causing the BSOD is also deleting the drivers. No dice. OK, I go Googling. Turns out this is a common issue. The Laptop 3 uses wonky drivers and the generic Windows installation drivers won't work right. This is ridiculous. Windows is made by Microsoft. Surface is made by Microsoft. And I'm supposed to believe that I can't even install Windows on the machine properly? Oh well, I'll try it. Apparently I need to extract the Laptop 3 drivers, convert the ESD install file to a WIM file, inject the drivers, then split the WIM file since it's now too big to fit on a FAT32 drive. I honestly didn't even expect this to work, but it did. I ran into quite a few more problems with autoprovisioning which required two more reinstallations, but I won't go into detail on that. All in all, I totaled up 9 hours on that laptop over the weekend. Suffice to say our organization is now looking very hard at DELL for our next machines.4
-
I'm sorry to say this, but C# along with other Microsoft tech stack is a crap show!!
*And now I'll be bombarded by all Microsoft fans in the house!!*16 -
Windows 7 could be installed without a Microsoft account.
Windows 8 required it, but had a “Skip” button.
Windows 10 also had a skip button, though obscured and inaccessible for those who just click through the process (95% of people).
Windows 11 home doesn’t have a skip button. You have to press Alt + F4 when Windows installer asks you for network connection to avoid it asking to create a Microsoft account.
My girlfriend, a linguist who has nothing to do with programming and computers in general, successfully transferred to a Linux distro after I told her about Microsoft supporting ICE. She says Linux is simpler, she had no problem installing additional software and she liked that cooling fans are never spinning now and that battery life is now solid two times better.
Think about it.6 -
I know Electron apps sometimes tend to be slow and consume a lot of RAM, but Jesus Christ Microsoft Teams is such garbage - it consumes a whole CPU core just for itself. My laptop fans start whirring and after a half an hour of MS Teams sitting in the background idle dmesg starts telling me CPU temperature has reached a treshold and is now thermal throttling. :(((((((2
-
I know a lot of people aren't fans of Microsoft here, but does anyone have some extended experience with using powershell?
I've been using it for creating a script that handles quite a large set of tasks for setting up and configuring some application servers and so far I have been really digging the language. Being able to invoke the script against remote hosts in parallel like ansible has been a really cool learning experience.
Admittedly it's verbose as fuck, so getting the same thing done in something like python/perl might be like half the lines of code. And I know that some of the commands illicit a "WTF?" every now and again. But I think one of the powershell tutorials I watched early on in attempting this helped make using powershell not suck ass.
Every command is basically 'verb-noun'. You don't know what the command or switches are:
> get-help "command" -showwindow
It will give you a list of options if you didn't select the exact command with get-help.
It feels* amazingly buttoned up as a scripting language and it's really cool to be able to take advantage of lower level stuff, like you can run alternative shells (we have cygwin installed on some of our servers), you can run C# code, you have access to interfacing with .NET api's. I haven't messed with anything azure yet, but being able to interface with products and services like SQL/Exchange/O365/azure/servers/desktops from the same language seems pretty cool.
Admittedly, the learning curve feels terrible though. I felt like a dunce for the first couple weeks, couldn't navigate the language at all, and was always in the docs trying to figure stuff out. I think I just needed to understand how the people developing powershell intended for it to be used. Once I was able to put two-and-two together about the verb-noun structure and how to find information/examples about the cmdlets it's been quite easy to work with it.
If anyone else has any extended experience with it, please share your thoughts/opinions. Curious to see if your experiences are/were similar to mine.
If you don't have Powershell experience, please feel free to share your opinions of Micro$haft and me for using Micro$haft products too! It's all good 😎9