498 karma · joined January 3, 2016
Then again, GPL v3 is on many people's danger list
Sure, but that only rules out a reimplementation of React. The question most people face is "React or existing alternative X?". If your chosen alternative is still actively developed, it's probably notably different from React in concept and implementation (why else would it still exist).
Now if Facebook owns any react-related patents, you use all of them by using react, your alternative has a good chance to be sufficiently different to not be infringing.
In terms of your chances of using Facebook patents, any alternative is strictly better than React itself.
The biggest issue I can think of is oil running out, but we're on a good trajectory to solving that. Other resources seem either abundant or replaceable. The threat of global nuclear war is problematic but not really solvable by throwing more people at the problem. Overpopulation isn't projected to be a problem. Climate change will be a major inconvenience and costly, but unlikely to be an existential issue.
Of course there's lots of injustice, hunger, disease, murder and torture that would be nice to resolve, but it's not an existential issue for humanity.
First provider I checked has a multiple server offerings with quadcore i7-6700 and 64Gb DDR4 RAM for 39€/month [1].
1: https://www.hetzner.com/dedicated-rootserver/ex41s?country=g...
The closest is uncompressing it and counting and immediately discarding the bytes in the output stream.
But of course the proper defense is to give up if you exceed a predefined memory or time budget.
You can say that about almost anything. I'm at liberty to murder my neighbor, I just have to accept the price.
I guess they meant that not every compound word is one that Germans actually use (as you would expect when somebody claims "it's a German word"). But you can totally make up words on the spot that every German will understand
If you integrate washing machine and dryer into one mashine, the cost-savings from electricity would be even bigger with very little convenience lost.
Unlimited in the computing world usually has practical limits many orders of magnitude above normal usage, making outliers much, much more expensive. But you can't substantially increase the price because you can't afford to lose your normal customers and be left with only outliers.
Then again in a lot of office applications that is irrelevant, meaning paper is of little use to them.
Of course there's other reasons to employ people (parent mentioned spending power, I would add political influence to the list). But the labor part of the employment decreases in value.
That's the kind of thing you usually hear from dictators. I hope she remembers to give citizens the same rights online and offline, not only the same restrictions.
Only in a very restricted framework. If one side goes out of business and one side only makes a minor gain (and lots of remaining competition exists), that is obviously not zero sum from any perspective
In my eyes it is simply a factual description of an architecture: the master gives commands, the slave obeys. The slave doesn't act without permission from the master and only speaks when spoken to. I wish no such thing for any human, but it describes a great architecture for software and hardware.
And when I can see how many people liked what I shared, that seems like a reasonable metric to optimize what to share
From the pedantic viewpoint the quote may be true, but then it doesn't say anything useful anymore.
>NUMBER = atoi(argv[1]);
argv is populated at runtime based on what the OS passed you.
But you are right if you meant that my statement is too strong: you can't do arbitrary loop unrolling. You can jump to a loop that's unrolled once if the number is even, etc.
There are certainly also optimizers that will just output the input without any loop, but that's beyond anything I would expect of a current production compiler.
But assuming his CPU takes one cycle for an addition and one cycle for a conditional jump, his CPU only needs to run at 1GHz to achieve his result.
Given that branch prediction should be nearly perfect for such a simple and short loop, modern x86 CPUs doing at least 4 integer additions per cycle, and typical CPU speeds in the range of 2-4 GHz, a properly optimized version should be nearly an order of magnitude faster.
So either more aggressive compiler flags and maybe SIMD intrinsics, or hand written assembly (easy here, not so easy in the real world)