BREAKING: Sinofsky out at Microsoft.


Recommended Posts

I think JLG will be in "charge" of Windows till they finish "blue" which could be v8.1 or however you want to think of it. Then a true president of windows will take over. If you notice she hasn't been given the title of president that Sinofsky had so I think her position is temporary since we already have rumors that "blue" is has been started.

is there some certain cabal of people that love to celebritize employees of tech companies? i dont get it. who is this guy and who cares if he's in or out?

"OMG <whatsherface> took over as CEO on Yahoo!"

"OMG Ballmer said what!?"

"OMG rich guy at Google was promoted!"

"Zuckerberg sold all his stock in FB! whoa!"

is there some certain cabal of people that love to celebritize employees of tech companies? i dont get it. who is this guy and who cares if he's in or out?

"OMG <whatsherface> took over as CEO on Yahoo!"

"OMG Ballmer said what!?"

"OMG rich guy at Google was promoted!"

"Zuckerberg sold all his stock in FB! whoa!"

Awwww are you mad that more people care about him then you?

I do wonder why he left, but it's hard to ignore the coincidence between Windows 8, and Sinofsky's departure... Windows 8, as much as you spin it otherwise, is not doing very well.. and Surface is a piece of garbage.

uh, according to what reports is it not doing very well, and how is the surface a piece of garbage ? methinks you're talking out of your behind.

Anyway, as has been said numerous times, when a high profile project leader leaves it's usually after a project is finished. this is the time for im to leave after the last and before the next. as for the reason for him leaving, it's simple. He wanted to much power and hated sharing it, he didn't want his department(windows) to cooperate with xbox, live, office, skydrive or any others, and he kept building walls and setting up roadblocks for other departments. Ballmer wanted more cooperated between departments and to make everything work together.

Sorry, but nope. Julie Larson-Green was also one of the folks behind some of the big changes here. She did a lot of work for Office. She was one of the folks that led the way for the Ribbon UI elements. She also is one of the primary people handling design for Windows.

So what you're hoping for and the scenario you are proposing? Not in line with reality.

people don't leave good jobs like that because they are happy. unless what was being done was leading to unhappiness. :(

people don't leave good jobs like that for because they are happy. unless what was being done was leading to unhappiness. :(

Actually they do. he's been there for well over 20 years. sometimes people, especially in those positions want new challenges and want to go out in the world, remember he has enough money to live the rest of his life, and he can get a new job that will pay even more, or less if he likes the challenge. Sometimes people just want to try something new.

  • Like 2

I do wonder why he left, but it's hard to ignore the coincidence between Windows 8, and Sinofsky's departure... Windows 8, as much as you spin it otherwise, is not doing very well.. and Surface is a piece of garbage.

Yes yes indeed :)

Steven Sinofsky, the Microsoft executive in charge of Windows, has left the company.. The changes are effective immediately, and no reason was given for Sinofsky's departure.

Hmm ... Windows 8 released ... executive in charge of Windows booted out.

Interesting coincidence. :shifty:

Hmm ... Windows 8 released ... executive in charge of Windows booted out.

Interesting coincidence. :shifty:

Not really considering they put Julie in charge, and she is the one who was in charge of most of the things that people keep complaining about.

Project finished up, he left. Happens all the time, without the need for conspiracy theories. He just happens to be higher up so it's more noticeable.

When you look at other levels you see this happening all the time...project is finished, person moves on to another team, another job, or retires, etc.

Hmm ... Windows 8 released ... executive in charge of Windows booted out.

Interesting coincidence. :shifty:

I believe it was just a coincidence but we may never know that for sure.I believe he was after Ballmer's job and Steve gave him the boot.

Actually they do. he's been there for well over 20 years. sometimes people, especially in those positions want new challenges and want to go out in the world, remember he has enough money to live the rest of his life, and he can get a new job that will pay even more, or less if he likes the challenge. Sometimes people just want to try something new.

another one of the rare posts of yours i agree on

yes, it is a very well known fact that people come and go, especially in the tech world, and especially in high positions.

Even with that known, I just cannot see this as even coming close to being a good thing.

Sure, Windows 8 has now launched, but that does not mean there is still a ton of work that needs to be done in regards to it.

To me it would be much better if the person that did all of the hard work leading up to the launch stuck around after the launch to see things through.

But really at the end of the day, who knows why he left, what really happened, etc. All we can do is speculate.

But again, I would think ultimately the person would want to at least stick around a little bit longer to see things through.

yes, it is a very well known fact that people come and go, especially in the tech world, and especially in high positions.

Even with that known, I just cannot see this as even coming close to being a good thing.

Sure, Windows 8 has now launched, but that does not mean there is still a ton of work that needs to be done in regards to it.

To me it would be much better if the person that did all of the hard work leading up to the launch stuck around after the launch to see things through.

But really at the end of the day, who knows why he left, what really happened, etc. All we can do is speculate.

But again, I would think ultimately the person would want to at least stick around a little bit longer to see things through.

He did. He stuck around through the launch, through the first set of updates to make sure things went smooth, and then went off 'into the sunset'.

Sticking around much longer would have put him directly into the next OS cycle as these things ramp up quickly after a launch has finished.

It may be a good thing, though. Apparently Sinofsky liked a toxic environment where people in the same company worked against each other. No matter how talented one is or how smart, or how good, an environment like that is never a good thing and hurts a company in the long run. Plus fighting with your boss will get you canned every time.

Click and drag takes too much effort compared to scrolling. It would be akin to click and dragging to scroll a webpage. No one wants to do that.

Yup I'm no one lol. It just seems natural for me for some reason to try to click and drag. If it was vertical I think I'd be fine with just the mousewheel, but the screen is horizontal so it feels weird for me to use a scroll wheel. Oh well not a deal breaker just annoying.

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!