- 0
My 'Microsoft Never Invents' rant
-
Recently Browsing 0 members
- No registered users viewing this page.
-
Posts
-
-
By Eder Cardoso · Posted
These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0 -
By Usama Jawad96 · Posted
Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year. -
-
By leonsk29 · Posted
Wow, Microsoft IS cooking lately... This only shows that they COULD improve, they just chose not to for whatever reasons. That obsession with AI was destroying them from the inside out.
-
-
Recent Achievements
-
AndrewSteel earned a badge
Very Popular
-
Taliseian went up a rank
Veteran
-
Clizby earned a badge
One Month Later
-
Timaximus earned a badge
One Month Later
-
Timaximus earned a badge
Week One Done
-
-
Popular Contributors
-
Tell a friend
Question
tapo
For context, this was supposed to be part of the IE 7 public preview released thread. It seems this is too big for that section, so I'll post it here.
And for the record, Xbox Live was a good idea. I'm not a blind troll or anything.
Yeah, Microsoft intended to make search faster by overhauling the filesystem by adding another layer. "WinFS", which ran on top of NTFS (Which is an actual filesystem) was intended to make searches easier.
Of course, it was never implemented, so it doesn't really count. If you think unimplemented things count, it used used Apple's concept of 'stacks', saved searches that behave as folders. They patented it in the mid 90's. WinFS was designed to use stacks all around the filesystem, not just for quick search.
When it comes to desktop search, I honestly don't know (probably a Windows shareware vendor), but Google's attempt at Google Desktop Search, was to create an index beforehand, so searches didn't take so long. It also searched inside files so you didn't need to know the file's name. MSN Desktop Search, aside from copying the name "Desktop Search", was a direct ripoff. Apple's "Spotlight" search, was jumping into the game. Bringing back stacks, and adding the same type of quick searches GDS was well known for.
Back in its heyday, RealAudio/RealPlayer was actually pretty good. Quicktime had been out for a number of years, for Mac OS as well as Windows. What is now known as Windows Media Player used to be "Video for Windows", and used the avi container. Video for Windows was essentially a copy of Quicktime. When streaming video became more popular than local video, Microsoft rebranded it.
And Windows media only 'works' if you're running a Windows-based PC. Whereas Real has good software for the Mac and Linux, Microsoft did a horrible job on the Mac player, eventually contracting an outside company to turn it into a quicktime plugin. They don't support Linux at all.
What? Are you kidding me? Microsoft has always copied Apple when it comes to user interfaces, and it became really blatant when they were working on Windows 3.0, when they even hired Susan Kare (designer of the Mac OS icons) to do the Windows 3.0 icons as well. Windows 95 is also a copy (move the start menu to the top of the screen, make the cursor black, and the icons to the right hand side rather then the left).
They also only started codenaming their user interfaces starting with Windows XP, which is the only time they changed it in years (and was right after OS X came out). OS X's UI, codenamed Aqua, was suddenly met by OS XP's UI, codenamed Luna.
And hell, if you still don't believe me, there's even a video showing how much of a ripoff the Vista UI is.
Actually, they were both pretty terrible (Anyone remember Netscape's <blink> tag?) but Microsoft had, and continues to have, a fear that if something is used worldwide and open, then Microsoft's dominance will begin to slip. Remember, they only made a clone of CP/M, and got to where they are today though no-good business tactics (as well as illegal) and being in the right place at the right time.
Netscape, being very popular and available for Mac, Windows, and Unix systems, is seen as a threat. So, after licensing the original Mosaic code from Spyglass, they build IE. Of course, they never paid Spyglass a dime, but that's another story.
So they take IE, mold it into Windows as much as possible, then force it on their users in Windows 98, saying it cannot be removed (though it could, and Microsoft got burned for that).
The hope is, if everyone's running IE and viewing ActiveX websites, instead of Netscape and Java, then nobody could use another OS if they wanted to use the web.
ActiveX didn't catch on as well as they hoped, since Java was popular for the language, as well as applets. So they make their own JVM (Java Virtual Machine) which is shipped with Windows. The Microsoft JVM is incompatible and does not follow the specifications that Sun licensed them the technology under, meaning MSJVM applets wouldn't run on other JVMs for other platforms. When that failed (Sun sued and won), Microsoft makes a clone. C# and .Net CLR to replace Java and the JVM.
And that, ladies and gentlemen, is why I do not like Microsoft.
Edited by tapoLink to comment
https://www.neowin.net/forum/topic/427349-my-microsoft-never-invents-rant/Share on other sites
43 answers to this question
Recommended Posts