On the contrary, 4Mb/s is almost certainly not enough (by the time you take into account contention etc) to stream video. Something like netflix will not work over that, and frankly, I expect any definition of broadband to include the ability to use a video streaming service.
There's no particular reason to not have comparable values of different types
Sure there is - they have different types, therefore they're not equal. It's a ridiculous, useless operation, because it doesn't actually do anything more than always return false.
That said, there's good reason to have an "isSimilarTo" function, but that's not at all the same thing as equality.
No, ultimately, their job is to carry passengers. That means they need to offer enough space for a passenger to sit in. The airline's only choice is to not shrink the seats any more. This may of course mean price increases for all seats.
Even if it were the original code. That would mean that the modder is the one violating mojang's copyright, not the reverse.
Actually, compiler theory is a great example of a language you can't easily learn in any language. The small lightweight structures it generates, and the referentially transparent transformations that you run those structures through lend it strongly to being done with functional languages, and if not, very close to the metal languages like C. Heavy weight OO languages tend to end up just causing you to write 3 tons of boiler plate, rather than actually learning the theory.
In Python you write "a?b:c" as "b if a else c". I think that is pretty obscure, and hard to read too.
You shouldn't. You should (in all languages), explicitly convert the type, and then compare things of equal type. For bonus points, you should only use languages that enforce that the arguments to == are of equal type.
What you just wrote is a strong indicator that you have no clue how much undefined behavior you have in your programs, and just happen to be getting away with just now.
Null-terminated strings were considered superior to using a length because they allowed strings to be > 255 bytes long (using 16 bits for the length would allow longer counted strings, but at that time with 4K of memory nobody in their right mind would suggest wasting a byte like that!).
Null-terminated strings also have the nice property that getting the "tail" is a very fast operation, since you just return a pointer to the middle. This meant that searches could return strings, rather than indexes. This then meant that every function that worked on text only needed one argument, a string, rather than two (a string and an index). The savings due to this were pretty significant.
Of course it makes sense. They can either cut their losses now, and leave with their profits. Or they can be sued into oblivion by Twitter, and let them, and the lawyers walk off with their profits.
I was talking about the pre-lambda stuff in std and boost, especially std::foreach.
C++11x did in fact fix a lot of this and I certainly use the new syntax.
I wouldn't say that learning to code necessarily outweighs a degree. But I do think university courses are too heavily focused on theory, and not enough practical application.
The job of a university is to teach theory. These are not vocational collages, they are universities. The practice is meant to be something you are more than capable of teaching yourself if you're any good at the subject.
No, exercise is not it. I mean, it does burn calories. But it's far harder to get thin by exercising more than it is to do so by eating less.
For example, even a relatively fit person will walk at 4-5mph at most. At that speed, they'll do about 10,000 steps in an hour. That's one hour to burn a whole 400 calories. If they run, they might make that half an hour, but that assumes that their cardiovascular system is up to running for half an hour straight, which lets face it. No fat person's is.
Alternatively, they can make the same dent in their net calories for the day by simply not eating one chocolate bar.
Exercise is great for you - but it's great for getting fit. Not great for getting thin.
That's kinda the point. No, humans don't need carbs. We did not evolve eating carbs, and we don't really gain anything very much by eating them (other than a craving for more of them).
If I still had mod points, you'd get a +1. Intel motherboards are great. They're nothing fancy pants, but everything that's on them is solid and well supported.
This file will self-destruct in five minutes.
