291–300 of 406 posts
Earlier quoted context omitted.
> Is this post AI-written? What if it was? What if it wasn't? What if you never find out definitely? Do you wonder that about all content? If so, doesn't that get exhausting?
Yeah, it does. Congratulations, you figured out why the future is going to be fucking awful.
Toolchains on linux are not clear from dependency hell either - ever install an npm package that needs cmake underneath? glibc dependencies that can't be resolved because you need two different versions simultaneously in the same build somehow... python in another realm here as well. That shiny c++ project that needs a bleeding edge boost version that is about 6 months away from being included in your package manager…
> The build.bat above isn’t just a helper script; it’s a declaration of independence from the Visual Studio Installer. I am so fed up with this! Please if you're writing an article using LLMs stop writing like this!
Earlier quoted context omitted.
Eww no. MingW is evil and no project should ever use it. Just use Clang + MSVC STL + WinSDK. Very simple.
From the capitalization I can tell you and the parent might not be aware it's "minimal GNU for Windows" which I would tend to pronounce "min g w" and capitalize as "MinGW." I used to say ming. Now it's my little friend. Say hello to my little friend, mang.
Earlier quoted context omitted.
> have popularized it It's hated by everyone, why would people imitate it? You're inventing a rationale that either doesn't exist or would be stupider than the alternative. The obvious answer here it they just used an LLM. > and clearly it serves some benefit to readers. What?
Then why does every vibe-coded "Show HN" app have it in README.md? Surely authors would edit it out if it was true that everyone hates it.
> msvcup is inspired by a small Python script written by Mārtiņš Možeiko.
No. Martins fixed. OP made a worse layer on top of Martins great script.
I don't get why people go through all these flaming hoops and hurdles to deal with MSVC when MinGW and MinGW-w64/MSYS2 are options. In the latter case you even still get (mostly complete) MSVC ABI-compatibility if you compile with clang.
Supporting Windows without MinGW garbage is really really easy. Only supporting MinGW is saying “I don’t take this platform seriously so you should probably just ignore this project”.
Earlier quoted context omitted.
You do not need a Professional or Enterprise license to use the Visual Studio Build Tools: > Previously, if the application you were developing was not OSS, installing VSBT was permitted only if you had a valid Visual Studio license (e.g., Visual Studio Community or higher). From ( https://devblogs.microsoft.com/cppblog/updates-to-visual-stu... ). For OSS, you do not even need a Community License anymore.
This does not apply if you're developing closed source: > if you and your team need to compile and develop proprietary C++ code with Visual Studio, a Visual Studio license will still be required.
I don’t need visual to write, read, compile, or link any code using the toolchain.
Earlier quoted context omitted.
You do not need a Professional or Enterprise license to use the Visual Studio Build Tools: > Previously, if the application you were developing was not OSS, installing VSBT was permitted only if you had a valid Visual Studio license (e.g., Visual Studio Community or higher). From ( https://devblogs.microsoft.com/cppblog/updates-to-visual-stu... ). For OSS, you do not even need a Community License anymore.
This does not apply if you're developing closed source: > if you and your team need to compile and develop proprietary C++ code with Visual Studio, a Visual Studio license will still be required.