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

201–210 of 406 posts

Re: I fixed Windows native development

#201

Post by Pay08 »

calvinmorrison wrote: post #115
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…

> Toolchains on linux are not clear from dependency hell either - ever install an npm package. That's where I stopped. Toolchains on linux distributions with adults running packaging are just fine. Toolchains for $hotlanguage where the project leaders insist on reinventing the packaging game, are not fine. I once again state these languages need to give up the NIH and pay someone mature and responsible to maintain pa…

The real kicker is when old languages also fall for this trap. The latest I'm aware of is GHC, which decided to invent it's own build system and install script. I don't begrudge them from moving away from Make, but they could have used something already established.

Re: I fixed Windows native development

#202

Post by Pay08 »

kristjansson wrote: post #200
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…

GCC is surprisingly simple to build, fortunately.

Re: I fixed Windows native development

#203

Post by marler8997 »

Groxx wrote: post #190
dotancohen wrote: post #176

Earlier quoted context omitted.

You don't have to install executables downloaded from an unknown GitHub account named marler8997. You can download that script and read it just like any other shell script. Just like those complaining about curl|sh on Linux, you are confusing install instructions with source code availability. Just download the script and read it if you want. The curl|sh workflow is no more dangerous that downloading an executable of…

It is somewhat different when your system forces binaries to be signed... but yeah, largely agreed. The abject refusal of curl|sh is strange to me, unless the refusers are also die-hard GPL adherents. Binaries are significantly more opaque and easier to hide malware in, in almost all cases.

Wait till they find out what the Visual Studio Installer itself does :) I guess this person just trusts a big company like Microsoft who keeps their source hidden more than a single developer who publishes all their source?

Re: I fixed Windows native development

#204

Post by p_ing »

tgtweak wrote: post #195
nanoxide wrote: post #89

Earlier quoted context omitted.

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.

https://github.com/dotnet/core/blob/main/release-notes/10.0/...

.NET 10 supports a Windows 10 build from 10 years ago.

Re: I fixed Windows native development

#205

Post by [deleted] »

Pay08 wrote: post #196
the__alchemist wrote: post #105

Earlier quoted context omitted.

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.

[deleted]

Re: I fixed Windows native development

#207

Post by scotty79 »

okanat wrote: post #55
dgxyz wrote: post #45

Earlier quoted context omitted.

[flagged]

Well, let's say this is the world view of all companies about open-source software. Then what happens. If people "tend to not give crap" about licenses, all the nice guarantees of GPL etc also disappear.

There are zero guarantees and commercial software uses GPLd software as parts of their products all the time. Licenses do not work and you shouldn't respect them whenever you can.

Re: I fixed Windows native development

#208

Post by ameliaquining »

marler8997 wrote: post #203
Groxx wrote: post #190

Earlier quoted context omitted.

It is somewhat different when your system forces binaries to be signed... but yeah, largely agreed. The abject refusal of curl|sh is strange to me, unless the refusers are also die-hard GPL adherents. Binaries are significantly more opaque and easier to hide malware in, in almost all cases.

Wait till they find out what the Visual Studio Installer itself does :) I guess this person just trusts a big company like Microsoft who keeps their source hidden more than a single developer who publishes all their source?

If any of this is relevant to you, you're already running Windows, which means Microsoft already has root on your machine, which means it's futile to try to limit the extent to which you trust their binaries.

Re: I fixed Windows native development

#210

Post by rdiddly »

forrestthewoods wrote: post #184
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.

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.
Post reply on HN