

GOOGLE MYTRACKS STILL USABLE INSTALL
One of the things I do with Google Earth is install a GPS tracker on my cell phone and take it on a skydive. My other alternative is to use OpenLayers, but then I have to write more of my GUI in JavaScript, which I kind of hate. I'd also been looking into getting around some of the limitations in Google Earth by setting up a socket server that pretends to be a web server and shoveling KML into Google Earth via fast-refreshing network links. I'd actually been kicking around the idea of using the Google Earth plugin to do some stuff, but I also know Google's tendency to do stuff like this. Google Earth is a nifty thing and I can think of several applications I'd really like to build around it. PNaCl is sensible, even if it did come from Google. Jesus Christ, Mozilla, get rid of asm.js and use PNaCl. This we're-doing-the-wrong-thing-and-it's-obvious-but-let's-keep-on-doing-it-even-when-our-few-remaining-users-beg-us-not-do philosophy of theirs has extended to all of their projects, and it shows. But that's just how Mozilla works these days. The third problem is, obviously, that Mozilla keeps on pushing this idiocy, even when it's clear that asm.js is a fucking stupid idea and the wrong way of doing things. It's the same principle when you try to use JavaScript as a replacement for a proper bytecode-based runtime. When you try to use some turds as a pair of boots in a storm, your feet will get soaked and smelly.

NET, or PNaCl, yet it's intended to be used as if it were a proper bytecode-based runtime. The second problem is, obviously, that asm.js not a proper bytecode-based runtime like Java. Mozilla needs to get over their raging hardon for JavaScript. That's lots of time for these goddamn stupid problems to have been fixed many times over. I don't give a fuck if Brendan Eich only had a week to get it working, back in 1995. It's riddled with unjustifiable flaws, from its very foundation to its very peak. JavaScript is, by far, the worst mainstream programming language ever to have been created. The first problem is, obviously, that asm.js is JavaScript. Mind you, it's a subset of JavaScript that's awful for humans to work with, but it's still just a subset of JavaScript. Asm.js just about sums up everything that's wrong with Mozilla today (and that's a whole helluva lot!).Īsm.js is just JavaScript.
