Agreed. I'd not ditch the STL completely, but only use its freestanding subset. Implementations contain some very fast SIMD-accelerated code[1]. +The STL works without exceptions.
The good thing is that all of these can and have been quite neatly put into RAII[1] or some memory arena with custom deleters which use the Win32 functions. One could manually `delete` those handles, but there be dragons. Vulkan does something similar; everything is a VkSomething handle. They may just be pointers directly exposed by the driver, but even so, users are explicitly supposed to use vkDeleteSomething functions to delete them.
Perhaps even more interesting winfile.exe the original Windows 3 File Manager was even updated (including a few open source contributions) with a few modern conveniences. There's not a lot of reason for launching progman.exe in Windows 11, but you might be surprised what you can do with winfile.exe still to this day, when you want a break from File Explorer.
> The "type server protocol" is a desperate attempt from microsoft to prevent pylance from becoming obsolete by outsourcing its type checking to other language servers like basedpyright, ty or pyrefly -- while continuing to keep certain language server features exclusive to pylance.
> This protocol benefits nobody except microsoft. It adds needless complexity to any language server that chooses to support it. Basedpyright does not support it and strongly advises other language servers to avoid supporting it as well.
To sandbox LSP servers in sphinxdocrs with bwrap in rootless containers, we needed to add a --no-procfs-mount CLI arg (and MXC JSON) to sandboxes, because you can't mount /proc in a rootless container.
I stopped using Windows Terminal altogether because it somehow tends to crash the processes running inside its tabs. And I have a lot of terminals open.
An example issue: https://github.com/microsoft/terminal/issues/16363 . This exact error message with different codes happened to me across many machines at many different times. Never seen anything like that with the classic console host.
If I recall correctly, a few of both - there were instances where some work could be done more lazily/minimally (https://github.com/microsoft/TypeScript/pull/64476), and there were instances where we changed our allocation patterns and played around with some struct layouts. We originally strived not to drastically reorganize our data structures to make things easier to port, and we have more flexibility now. We're continuing to experiment more here.
i see a lot of complaining about the login part of Win11, and i dont like it either, but i have not seen anyone mention that you can build an autounattend.xml file (generator here: https://schneegans.de/windows/unattend-generator/) that allows you to bypass all this. I have a USB Key with the file and the latest copy of the 11 Pro download, and when setting up a new machine, i run a fresh install. Then once booted, i run the developer config (https://github.com/microsoft/WindowsDeveloperConfig/) and it gets everything i need installed. No Microsoft Login, no Candy Crush, WSL installed and all the tools i need.
It's perhaps a good time to bring attention to this open issue [1] on vscode from 2015 with thousands of upvotes, hundreds of comments pleading, the collective hive mind losing their minds over how a usability requirement so basic can be left neglected for years altogether even as so many other not so requested features seem to have no problem getting piled on.
While this issue has been a personal pain point, I do recall there were quite a few widely requested usability issues that went unaddressed over the years. So I'm not sure about how to react when I read this blog post about "modernizing" vscode UI in 2026. How can you talk about modernizing and journey through a 5-stage evolution when fundamental aspects are so obviously unaddressed? What is a modern UI anyways and how is it better than ancient UI? What specific advancements in HCI research from the last 10 years are being incorporated here to call the UI modernized?
I have to take a dig at the larger design community because I think this is not an isolated problem. Software usability in general has been going down for me over the years. There was a time when you would hear more from the community about the science of interaction and why you would design an interface in a certain way. Of late I feel the emphasis shifting more towards visual design with things like colors, spacing, border radii etc. with this blog post being a case in point.
If HN were to be launched today, I'm sure it would look nothing like what it does and instead have a more "modern" UI. But, would it be an improvement?
Most of the features are undocumented. I think because most of the behavior is not really defined and varies greatly between the different backends.
The backends are also not documented, you need to try out what's working and what isn't working. It doesn't explain the supported and unsupported features of each backend, neither their quirks.
A lot of behavior is surprising. For example if you have powershell in path on windows inside MXC it will just silently add the whole C drive with read-only permissions. Circumventing all other policies. https://github.com/microsoft/mxc/issues/1455
A lot of common error cases regularly happen and don't provide reasonable error messages. No documentation how to deal with them.
Check the issues on GitHub, there are many things that are expected to just work and they don't. One would at least expect some documentation why it doesn't work and where the limitations are: https://github.com/microsoft/mxc/issues
I don't think that's actually the case. There were some rumors flying around about this but in their recent event they actually referred to Copilot+ PCs as generally the line targeting more casual users with support for less powerful local inference. And the new devices based on Nvidia RTX Spark (and likely the more powerful solutions from AMD, Intel, Qualcomm with large unified memory) as a "Builder" class targeting developers and heavy local inference users. They also revealed a quantized version of their coding model designed to run on these devices.
So it does seem they may be somewhat working from the bottom up building smaller models or focusing on capable local inference and balancing with more powerful frontier model access.
This is a lot of marketing speak but covers much of what they revealed.
This is actually the case. Windows ML (https://github.com/microsoft/windowsML) is the inference framework wtih vendor agnostic support for inference on CPU, NPU, and GPU. They also announced quite a bit more including an isolation solution with MXC. There's a lot of marketing fluff in the below link but it covers the recent announcements.
https://blogs.windows.com/windowsexperience/2026/10/07/build...
I suppose my comment sort of implies this. I think the naive knee jerk reaction is that if you can spit out perfect machine level code against a specification, then logically being closer to bare metal would help with performance. However, without knowing the details of how things worked it is tough to say whether it is truly "reasonable" or not.
But more importantly, the Typescript team themselves [1] picked Golang mostly out of ergonomics and ease of porting at the time. It is becoming more increasingly more to "taste" what ergonomics means. Notably, they did not pick it because they believed it to be the fastest option. But speed was on the mind, giving way to ergonomics and ease of porting. At least, this is my read.
https://github.com/microsoft/terminal