![]() A Google support page details how you can export your data, with the simplest option being to package it for Google Drive or send it directly to Google Fit if you want to try out the company’s newest take on fitness tracking. The death of MyTracks shouldn’t be a huge surprise, as the app has been neglected in favor of the cool new kid, Google Fit. ![]() The interface is more consistent with the Holo theme from Ice Cream Sandwich than the current trend of Material Design. All the momentum is clearly behind Google Fit, which now replicates these functions and is designed as a platform for fitness data from other services. The app will stop working on April 30, though Google does say your data will be available to transfer after that date. The story behind the story: Google Fit is clearly the future for the company’s foray into fitness tracking, as it recently picked up the same abilities as MyTracks. It wouldn't even really be all that much work, but I don't really like how I'd have to do the design, and that's kept me from it.The other feature set is far more involved, as it can assist you in counting calories, other workouts, and serve as the hub for data from other fitness apps. I could pull this off using the socket server method of putting KML into Google Earth and updating a new point for each wingsuit's location every second. It'd be really neat to plot an entire load of skydivers together on Google Earth and do a real-time replay of each one's position along their track during the jump. There are custom skydiver GPS units available that have much higher accuracy, and they're used regularly in wingsuit competitions and stuff like that. The S3 used to regularly lose 2/3rds of the points on my jump. The cell phone isn't a great GPS tracker to use for this - the GPS hardware in the Samsung Galaxy S5 I'm using now is actually almost usable. Apparently the developers didn't consider the "I'm 2.5 miles above the surface of the planet" use-case when they wrote the thing heh. MyTracks actually has an "Export to KML" option, but it doesn't handle altitude very well and just clamps your entire track to the ground. I use MyTracks to log my coordinates every second and use a little application I wrote to turn the MyTracks data into a KML file, detect where I deployed my canopy and drop a push-pin there and plot the jump on Google Earth so you can see the jump in 3D. 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |