I like the tool, I like the article, but I'd prefer it it was half as long but without AI touch.
I fixed Windows native development
91–100 of 406 posts
Re: I fixed Windows native development
#92> On Linux, the toolchain is usually just a package manager command away. On the other hand, “Visual Studio” is thousands of components.
That package manager command, at the very least, pulls in 50+ packages of headers, compilers, and their dependencies from tens of independent projects, nearly each of them following its own release schedule. Linux distributions have it much harder orchestrating all of this, and yet it's Microsoft that cannot get its wholly-owned thing together.
Re: I fixed Windows native development
#93Actually not that complicated: You simply check in a global.json [0] where you specify the sdk and workload versions. Then you also specify target platform sdk versions in the .csproj file and VS will automatically prompt the developer to install the correct toolchain. [0] https://learn.microsoft.com/en-us/dotnet/core/tools/global-j...
[dead]
Re: I fixed Windows native development
#94You can do a lot of "native" windows development from modern C#/.NET via win32 interop.
Newer C# features like ref returns, structs, spans, et. al., make the overhead undetectable in many cases.
Re: I fixed Windows native development
#95Came in getting ready to hate on this article, but was actually pleasantly surprised, this is great. Good work OP.
Re: I fixed Windows native development
#96At the risk of being that guy , I haven't had any issues onboarding people onto native projects written in Rust. rustup does a great job of fetching the required toolchains without issue. I'd imagine the same is also true of Go or Zig.
While Microsoft Incremental compilation, and linking, parallel builds, hot code reloading, REPL, graphical debugging optimised builds, GPU debugging....
Go is better left for devops stuff like Docker and Kubernetes, and Zig remains to be seen when it becomes industry relevant beyond HN and Reddit forums.
Re: I fixed Windows native development
#97One day I decided to port my text editor to Windows. Since it depends on pcre2 and treesitter, these two libraries had to be provided by the system. In the span of ~2hrs I didn't manage to find a way to please Zig compiler to notice "system" libraries to link against. Perhaps I'm too spoiled by installing a system wide dependency in a single command. Or Windows took a wrong turn a couple of decades ago and is very ho…
I think providing purely-functional libraries as system dependencies that's tied to the whole tool chain at the time was the wrong decision by the Unix world.
The system libraries should only ship system stuff: interaction with the OS (I/O, graphics basics, process management), accessing network (DNS, IP and TLS). They should have stable APIs and ABIs.
Windows isn't hostile. It has a differnt paradigm and Unix (or more correctly usually GNU/Linux) people do not want to give up their worldview.
PCRE is basically only your apps's dependency. It has nothing else to do the rest of the operating system. So it is your responsibility to know how to build and package it.
Re: I fixed Windows native development
#98At the risk of being that guy , I haven't had any issues onboarding people onto native projects written in Rust. rustup does a great job of fetching the required toolchains without issue. I'd imagine the same is also true of Go or Zig.
You have to do this for certain rust things too. I can't remember which, but I inevitably run into a need to install the MSVC toolchain to compile rust. I think it might be related to FFI, or libs which use FFI? The same thing comes up in Linux, but the process to install it is different. I got anxiety reading the article, describing exactly why it sucks. It's nice to know from the article and comments here there are…
It makes use of MSVC linking infrastructure, and import libraries.
Re: I fixed Windows native development
#99I hope it would work with wine. Then cross compiling Win64 binaries from Linux would become convenient without requiring spinning up a Windows VM.
Re: I fixed Windows native development
#100Is this post AI-written? The repeated lists with highlighted key points, the "it's not just [x], but [y]" and "no [a] just [b]" scream LLM to me. It would be good to know how much of this post and this project was human-built.
Perhaps people have mimicked the style because LLMs have popularized it and clearly it serves some benefit to readers.
Perhaps LLMs have mimicked the style because authors have popularized it and clearly it serves some benefit to readers.