Trademark is not copyright.

False

You use "conspiratorial" as though Enrico is the one being conspiratorial. That's obviously not the case as far as what's publicly known. With whom is he conspiring? And against whom?

Please don't post deliberately false information on HN.

https://www.law.cornell.edu/uscode/text/47/230

Let me rephrase, since saying they lose their safe harbor was a poor choice of words. The safe harbor does indeed prevent them from being treated as the publisher of the illegal content. However illegal content can incur liability for acts other than publishing or distributing and section 230's safe harbor won't protect them from that.

The idea is that you want functions that can return functions, those inner functions being defined in part by the arguments to the outer function. This can't happen without intentionally leaky namespaces.

Bad pseudocode:

function stepincrementgenerator(step) -> function (num) -> num + step

addsix = stepincrementgenerator(6)

addsix(5)

11

In my experience, the wxWidgets documentation and forums are pretty good resources for Windows manifest files. YMMV.

An example from one of my projects: https://pastebin.com/Jvjn5C6S

You need to reference it from your resource source like so: https://pastebin.com/8FUi4tMz

And then compile that into an object file with windres: x86_64-w64-mingw32-windres rsrc/metadata/windows.rc -o winbuild/windowsrc.o

And link it with your project like you would any other object file.

The entire structure is also documented on MSDN with all possible values - https://learn.microsoft.com/en-us/windows/win32/sbscs/applic....

While MSDN is a bit impractical to browse (there's simply so much stuff in there) it's usually the best place to go to for documentation when doing Windows dev.

Strongly disagree. There's way too much mystery and magic number usage in the official documentation.

The magic numbers (hashes and UUIDs) sort of make sense because there's a slightly adversarial interaction between developers and Microsoft. If you just had a compatibleWindowsMin and compatibleWindowsMax field with version numbers, people would just go ahead and put "9999" in the max field, and then OS upgrades break applications again. By using UUIDs instead, an application developer can't intentionally or unintentionally declare compatibility with unreleased Windows versions.

Can you recommend any good alternatives for someone looking to learn programming using windows APIs?

Love this idea.

Rightly or wrongly, people judge based on first impressions, and your landing page can cause frustration. First, your floating nav bar is huge on mobile, but nothing a zoom out can't fix. Second, the animated "Learn" hero isn't a constant size, causing the entire page to jump around while trying to read it. Again, can be fixed with zoom... but only with a lot of zoom, so that everything else is almost unreadable.

An OS that won't let you do what you want to do is malware.

It is indeed starting to feel like that.

> the same cows make milk

lol what?

https://www.merriam-webster.com/dictionary/milcher

Point was that coders are often valued by the amount of code they produced in the same way cows are value by the amount of milk they produce. I feel the usage of "coder" promotes this mentality

But it isn't true that "cows are valued by the amount of milk they produce" any more than "men are valued by the amount of code they produce." It's a false statement and a category error.

In fact, many cows are not used for milk at all. Some breeds make for great dairy; some breeds make for great beef; but few are great for both... Dexter cattle maybe.

(Nobody's out here clamoring for Black Angus cheese and absolutely nobody likes Jersey steak. While a Jersey cow or Holstein cow may be valued in part by the milk they produce, a Japanese Shorthorn or Belgian Blue cow is valued by the muscle tissue she produces and the genes that cause her offspring to produce similar muscle tissue.)

Your comparison is a category error. The trait "is valued for milk production" does not pertain to the superclass of "cows" but only to the subclass of "milchers."

"Coder" : code :: "milcher" : milk.

Thanks for the clarification there, but you are going on a tangent there. Point is that people are being valued based on metrics that make no sense.

Pointing that my specific example has some error does not detract from the main point and diving into the specifics of cow breeds or whether all cows are used for milk or not is irrelevant imo. The cow-milk analogy was just an example that could be replaced for any other.

There is nothing meaningful in this "update."

If anything, it's worse, in that they EXPLICITLY admit that they are getting kickbacks—“'monetary' or 'other valuable consideration'”—for providing your user information.