24 karma · joined September 25, 2016
Thanks, agreed. On the last part though, it doesn't hurt to explore, a lot can be learned in the process alone, outside of actually finding anything.
Indians had no trouble crisscrossing America.
http://www.cfr.org/defense-budget/trends-us-military-spendin...
Asteroids, since I assume they move and possibly in odd orbits might be difficult to reach in emergency situations, I'd rather not see any nation's Astronauts stranded on a remote asteroid.
Embrace, extend, extinguish is how it always plays out.
Add more nodes. Scaling is not difficult.
[But ask yourself: how does your car's engine work?]
Today kids learn Java in High School and carry powerful computers in their pockets and on their wrists. I'll probably be pushed out of the Java industry before I even retire by one of them.
I'm curious why those states?
Replace JavaScript with Java in all browsers and make it much easier, dependable, predictable and reliable.
That's a rather condescending thing to say and not accurate or supportive of the view of git you seem to hold.
> The truth is commands like filter-branch, rebase, cherry-pick, etc. which are notoriously difficult to use... you don't even have to use them.
Until someone on the team _does_ use them and then things can become messed up in ways it takes a git expert to figure out how to fix. I've used git for several years and had never even come across filter-branch, I'd have to chase down the git docs to see what it even does. I never had to filter anything with CVS, Continuus, Perforce, SourceSafe or Subversion.