Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I fixed Windows native development

marler8997.github.io

Post reply on HN
Print view View original

191–200 of 406 posts

Re: I fixed Windows native development

#191

Post by PKop »

evanjrowley wrote: post #58
its_notjack wrote: post #34

Is 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.

> 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?

Re: I fixed Windows native development

#193

Post by quikoa »

jezek2 wrote: post #75

I wish open source projects would support MingW or at least not actively blocking it's usage. It's a good compiler that provides an excellent compatibility without the need of any extra runtime DLLs. I don't understand how open source projects can insist on requiring a proprietary compiler.

Agreed I also like to see more support for MingW especially from open source projects. Not even a passing mention in this blog post.

Re: I fixed Windows native development

#194

Post by qingcharles »

foepys wrote: post #38
dgxyz wrote: post #26

Earlier quoted context omitted.

You can install the LTSC toolchain without a license. Just not the IDE.

That's not correct. You don't have to give your credit card details or even be logged in but you are still required to have any Visual Studio license. For hobbyists and startups the VS Community license is enough but larger companies need a VS Professional license even for the VS Build Tools. How strict Microsoft is with enforcement of this license is another story.

And a VS license isn't too expensive if you really want to buy one. Stack Social have legit licenses discounted to $15:

https://www.stacksocial.com/sales/microsoft-visual-studio-pr...

Re: I fixed Windows native development

#195

Post by tgtweak »

nanoxide wrote: post #89
tgtweak wrote: post #64

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…

When was the last time you actually used. NET? Because that's absolutely not how it is. The. NET runtime is shipped by default with Windows and updated via WU. Let alone that you're talking about .NET Framework which has been outdated for years.

The issue is in supporting older windows versions - which sadly is still a reality for most large-scale app developers.

Re: I fixed Windows native development

#196

Post by Pay08 »

the__alchemist wrote: post #105
tgtweak wrote: post #64

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…

This is one of the things that tilts me about C and C++ that has nothing to do with mem safety: The compile/build UX is high friction. It's a mess for embedded (No GPOS) too in comparison to rust + probe-rs.

That hasn't been my experience at all. Cross-compiling anything on Rust was an unimaginable pain (3 years or so ago). While GCCs approach of having different binaries with different targets does have its issues, cross compiling just works.

Re: I fixed Windows native development

#198

Post by Pay08 »

fao_ wrote: post #131
crote wrote: post #128

Earlier quoted context omitted.

The counterpoint of this is Linux distros trying to resolve all global dependencies into a one-size-fits-nothing solution - with every package having several dozen patches trying to make a brand-new application release work with a decade-old release of libfoobar. They are trying to fit a square peg into a round hole and act surprised when it doesn't fit. And when it inevitably leads to all kinds of weird issues the p…

> The counterpoint of this is Linux distros trying to resolve all global dependencies into a one-size-fits-nothing solution - with every package having several dozen patches trying to make a brand-new application release work with a decade-old release of libfoobar. They are trying to fit a square peg into a round hole and act surprised when it doesn't fit. This is only the case for debian and derivatives, lol. Rollin…

I'm going to need a source for both of those claims.

Re: I fixed Windows native development

#199

Post by groundzeros2015 »

its_notjack wrote: post #34

Is 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.

Yes. It appears that way

Re: I fixed Windows native development

#200

Post by kristjansson »

whatever1 wrote: post #197

“Build Requirements: Install Visual Studio”. You’ve never experienced genuine pain in your life. Have you tried to change the GCC compiler version in Linux?

   apt install gcc-11

   CC=gcc-11 make
?

If it’s not packaged and you’ve got to build it yourself, Godspeed. An if you’ve got to change libc versions…

Post reply on HN