forgive me my rant, but when I see "just install it with cargo" I immediately lose interest. How many GB do I have to install just to test a little tool? sorry, not gonna do that
I don't think so? The PDF includes "today (2009)", and also "started in 2004". It's been featured on HN before.. as far back as 2009. Unfortunately the archives first caught the (same) text in 2021, so that's not helpful.
I played kind of the same thing a little while ago. I and a friend wanted to watch a movie, "Blast of Silence" it was called. We met in the bar two people, one of them I knew, the other one asked what we were about to watch, I answered "Blast of Silence", pronouncing it completely wrong (our mother tongue is some sort of German), she thought I made a joke and I told her with a completely straight face that I didn't learn English in school as I was going to a very basic school. I had to completely rely on the subtitles. She was a little bit embarrassed to have brought it up. moral of the story: you have to play dumb convincingly then you can have a little bit of fun
considering that they have still Russinovich and Raymond Chen in their midst it shouldn't be too hard to have a two week boot camp for those who write programs for the OS
my guess is many junior developers without guidance and perhaps a little vibe coding. could be that these new developers are not comfortable anymore with C++ and MFC so they use what they learned in their courses directed at web standards
Sounds like bullshit, I'd rather bet that Microsoft wanted to make some Cloud OS, web friendly thing and expected it to be as successful as Visual Studio Code
Also, I don't think that integrating react app into Windows is trivial
"contaminated by GPL/LGPL code"? really? if you want to make profit off of your code buy for several thousands of dollars commercial libraries and you are in the clear. if you don't want to pay for libraries you have to accept their conditions
I usually prefer releasing under Apache 2.0 license, as I can't predict what people will need 10 years from now.
People use LGPL libraries in commercial software all the time, as the shared objects (.so) do not contaminate the source application license. The instant someone static links LGPL/GPL lib into an application binary its source also must carry a compatible open license. Note this obligation differs from publishing patches back to the main lib branch.
It gets messy when people release libraries under multiple licenses. Porting games and applications from *nix systems can be non-trivial. Best regards =3
reply