Then you clearly didn't pass the screening question at the beginning of my post;) The Model X is certainly not for everyone, but that's not to say there isn't a market for it. Remember that Tesla's goal is to make the best damn electric drive trains they can, and to develop a market for electric vehicles. They've hit the two-seater sports cars, now the luxury sedans, and are moving on to the family SUV. I wouldn't be surprised if their next announcement was the Model T ('T' is for 'truck').
Personally, I prefer the sedan -- I don't need the extra space of the Model X, but I need more than the two seats of the roadster. Before that, though, I need to live somewhere where I can actually plug the damn thing in =(
p.s. I'm a 'vette boy myself ^^, but it would have to be as a second car
How short is your garage? I admit that I have concerns about this (not legitimate ones, since I'm not really in the market to purchase this vehicle at this time), but I have considered the size of my garage and, although I'd like to take a tape measure to it, I suspect it will be fine. And mine is by no means a tall garage.
Whence comes your 30 mile driving range? The Model X is offered with a 60 kWh or a 85 kWh battery pack, the same as the top two options for the Model S. In the Model S, those packs give it 270 miles and 370 miles range respectively. Granted, the Model X is a larger, heavier vehicle, but a 90% drop in range? I don't think so.. probably closer to 10%. Also, the top two drive-train options have dual motors, which may offer better efficiency overall.
Because their founder has a lot of money to keep them afloat while they build up their technology and product line, and they are busy selling their drive-trains to companies such as Toyota.
I fail to follow your point; "Do you want an electric car? Do you need a little more space than the Model S can give you? Here, have a Model X." If your complaint is that it's an SUV, then it is a complaint without merit -- there are certainly practical advantages of this platform over that of the Model S (granted, not everyone that buys one will make use of them). If your complaint is about the gullwing doors, then I still disagree -- the take less space to open than a normal door, offer stand-up exits for mid-row passengers, and allow direct access to the third row. This last point is actually a big problem for anyone with two car seats -- if you can't get to the back row with the seats installed, you'll can't use it anyway.
I suppose lastly, if your complaint is that it's an electric vehicle, then get out.
I absolutely love the use of "Majel" here; Star Trek has influenced so much of our lives and of our tech, and now that are finally starting to get into responsive voice-operated systems, it shows a great deal of respect to bring it back to the original visionaries.
I just started reading it; I'm about 10% of the way through. Since the raw text was freely available (for a while), I used it as an opportunity to learn about the ePub spec and to compile one from scratch. Looks awesome, IMO! Trickiest part was properly replacing the straight quotes with left- and right-quotes =S
This would certainly explain why the Reader link recently disappeared from the Gmail navigation bar. I find it really unfortunate that Google decided to string us along for so long, offering alternatives like "use a bookmark." Google has yet to sell me on +, and I am far from convinced that merging Reader into the fold will do much to change that. The time is fast approaching to move to a new RSS reader.
I am typically onboard with the software purists, but in this case I disagree -- I like the new numbering systems! Well, not exactly the number systems, but the development strategies they imply. For a piece of software that you write once and remains relatively stable, the major/minor/bugfix method is acceptable, because you very rarely do major design changes.
In something like Firefox, Chrome, Thunderbird, and their ilk, the distinction of when exactly a major version number should be bumped becomes a little less clear -- one UI update is deemed slightly more important than another, and all of a sudden you have a major version jump instead of a minor one. With rapid release schedules, the idea is that the changes from one release to the next will/all/ be small, but after a while if you compare e.g. FF 3.18 vs 3.1, they will be nothing alike, so why should they share a common major version number?
Moving to a Year/Month (e.g. Thunderbird 11.09) system I think is overall much cleaner for software releasing on a rapid development cycle.
If you are near the US border, cross over and find a library with Overdrive that will allow you to get a card (many rural libraries will--we need registered users). Sign up for your Overdrive account on one of the library's computers, and through the magic of the internet, you should be able to reserve and check them out from your computer at home.
Interesting idea! If a little fraudulent.. I would first want to make sure there was no way this could come back and affect my existing purchased items. In an ideal world this would be a no-brainer, but this is Amazon we're talking about =/
FYI for Canadians waiting to borrow eBooks for the Kindle from their local library, I received the following response from the Kindle feedback team:
[...]
At this time, public library books for Kindle are currently only available for libraries in the U.S. that offer digital services from OverDrive. Don't worry, our Kindle Team is working on having this feature available to libraries outside the U.S. as well. We'll announce any updates on our website.
[...]
---- Original message: ----
From the Kindle/OverDrive press release, I see: "Visit the website of a U.S. library that offers digital services
from OverDrive."
As a Canadian Kindle owner, I am very keen on being able to use this service with my local library (in this case, Toronto), which already supports OverDrive for other ebook readers. Often I am turned off paying $10 to $20 for a Kindle ebook when I don't know if I will like it; being able to try a great number of books from my local library will let me better decide which ebooks I want to purchase for my device.
IIRC, there was a motion to delay the court proceedings until the USPTO ruled, but the judge ruled that the court case couldn't wait for the USPTO review.
The courts ruled that there was an infringement, but the deal to use the technology after that wasn't court mediated. That could mean a reversal in the patent status won't automatically even give valid justification for a refund - it'll depend on the settlement terms. If it's written such that one party is paying for technical expertise, design parameters, surcharge per unit installed, or etc... it could be pretty murky.
Hmm, a good point; I've never liked the concept of settling from an idealistic point of view, but this would certainly be an instance that actually backs that up.
Inquiring minds want to know. If the use of said patents was the sole factor in the suit, then I would say, the company is entitled to reimbursement. If there was anything else going on at the time, or if for example it involved two patents and only one patent was invalidated, then I think the case would have to be revisited. IANAPL, this is just wild speculation.
What I want to know, however, is how those patents made it through said suits intact, only to be declared invalid by the USPTO at a later date -- wouldn't, in the course of the suits, the patents get thoroughly vetted by the USPTO, under scrutiny of the court? Or am I applying too much logic and common sense to the patent system?
Thank you for sharing this, that is really an amazing video! It's always good to look back and remind ourselves just how far we've come, and just how thankful we should be for the advances in technology around us.
Slashdot Mirror
Then you clearly didn't pass the screening question at the beginning of my post ;) The Model X is certainly not for everyone, but that's not to say there isn't a market for it. Remember that Tesla's goal is to make the best damn electric drive trains they can, and to develop a market for electric vehicles. They've hit the two-seater sports cars, now the luxury sedans, and are moving on to the family SUV. I wouldn't be surprised if their next announcement was the Model T ('T' is for 'truck').
Personally, I prefer the sedan -- I don't need the extra space of the Model X, but I need more than the two seats of the roadster. Before that, though, I need to live somewhere where I can actually plug the damn thing in =(
p.s. I'm a 'vette boy myself ^^, but it would have to be as a second car
How short is your garage? I admit that I have concerns about this (not legitimate ones, since I'm not really in the market to purchase this vehicle at this time), but I have considered the size of my garage and, although I'd like to take a tape measure to it, I suspect it will be fine. And mine is by no means a tall garage.
Whence comes your 30 mile driving range? The Model X is offered with a 60 kWh or a 85 kWh battery pack, the same as the top two options for the Model S. In the Model S, those packs give it 270 miles and 370 miles range respectively. Granted, the Model X is a larger, heavier vehicle, but a 90% drop in range? I don't think so.. probably closer to 10%. Also, the top two drive-train options have dual motors, which may offer better efficiency overall.
Because their founder has a lot of money to keep them afloat while they build up their technology and product line, and they are busy selling their drive-trains to companies such as Toyota.
I fail to follow your point; "Do you want an electric car? Do you need a little more space than the Model S can give you? Here, have a Model X." If your complaint is that it's an SUV, then it is a complaint without merit -- there are certainly practical advantages of this platform over that of the Model S (granted, not everyone that buys one will make use of them). If your complaint is about the gullwing doors, then I still disagree -- the take less space to open than a normal door, offer stand-up exits for mid-row passengers, and allow direct access to the third row. This last point is actually a big problem for anyone with two car seats -- if you can't get to the back row with the seats installed, you'll can't use it anyway.
I suppose lastly, if your complaint is that it's an electric vehicle, then get out.
Aikon-
Why are we introducing a dramatically new interface feature for a long-term support (LTS) release?
Since when has temperature been measured in kilofarads?
What, and SOPA won't cost them a dime?
If we give you enough +Funnys, will it eventually bump to Score:6?
We'll make our own Internet! With blackjack, and hookers!
Aikon-
New tagline: "Google is coming"?
I absolutely love the use of "Majel" here; Star Trek has influenced so much of our lives and of our tech, and now that are finally starting to get into responsive voice-operated systems, it shows a great deal of respect to bring it back to the original visionaries.
Aikon-
[...] has a digital analogue.
Guh.. div by zero ><
You should get a research position with the lab, you obviously have a far deeper understanding of the subject.
... get out of my head!
I just started reading it; I'm about 10% of the way through. Since the raw text was freely available (for a while), I used it as an opportunity to learn about the ePub spec and to compile one from scratch. Looks awesome, IMO! Trickiest part was properly replacing the straight quotes with left- and right-quotes =S
This would certainly explain why the Reader link recently disappeared from the Gmail navigation bar. I find it really unfortunate that Google decided to string us along for so long, offering alternatives like "use a bookmark." Google has yet to sell me on +, and I am far from convinced that merging Reader into the fold will do much to change that. The time is fast approaching to move to a new RSS reader.
Aikon-
main() { printf("Goodbye, World"); }
-RIP dmr
Win.
Solar sail, not solar collector.
Aikon-
I am typically onboard with the software purists, but in this case I disagree -- I like the new numbering systems! Well, not exactly the number systems, but the development strategies they imply. For a piece of software that you write once and remains relatively stable, the major/minor/bugfix method is acceptable, because you very rarely do major design changes.
In something like Firefox, Chrome, Thunderbird, and their ilk, the distinction of when exactly a major version number should be bumped becomes a little less clear -- one UI update is deemed slightly more important than another, and all of a sudden you have a major version jump instead of a minor one. With rapid release schedules, the idea is that the changes from one release to the next will /all/ be small, but after a while if you compare e.g. FF 3.18 vs 3.1, they will be nothing alike, so why should they share a common major version number?
Moving to a Year/Month (e.g. Thunderbird 11.09) system I think is overall much cleaner for software releasing on a rapid development cycle.
Aikon-
If you are near the US border, cross over and find a library with Overdrive that will allow you to get a card (many rural libraries will--we need registered users). Sign up for your Overdrive account on one of the library's computers, and through the magic of the internet, you should be able to reserve and check them out from your computer at home.
Interesting idea! If a little fraudulent.. I would first want to make sure there was no way this could come back and affect my existing purchased items. In an ideal world this would be a no-brainer, but this is Amazon we're talking about =/
-Aikon
FYI for Canadians waiting to borrow eBooks for the Kindle from their local library, I received the following response from the Kindle feedback team:
IIRC, there was a motion to delay the court proceedings until the USPTO ruled, but the judge ruled that the court case couldn't wait for the USPTO review.
Wow, what a gong show =/
Aikon-
The courts ruled that there was an infringement, but the deal to use the technology after that wasn't court mediated. That could mean a reversal in the patent status won't automatically even give valid justification for a refund - it'll depend on the settlement terms. If it's written such that one party is paying for technical expertise, design parameters, surcharge per unit installed, or etc... it could be pretty murky.
Hmm, a good point; I've never liked the concept of settling from an idealistic point of view, but this would certainly be an instance that actually backs that up.
Aikon-
Inquiring minds want to know. If the use of said patents was the sole factor in the suit, then I would say, the company is entitled to reimbursement. If there was anything else going on at the time, or if for example it involved two patents and only one patent was invalidated, then I think the case would have to be revisited. IANAPL, this is just wild speculation.
What I want to know, however, is how those patents made it through said suits intact, only to be declared invalid by the USPTO at a later date -- wouldn't, in the course of the suits, the patents get thoroughly vetted by the USPTO, under scrutiny of the court? Or am I applying too much logic and common sense to the patent system?
Aikon-
Thank you for sharing this, that is really an amazing video! It's always good to look back and remind ourselves just how far we've come, and just how thankful we should be for the advances in technology around us.
Aikon-