It's tax policy, plain and simple. Stop paying taxes and you'll get richer, relative to those paying taxes. All the communication and technology changes have made it much easier to evade taxes. That and government complicity.
For the last 40 years, we were promised a better living standard in exchange for lower taxes. It backfired. We forgot about the vice that has no bounds - greed. That's why we have to set limits. Paul alludes to the correct and only solution - make tax rates so high to discourage accumulating wealth beyond a certain point.
It's a wave, but the wave has crested. Tax rates will rise, the loopholes will be removed, and the existing tax laws will start to get enforced. Too bad, it could have been different.
To suggest that "Planned Parenthood provides fetal tissue samples from abortions to scientific researchers" is even remotely true is, well, sad. I saw the videos. That's some sick stuff. If this is one of your arguments for objective science, then count me out.
I agree that these are interesting services. But please, do some simple math. The prices climb astronomically even for relatively low rps. It's only useful for small services at this point.
Here are the costs for a 50 rps lambda function served by API Gateway for one month:
Requests = 50x60x60x24x30 = 129,600,000 request per month
API Gateway Costs = 129,600,000 x 3.5/M = $453
Convert the requests to GB/s at 512M and 100ms requests, we get:
129,600,000 x 512/1024 * .1 = $113
$453 + $113 = $566/mo for 50rps. Please note the .1 multiplier. For every 100ms increase in your request time, add another $113. So for a 1 second request, you get $1130.
This doesn't even count other machines you need to run to handle databases, etc, it's for the most bare vanilla request.
For a simple lambda function with no external servers, you can easily serve 50rps from a micro for $9/month.
Do some math. It's expensive. 100 r/s for one month is about $900. Plus your bandwidth and EC2 charges (unless your using Lambda). For simple Lambda functions, you can get 100 r/s on a micro for $9.
The main reason I felt Scott A. (and company) lost the debate is because he could not point to a single experiment that actually uses qubits to do a calculation above a very small threshold. There is much written about experiments that seem to show entanglement of multi qubit systems, but none of them actually do any calculations with the qubits.
Brady and Anderson's point is that it's not a qubit until you can calculate with it. And their theory suggests it will get exponentially harder for each qubit above 4 (I think), which throws out all of the interesting quantum algorithms.
I also felt Brady and Anderson silenced every objection. After one or more of their rebuttals, they were no longer challenged. The most recent post about Feynman is also interesting.
If you are in the US, look into getting a provisional patent. It's an extremely inexpensive way to get some protection for a year before having to file a full patent application. You can file a provisional patent yourself online for $60 (for a 'small entity', last time I checked).
You'll need to spend a little bit of time learning how to write a patent description. It's a tedious (rather than say, hard) thing to do, but is a great skill to learn anyway.
Once you get the hang of it, getting a provisional patent for any or your ideas is quite easy. Then you shouldn't have any qualms about divulging any aspect of your idea to anyone.
You can legally say that your idea or product is 'patent pending' with a provisional patent. This may sound silly to some, but will definitely sway a serious investor. Like them or not, patents are powerful.
As I said, this buys you a year. That should be enough time to determine if the idea is worth the time and expense to obtain a full patent.
What qualifies Gradberry to be the vetters (candidates are "vetted by the Gradberry team"). Because the founder is a "nerd". Another stupid power play.
Why should we applaud an obvious ionic ripoff? Add a few bells and whistles and try to claim credit for the great performance of ionic? Hide it all in the cloud? Big deal.
I can't believe I read most of this article only to realize it's an advertisement for the authors js framework. I'll throw in my 2 cents anyway.
I've used angularjs, and like it quite a lot. I'm not a lover of magic, but I think the dependency injection in angular is 'controlled' magic, and saves you a ton of boilerplate. The biggest drawback to angular is there are too many concepts to know. With a little thought, I think the developers could easily trim down the number of concepts you need to know to be productive.