Have they realized their cost savings yet? Or are the teardowns and smaller redesigns still keeping the launch price up? Basically, are we in the future yet?
Well it was a continuation that would have happened with or without the Germans, but they had made significant gains that we're a natural fit for the aspirations of the two blossoming superpowers at the time. The difficulty in getting to the moon was so vast that the statement that only Germans did it was just strange. German knowledge was a key part to a very large rocket initiative. It was going to happen, but faster with German help. By the way, it turns out that all the money the Germans spent on the V-2 was wasted since it took money from other programs that might have helped them with the war effort. So one could say that spending it on rockets was a bit premature.
The Germans had copied Goddard's, an American's, liquid rocket design and expanded upon it. These are Von Braun's words when speaking about Goddard: "His rockets ... may have been rather crude by present-day standards, but they blazed the trail and incorporated many features used in our most modern rockets and space vehicles"
also:
"He once recalled that "Goddard's experiments in liquid fuel saved us years of work, and enabled us to perfect the V-2 years before it would have been possible"
And if you don't believe me, here's Goddard's patent for a liquid fueled and a multi-stage rocket. Exactly what put a man on the moon:
There's nothing objectively wrong with a large company unless they begin to squash competition with regulatory lock-in. This is what led to the breakup of AT&T/Bell. As far as I can tell, Google doesn't keep others out of the search market through any other means than just being better than the other guys. Correct me if I'm wrong, but I certainly haven't seen any shortage of search engines and alternative cloud services providers.
Notably some of them like the Millennium Prize offer a reward of 1M dollars if you solve it. There's definitely still some absolute mysteries out there!
You are correct in that this does not use propellant, however the Earth would need to be nearby for this to be viable for any sort of space travel. Perhaps maybe keeping a satellite in orbit or doing orbital maneuvers, but even then the amount of thrust is so small that it would likely not be usable. So unless the review team comes back and says they've eliminated magnetic interference then we're probably back to square one.
After further review I believe they found that for the EmDrive, the thrust was being generated by interaction of the electricity through the cables with Earth's magnetic field. Someone tested it by dampening the actual microwaves and still getting the same thrust result, which eliminates the microwave cavity as a source for the thrust. However the follow up test was with very low power, so they wanted to run it with magnetic shielding and higher power to fully rule it out.
Very unlikely. They probably account for things like absorption when calculating redshift and the corresponding numbers that they're getting from their measurements. For instance, each star/galaxy has a spectral composition that can indicate what it's made of. This can be correlated with brightness for other stars and can be determined how bright it should be. Redshift would shift the entire spectral composition towards the red, while absorption would remove certain bands. There's probably many other ways they've verified redshift too that I'm not thinking of.
You're not wrong. This is a Rust post after all. I'm of the opinion that C++ by itself is both unfinished and bloated at the same time. Most memory access should be funneled through libraries better equipped to handle memory than our feeble minds, and when we really need the performance, we know when to break out of the cage and get things working. Most of the problems I've encountered in C++ is interpreting the crazy stuff other developers have done, because alas C++ has allowed it! Funny enough, the object oriented nature of the language has been the biggest thorn in my side. You'll get no shortage of complaints by me of how C++ is designed. Somehow I manage to forgive a lot due to the incredible performance of the code a C++ compiler generates.
Certainly willing to give it a try. I can say that I can't imagine any tagging system to be any better than CDT, so at best it may be comparable. Though if the system is comparable with an interface that's faster than Eclipse, it would be quite nice.
Generally Java has a large footprint on the machine and startup time can be slower (however they're attempting to solve through the Graal VM). Also Java's syntax is extremely verbose and the API usage is verbose as well. All common complaints coming from a C++ programmer. When comparing programs for daily use, native applications tend to feel snappier, though there's no reason a Java program can't feel that way if properly written.
I like Java for the comfy warm embrace that a business language provides, but C++ wins out in the world of 'get out of my way and let me get stuff done'.
After using Eclipse for C++ (CDT) off and on for a while now. I've come to the conclusion that when set up properly there's no better C++ tagging system (F3 Open Declaration) and auto-complete in any IDE except perhaps Visual Studio. It works so well that people like myself who dislike Java still use it on C++ projects out of the sheer advantage it gives you when browsing through a code base. I don't know what they've been up to there on the CDT project, but they sure have managed to get it right.
Heck YEA. Get shit DONE. I've watched projects go in reverse because of process. I've watched people waste 5 hours a day in scrum. It's so corrosive, addictive to the scrum master/leads who benefit from tossing around their opinion, it favors the worst performers, isolates the best.
Handle process in a case-by-case basis. If something needs changing, change it, but move on and GET SHIT DONE. That's the only way to go. I don't care what people say, good programmers don't need to be babysat.
Do you mean West facing? If you had a large East facing exposure then it would give you that pulse of blue light in the morning. I've got a big East facing exposure and don't have any issue with blue light screens. Watch TV every night before bed. No problems.
Ah I'm following now. Transfer of stack references in cases where it's unnecessary to share objects. Actually interesting that it raises the bar for the need to allocate on the stack.
I'm still having trouble seeing how move semantics and copy elision help me get rid of smart pointers. I read up on it after reading these comments and just still am not following. I see how move semantics avoid a copy, but if I'm dealing with cases where multiple objects need to use or hold a reference to the same object, how can move semantics help me do this? Seems good for ensuring only one object contains the reference.
The takeaway from this is that management defines reality. Opinions and objectivity goes out the door if management doesn't like the decision. This is why a clear chain of command is vital. Humans need it to function in groups if the group is to stay together as one unit.
I'd like to think so, though wouldn't dynamic typing insist branching would still be possible so there's still likely some runtime checking before being sure a precompiled bit is valid. All fascinating stuff.
I'm no hacker. But if I were I'd first hack North Korean servers, then use those servers to do all my outward hacking. This would ensure no cooperation of authorities and no traceback. North Korea is essentially a black hole for hackers to launch their attacks from. Not sure why people think this third world country is fostering the creativity and science and engineering background necessary for the hacking that's attributed to them.
There is more time in the summer because of the angle of the Earth to the Sun. Can see the effects even more when at high angles like closer to the North Pole. And to boot, Daylight savings makes it even more pronounced.