311 karma · joined January 5, 2012
Asteroids occupying these spaces in our solar system are called Trojans: https://en.wikipedia.org/wiki/Trojan_(celestial_body)
Additionally, Blue Origin and SpaceX have different goals from traditional aerospace firms that requires them to drive costs down below what a government would require. Blue Origin want to offer rides to space to tourists; for that, their costs need to be low enough for a person to buy a ticket. SpaceX wants to land their rockets on Mars, and then take off again. Being able to land the first stage of the Falcon 9 allows them to perfect the landing and reuse of rockets on Earth, before taking that knowledge to Mars.
I completely agree with this. I've downloaded some apps for blogs on my phone, but I realized that they just sit there in a folder, on a home page a rarely visit, while my RSS app is front and center in my dock.
Well, if using the definition of pop culture described in this article, pop culture evolves. Where countries drive on the road can be related more to how programming languages define blocks of code. C-like languages use curly braces to define blocks. This can be related to how since medieval times, horses rode on the left side of the road. More modern languages use different ways to define blocks of code. For example, Python uses tabbing and whitespace, Ruby uses the `end` keyword.
Continuing to use the traffic analogy, you don't have to use cruise control while driving on a long stretch of highway, but it's a lot easier to, and everyone else does. In the article, raganwald is talking about how coding conventions and techniques evolve over time. The analogy about driving in the UK vs the US is more equivalent to the syntactic rules of the specific language you are working with; it's the law which side of the road to drive on. You'll get penalized if you do otherwise. Using or not using cruise control is your choice, and so are naming conventions in different languages. Conventions evolve, even when the specific "laws" of the languages don't change as quickly, or at all.
At one point, they mention how when you pass a variable into a function, it only passes the value really, "copying" the variable, in a way. Then they go on to say that changing the original variable is talked about in chapter 5, which covers pointers. Then it just clicked. If you want to change the original value, pass a pointer to said variable. If you want to just use the value of a variable, pass the variable through the function.
It's so much easier than what I was doing before, assigning the variable to the return value of a function.