1,240 karma · joined June 7, 2012
Everyone believes this before and while it is actually happening. The US already has literally all required elements. All that is missing is scale.
The US gets away with much of what it does because of the enormous US market. But at some point other countries will realize that the cost of that market has gotten too high and then a large chunk of the the US' power will dissolve.
Obviously you couldn't get that many people to allow themselves to be tortured to death to prevent future enslavement, but the thought exercise makes it appear that the GP's assertion has merit even if it's not entirely practical.
The bible, on the other hand, has inspired untold millions throughout the entire world, regardless of your stance on religion.
That doesn't follow at all. If the government is actively trying to ensure stories make them look good, they certainly wouldn't want any to make them look bad. They certainly wouldn't be creating/planting/whatever stories to do that unless they were provably false and would be used to advantage later (e.g. "look at this bias reporting!").
I also laugh at people who believe in flying saucers and so on. But I'd probably stop if an actual flying saucer landed on the highway and started blowing things up.
Both Smalltalk and VS+Resharper have great refactoring tools. Both have great debugging tools (and in Smalltalk I can even do a lot of development right inside the debugger and watch how the code is reacting while I'm writing it). In the CL/Emacs setup debugging is so bad most people recommend not to even bother; just use tracing. And I can't understand why it needs to be like this, CL is closer to Smalltalk than it is C# (that is, CL is a "live" language as Smalltalk is or at least it very much can be. Even a compile-only CL like SBCL).
The other issue is project management. In Smalltalk it doesn't really come into play as much since the image is your "exe", but despite this Smalltalk has great tools for organizing classes, methods and so on (and Dolphin's way of letting your image be a "solution" and you make individual exes from that that drop everything they didn't use was absolutely brilliant). In VS, I create my assemblies, make dependencies and so on and the IDE just handles all this for me.
Contrast that with CL/Emacs: CL has ASDF files that can manage all your dependencies for you (people complain about it, but I've used them for several years and never had any problems) but you have to manage all this stuff manually. If you want a nice way of saying "create new package" or "create a new file that is in this package" you'll need to write all that handling, UI, etc. yourself. And after you write it all, what will you have? The interface will be hideous no matter how you do it because you're restricted to just text. In Visual Studio you can have the disapearable side bars approach, the "old school mac" approach of different info windows floating all over the desktop, etc. With emacs you'd be restricted to doing that stuff via ascii art or popping up more windows with ugly ascii art in them.
The only way I could see CL/Emacs as the future is if we're talking post-apocalyptic.