Typeless variables are a delusion, they're just guessing what type they should be for you.
MangoCats
joined 2 years ago
That's year-month-day hour:minute:second.millisecond +/-TZ, you heathen!
The choice doesn't matter - consistency does a bit.
Once you blast the lawsuit into the press your software gets better known. FFmpeg was fairly well known before it got hijacked and stuffed in every set-top video decoder box on the planet, but now it has that reputation as well.
Certain areas of law have provisions for this, others don't. GPL law tends toward the not very lucrative side of things. What are your monetary damages? Well, I was going to make $0, but they broke my terms so now my GPL software is better known but I still make $0 - compute damages please?
Both parties virtually paved the way for jobs to leave the country - it didn't benefit the majority of their constituents.
I knew a guy who left Detroit at 30 to install A/C systems in Florida, made good money but by 40 he was tired of crawling around hot attics, so he went back to school, learned to code and went back to Detroit to work software instead of the factory floors... he did alright, didn't set the world on fire, but also didn't retire to an early grave with health problems from breathing fiberglass in 130 degree confined spaces.
It was true around the .com boom, and the advice might have been good for a few years, but like everything else: following yesterday's trends will get you lost in a crowd of the clueless and under-informed.
In the late 1990s our MSCE graduates were starting at $70K which is easily in six figure territory today when adjusted for inflation.
Six figures is far from what it used to be.
Only if you can afford better lawyers than they can.
I tried to use C++ in 1991 but the Borland Turbo C++ compiler was too buggy, so we used C instead. By 1996 C++ was "ready for primetime" on IBM-compatible PCs (yes, they still called them that, sometimes in 1996) and I switched - for 30 years.
I just spent 10 days building a proof of concept in Python, all the "common wisdom" says that was the fast way to get it done. Now that the prototype is done and the (initial) user feedback is addressed, I'm running a port to something better for lightweight, performant, easy deployment... sadly, C++ isn't even on the radar for potential targets - top 3 candidates were Go, Rust and C#. I can't abide the C# ecosystem, and Rust is just a little too rigid and immature for my tastes, so here we Go... anticipated to take 50% longer to port from Python than the Python took to develop in the first place... we shall see...