Sure, it's just a map now. But in the self-driving car future, it's going to be slightly more critical.

The guy is a jerk, and deserves what he gets. However as a side note, have you looked up what it costs to dump a truckload of construction trash these days? It might not be astronomical if you have the budget for a home improvement project, but it's definitely not "miniscule" in my neck of the woods.

Not likely. People understand what e-waste is. It's just far easier, and many times a lot cheaper, to toss it in the trash bin than try and figure out how to properly dispose of it.

If there was a bin for e-waste like there is for recycling and trash in many places, you'd have a lot less e-waste mixed into landfills with general trash. Not sure what you'd do with it, but at least it would be pre-sorted.

You get to learn something today.... "the motor is attached directly to the shaft" is just plain wrong. EV's have differential gears just like every ICE car, unless there are 4 motors, one per wheel. And even then, there might be some gearing or disconnect involved. There might not be a transmission, but there are still mechanical elements and gears/bearings/etc. involved.

No doubt, EV's have far fewer mechanical parts than an ICE engine, but they still have a lot of parts!. And while electrical components tend to last longer than mechanical components as a general rule, it's not an *exclusive* rule. Electronics can fail and wear out over time as well.

As for motor replacement cost? Used Tesla motors right now are $3-5K. A use 3.0 ecoboost, common in a lot of Fords as an example, is $4-6k. There's not *that* much difference there, and I'd argue you'll pay a lot less to replace the ICE than the EV just because there are so many more mechanics available to do the job. EV's are also still relatively new, and their long term reliability and cost is still being determined. Very few have reached their EOL for battery packs, so that replacement cost and hassle hasn't even hit the general market in any volume yet to determine a reliable cost.

Disclaimer: I own both ICE and EV vehicles. I like them both for various specific reasons. TBH, the ROI/Cost on each of them is pretty close. The EV was far more expensive than the ICE, but it's way cheaper to operate. The ICE is more expensive to operate, but it's a quarter the monthly payment that the EV is. And I can use it in more long-distance scenarios without the hassle of figuring out go-juice issues.

Buy what you need, and debate all you want. (after all, this is the internet) But there are still a ton of unknowns about the future of EV's, other than the singular fact that they are here to stay.

Why would you even publish this? It's just giving someone who shouldn't get the time of day, the time of day, just so you can get more clicks? Bad Slashdot.

It's somewhat impressive that there are still people with these super low UID's still lurking on /. after all these years. (:

It says right on the homepage:

        the xonsh shell

~ It is pronounced zonsch ~

Either way, it's still terrible name.

The phone is just a small part of the puzzle for an investigation. You can't blow something up with *only* a phone. You have to move around, communicate across public networks, and physically acquire elements. Sure, having the data on a phone with documented communications might be handy, but it's not strictly necessary for any investigation of physical activity. Saying it is, is just being lazy.

Wrong. You absolutely can use pre-generated keys for google's authentication services. They call them backup codes.

Wrong again. You can absolutely setup accounts in Google Authenticator (And most other similar apps) without network access. You can even install the app itself without access in many cases, if you want to side-load from a PC or something.

Sorta wrong. The clocks don't have to be perfect, they just have to be close. Pretty much every service has the ability to deal with a certain amount of clock skew. Smartphones these days are pretty good at keeping time, even when not connected to the network, so this usually isn't an issue. But this is also dependent on if the service is using TOTP or HOTP. (Time based or Counter based codes)

Here you got one right, every code has a 60 second lifespan. (:

But to the point of the original post (GGGP?) that brought up the autheticator... They should at least have HOTP/TOTP as an option for those with smartphones in this case. They probably can't drop SMS altogether because of the users that *don't* have smart phones, but no reason not to support both.

          Actually, the cheapest plan they have seems to be ~$15/month.

-= Jay =-

I generate this data. I own this car. This is my data, not the company who made my car. If it's a rental, sure, go ahead and do what you want with that. But if I own the car, that data is MINE to choose whom I give it to, or don't give it to, and use as I see fit.

This isn't any different than any other appliance or device. I own my computer, The manufacturers that made it don't own the data that's created by using it. Tired of companies thinking they own what I do with the stuff they sell me. It's getting ridiculous.

          Valid point.

          I still believe that there should be a way to (securely) provide the government with only the data it needs to levy the tax. i.e. the miles driven on Oregon roads, without giving away more data than necessary and allowing the government to potentially abuse it.

This is pretty short sighted, and my hope is that you are not on any committees or groups planning for anything in the future, as you seem to not be able to think ahead. EV's are a small segment now, but it is growing fast, and there will be a point in the future where it will become an issue having EV's essentially free from any sort of tax that allows for maintenance on the roads they use. Oregon is simply experimenting with ways to work through that scenario, and working on a plan for the future.

Wouldn't a simple wheel odometer work just fine for this? All you're tracking is miles traveled. No need to collect all the other location/speed data that a GPS offers up and risk abuse, privacy lawsuits, etc.

You lost all *your* credibility there. systemd has absolutely nothing to do with cloud deployment, if anything, it complicates existing tool sets that are already being used for cloud deployments, because it obfuscates underlying process making it even harder to debug mass deployments.

Robust? Efficient? Easy to Use?Just Works? You might be talking about the kernel, but you're definitely not talking about systemd anymore. I would put good money on any kernel developer pissing in your coffee just for saying systemd architecture is anything even remotely comparable to the kernel.

If it ain't broke, don't fix it. The old init system worked just fine. So what if it was scripts, scripts are the heart of any unix system, and have been for years. So what if the more complicated your app was, the more complicated your init process was. Using systemd isn't going to make your special purpose Linux OS any simpler, it still has to do the same damn thing. It's only going to hide that complexity in yet another tool.