Checking and handling all possible error conditions is a GOOD thing.
630 karma · joined October 15, 2012
Checking and handling all possible error conditions is a GOOD thing.
rimantas is referring to using open source in a cloud service, not authoring and distributing it.
http://www.guardian.co.uk/world/2013/jul/11/microsoft-nsa-co...
e.g. The "Order Now" button on your first banner links to this page: http://www.balsamicsauce.com/collections/frontpage/products/... which is a 404.
If you have a point to make, please try doing it without blatantly lying. It's common knowledge that the US has substantially higher corporate tax rates than almost anywhere else:
http://www.guardian.co.uk/news/datablog/2011/feb/21/corporat...
Technically: if the browsers were somehow phoning home, even if the data were highly fuzzed, I'm sure there would be guys like tpatcek who would manage to detail, if not the content of the tracking, at least the amount of data sent and the targets. I don't recall there being such a scandal in recent memory.
Most of the time, yes. Some lottery games with fixed odds and variable payouts have rare moments when the expected value of a ticket turns positive. I'm fairly good at math and I always play powerball every one or two years when this is the case.
That said, I'd be hesitant to bring up Revel's session as a positive. It shoves everything into a cookie instead of using the cookie token as a key to a serverside data store. Not only are you limited to 4k of session-local storage, but you're sending the entire payload across the wire for every single request. This is absolutely stupid and needs to change. I'm sure Rob is boxed in by limited time, and this is not intended for production use yet, but holy god, it's by far the worst thing about the framework.
"Could someone explain what problem Play/Wicket solves? Java and servlets already has http, StringBuilder, and trivially created threads. What is Play/Wicket adding?"
What it's "adding" is the 8432579842375 hours you don't have to spend writing your own routing, template-loading-and-management, and logic separation code.
EDIT: Your #2 is a strawman. "revel run" mode statically compiles all files and dependencies if the timestamp changes. It's not even remotely comparable to PHP. Just because it has a friendly error message doesn't mean revel magically dispenses with static type safety.
Are there browsers where virtual pixels are not automatically scaled on retina displays?
The initial audience of the site was, ergo, primarily windows developers. As popularity grew, more developers from the broader community showed up, driving the proportion of windows questions down.
And yet, the "establishment of a dictatorship of the proletariat" in the history of communism's spread, without a single exception, has been accomplished at the barrel of a gun, with extraordinarily bloody results.
And then there's the starvation purges of entire regions of huge populations of people.
Oh, those wily leftist fringe thinkers and their peaceful ideas!
1.0 is supposed to mean production-ready. Are you suggesting this should be a 0.7 release?
http://en.wikipedia.org/wiki/Mike_Gogulski
Always annoying when Wikipedia is wrong about everything.
You're more than welcome to help make laravel look better in these benchmarks. But unless you're running the PHP through HipHop, I doubt you're going to get anywhere near the statically-compiled platforms near the top.
http://www.techempower.com/benchmarks/
Would be nice to see similar benchmarks using a framework that doesn't resemble a honeypot's tarpit.
You're probably doing something wrong.
Go tops the techempower benchmarks for concurrent db access and page rendering, and for pure math performance, it has an average case performance of 17% slower than Java( highly dependent on problem chosen of course )
refs:
http://www.techempower.com/benchmarks/
http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?t...
Bread and circuses are far cheaper today than in ancient Rome. It doesn't take much.
There's nothing to see here, people. The participating companies are not actually participating at all, and a damage control press release is absolute, unquestionable confirmation of this fact. Nothing is more truthful than a press release.
[1] http://www.treasury.gov/resource-center/data-chart-center/ti...
Why I will never take seriously foreigners' reactions to our wars, surveillance, human rights violations, etc:
You people, and the governments and central banks who represent you, keep buying our debt and financing all of this. The US Government would be incapable of funding these programs and wars at low cost without YOU stepping up to the plate every single auction to buy up our treasuries at ridiculously low yields.
I'll believe your outrage when I see action behind it.
I think the Go designers wanted the language to be approachable for people who habitually use null to indicate meaningful state. Multiple return values offer a way out, while still allowing newbies the option to abuse nil. (although, sum types would be nicer)
I think on balance, getting people from the 1970s to the 1980s who otherwise would not have gone there is a positive thing. Even if it's not the ideal thing.
It's not out of the question that Go will make your suggested fixes once it acquires enough mindshare.
- Lack of generics (this will be resolved in the future)
- nil exists
- interface{} is a *void style type safety loophole
These are all very minor issues, but the Go haters just love to harp on them. 99% of the time, I find they hold up ml-style languages as some sort of Holy Perfection. (lulz)