Live data from Hacker News

I fixed Windows native development

marler8997.github.io

401–406 of 406 posts

Re: I fixed Windows native development

#401
post #390

Earlier quoted context omitted.

I don't know much about glibc's specifics, but in general: Security comes before a lot of things but not before accidental breakage. If you say "our compat guarantees are so strong you shouldn't keep track of versions at all", I expect this to mean that APIs and ABIs will never change, or at least not without a massive awareness campaign and transition plan being announced before - because such a breakage would take…

> Security comes before a lot of things but not before accidental breakage. It didn't really sound accidental, though the bugzilla report sounds like they underestimated the impact. But I'm quite sure they were aware this would break at least some old software, it's not like it's hard to understand what exactly is happening here. Old software (or rather, builds) used executable stacks by default, and some edge cases…

> Because what's at question in this case is the actual impact size, which to me seems quite limited.

It was widely covered in media. Some of the most popular games and software broke:

1. https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-...

2. https://www.phoronix.com/news/Glibc-WA-Steam-Exec-Stack

This is the attitude that will always prevent GNU/Linux from becoming prevalent for personal computing. There is a such a lack of empathy for users' hardships and it shows.

Re: I fixed Windows native development

#402

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.

The license doesn't actually permit OSS development. Only compilation of near-unmodified third party OSS libraries. You may not compile OSS software developed by your own organisation. The OSS software must be unmodified, "except, and only to the extent, minor modifications are necessary so that the Open Source Dependencies can be compiled and built with the software." https://visualstudio.microsoft.com/license-terms…

Using VS build tools for open source development is covered by the Community licence [0], separate from this Build Tools licence change. That license is more open than you might expect, working as an individual it even permits proprietary development for commercial purposes.

Under that usage, the Community license counts as a valid Visual Studio license for Build Tools purposes, hence the second paragraph:

> This change expands user rights to the Build Tools and does not limit the existing Visual Studio Community license provisions around Open-Source development. If you already are a developer contributing to OSS projects, you can continue to use Visual Studio and Visual Studio Build Tools together for free, just like before.

[0] https://visualstudio.microsoft.com/license-terms/vs2022-ga-c...

Re: I fixed Windows native development

#403
post #366

Earlier quoted context omitted.

I worked with VC++ 6.0 up until Windows 11 when it really, really wouldn't run any more, then switched to VS 2008. The code is portable across multiple systems so it didn't really matter which version of VS it's developed with, and VC++ 6.0 would load, build the project, and have it ready to run while VS 2022 was still struggling through its startup process. VS 2008 is starting to show the elephantine... no, continen…

Yeah recent VS is awful. I recently tried VS2022. What a mess.

VS2026 is even worse. And if you thought the CoPilot enshittification in 2022 was bad, wait'll you see 2026. We only use it for final builds now, so develop under a bloated but at least not enshittified yet version, then do release builds and testing with whatever the latest version is before shipping.

Re: I fixed Windows native development

#404

Earlier quoted context omitted.

That's not an AI problem, it's a a general blog post problem. Humans inject their own sawdust all the time. AI, however, can write concisely if you just tell it to. Perhaps you should call this stuff "slop" without the AI and then it doesn't matter who/what wrote it because it's still slop regardless. I completely agree with your parent that it's tedious seeing this "fake and gay" problem everywhere and wonder what a…

It never used to be a general blog post problem. It was a problem with the kinds of blogs I'd never read to begin with, but "look, I made a thing!" was generally worth reading. Now, I can't even rely on "look, I made a thing!" blog posts to accurately describe the author's understanding of the thing they made.

I see your point. You need to recalibrate how to decide what to read since the proxy has changed its meaning. I found a similar issue when monetized Youtubers started making things. It used to be amazing to see some hobby project that was a little bit sophisticated but now big stars have lots of money and their full-time job is doing incredible projects just to make videos of them. It's not AI but it's something that didn't used to exist. I'm thinking channels like "Stuff Made Here" and "I Did A Thing" that sound humble but doing difficult, expensive projects that have no purpose except to look good on a video.

Re: I fixed Windows native development

#406

Earlier quoted context omitted.

Humans invented writing, not LLMs. They are copying us not the other way around. You can’t jump on 1 sentence that vaguely sounds like an LLM and say it’s written by AI. It’s so silly. I understand the aversion to AI slop but this is not that.

people run on heuristics and no amount of our righteousness will change that. the entire article absolutely reeks of LLM style so the original commentor isnt off the mark. to address your point, LLMs are copying that which leads to the most human engagement, so the way you expressed things makes it seem like you are defending junk food as real food. which of course it is, however it is designed to make someone money…

I don't think the article "reeks of LLM style" at all. It's actually very obviously written by a human in my eyes, there are several phrases that LLMs would not write. I see this accusation leveled at basically any piece of writing that is long and not very casual now, it just doesn't make any sense.
Post reply on HN