1,257 karma · joined August 29, 2011
(The alternative is to refuse to build new housing or do any reasonable urban planning out of resentment towards newcomers, and then watch in frustration as traffic becomes even worse, housing prices continue to skyrocket, and you have rapidly rising homelessness and crime. The same way most cities in California handled this situation.)
Uh, yeah. All the time actually.
Nobody used the term "open source" before it was deliberately invented. There was plenty of software in the 80s and 90s that we could retroactively call "open source," but nobody used that phrase at the time. The phrase "open source" was specifically created in 1998 because the term then in common use, "free software," was too generic and people were confused about what it meant. So a new term was created for the express purpose to have a term with no prior meaning so that a specific meaning could be assigned to it.
You seem to think that because "open source" is a phrase you see a lot, it's a generic phrase that was always used informally and grew out of natural language. But that's not the case. It's a term of art that was artificially created with a specific meaning.
Recursion uses space on the call stack. The concern is not so much that you'll be using more memory, it's that the call stack has a fixed size and you might blow past that size, which will cause your program to terminate.
The comparison between recursion and "nested for loops" seems a bit off - generally it's recursion vs a single loop.
Whether it's best to avoid recursion depends on many factors. In any case, even when I do want to use iteration, it's often easiest to first formulate the algorithm as a recursive one, and then change it to use iteration.
Your argument is roughly equivalent to this one: "I can call this random cereal Cheerios, because language evolves and neither you nor General Mills decides how people use language."
If a project wants to do something different, and develop an "open project" under some terms that aren't open source, they are free to do so, but they shouldn't call it something it's not.
It honestly makes me feel a little nihilistic about versioning and upgrades. I know there were many legitimate technical challenges for many people in moving from Python 2 to 3. But I now feel that versioning is always going to be bumpy, regardless of the technical issues, because a substantial number of users will make strange decisions.
Contrast that with the topic of the article at hand, which is a solution for a non-problem and serves no purpose.
For me it's kind of the converse issue. I watch 2 or 3 videos on a topic and then YouTube thinks I'm obsessed with that topic and nothing else.
Yes, one is that a lot of people want to live there. That one's inevitable though. Some places are more desirable to live than others. I don't want to live in a small town with nothing to do.
The other factor is when a city refuses to build sufficient housing. This one is not inevitable. It usually comes about due to entrenched interest in the value of existing housing. For instance, north San Jose has built no new housing in a decade, despite a well known housing crisis.
Although it’s interesting to think about how software could help with branch prediction, the simple answer about the kernel thing is that software is the wrong place in the architecture for branch prediction to happen. Maybe there’s some crazy alternative way things could be done, but in anything like the current computing model branch prediction has to happen in hardware.