Alternatively, you could be a schizoid with paranoid tendencies. :-)
987 karma · joined March 2, 2013
Alternatively, you could be a schizoid with paranoid tendencies. :-)
- CNG, LPG, and gasoline have significantly different mass density, so you can't compare the fuel tank sizes easily.
- CNG (methane), LPG (propane/butane), gasoline (octane), and diesel have different energy density, so it doesn't make sense to compare mileage by volume.
- They also may have slightly different energy efficiency in the engine.
My conclusion is that the best way is probably miles per MJ of the calorific value of the fuel.
Or, you know, you could simply state miles per $ of the fuel price + power train depreciations/maintenance, or even include the vehicle's TCO, which is what intensive car users are aiming for anyway. :-)
Since when is gas measured in gallons? Around here, we've always had it measured in cubic meters at atmospheric pressure.
To me, it always seemed that in the provinces, quite little has changed after the end of the 5th century from the POV of your ordinary peasant. The more remote provinces have never been that much urbanized to begin with, and the non-Roman east of Europe didn't notice a thing anyway.
Obviously, that doesn't diminish the value of the effort (and, I hope, the eventual schievement), but whenever I see claims like that I cringe. So many people have so little notion of history... (I blame in on the Renaissance people, they were the ones who tried to blacken (pun intended :-)) the previous centuries so that they could feel good about the world they remade for themselves. And then the term got stuck.)
That's useless, the right reaction would be to shoot them.
Actually, all serious Common Lisp implementations, for example, do incremental AOT compilation these days, and none of them is ever going to "move towards using LLVM". In the broader landscape of programming language implementations, as far as IR generality is concerned, LLVM is actually not significantly better than Java bytecode, and for many languages, trying to use it would probably generate more problems than actually using it would solve.
Where do they say anything of the kind?
Need two versions of the same library for two different applications? No problem, because each app gets its own inferface.
One app needs to accesses a physical block device and another a virtual one? No problem, because each app gets its own inferface.
Is the capability required by the app deployed on another machine and you want to expose it to the application transparently? No problem, because each app gets its own inferface.
And if the current hardware isn't amenable to running such systems with ease, well, that might have something to do with the fact that everything we're running has its roots in the 1980s. The unprecedented success of the PC revolution has essentially frozen all development of substantially new systems.
Recently, a third half of it was based on Java. :-)