If you draw a line from Honduras through the rumored location of Atlantis in the middle of the Atlantic Ocean and then through the Congo where the lost city of Zinj is, it points directly to northern Australia, so there has to be another lost city there. Get your machetes out Australians and start looking!
You've just described half the drivers on the road! On their phones, eating, putting on makeup, READING shit. It's those people that are the dangerous ones.
Don't buy one now. High-dynamic-range television is coming, and a consortium of TV suppliers was announced at COMDEX recently. They will work together on coming up with a single standard for HDR. Netflix has also promised to deliver HDR content by year's end. It would be silly to buy a 4K panel that can only process rec-709 now when HDR is right around the corner.
We lived on a mountain in Virginia. When I was in second grade the neighbor kid and I would go hiking up the mountain, following streams and looking for waterfalls. I remember one waterfall we found, probably 70 feet high. We found a way to climb up the sides, got to the top, and found these big boulders. We'd roll the boulders off the top of the fall and listen to them crack on the rocks far below. We'd be out doing that all day long. Later we moved to a lake and I would just disappear for the day exploring the surrounding are. This was life in the country.
I recently got two take-down requests for two videos I put up on YouTube. They were both trade-show demo reel videos that I helped produce showing post-produced results in television shows and movies from software I wrote. These videos were 20 years old, but I thought it would be good to preserve them.
Paramount wanted one taken down for a 2-second clip from a Paramount movie. Someone else wanted the other taken down because I guess they owned the copyright on the music we had bought to accompany the video.
One could argue that putting these videos up was entirely fair use but I didn't argue at all and just yanked them. Not worth it.
One area where the C++ compiler optimizer excels is in the template compiler. When using templates, the compiler is free to inline pretty much anything, and if you have a deep enough template call tree, it can boil the code down into extremely tight instructions.
C++ doesn't "simply have too much overhead". Most C++ features compile down to the equivalent, or faster (sometimes much faster), C code. C++ being "slow" or having "overhead" is a common misconception, and quite possibly the worst argument against using C++.
Honestly, pretty much all of the "real" arguments I've seen against using C++ boil down to either "I don't understand it" or "I don't like it" or "why would anyone need anything other than JavaScript?". These are hardly faults of C++.
Programmers can be bad (or assholes) regardless of the language. I personally am thrilled that I've been allowed to shoot myself in the foot for 30+ years. It's made me a better programmer. I can't imagine being shacked to the incomprehensible mess that is Option B out of fear of what some bad egg might do to the api.
Option A is provably easier to type, easier to understand, and vastly more efficient to execute, usually optimizing down to a handful of vector instructions.
You don't have a single good reason why Option B is "better" except that you don't like C++, which really isn't a good reason. Let me guess - you also hate Python because of the indentation.
You can easily do automatic memory management in C++ using reference counted smart pointers. This allows you to control when "memory management" occurs when necessary, as is common in the case of high-performance applications (games, imaging software, etc) where C++ excels. The ability to overload operators allows you to write vastly more readable (and efficient) code than with Objective C. And in Objective C all method dispatches are effectively virtual, where in C++ you can control when you pay the cost.
Objective C is definitely NOT well-suited to solve all the same problems as C++. It's fine that you don't need to write high-performance (or portable) applications, but sweeping generalizations like this just show your ignorance.
Disclaimer: I use C++, Objective C, and Python on a daily basis.
Maybe it's not part of C++ because this kind of initialization is trivial to do, and more readable, with helper classes and constructors. Just a theory - I wasn't even aware of designated initializers.
What I find pathetic is all of the C programmers who still think C++ is slow, bloated, or impossible to understand.
auto definitely makes writing looping constructs with iterators shorter/easier, without additional typedefs, but by far the nicest use for it is in writing templates, where a specialization or type-dependent mapping my occur in the template using a helper function, and you don't necessarily know what the intermediate type might be. Sure, you could use some complicated typedefs, which may require additional traits classes, but auto handles it nicely.
Slashdot Mirror
I clicked on it and it's working for me (300Mps fiber helps).
But the video quality looks like crap on my 2010 MacBook Pro. Clearly 8K technology is not quite ready for prime time.
If you draw a line from Honduras through the rumored location of Atlantis in the middle of the Atlantic Ocean and then through the Congo where the lost city of Zinj is, it points directly to northern Australia, so there has to be another lost city there. Get your machetes out Australians and start looking!
You've just described half the drivers on the road! On their phones, eating, putting on makeup, READING shit. It's those people that are the dangerous ones.
Don't buy one now. High-dynamic-range television is coming, and a consortium of TV suppliers was announced at COMDEX recently. They will work together on coming up with a single standard for HDR. Netflix has also promised to deliver HDR content by year's end. It would be silly to buy a 4K panel that can only process rec-709 now when HDR is right around the corner.
What happens if the doomsday clock sees its shadow again?
We lived on a mountain in Virginia. When I was in second grade the neighbor kid and I would go hiking up the mountain, following streams and looking for waterfalls. I remember one waterfall we found, probably 70 feet high. We found a way to climb up the sides, got to the top, and found these big boulders. We'd roll the boulders off the top of the fall and listen to them crack on the rocks far below. We'd be out doing that all day long.
Later we moved to a lake and I would just disappear for the day exploring the surrounding are. This was life in the country.
I recently got two take-down requests for two videos I put up on YouTube. They were both trade-show demo reel videos that I helped produce showing post-produced results in television shows and movies from software I wrote. These videos were 20 years old, but I thought it would be good to preserve them.
Paramount wanted one taken down for a 2-second clip from a Paramount movie. Someone else wanted the other taken down because I guess they owned the copyright on the music we had bought to accompany the video.
One could argue that putting these videos up was entirely fair use but I didn't argue at all and just yanked them. Not worth it.
One area where the C++ compiler optimizer excels is in the template compiler. When using templates, the compiler is free to inline pretty much anything, and if you have a deep enough template call tree, it can boil the code down into extremely tight instructions.
C++ doesn't "simply have too much overhead". Most C++ features compile down to the equivalent, or faster (sometimes much faster), C code. C++ being "slow" or having "overhead" is a common misconception, and quite possibly the worst argument against using C++.
Honestly, pretty much all of the "real" arguments I've seen against using C++ boil down to either "I don't understand it" or "I don't like it" or "why would anyone need anything other than JavaScript?". These are hardly faults of C++.
I suspect that a lot of them were just vacuous celebrities whose publicists arranged to get them a ticket at a discount, as a PR stunt.
Oh come now! No need to be so harsh. JUSTIN BIEBER is on that list!
why Apple would make a change that impedes legibility, requires more screen space, and makes the GUI appear fuzzy?
You're viewing it wrong.
I was going to swing by West Central Africa on my way back from my vacation to Syria. Thanks for the warning!
We'll have to agree to disagree then.
Nobody writes math like Option B, unless they are forced to.
If someone wants to do this:
Vec4 operator+(const Vec4 &lhs, float scalar) const
{
reformat_hard_drive();
return 0.0;
}
Well, they're an asshole. That doesn't prevent the same asshole from doing this:
- (Vec4 *)multiplyScalar:(float)scalar
{
reformat_hard_drive();
return nil;
}
Programmers can be bad (or assholes) regardless of the language. I personally am thrilled that I've been allowed to shoot myself in the foot for 30+ years. It's made me a better programmer. I can't imagine being shacked to the incomprehensible mess that is Option B out of fear of what some bad egg might do to the api.
Option A is provably easier to type, easier to understand, and vastly more efficient to execute, usually optimizing down to a handful of vector instructions.
You don't have a single good reason why Option B is "better" except that you don't like C++, which really isn't a good reason. Let me guess - you also hate Python because of the indentation.
Which do you think is more readable?
Vec4 a = 1.0;
Vec4 b(2.0, 3.0, 4.0, 5.0);
Vec4 result = matrix * a * b / 10.0 + 0.5;
or
Vec4 *a = [[Vec4 alloc] initWithScalar:1.0]; ...
Vec4 *b = [[Vec4 alloc] initWithX:2.0 Y:3.0 Z:4.0 W:5.0];
Vec4 *result = [matrix multiplyVec:[[a multiplyVec:[b multiplyScalar:1.0 / 10.0]] addScalar:0.5]];
[result release];
[b release];
[a release];
Personally, I prefer the first one.
You can easily do automatic memory management in C++ using reference counted smart pointers. This allows you to control when "memory management" occurs when necessary, as is common in the case of high-performance applications (games, imaging software, etc) where C++ excels. The ability to overload operators allows you to write vastly more readable (and efficient) code than with Objective C. And in Objective C all method dispatches are effectively virtual, where in C++ you can control when you pay the cost.
Objective C is definitely NOT well-suited to solve all the same problems as C++. It's fine that you don't need to write high-performance (or portable) applications, but sweeping generalizations like this just show your ignorance.
Disclaimer: I use C++, Objective C, and Python on a daily basis.
He was being ironic.
Or the ever popular Minecraft-themed Bag of Glass.
Good point!
Maybe it's not part of C++ because this kind of initialization is trivial to do, and more readable, with helper classes and constructors. Just a theory - I wasn't even aware of designated initializers.
What I find pathetic is all of the C programmers who still think C++ is slow, bloated, or impossible to understand.
auto definitely makes writing looping constructs with iterators shorter/easier, without additional typedefs, but by far the nicest use for it is in writing templates, where a specialization or type-dependent mapping my occur in the template using a helper function, and you don't necessarily know what the intermediate type might be. Sure, you could use some complicated typedefs, which may require additional traits classes, but auto handles it nicely.
I should have a put a smiley.
And then he went on to write Facebook. I'm not sure I like this guy.
Okay okay I'll get off your lawn!
Yikes! Put your clothes and phone in a burn barrel and take a shower immediately!