To illustrate that electric vehicles are a luxury item and the Tesla 3 doesn't change that.
The comment I was responding to was comparing the vehicle (favorably) to non-EVs, overestimating both the speed of the Tesla 3 and the cost of conventional gas vehicles that could match it.
Tesla advertises the standard Model 3 as doing 0-60 in 5.6 sec, with a base price of about $35k.
If your primary use case for a car is quick acceleration that probably is a bargain. But for most people the world isn't going to changed by a car that can do rabbit starts more effectively (unless they end up rear-ending someone in the process).
Instead of a Model 3, someone could go pick up a Prius One for about $23k. Sure you won't turn many heads and playing "Fast & Furious" will be less satisfying, but even if gas averaged $5/gallon the $12k in savings is enough to dive over 120,000 miles. And that comes with a decent amount of cargo space (25 vs only 15 in the Model 3) and similar if not greater passenger volume. Tesla doesn't advertise the passenger volume, but since it is classified as a compact it is somewhere between 85-94.9 versus 93.1 for the mid-size Prius.
With the price and trade-offs the Telsa 3 is still a luxury purchase, albeit a more broadly obtainable one. When it comes to serving practical transportation needs, there are far more affordable options. Even if you just want performance you can beat 5.6 in a $28k V6 Camaro.
If you believe coinmarketcap.com it's at $16,441.40, while Yahoo Finance has it at $15,994.11. Both are pretty far off "fully rebounded" consider it peaked over twenty grand.
Manually enter my name on a device? What century are we in?
I'll start attending funerals when I can check in via E-ZPass. And they better have a 20MPH lane. I'm not slowing down to 5MPH for anyone but immediate family.
It also lacks feature parity with the old plugin system. I've got a friend that I have locked onto 56 specifically because he needs (not wants) a toolbar for his password manager / form filler.
For someone who is almost blind and suffers significant neuropathy, going from a single click form fill to clicking on an icon, then navigating to a menu entry, then navigating to a sub-menu, then clicking on an entry is a non-starter.
And the interface churn is a very real problem and a valid complaint as well. Spend a week trying to learn a new interface at 400% magnification and tell me how often you'd like to repeat the experience.
"We say maintained for approximately 13 months because the supported period for releases is dependent on the date the release under development goes final. As a result, Release X is supported until one month after the release of Release X+2.
This translates into: Fedora 26 will be maintained until 1 month after the release of Fedora 28. Fedora 27 will be maintained until 1 month after the release of Fedora 29."
If you want more stability, there's CentOS, which has a new release every 3-4 years, but will provide updates for 10 years. The core release doesn't have the latest software, but that is what Software Collections are for.
1) ARM is not and never was big-endian. It was historically little-endian, but is now switchable (though it still defaults to little).
2) This is not an insurmountable issue. Rosetta did dynamic translation of binaries built for a big-endian architecture (PowerPC) to little-endian (x86).
3) Because this is such a common operation, it is highly optimized in hardware. ARM in particular not only has an operation (rev) to do it, you can specify data access operations in either byte order.
4) Network traffic is big-endian but works just fine on little-endian architectures.
5) Many file formats are natively or potentially big-endian but work just fine on little-endian architectures.
6) Java is big-endian but works just fine on little-endian architectures.
7) To my knowledge there are scant details on how emulation is implemented, but it seems likely they would employ dynamic recompilation.
The reality simulator doesn't actually render at that level of complexity unless one of the players is actively looking that closely. What should worry us is the moment when some too smart for his own good scientist ends up crashing the process and the rest of us with it.
I'm baffled by people who say they can't see the appeal of this kind of device. Are they being deliberately obtuse? Have they simply not thought about it very much? Are they so myopic that they are simply unable to imagine having preferences and likes different than their own?
Assuming Apple catches up to where Microsoft was two years ago, no. My Surface has an IR LED coupled with an Intel RealSense 3D camera to power its biometric authentication. Quick and accurate, even with variance in facial hair and eyewear.
I've been using the Surface Pro 4 keyboard daily for over a year and a half. It's hardly my ideal keyboard, but I'm also not going to carry around a Model M around with me. Given the size and weight constraints, it's a solid keyboard. Surprisingly little flex, good spacing, and decent key travel for being so thin, a backlight with adjustable brightness, and a sane layout including function keys.
A larger track pad would be nice, but not at the expense of a smaller keyboard, but other than that I have no real complains. It's responsive, accurate and all the multi-touch gestures work fine.
The base leaf is $30,680. Minus a $7,500 federal tax credit and a $1,700 rebate from NYSERDA that would come to $21,480; that's $9,490 more than an entry level Versa. Even assuming an average fuel cost of $4 (well above current levels, and unlikely given trends in oil prices) that is enough money to buy fuel for 6-7 years of driving.
But that tax credit is non-refundable, which means buyers with lower income will actually pay more. In fact about 45% of households pay no federal income tax, so would get no federal credit.
You're quoting current numbers again. That shows what Piper can handle; not Perforce. They dramatically increased their commit rate (and in particular their automated commits) after the migration: ahref=https://youtu.be/W71BTkUbdqE?t=461rel=url2html-11078https://youtu.be/W71BTkUbdqE?t...>
I suspect Google could have found a way to stay on Perforce as well, but ultimately there are good reasons to evaluate (and adopt) other options when you are running at unusual scale. It's interesting that the two companies went in opposite directions, and that it is Microsoft that decided to adapt and adopt an open source distributed solution while Google build a proprietary solution tailed to fit a more centralized system.
Apparently Google did evaluate git, but it could not scale to larger repositories and they decided against breaking up into smaller repositories. In theory GVFS could make it a feasible option again.
But yes, the broader point that 300GB is small by comparison stands. Scale is a funny thing. An elephant seems huge - and by all accounts *is* huge in most contexts - but is about the same size as just the tongue of a mature blue whale.
Slashdot Mirror
To illustrate that electric vehicles are a luxury item and the Tesla 3 doesn't change that.
The comment I was responding to was comparing the vehicle (favorably) to non-EVs, overestimating both the speed of the Tesla 3 and the cost of conventional gas vehicles that could match it.
Tesla advertises the standard Model 3 as doing 0-60 in 5.6 sec, with a base price of about $35k.
If your primary use case for a car is quick acceleration that probably is a bargain. But for most people the world isn't going to changed by a car that can do rabbit starts more effectively (unless they end up rear-ending someone in the process).
Instead of a Model 3, someone could go pick up a Prius One for about $23k. Sure you won't turn many heads and playing "Fast & Furious" will be less satisfying, but even if gas averaged $5/gallon the $12k in savings is enough to dive over 120,000 miles. And that comes with a decent amount of cargo space (25 vs only 15 in the Model 3) and similar if not greater passenger volume. Tesla doesn't advertise the passenger volume, but since it is classified as a compact it is somewhere between 85-94.9 versus 93.1 for the mid-size Prius.
With the price and trade-offs the Telsa 3 is still a luxury purchase, albeit a more broadly obtainable one. When it comes to serving practical transportation needs, there are far more affordable options. Even if you just want performance you can beat 5.6 in a $28k V6 Camaro.
If you believe coinmarketcap.com it's at $16,441.40, while Yahoo Finance has it at $15,994.11. Both are pretty far off "fully rebounded" consider it peaked over twenty grand.
Kinney gets machine gunned.
https://media.giphy.com/media/FvaTwHY7YDn20/giphy.gif
Because it's nice to be able to access your collection from your car, work machine, phone, and other connected devices?
I would never put my content *only* in the cloud, but a copy? Why not?
Manually enter my name on a device? What century are we in?
I'll start attending funerals when I can check in via E-ZPass. And they better have a 20MPH lane. I'm not slowing down to 5MPH for anyone but immediate family.
In other words, the world is going the way of WebOS in spite of WebOS going the way of the Dodo.
One could argue this will be a boon for Microsoft in the mobile space since it lets customers break out of the Chrome / ChromeOS / Android ecosystem.
It also lacks feature parity with the old plugin system. I've got a friend that I have locked onto 56 specifically because he needs (not wants) a toolbar for his password manager / form filler.
For someone who is almost blind and suffers significant neuropathy, going from a single click form fill to clicking on an icon, then navigating to a menu entry, then navigating to a sub-menu, then clicking on an entry is a non-starter.
And the interface churn is a very real problem and a valid complaint as well. Spend a week trying to learn a new interface at 400% magnification and tell me how often you'd like to repeat the experience.
It is documented in their release schedule:
"We say maintained for approximately 13 months because the supported period for releases is dependent on the date the release under development goes final. As a result, Release X is supported until one month after the release of Release X+2.
This translates into:
Fedora 26 will be maintained until 1 month after the release of Fedora 28.
Fedora 27 will be maintained until 1 month after the release of Fedora 29."
If you want more stability, there's CentOS, which has a new release every 3-4 years, but will provide updates for 10 years. The core release doesn't have the latest software, but that is what Software Collections are for.
1) ARM is not and never was big-endian. It was historically little-endian, but is now switchable (though it still defaults to little).
2) This is not an insurmountable issue. Rosetta did dynamic translation of binaries built for a big-endian architecture (PowerPC) to little-endian (x86).
3) Because this is such a common operation, it is highly optimized in hardware. ARM in particular not only has an operation (rev) to do it, you can specify data access operations in either byte order.
4) Network traffic is big-endian but works just fine on little-endian architectures.
5) Many file formats are natively or potentially big-endian but work just fine on little-endian architectures.
6) Java is big-endian but works just fine on little-endian architectures.
7) To my knowledge there are scant details on how emulation is implemented, but it seems likely they would employ dynamic recompilation.
The reality simulator doesn't actually render at that level of complexity unless one of the players is actively looking that closely. What should worry us is the moment when some too smart for his own good scientist ends up crashing the process and the rest of us with it.
I'm baffled by people who say they can't see the appeal of this kind of device. Are they being deliberately obtuse? Have they simply not thought about it very much? Are they so myopic that they are simply unable to imagine having preferences and likes different than their own?
Lucky to get two. There isn't a country in the world that has a total fertility rate as high as eight.
That would certainly explain the inverse relationship between wealth and fertility...
I got one as a piece of vendor swag. The process of installing iTunes was bad enough I gate it away without using it once.
Sure, and vendors tend to sell people brand-new hardware, and not the hardware that they already own and use. :)
Assuming Apple catches up to where Microsoft was two years ago, no. My Surface has an IR LED coupled with an Intel RealSense 3D camera to power its biometric authentication. Quick and accurate, even with variance in facial hair and eyewear.
I've been using the Surface Pro 4 keyboard daily for over a year and a half. It's hardly my ideal keyboard, but I'm also not going to carry around a Model M around with me. Given the size and weight constraints, it's a solid keyboard. Surprisingly little flex, good spacing, and decent key travel for being so thin, a backlight with adjustable brightness, and a sane layout including function keys.
A larger track pad would be nice, but not at the expense of a smaller keyboard, but other than that I have no real complains. It's responsive, accurate and all the multi-touch gestures work fine.
You mean the Surface Cover that has 4.8 stars at Amazon, 4.6 stars at Best Buy, 4.5 at Walmart, etc?
The one that is a full keyboard (including a high precision touchpad) and still managed to be twenty bucks cheaper than the Apple cover?
When performance is a significant consideration there's JRuby.
Or seven Echo Dots.
The base leaf is $30,680. Minus a $7,500 federal tax credit and a $1,700 rebate from NYSERDA that would come to $21,480; that's $9,490 more than an entry level Versa. Even assuming an average fuel cost of $4 (well above current levels, and unlikely given trends in oil prices) that is enough money to buy fuel for 6-7 years of driving.
But that tax credit is non-refundable, which means buyers with lower income will actually pay more. In fact about 45% of households pay no federal income tax, so would get no federal credit.
The Venn diagram of "crap hardware I've owned / used" and "the Surfaces I've owned / used" is two circles without overlap.
You're quoting current numbers again. That shows what Piper can handle; not Perforce. They dramatically increased their commit rate (and in particular their automated commits) after the migration: ahref=https://youtu.be/W71BTkUbdqE?t=461rel=url2html-11078https://youtu.be/W71BTkUbdqE?t...>
I suspect Google could have found a way to stay on Perforce as well, but ultimately there are good reasons to evaluate (and adopt) other options when you are running at unusual scale. It's interesting that the two companies went in opposite directions, and that it is Microsoft that decided to adapt and adopt an open source distributed solution while Google build a proprietary solution tailed to fit a more centralized system.
Apparently Google did evaluate git, but it could not scale to larger repositories and they decided against breaking up into smaller repositories. In theory GVFS could make it a feasible option again.
But yes, the broader point that 300GB is small by comparison stands. Scale is a funny thing. An elephant seems huge - and by all accounts *is* huge in most contexts - but is about the same size as just the tongue of a mature blue whale.
Because they're not crap hardware.