Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Re:My experience: Google vs Amazon (Score 1) 215

Big O is an upper bound, big Theta is both lower and upper bound. So, big Theta(x) always implies big O(x).

Most people don't bother writing big Theta, because you usually don't care that much about the lower bound. If you want to use those terms, you should know what they actually mean. Saying that something is big Theta(1) or big O(1) is useless if you don't know what that means.

Comment Re:commercial vs volunteer free (Score 4, Insightful) 194

Just because Wikipedia is not for-profit doesn't mean the same rules don't apply.

If a commercial encyclopedia is not good enough (what you describe as "accuracy and reliability reputation"), it means people won't buy it and so the publishing company will go bankrupt.

If an open encyclopedia like Wikipedia is not good enough, it means people won't visit it. And that means nobody will edit it and nobody will donate to it and so the publishing organization will have to close down. And even if it would technically keep running, no visitors and no editors means it's a dead project anyway.

Either way, if an encyclopedia is not good enough, it will eventually go down. It doesn't matter whether it's made for profit or not.

Comment Re:java backend is not simple. (Score 2) 138

Maybe that would be a good idea in an ideal world. But in reality, such behavior would be deeply confusing for people who know C, C++ or Java. And I think that "it should be easy to write correct code" applies to people who already know another language too.

Also, from my experience, fall-through is not that useful anyway. I don't think I ever wrote code in C# where it would be useful. Having two cases for the same code sometimes is useful, and C# does support that.

Comment Re:java backend is not simple. (Score 3, Interesting) 138

That's interesting. The creators of C# have a somewhat similar philosophy: they say that they would like it to be a "pit of quality", it should be easy to write correct code. But that doesn't mean they removed features that can be abused.

As a consequence, the things you mention (pointers, gotos, operator overloading) are all included. But for example in the case of pointers they are "hidden" (they have to be in an "unsafe" block).

On the other hand, for example fall-through switch cases are not allowed in C# at all, they thought those are not worth all the bugs they cause.

Comment Re:Android (Score 2) 351

But it's not just about writing. Reading is at least as important. And you need to read thought a lot of noise to get to the signal if you're using an anonymous class.

Slashdot Top Deals

There are two ways to write error-free programs; only the third one works.

Working...