Comment Re:Still A Toy (Score 1) 627
I wonder why they don't help out with the Lithium-Sulphur battery idea and start from there...
I wonder why they don't help out with the Lithium-Sulphur battery idea and start from there...
Done and done: see Demolition Man
I think you've got it right - for some ideal world lacking other impetuses.
A more interesting question in my mind is: how to predict business' push for one type of app over the other(s)?
Microsoft is in some respects falling by the wayside, so they've jumped on the subscription bandwagon for applications - not just support/service - which seems to contradict all of their previous practices as they nix MSDN subscriptions and forbid Windows versions of some Xbox games...
Concurrently Google has been removing many services people like and charging more for things like map-related services while they play around with YouTube and other websites many netizens seem to love. But they're also pushing their own OS, browser, and now hardware...
We live in interesting times, my friend.
8-PP
> without resorting to violence
From paralyzation and death from "accidents" for participants through nigh-typical gameplay, to soccer hooligans and riots when men's college, national, and international teams win (or lose!), to a figure skater having a competitor's leg(s?) broken...
I think you can see the violence inherent in the system.
8-PP
Joda is not the solution to anything, except another academic's ego.
You can thank the SpringSource people for that xml configuration POS.
They even thought they'd make their own version of Rails (even they already have SpringMVC) and came up with Grails - which is actually much, much worse than you might expect when it *cannot* produce a stack trace less than 150 lines long, and it makes all the problems with all of their other frameworks (which Grails relies on, even though it is rumored to have been based on Groovy) that much worse - imagine the lack of implicit configuration and frameworks you've experienced so far, except that *if you're lucky* you get less informative error messages than you've seen before. Typically instead of that something simply doesn't work as you would expect and you have to research it for a couple hours (or in the case of one of my colleagues, a couple WEEKS) to figure out why it doesn't work. And then use Groovy to change class behaviour to work around SS's POS.
Yeah, like that.
Get hold of portable property. -- Charles Dickens, "Great Expectations"