Note that "they" are one person, Colin Percival. That's all Tarsnap is; one person, some backup code he wrote, and data stored on Amazon S3. As the sole owner and only person working on a product aimed at a niche audience, I don't think it's unreasonable that he has a little fun with the way he runs it. If this kind of thing bothers you, this service probably isn't for you.
If prices were listed in dollars per GB instead of picodollars per byte, it would be harder to avoid the what-is-a-GB confusion (a GB is 10^9 bytes, but some people don't understand SI prefixes). Picodollars are perfectly clear — nobody is going to think that a picodollar is 2^(-40) dollars.
Specifying prices in picodollars reinforces the point that if you have very small backups, you can pay very small amounts. Unlike some people, I don't believe in rounding up to $0.01 — the Tarsnap accounting code keeps track of everything in attodollars and when it internally converts storage prices from picodollars per month to attodollars per day it rounds the prices down.
And finally, the price in dollars per GB are also prominently displayed, right after the price in picodollars per byte. So really, you're just being bothered that he's having a little bit of geeky fun even though it has absolutely no effect on you.
We taxpayers are still paying in the form of the tax credits you get for buying EVs.
Why is it that I pay $7,500 more in federal taxes for riding my bicycle to work than someone who purchases a $70,000 luxury car? Why don't people who don't even own a car in the first place, and take the bus to work, get that tax credit? We're basically transferring wealth from the middle class to the wealthy by offering these sorts of tax credits (at least, in the case of Tesla; other manufacturers like Nissan are offering more affordable electric cars that are actually within the price range of the middle class).
By offering a tax credit to people who buy electric cars, yes, the average taxpayer is still funding Tesla.
Now, the carbon credits are another issue. I think that those are somewhat more reasonable; you are making the manufacturers of vehicles that have substantial negative externalities fund ones that have significantly less.
Again, though, I wonder why only other automobile manufacturers are able to sell these credits; it would be nice for, say, bicycle manufacturers, electric bike manufacturers, public transit systems, and municipalities which build infrastructure more suitable for living without cars to be able to sell credits as well. Only allowing automobile manufacturers to be in the game means that you are still supporting transportation that requires each individual person to haul around a couple of tons of metal with them for 20 or more miles a day, taking up lots of extra space for storing them both at home and at work, leading to congestion and the necessity for more money to go into infrastructure.
As pointed out elsewhere, if you are wealthy (qualify for the Alternate Minimum Tax) you don't get the tax credit. So that claim is false.
Secondly, the total cost of those tax credits is miniscule. We subsidize a lot of other much worse things a lot more. If you're going to get up in arms about tax subsidies, we'll be here all day.
Additionally, EV subsidies are not unique to Tesla. The only thing that was unique to them was the loan which they're paying back early. So bringing up the rest of it in an article ostensibly about Tesla is a bit misleading.
I think EV subsidies make sense, and I made the point of NASA for a reason. Sometimes when we have an important goal (interstate freeway, getting to the moon, moving the entire country over to electric vehicles) it's worth investing in.
You may disagree, and you can express that disagreement by writing to your local Congress critters and by voting.
And if you check IRS form 1040 http://www.irs.gov/pub/irs-pdf/f1040.pdf and its instructions http://www.irs.gov/pub/irs-pdf/i1040.pdf, you will see that the tax credit for electric vehicles is added to line 53, which is subtracted from your tax liability whether or not you paid AMT (line 45). AMT applies to taxable income, preventing you from claiming exemptions if your income is over a certain amount. Tax credits apply to your tax liability, which are subtracted after computing your tax and alternative minimum tax.
So yes, you get the tax credit no matter how wealthy you are.
> I think EV subsidies make sense, and I made the point of NASA for a reason. Sometimes when we have an important goal (interstate freeway, getting to the moon, moving the entire country over to electric vehicles) it's worth investing in.
I agree that EV subsidies are worthwhile, but I think that there are better places that we could apply subsidies, such as all of the other infrastructure improvements I suggested, and promoting low-car lifestyles rather than pouring all of that investment into alternative types of cars. But those other improvements aren't as sexy, because they frequently don't involve exciting new technologies but instead simple restraint, better planning, and investment in things that are associated with lower classes (busses, trains, dense urban planning), rather than upper and middle classes (sexy cars, suburban living).
And you know, another way for me to disagree is doing exactly what I'm doing here; trying to urge restraint of many people who think that Tesla is so amazing and so much the future that they lose sight of other, simpler, cheaper ways of solving the problems that Tesla is supposedly solving. There are an awful lot of people here who equate negative opinions of Tesla with being evil, backward thinking, luddites, while really, some people are just asking "is Tesla really profitable (as paying off the loan early might make you believe), or are they still making money off of the taxpayer and zero-emission credits paid for by other manufacturers? How long should the taxpayer fund toys for the wealthy in order to help bootstrap an EV manufacturing industry, as opposed to putting money into other, even more sustainable infrastructure improvements?"
Skype was originally marketed as having end-to-end encryption. Now, we know that since Microsoft bought Skype they've added wiretapping support, which works by making themselves a man-in-the-middle. They claim they only do this temporarily for people they are actively wiretapping.
This, however, shows that Microsoft regularly MITMs you, for the purpose of evaluating whether links are dangerous. This means that basically all of Skype's former privacy claims are no longer true. They simply regularly look at your unencrypted traffic, which means that they are a target for attackers, governments, and pretty much anyone who wants to eavesdrop or read your messages.
How do you know if Microsoft is actually eavesdropping the entire conversation, or it's just the Skype client filtering out URLs in the conversation for additional screening? Sorry if I missed something in the article.
The URLs are being pinged by computers within Microsoft, so even if the filtering was only occurring on the client side (which I doubt) it still makes its way back to MS servers.
I wouldn't call this man-in-the-middle, they are the man at both ends and in the middle.
MITM usually refers to 3rd parties routing your traffic. So if your ISP or network admin was sniffing your Skype messages, that would be what is generally called MITM.
You know, I understand wanting to put a little pressure back on the "make everything configurable" crowd; there are a lot of software engineers who go a bit overboard on the "just make it an option" approach to design, and then wind up with big, bloated, buggy software that tries to do everything but fails at most of it and is frustrating to configure.
However, "choice is poison" is a rather extreme over-compensation for this problem. Sometimes, options really do provide value. And many times, if they are designed correctly, they don't substantially increase cost; if the features are orthogonal and implemented independently, the additional complexity is only linear with the number of features, not quadratic or worse as happens if they are too interrelated.
I understand that we want to get away from the "you need to spend hours customizing your environment to make it usable" approach to design that plagues some open source project, but going to the other extreme and saying that "choice is poison" is just as bad.
I'm not sure this has ever been tested in court. But yes, as far as I can tell, that is what they are trying to claim.
It's interesting, because to stream H.264 video, you don't even need to necessarily have encode it. You could get video encoded by a third party (perhaps you got it that way, or perhaps you sent it to a third party to re-encode), serve it to your users, and they could play it with licensed H.264 player. The MPEG-LA seems to think that for doing that, you should have to pay them a license, despite the fact that you have never touched an H.264 encoder or decoder.
I would find it hard to believe that they could sue you for this and actually succeed, though they could probably bleed smaller players dry in the process of defending themselves.
It would be interesting to set up a video service that did this; used H.264 without ever using an encoder. You could make your users upload it encoded appropriately, or use Zencoder or AWS Encoding to transcode it for you.
I decided to try the UK calculator, for literary works. I'm somewhat horrified by the fact that one of the questions is 'Is the work "Peter Pan" by Sir James Matthew Barrie or an adaptation of that work?'
When specific works and specific authors have special laws passed for them, there's something a bit wrong with your legal system.
(And yes, I knew about this exception already, but wasn't thinking about it going in so the question caught me by surprise)
I knew about the exception also but I always think its a bit strange. Wikipedia refers to it as more of a tax on performances than perpetual copyright[1] because European copyrights for Peter Pan expired on December 31 2007.
The legislation is 301 Provisions for the benefit of the Hospital for Sick Children from the Copyright, Designs and Patents Act 1988[2]
No it's not. The lower range, low number of charging stations, and long charging times make it quite inconvenient for long trips.
I bought a used car 3 years ago for less than the cost Tesla charges for replacing the batteries on its car (which you are estimated to need to do after about 8 years). This car is a station wagon, so has much more storage space than a Tesla. I go camping every year, about 550 miles from where I live. I can make that trip in about 10 hours including food and gas stops. For the same trip, I would need to make at least two hour long charging stops at Supercharger stations along the way (if I had the highest-end battery option). But there are no Supercharger stations along my route; so I would need to find places to charge with ordinary power sources. If I used ordinary 10 kW 240 V sources, it would charge at a rate of about 30 miles of range per hour, effectively tripling the length of the trip; now what was a long 10 hour drive has turned into a 30 hour trip, which means finding places to stop and sleep overnight (which hopefully can give you a charge).
Furthermore, I live in an apartment, without a dedicated parking space. I need to park on street. So there's nowhere I could charge my car at home; I can't exactly run a power cord down and across the sidewalk to my car. Neither is there anywhere to charge my car at work. There's no way I could even use a Tesla for commuting right now, let alone longer trips.
With a gasoline powered car, I just fill up at any gas station, my car holds the gasoline overnight so it doesn't matter where I park, and for the above describe trip, I need to stop for gas once before leaving and once on the trip, each a 5 minute stop.
The Tesla Model S is an amazing car. But claiming that it's more convenient, or is a better car in every way but range, is a vast overstatement. It would be absolutely awful for me, and many other people with similar needs.
Some of these problems are solvable; there will be more Superchargers installed, the price will probably come down, there will probably be more electric vehicle infrastructure. But it's still a gamble to say that they will completely eliminate all of these advantages that a gas powered car has over an electric car, at least unless the price of gas spikes dramatically.
> The Tesla Model S is an amazing car. But claiming that it's more convenient, or is a better car in every way but range, is a vast overstatement. It would be absolutely awful for me, and many other people with similar needs.
Obviously convenience is different for different people. The OP is probably someone who finds car maintenance very inconvenient and as the owner of a used station wagon I am guessing you are not. If you don't take frequent road trips and have the ability to charge at home, the Model S is indeed very convenient--never have to worry about fuel and hardly ever have to worry about maintenance.
I too find maintenance inconvenient; but my used station wagon doesn't require much of that either. In the past three years, I've only ever had to have it inspected, tires replaced, and oil changes. Now, the Tesla doesn't have oil changes, so that one aspect is removed, but it does have annual maintenance. So, I'm looking at maybe two oil changes per year, vs. one annual servicing; a small improvement in maintenance hassle, but not amazing.
But anyhow, I'm not claiming that there are no convenience advantages of a Tesla; just that there are also a lot of things that are quite inconvenient, especially if you don't have a driveway or need to take long trips. Claiming that the Tesla is better in every regard but range is vast hyperbole. For some use cases, it may be more convenient; for mine, far less.
Beyond that, the price is a major disadvantage; at 4 times the price of a new economy car for the entry level model, and twice the price of lower-end luxury brands, it's well outside many people's price range; and you don't even save that much because you're not buying gasoline, as the combined cost of electricity plus replacement batteries winds up being pretty close to the cost of gas you would pay for the same number of miles (depending on exactly how long the batteries last, and assuming that the relative costs of gasoline vs. electricity don't diverge too much; of course you could say that gas prices are likely to go up faster than electricity, but they may go down too).
The Model S may not be the best at everything, but it appears to be the best overall car you can buy right now. It just scored an almost unheard of 99/100 from Consumer Reports (I believe the Civic got in the high 70s to mid 80s this year)
>If you don't take frequent road trips and have the ability to charge at home, the Model S is indeed very convenient--never have to worry about fuel and hardly ever have to worry about maintenance.
Doesn't the maintenance bit kind of remain to be seen? It seems to me there are two factors working against each other there: the high failure rates in new product categories, and the low failure rates associated with a simpler engine. I don't know that you can say which will win out yet.
The Model S is much, much, much simpler than a gasoline car.
- No engine.
- No fuel system.
- No alternator, starter, or belts.
- No oil.
- Single speed transmission! No shifting,
no transmission fluid.
- No fuel system.
- Lower brake wear, thanks to regen braking.
The downside is that the battery costs ~$10,000 and has to be replaced every 8 years.
I suppose, but its not needing oil changes alone is a big win for convenience. Tesla also will come to you for all service (and leave a loaner), so if it turns out to need some time in the shop you should not have to waste more time than it takes to make a phone call.
If you have to go five minutes out of your way then spend five minutes filling up, that's fifteen minutes. That's not uncommon, not everyone has a gas station on their route to and from every place they go.
Look if you are comparing a station wagon to a Tesla, you are just not even close to their target market. A BMW M5 sucks for camping too, and it has nothing to do with the range.
Why would you do this instead of #if 0/#if 1? Has exactly the same effect, is a one character toggle (sure, it's editing one character rather than inserting/removing one character), and is much easier to read and remember.
Yeah, but yesterday the same was true when it got to $100 or so. After a crash, there are always enough hopeful people to support a price for a little while, before it starts sliding down slowly again, until it reaches its next plateau.
I would expect this to get back down under $50 again (and I think even down to $30-$40) before it makes any kind of real recovery.
But of course, I'm guessing as much as anyone. I just wish I hadn't been busy at a trade show this week, or I would have sold when they were in the $150-$200 range.
Right now there are no trading fees on Mt.Gox until tomorrow. This probably gave (a) the guys with automated trading bots a field day to tweak their algorithms and (b) Mt.Gox a chance to take advantage of this to see if they can handle the increased load in trading.
My guess is that there's going to be a last minute scramble to buy before the trading fees get reintroduced probably pushing the price up a bit. When trading fees go in there might be slightly less liquidity, compared to yesterday and today.
Entirely speculative on my part, but plausible anyway.
Why do you doubt that it makes a difference in the real world?
One of the things you need to remember is that in general, web app developers need to target yesterday's browser on yesterday's hardware. So they tend to be fairly conservative about the performance requirements. But as browsers and hardware improve, the benefits trickle down until suddenly, it's possible to do something that you never could do before. So sure, the average web app, which is designed to run on old versions of IE on outdate hardware, probably won't see much of an improvement to this. But cutting edge demos absolutely will. And when this version is the "old browser running on old hardware", general purpose web apps will absolutely be able to take advantage of these improvements and do things that would simply be unheard of beforehand.
I have been building and architecting very rich web applications before most caught onto this web thing. I was an original tester of XmlHttpRequest back when it was a safe-for-scripting ActiveX "abomination". I recently made a ridiculously full featured stop-motion recording studio -- in the browser -- for my children after they were enamored by something similar at the Science Centre.
And JavaScript performance has not been -- remotely -- an issue for a long, long time. The facets that make these apps powerful are technologies like WebGL, Canvas, SVG, CSS, and so on. Things that I wouldn't imagine doing more than simple orchestrations in code.
People use JavaScript performance on a completely artificial benchmark like Sunspider as a proxy for real-world browser performance. Yet it is at most a minor correlation, and has incredibly little to do with causation of a good experience.
If you think I'm joking or overstating, turn off the JIT in your browser and use it for a day. Is your experience devastated? Can you even tell the difference?
There's a big difference between "my use case" and "all use cases".
Sure, JavaScript is fast enough for a lot of things.
But it's also too slow for many things that reasonable people would like to do on the web.
See Mozilla's pdf.js: it makes perfect sense to have a PDF viewer written in JavaScript (and not a blob of insecure C++ code in the form of the plugin).
pdf.js would not be possible at all "long, long time ago", even though JS was adequate for your use cases at that time.
pdf.js is barely possible today - it works for simple documents but its performance on more complex documents is still so much worse than what C++ plugin gives that many people go back to plugins.
Performance is one of the most important competitive aspects of software. Given 2 products with similar features, people go for the faster, which is a big reason why Chrome was so successful.
We're still far away from making JS speed covering all the important use cases.
Until JavaScript can decode mp4 in JavaScript (at speeds not much slower than optimized C++), JavaScript is not fast enough.
> There's a big difference between "my use case" and "all use cases".
Yes. This is an appropriate response to a significant fraction of the complaints on this site and all other tech sites. I usually think of it as "your experience is not universal".
Given the direction of gaming and streaming, your mp4 example seems apt... I think being able to do a 1080p stream at 30-60fps in JS is an appropriate goal for both hardware, and software. Canvas+JS is likely to be the "thin" client structure or the future... I think if it were possible to do this in JS, we wouldn't need ignorant plugin points for DRM.. encrypted streaming could "just work" on any platform, not that I want more DRM.
I like that we are finally at a point, where legacy emulators in JS are a reality. I do think some attention to worker interaction, and perhaps locking say a canvas, or audio channel to a worker should be something able to be done.
I think being able to do a 1080p stream at 30-60fps in JS is an appropriate goal
Why is that an appropriate goal? How about a video element -- which the browser implements in the ideal manner (which is usually a thin layer over hardware decoding) -- that handles h264? Why in the world would you want to do that in JavaScript, besides as a "because I can" challenge?
Further your notion that DRM would "just work" is really unclear. I don't think you understand the concerns of the DRM folks if you think that you'll just do it in decrypt.js and all will be good.
I'd like to have a meet-up and invite all the dudes like you and all of the kind of dude that complains about how asm.js performance is still so slow that they don't see the point and will just keep writing "native".
You're wading into a discussion that is above you. Generally that isn't a good idea.
JavaScript proper cannot be a high performance language because of fundamental design choices. Asm.js, which I've referenced multiple times, undoes many of those choices, effectively becoming a completely different language (which is why you target it with C/C++ and LLVM, not by writing it directly). The notion that there are going to be legitimate video stream processing or h264 decoders in JavaScript -- that are more than a impractical "if you ignore normal considerations" demo -- is 0%. It makes no sense, and it is using the wrong tool, making everything into a nail because someone "knows JavaScript". This is doubly true on mobile where you want to make every instruction count.
All of the examples in here are a riot. Further gaming in HTML5 thus far has been "welcome to the 80s". It has gone nowhere. Nor has any other "pure JavaScript" high computing adventure. nodejs, which I love, is a wonderful asynchronous glue, but everyone knows that you dare not do any actual computations in it because...JavaScript.
> You're wading into a discussion that is above you. Generally that isn't a good idea.
Making assumptions about the knowledge of people you're responding to is cool though.
> Further gaming in HTML5 thus far has been "welcome to the 80s".
Oh, see I guess I was thinking Unreal 3 and Sauerbraten were released much more recently than that. Oops, silly me.
You're right, the browser should just only ever be for web pages, everything should just stay how it is now and all these damn kids should get off your lawn.
The Unreal 3 demo was an entirely different thing. Asm.js is a dramatic rethinking of JavaScript that tosses much of the language, and adds hacked typing metadata, to essentially act as a proxy for C. The single benefit that it brings over just going with C is that existing browsers can limpingly run it in crippled mode.
You're right
And then you boringly completely misrepresent my argument. You should tell the kids to get off your lawn, as you're busy trying to pretend everything is a nail because all you know is your hammer.
It's interesting you truncated my example which was pre-Asm.js but still managed to be playable.
They took a shortcut, sure. Historically JS performance hasn't supported that kind of application, and thus there are few modern or impressive 3d game engines written in it.
You were wondering why we want JS to be faster, there's your answer. I'm not sure what's left to explain.
You seem to be saying "Browsers shouldn't do X because they are too slow." "Barring X, browsers are plenty fast and don't need to be any faster." I'm not sure why you don't see that those cancel out. Also X seems to be a fairly vague set of applications, some of which have working demos.
Regarding "my" nails and hammers, I'm actually not a huge fan of much of the tech involved in modern browsers. I'm just not able to ignore what Mozilla and Google are accomplishing here nor the interest that it garners from developers as a cross-platform VM. Can we stop trying to insult me out of having a valid opinion?
If we want make this personal - personally, I don't really care about any platform besides the ones I use, and those (deliberately) tend to be easy targets for portable C/C++.
That's apparently too much work though; people want (to at least believe they have) a single target. The browser is coming to be an option for that, whether anyone likes it or not.
But also, you picked out only one of the three reasons he listed (http://www.tarsnap.com/picoUSD-why.html); the other two are also important:
If prices were listed in dollars per GB instead of picodollars per byte, it would be harder to avoid the what-is-a-GB confusion (a GB is 10^9 bytes, but some people don't understand SI prefixes). Picodollars are perfectly clear — nobody is going to think that a picodollar is 2^(-40) dollars.
Specifying prices in picodollars reinforces the point that if you have very small backups, you can pay very small amounts. Unlike some people, I don't believe in rounding up to $0.01 — the Tarsnap accounting code keeps track of everything in attodollars and when it internally converts storage prices from picodollars per month to attodollars per day it rounds the prices down.
And finally, the price in dollars per GB are also prominently displayed, right after the price in picodollars per byte. So really, you're just being bothered that he's having a little bit of geeky fun even though it has absolutely no effect on you.