“From the beginning, the employees dedicated to Project Titan looked at a wide range of details. That included motorized doors that opened and closed silently. They also studied ways to redesign a car interior without a steering wheel or gas pedals, and they worked on adding virtual or augmented reality into interior displays.
The team also worked on a new light and ranging detection sensor, also known as lidar. Lidar sensors normally protrude from the top of a car like a spinning cone and are essential in driverless cars. Apple, as always focused on clean designs, wanted to do away with the awkward cone.
Apple even looked into reinventing the wheel. A team within Titan investigated the possibility of using spherical wheels — round like a globe — instead of the traditional, round ones, because spherical wheels could allow the car better lateral movement.”
This so reminds me of the discussion about fire from the Hitch Hikers Guide to the Galaxy.
The challenge of a self driving car is to get it to drive by itself, not to try to make it look good and to solve a whole pile of engineering problems that have had everybody in engineering looking at them since as long as we have the profession.
Making gadgets and making a self driving car require a different mind-set. The first is an exercise in consumer packaging, the second is a serious endeavor in engineering something tremendously difficult from the ground up.
What the vehicle looks like is not important at this stage, what is important is whether it can be done at all with sufficient reliability to let it out of the lab and into the mass market.
When someone seriously suggests to 'reinvent the wheel' it is time to re-focus.
Yes and no. Part of doing a technology leap is getting people to dream. There are always rough edges associated with the new technology, and in those times, it's nice to be able to still enjoy the dream.
As an example, consider the transition from MacOS 9 -> Mac OS X (public beta days). The tough challenge was what's below the hood, the new UNIX foundation, the NeXTStep APIs, being able to mitigate the conversion pain, etc. Yet in the midst of all these challenges, they added Aqua: an ambitious, over-the-top UI. Was it overkill? Yes. Did it get scaled back? Yes. Did it impact performance? Heck yeah it did. But it did one thing very well: it got people to dream of a (literally) shiny new Operating System. In the moments when Mail.app would get stuck or when one felt the absence of many Classic features, seeing the shiny OS helped sugar-coat the transition and from a UX perspective, it helped people stick with it until the bugs got ironed out.
[citation needed] — how do you know what Apple has or doesn’t have? People are making assumptions based on leaks — leaks, that wouldn’t surprise me if they were actually coordinated and on purpose designed to mislead the media.
Five random Titan engineers wouldn’t just start talking to the Times. Not if they wanted to stay working at Apple. So it makes you wonder if their “leaking” is designed to mislead.
However, in the OSX analogy above, Apple had a very good platform (NeXTSTEP) that had been commercially available and proven in real-world use for ~a decade before they started modifying it to become OSX. There is no similarly mature self-driving car platform for them to be working from, and we can be sure of that.
Hah, yes. Glad to see others were weirded out by that too. It's so strange to see people seriously discussing how to redesign the trimmings, when nobody even has an existence proof that fully autonomous navigation _is even possible!_
And it's not like robotics research hasn't been working on this problem for half a century now. It's a hell of a hard problem that one can't just product-design their way out of.
Apple often tries to re-engineer the thing they develop.from the ground up. Seems it started this way on Titan, too, then scaled back and decided to focus on the main problem: safely getting around. Nothing wrong with this I think.
On reinvented wheels, early ideas rejected today may get a second life later, e.g. spherical wheels for moving in very constrained environments.
It is absolutely fine to re-engineer something from the ground up once you have a working example in your hand. But before then you are simply wasting your time.
the iPod was not the first music player, the iPhone not the first smartphone. Re-engineering those was the only way to get them to market in a way that might drive mass adoption.
As for the spherical wheels, yes, however such a development is totally tangential (pun intended) to self driving cars.
> But before then you are simply wasting your time.
I disagree. You seem to be discounting the learning aspect. Building an institutional knowledge base of the pile of systems that make up a car is a large task by itself. Different shops approach it differently. One may obsessively reverse engineer the competition, another might tinker with longtime designs.
I fully expect the managers in question saw the spherical wheels as something with maybe a 2% chance of becoming a reality, if that. The point at that stage is not to take a particular design to market, it is to explore the problem space, develop expertise, and work out what strategy to pursue.
From this article, it sounds like they figured out the strategy.
I can't see spherical wheels working well. They would have a smaller contact patch on the road surface than a standard wheel, and consequently less traction.
And then there is stronger braking to be considered, which almost always is some kind of disk brake which you can't do if there is no shaft to mount one on. Which means the spherical wheel system would have to be oversized to compensate for lack of such a shaft even if it would work to drive the car. Magnetic wheels have other interesting problems that would need to be solved such as when two cars get close to each other the wheels would start to attract or repulse depending on their orientation.
This is mostly likely not something that could be rolled out even in a concept car with present day technology unless there is some kind of trick that I'm not aware of. Halbach arrays are not without problems if you allow them to be unconstrained in all dimensions.
It's a lot simpler with independent electric motors per wheel, but generally not that useful as self drivings cars can already parallel park just fine.
That's true. But then again, I did come up with live streaming video on the web and some other lesser known bits and pieces of technology. And I'd argue my lego sorting machine also required plenty of creative thinking.
There are definitely major challenges, although maybe those could work in areas where the motion is slow but constrained (e.g., a cart to move cars in/out/around a dedicated parking lot). Maybe flatten the surface used for normal motion and use sides for infrequent, slow maneuvers. I do not know.
But those ideas are tangential (being generous) to self-driving, so better not steal cycles from it.
Whenever Apple introduces a new product line, they do so with a major usability innovation. In fact their major new lines often have several usability innovations, that work together.
The iPod had click wheel. The Mac had the GUI. The Apple II was plug-and-play in a time when people built from scratch. The iPhone had multi-touch the Apple Watch had a bunch of stuff.
The challenge is not to solve an already solved problem.
Remember when the iPhone was introduced? It's obvious now it was quite revolutionary-- but at the time people complained that it wasn't anything significant and that lacking a keyboard meant it was doomed to failure.
If apple introduced a self driving Camry it would not really be compelling enough. For a new product category, Apple's only interested if they can create or redefine the category.
What if 'self-driving' was just one possible feature among many in a potential Apple car and wasn't necessary? I'd happily buy an apple electric car that I had to drive myself.
You're shitting on the project without knowing anything about it yourself... but you ask how he can be interested without knowing details?
And yes, the brand-- which is to say, their 40 year history of delivering products at a level of quality and innovation unmatched by any company in the world-- is enough to be interested in anything they produce.
They definitely should have not wasted time with multitouch and just used a stylus and a physical keyboard for iPhone. Right? Any time someone says “no stylus” it’s time to refocus right? After all, that just isn’t how portable devices in 2002 already worked?
Apple doesn’t care about incremental improvements when talking about a new product category. They look to leapfrog. Have you considered the benefit of spherical wheels? I haven’t, but I am not part of that project.
Incrementalism would have been making a better Apple Newton or a prettier Palm Treo. Or a slightly better Tesla. Why bother entering the car market if you’re just going to marginally compete with everyone else?
It seems like you don’t get Apple or their history of product development.
> It seems like you don’t get Apple or their history of product development.
I get it just fine. They are improved user interfaces over things that already existed. Changing the main method of transfer of energy from the motor to the road in a vehicle is a fundamental change that has significant implications for everything else in the vehicle to the point of making it very unlikely that that vehicle will ever be completed.
People would not buy a car with spherical wheels for the 'cool factor' they would not buy it because it is untested technology with significant implications for the safety of the occupants and others on the road.
> Apple doesn’t care about incremental improvements when talking about a new product category.
Well, what is a leapfrog to you looks suspiciously like an incremental improvement to me. There were some phones that had a fair amount of resemblance to the iPhone before it launched and the iPod had a large number of predecessors as well. And without iPod no iPhone.
Arguably the iPhone could have been a success without multitouch, it's perfectly possible not to have multitouch and at the same time not to have stylus and not to have a keyboard.
As for the benefit of spherical wheels, yes, I can see some benefits, but I can also see significant drawbacks that are not easily engineered away.
A car is a device on an entirely different plane than a phone, the only time your life depends on your phone is when you're trying to call 911 after an accident, with a car you (and the people on the road around you) depend on your car from the moment you get into it until you disembark. That requires a more conservative kind of development.
Such as Tesla is showing, and which they occasionally get wrong, usually when they release stuff that isn't quite as reliable as it should be for mass deployment.
They also tend to qualify it as "refinement" instead of "invention" because their definition of "innovation" can't include Apple for some dogmatic reason.
>The challenge of a self driving car is to get it to drive by itself, not to try to make it look good and to solve a whole pile of engineering problems that have had everybody in engineering looking at them since as long as we have the profession.
This is why I believe that comma.ai was so visionary, say whatever you want about George Hotz's personality. He truly _gets it_ that self-driving is the critical part, not the car.
"Visionary"? Hardly. His self driving technology was basically a big giant hack. He is a good hacker but calling him "visionary" is a bit of a stretch.
Supernova's have a bright future too. But a very short one.
Comma one has been canceled and the new offering is more along the lines of a kit for DIY car hackers than for serious deployment and at a guess if you would be involved in an accident while deploying one of these kits your insurance would be void.
comma was a scam. The car Hotz used for his "demonstration" already comes with the functionality he "demonstrated" from the factory. He just added wires and a joystick to his dashboard.
Agreed. It seems like a great deal of engineering distractions from the core problem to solve. Seems like they were using precious resources to fluff up a potential keynote and make a car from a scifi movie.
You're missing my point. It may not be stupid to reinvent the wheel at all. But that's not a project that you should mix with inventing a self driving car unless you conclude that spherical wheels are the only way a self driving car will ever become a reality.
Similar to how every software application project could theoretically result in a new database, a new operating system and if you really want to go all out a new CPU it is much more efficient to concentrate on your application if you actually want to see it go to market.
> Goodyear released spherical wheels.
No, they didn't, that's just some fancy CG stuff, not an actual product.
Also, it just so happens that Good Year is in the wheels-and-tires business so for them such research makes good sense, and of course it is a theory of a concept, not an actual proof of concept much less something that they are ready to roll out. It's more like serious science fiction even than actual science, it's how things maybe could work, not how they actually work.
>You're missing my point. It may not be stupid to reinvent the wheel at all. But that's not a project that you should mix with inventing a self driving car
That's only true if the team that reinvents the wheels and the team that does the self-driving tech is the same, and you're stealing members from the latter to the former.
Obviously those are not the same teams, nor they need to be.
And when you get out with your self-driving car, as 3-4 companies will do at more or less the same time or within a few years of each other, having other great new innovations on top of that will give you an edge.
The degree to which globular wheels would complicate such a design is such that it would leave you being passed by your competitors right out of the gate, on top of that it would complicate all kinds of things such as certification and potentially reliability and safety as well as supply chain issues after delivery.
Solving too much is a fantastic way to crash a project.
>The degree to which globular wheels would complicate such a design is such that it would leave you being passed by your competitors right out of the gate
We don't know that. We just know that we're not familiar with them. If anything, globular wheels could make some kind of automated steering easier.
And of course, it's obviously not like Apple only tried that design: they tried globular wheels, fat wheels, thinner wheels, wooden wheels, and what have you to see what works better -- like they did when they designed the iPhone, etc.
> tried globular wheels, fat wheels, thinner wheels, wooden wheels, and what have you to see what works better
Yes, and 'standard wheels' would have saved them time, money and other resources and would have increased the chances of bringing a self driving car to market.
Seems like they were biting off way more than they could chew.
If Apple partnered with an existing car company to apply their design principles on top of an existing car platform (e.g. https://en.wikipedia.org/wiki/Fiat_Mini_platform ) they could see a lot of success if they weren't too ambitious. They wouldn't win if they tried to reinvent the wheel because there would be far too big of a chance of either taking 10 years to build nothing or for building something that ended up being overly strange (e.g. Segway)
Build a car that was familiar built out with quality materials and an iOS dash interface and you'd sell like hotcakes.
We have the iPhone because Apple was so ambitious. Imagine if they had just partnered with existing phone manufacturers rather than trying to build a magic touch slate.
Wait, we do know what would have happened - the Motorola ROKR, which everyone should be forgiven for forgetting.
> We have the iPhone because Apple was so ambitious.
When you say that, you conventiently forget that Apple re-invented the smartphone. It was an proven thing, which already sold in spades in the tech/enterprise market.
They took something which existed and was awkward to use, and re-did the UI layer of the whole thing. They refined something else which was already proven. They didn't invent something original from scratch.
Here Apple is clearly trying to design a new kind of a car, where every part is different from what's already out there in the industry. Where none of the new bits has been invented yet.
They are trying to do original discovery in addition to refining things, in an industry where they have absolutely zero experience.
> Project Titan looked at a wide range of details. That included motorized doors that opened and closed silently .... Apple, as always focused on clean designs, wanted to do away with the awkward cone.
That they were even considered things like this important in a self-driving car when they hadn't even solved the self-driving bit (or even car-bit) yet tells me all I need to know about the realism of this project. There was none.
Also, the iPhone was preceded by years of producing iPods, which at least gave them expertise in portable electronics. What has Apple produced that is remotely similar to an automobile? It's not just design expertise, but the supply chain and manufacturing. Auto parts industry is massive. Is controlling the parts for a computer on the same scale as for an entire automobile? I suppose if Tesla can do it...but Tessa's cars so far don't seem as ambitious as what Project Titan was looking at.
Remember Tesla's first car? It was not the Model S. The Roadster was based on a Lotus chassis. They built a car on an existing vehicle platform before venturing into producing their own.
>When you say that, you conventiently forget that Apple re-invented the smartphone. It was an proven thing...
That's what it looks like from the outside, but listening to interviews with current and former Apple people that's not at all how it looked from the inside.
When they initially developed the OSX derived core OS, System architecture and UI libraries they weren't thinking about phones at all. It was intended to be a tablet computer OS. It's only fairly late on in development that Jobs pivoted the team to adapt the technology to a phone form factor and tacked on a phone app and cellular radio. It was not at all developed from the starting point of looking at existing phones and going from there. Things like touch swipe to scroll and pinch to zoom were taken straight from contemporary touch UI research, not Palm or any other existing commercial products.
Interesting what-if: would the iPod touch have been significantly less irrelevant in absence of the iPhone?
Could the iPad have been a success without the iPhone paving the way for apps?
I remember the last generations of high end feature phones as quite capable media consumption devices, who knows what could have come from that strain of development had they stayed in the limelight a few years longer.
iPod Touch sales were about one quarter as many as iPhone sales. That came to 100 million units in the first 6 years. Given their lower ASP that's a bit less in revenue but it's still pretty significant.
Sure, without the iPhone they'd probably have sold a lot more, but it's not a very compelling counterfactual. Palm started off selling PDAs, but a smartphone is really just a PDA with a cellular radio and a phone app. By the time the iPhone came out standalone PDAs were already dead.
I don't think it would have made a lot of difference to the iPad. It is what it is. It might have had more of a 'wow' factor rather than the 'just a big iPhone' jibes, but even so it sold, and is still selling in very large numbers. Sure sales are down, but they're still selling about 40 million a year. That's more than Dell's annual PC sales and twice as many as Apple's Mac sales, it's also one sixth of global PC sales. So bear that mind when people say it's a declining business. It's slowly declining from spectacular success.
Or you know, the have multiple teams, and they don't just want to put out a "self driving car" out, but a great self driving car that rethinks what a car should be like -- on top of "self-driving".
But does that even make sense? That would mean they redesigned something that they are not able to build in realistically at least the next 5-10 years. Or to go even further, they tried to make something better that does not exist yet. Wouldn't it make more sense to just go for the self driving car first and then, after you are sure that you can build that, creating teams which make it better?
>That would mean they redesigned something that they are not able to build in realistically at least the next 5-10 years. Or to go even further, they tried to make something better that does not exist yet.
At Apple don't do basic research and leave it at that.
They are trying to build a commercial product.
In that sense, it makes sense to try to solve the problem of self-driving along with how an Apple car should be like (besides self driving).
So that, if the self-driving research pans out, they have a complete product, not just some run-of-the-mill car design that basically sells for its self driving capability.
And even if their self-driving thing doesn't pan out, they can always enter the car market licensing some other self-driving technology (like they license/buy batteries, ssd, cpus, etc) but with their own spin on the general product.
> In that sense, it makes sense to try to solve the problem of self-driving along with how an Apple car should be like (besides self driving).
No it doesn't. Self driving takes decades to solve, designing pretty cars takes a year or two. There is an order of magnitude difference there.
They were seriously trying to constrain the location of the LIDAR before actually knowing what types and numbers of LIDAR a self driving car actually needs! That is utterly backwards.
>No it doesn't. Self driving takes decades to solve, designing pretty cars takes a year or two. There is an order of magnitude difference there.
They are not the same teams doing each, so there's no opportunity cost involved.
And whether it might or might not actually "take decades", if Apple considered it would "take decades to solve" they wouldn't be interested in it in the first place. The idea was that we are close to a breakthrough and commercial applications, not that we'll have something in the market by 2040, maybe.
So, for Apple it was more like "can we get something out in 5-10 years at most? Oh, and if it just self-drives, nobody will care -- by that time there would be 10 more self-driving cars from Google, Tesla, Audi, GM, etc. We also want it to be great/different in other aspects".
>They were seriously trying to constrain the location of the LIDAR before actually knowing what types and numbers of LIDAR a self driving car actually needs! That is utterly backwards.
There's nothing backwards about it -- given that the car will need a LIDAR (which I don't think their self-driving researchers where doubting), they should explorer the design space for placement/hiding it etc.
I'm not sure why you're arguing with the person that keeps responding to you. I think you've clearly made the point that Apple feels like they don't need to work off of existing design or technology methodologies and yet this person seems to think that Apple's entire predicted failure is that they're not working off of existing processes and technologies. He seems to be arguing a straw man of your argument rather than your actual argument and part of me feels like he's being willfully disingenuous in doing so. It's "Apple can't possibly do it different than everyone else because everyone else has only been able to do it in this one way" without any room for the possibility that the "best" (subjective, of course) solution may be one that doesn't exist yet because it requires the very paradigm shift you're referencing.
What you are suggesting is like designing how a hotel will look before you know where it will be or how big it will be.
It's completely backwards. You can kind of do it, but it's a huge waste of time and money.
Apple did not do that because they "knew what they would need, so let's get started", they did that because they had no clue how to make a self driving car, but despite that, the team needed to show something, anything.
>What you are suggesting is like designing how a hotel will look before you know where it will be or how big it will be.
Well, you know most things. You know you're making a car, you know it will have LIDAR, you know it will be self driving etc. You are free to (and if you want to win time, you pretty much got to) design the car, the interior, materials, displays, etc -- even the transmission, engine and wheels -- independently of the self-driving algorithms.
If and when those self-driving algorithms are ready, you don't then have to spend another 1 year to design the rest.
There's not any real dependency between them -- so much that you can even test your self driving algorithm in ANY random car as almost all companies do. It's not like being a self-driving car dictates the car form and the latter has to be designed around that property.
(That said, before even Google's car and the self-driving hype, a lot of rumors insisted on Apple merely making an electric iCar -- Tesla competitor, not some full self-driver type 5).
>Apple did not do that because they "knew what they would need, so let's get started", they did that because they had no clue how to make a self driving car, but despite that, the team needed to show something, anything.
I, for one, have no doubt that Apple got some top notch researchers in ML and driving car technology. I also have no doubt they got some top notch car guys (plain car). I also have no doubt that there's nothing to know about "how to make a self driving car" that the Apple team doesn't know (or any team for that matter), apart the ML/self-driving algorithm aspects. So there was nothing about the form of the car holding them back.
I don't agree with everything you said, but let's assume you are right - for the sake of the argument.
So what's the plan? Design a car, then let the designs sit on a shelf for 10 years (or more)? In 10 years tastes will change, and the people who made the designs will no longer have them fresh in their mind - if they are even still employed by Apple.
> They took something which existed and was awkward to use
This is the key difference: people already love their cars, more than they love their home and more than they love their iPhone. The enjoyable smartphone was an unsolved problem, the enjoyable car has been comically over-solved for decades.
Everything unpleasant about cars is happening to the outside. Not just to pedestrians, cyclists and residents, but also to other drivers: just imagine how much nicer your commute would be without all the other commuters. A Lada on an open road would be more enjoyable than a Rolls Royce in a traffic jam. It's a commons problem, one that cannot be designed away with cute UI and expensive surface finishing. Even self-driving won't really solve that, as anyone who has been a passenger in gridlock should know. The only way to significantly improve transport is by making it more space-efficient by cooperation. Public transit with the Apple doover? Could be amazing, but it's just not in the Apple DNA. Autonomous cars with extreme platooning? Massive potential, but just like with public transit, the biggest benefit goes to those who refuse to cooperate and stick to individualistic reaping of the benefits of lower congestion.
> This is the key difference: people already love their cars, more than they love their home and more than they love their iPhone.
I'm part of that (seemingly ever shrinking) demographic that does indeed love cars; I love their shapes and their looks, the roar of an engine (or the thrust of an electric, both hit me in different places), but even I have to admit that people like me are going away. The vast majority of people want a way to get from point A to point B relatively quickly in some measure of comfort; they don't give a shit how cheaply the car is built, as long as it comes with a warranty and the cabin is spill proof, and they don't care how ugly or bland the outside is as long as it keeps the rain out. There's not nearly the same appreciation for cars and driving as their once was, which is why I firmly believe a lot of people these days can't drive very well nor take decent care of their cars; they don't care. Driving is a means to an end, whereas to me, driving is half the fun of doing anything.
> The enjoyable smartphone was an unsolved problem, the enjoyable car has been comically over-solved for decades.
I'd say the enjoyable car and the enjoyable smartphone (iPhone, yes I know, my opinion) have about the same market share these days. :)
I don't mean to say Apple was on to something: I think it was doomed from the start for many of the reasons listed here. I just think you're misreading the market is all. That being said, I do hope the self driving revolution leaves room for enthusiasts who truly love putting the hammer down and seeing what our machines can do; I'm willing to pay more for manual mode or even a much higher fee to continue to have a license to operate; I understand what being put into an enthusiast market means and I'm willing to put up the cash.
There is no such thing as a UI layer. UI and function are inextricably linked.
For example, see iPhone's voicemail. Or the touch screen. Or the app store. None of those things could have been executed by UI teams at any other device manufacturer at the time.
Only when you're talking about software, which is arguably the "UI layer" of a physical computing device. Hardware needs actual things which do the things, independent of interface.
Palm OS apps were using swipe to scroll for several years before that. As far back as at least 2002.
That doesn't take away from what Apple did. They really took all of the best ideas (and in many cases hired the engineers who made them in the first place) and put them into one incredibly tight and delightful package. Just about every individual feature can be traced to Palm, Symbian, or a host of other systems... but the magic is making the whole thing work.
Still, it's important to remember that the iPhone was largely a logical evolution more than something invented by Apple wholesale. The iPhone was not the first touch screen slate phone that I ever saw FWIW. That honor belongs to an internal project at Nokia (based on Series 60) that died under it's own engineering weight.
Which again is meant as a compliment to Apple. They actually were able to execute on the thing where others failed.
That is seriously laughable how bad that is. The parent to your comment either doesn't remember what things were like prior to the iPhone or they're intentionally ignoring the differences.
Capacitive screens were less responsive than resistive screens.
The difference was that you used your physical finger instead of a stylus. Personally speaking, I preferred resistive screens for their responsiveness and accuracy.
The capacitive screen was needed for "pinch to zoom" and other gestures of the modern era. The delay in the UI compared to resistive screens (as well as the higher-CPU time required for processing) turned out to be a smaller deal than multi-touch technology.
Is there some more information on that? I believed so far (or the industry made me believe) that capacitive screens were much faster than the resistive ones.
I don't have like, hard tested data. But the delay is enough that experience was all I needed to convince me.
Nintendo DS / 3DS and Wii U are all resistive screens. I also have experience with resistive screens of Palm Pilot and Palm phones of the early 2000s. And all of those were more "responsive" than a 2007-era iPhone, despite the iPhone's significantly higher processing power.
Play a serious game like Monster Hunter (very timing intensive) and compare it to a serious timing-intensive game on a capacitive screen (I know I've seen people play Marvel vs Capcom 2 on an iPhone emulator...). The lag and delay is noticeable even in the modern era.
But people wanted multi-touch pinch to zoom. Capacitive sensing also requires a microcontroller to literally "charge up" the screen over and over.
When your finger is on the screen, it "charges up slower" (because your finger changes the capacitance at that location). Innately, that "charge and discharge" cycle requires a measurement over time.
And to make sure that power isn't wasted, only one part of the screen is often tested (there are grids and stuff that then calculate where the fingers or multiple-fingers are located). So innately, there's a delay as the "scan-lines" of the sensors test each point of the screen.
Resistive screens instantly tell you where the stylus is without any such delay or processing. So it just makes sense.
I don't have any direct links, but the latency on processing touch input from a capacitive display can be as high as 40ms, remember there is a lot of filtering going on and spurious crap that has to be filtered out.
Think how crazy the trackpad goes on a cheap laptop when you plug in a knock-off power supply with poor power conditioning.
No. Apple invented the smartphone. There were no smart phones before the iPhone. There were PDAs and feature phones.
People like to pretend Apple never invents anything and to do so they always point at vaguely similar things that aren't nearly as good as if they support the point.
Someone one here once told me that Apple didn't invent multi-touch because it existed in the movie 2001: A Space Odyssey
> When you say that, you conventiently forget that Apple re-invented the smartphone. It was an proven thing, which already sold in spades in the tech/enterprise market.
Isn't a car a proven thing? All apple is need to do is re-invent it and slap a nice AI on top of it.
They have no clear visionary at the top vetting things for quality user experiences. Had Jobs still been with us we might actually have beautiful 3D Touch experiences. We might be seeing a beautiful refinement of the driving experience. Instead they're flailing. Hopefully this is a realignment and rededicated effort to do what they do best: make cool, proven tech perfect and accessible.
there is a 20+ year history of PDAs before the iPhone. For all intents and purposes my 1998 Windows CE Casio PDA looks and acts like a first gen iPhone. It's home screen has a grid of 3x4 icons of apps and general works very analogous to the iPhone. Apple did an amazing job of polishing the PDA but they made an incremental jump being at the right place at the right time with affordable cellular data and capacitive touch and an amazingly well designed ui
it sounds like they we're doing much more with their car efforts
> For all intents and purposes my 1998 Windows CE Casio PDA looks and acts like a first gen iPhone
I assume you also think a Hyundai looks and acts like a Ferrari.
Because that is what you are saying. I owned that PDA as well as the Treo 650 which was far better and the iPhone isn't an incremental jump. It was a complete revolution.
> I assume you also think a Hyundai looks and acts like a Ferrari.
He argued against an assumption that apple reinvented smartphone. If you want to use this argument, you have to show that people think that Ferrari reinvented the car.
Only if Ferrari came into the market with a bunch of innovations that every manufacturer then adopts. I would call that a reinvention and more or less what Apple did.
People were using styluses, the phones were blocky and thick, the UI was confusing and adopted from desktop instead designed for mobile, hardware keyboards, small screens, business focused
I had every "smartphone" and internet tablet back in day running on Palm, Symbian, Blackberry. All of those OS's are completely irrelevant today because of how far Apple pushed the envelope. Though I thought Palm was headed in the right direction with the Pre.
You can call it an evolution but it was such a major leap it was essentially a redefinition.
That's like saying that the first mobile phone used technologies that were all proven and that the inventors just combined them in a much better way because radios and phones existed. The combination itself is exactly what made it an invention and a revolution. Nearly every technology right now that's a revolution (Uber, for example) is a revolution precisely because it did something that's never been done before by standing on the shoulders of what came before it. The difference is that the combination and or features gained from that combination allowed the invention to leap frog over what existed before it.
reinventing the wheel and more changes to how current equipment works, in particular viewing aids, would bury this car in regulatory hell. it would take years to get permission for it to be on the road. figure it this way, if it takes many years just to get permission to change headlight technology can you imagine the time it would take to adjust to what Apple was proposing?
phones are dead simple compared to cars because phones NHTSA and Insurance issues to face up to
With the percentage of this project being a drop in the bucket compared to the 260B war chest I have nothing but positive thoughts for Apple attempting ambitious projects. In the next ~10 years they could be a trillion dollar company if they figure out how to get iPhone like growth out of another industry.
Yeah...I suspect a lot of people said something similar when it was rumoured they were going into the phone business.
I know a car is a very different beast to a small touchscreen computer that makes phone calls, but at the time everyone was looking at it from the perspective of a computer and entertainment company making a phone in a cut-throat thin-margin industry. What they did is make an iPod Touch with a cellular component, priced it higher than the flag-ship phone of the day and started with a single and not-very-loved service provider in the United States.
> a consumer electronics company that wants to enter the automotive industry.
I'd argue electric cars paired with automation are as near consumer electronics as they are to the automotive industry. Shedding the engine, transmission, steering column, and pretty much all mechanical systems bar the electric motors and braking systems, why couldn't they design it in California and outsource manufacturing to Hon Hai/Foxconn and their partners the way they do with their phones?
> pretty much all mechanical systems bar the electric motors and braking systems
... and the shocks and dampers and steering and servos and diffs and transfer boxes and electronic stability systems and dozens of sensors regularly exposed to harsh conditions and lights and crumple zones and doors and windows and air bags and seat belts and seats and air conditioning and ...
Elon Musk said something very true about the myriad of components and OEMs Tesla use - that having 99.9% of the parts on a car available and working, is a lot like having 0% of the parts.
You make a good point but my question still stands, why couldn't they design it in California and outsource manufacturing to Hon Hai/Foxconn the way they do with their phones? Unlike Tesla, sourcing the parts wouldn't be Apple's problem.
Because outsourcing car manufacturing doesn't make much sense. The transportation costs eat up most of the savings. That's why Toyotas, Volkswagons, etc sold in the US are made in the US.
One shipping container holds 60,000 iphones. One shipping container holds one car.
I agree. and it's not just transportation, or even taxes, it's also the cost of labor. iphones are assembled in china because chinese workers are cheaper than automating those particular jobs. cars, on the other hand, are almost entirely made by robots these days.[1] there's not as big a price difference between chinese and american robots as there is between chinese and american humans.
apple has a history of entering fairly high-margin markets where the existing products don't look or feel or function very well, and then they give it the jony ive treatment. but tesla is already there, they applied apple's playbook to cars and honestly took much bigger risks to get there than apple ever would. tesla took on a LOT of debt to be competitive, and it'll be a while before they even have profit, much less good margins. it'd be very hard for apple to compete. if apple ever enters the car market, a tesla acquisition is the only thing that would make sense to me.
Fascinating! Specifically with respect to NAFTA & its possible renegotiation.
It also makes me realize how terrifying it must be for major manufacturers to site capital-intensive factories. Wrong country? Or country that becomes wrong country a decade later? 25% tariff.
> Because outsourcing car manufacturing doesn't make much sense.
#1 It allows you to focus on design as opposed to supply chain management. #2 If the supply chain is centralised where production takes place then that bit of missing trunk carpet, as Elon Musk lamented, won't take two weeks to get to you and hold up the production line - It's down the road.
> One shipping container holds one car.
Which makes me think - the economics change if the vehicle you're shipping is only 1/2 or 1/3 the size of a typical car. When you have an electric automated vehicle why are you sticking with a sedan or truck sized vehicle when you can move individuals or couples?
Electric cars stick with the sedan/truck model for the same reason non-electric cars do: it is what people actually want. 90% of the time a car/truck only carries one person to/from work with nothing else. However that other 10% means the single occupant car will not work.
I have a car that gets 40mpg, and a truck that gets 18mpg. After you account for the extra insurance, license, taxes, and maintenance on my car, I'd be money ahead getting rid of the car and just driving my truck for everything even though times when I need a truck and a car will not do account for maybe 2% of my driving. Note that my car and truck a both paid for, if I'm making payments on both the math is even more lopsided toward not having a car.
People keep pointing out that I can rent a truck when I need on. However this is something is is true in theory, but not practice. It is actually hard to find someplace that will rent you a truck that allows you to use it. Want to take your rental truck off road - not allowed. Want to tow a trailer - most don't allow that. Want to put a sheet of plywood in the back - most don't allow that soft of damage. (though in this case the store probably has the best price and will allow it)
> Electric cars stick with the sedan/truck model for the same reason non-electric cars do: it is what people actually want.
Precisely this. Actually, you don't need to take our word for it. Several manufacturers small and large have tried the "tiny electric car" concept in Europe, a continent much more in love with small cars than the US, starting over a decade ago, and none have actually made it a success. E.g. the Reva (G-Wiz in the UK) was in sale from 2001 to 2013 with a total of 4 600 cars sold worldwide.
Compare that e.g. to the sales volumes of the Renault Zoe (60 000 cars sold since 2012) or the Nissan Leaf (250 000 cars sold since 2011).
You make the mistake of thinking Apple cares about market share. Their philosophy has always been to take the largest share of profit [1], with their phone market share hovering around 10% depending on country. Similarly their computer market share hovers around 5%, but it remains highly profitable.
Pair automation with a small, likely stylish car and demand from city-dwellers would be enough if Apple released something compelling.
Apple has never been a company that serves everyone, hence the reason they have a only a minor market share. They care about aesthetics and ease of use - which is why there isn't the tractor equivalent of a smart phone in their lineup. Your shoulder use cases means you probably wouldn't buy a vehicle made by Apple, similar to how if you need X feature in a phone and Apple doesn't provide it you'd buy a suitable alternative.
Let's go backwards with this one: What are most road trips for? Commuting. Would Apple want to make a vehicle for all uses and conditions? Doubtful. Would Apple want to make a truck? Highly doubtful.
They only need to make a vehicle that covers a considerable number of (but not all) use cases. If it can get people to work, to a store, to a friends house, to a restaurant or bar then the number of people who would want one is considerable. It would probably be better suited to those living in cities, but that's still a lot of people who notably require something that doesn't take up much space as parking is at a premium. Better yet, the vehicle could park itself, return home when not needed, pick up the occupant on demand or even car-share the way Elon Musk predicts Tesla owners might lease their vehicles.
> Seems like they were biting off way more than they could chew.
They are building a patent portfolio that will be valuable over the next 20 years. No way will Apple enter a completely new market outside of consumer electronics.
Very large tech companies always have people looking into weird slightly bullshit things. Doesn't necessarily mean that they had any real intention of committing to these ideas.
Someone correct me if I'm wrong but it was my understanding Apple specifically stopped having teams "looking into weird slightly bullshit things" when Jobs returned.
The Apple Knowledge Navigator video comes to mind, it feels very similar to video-vaporware like Microsoft Origami and Microsoft Courier
Spherical wheels are such a stupid, dangerous idea. The contact patch on regular tires is already tiny. Make them spherical and the contact patch becomes even smaller, which will cause them to lose traction and spin out in any rapid maneuver (like to avoid a collision).
Only if you massively increase the PSI so that the tire stays spherical.
If you keep the PSI at normal levels the contact patch will be exactly the same size as it is now, and the tire will deform on the bottom. So just design it to be extra flexible.
Dropping the pressure in the tire will lead to (way) higher risk of tearing of the tire fabric. You should never drive with a deflated tire, it multiplies the risk of tire failure like crazy.
So no, deflated spherical wheels is not a good idea :/
No that's not how it works. Look at a regular car tire. It's basically flat perpendicular to the direction of travel so the entire width of the tire is in contact with the ground. With a spherical tire the sides bend up away from the ground and only a single point is in contact. In order to get a larger contact patch you would have to run much lower tire pressure leading to worse handling, higher fuel consumption, and accelerated tire wear.
The surface contact of perfect cylinder (a regular car tire), and a perfect sphere (the iTire) is the same: 0 cm^2.
From that fact, you are saying that "obviously" the deformation of a cylinder (with some diameter/width ratio) filled with gaz at a certain pressure against a flat surface will lead to a higher surface than a sphere with the same pressure?
It's not obvious at all. Give me math+physics proof or GTFO.
>The surface contact of perfect cylinder (a regular car tire), and a perfect sphere (the iTire) is the same: 0 cm^2.
A perfect cylinder has a line of contact with the road: the width of the wheel. A perfect sphere has a point of contact.
Obviously you wouldn't see perfect eithers when talking about real-world tire implementations, but the perfect examples here are indicative of cylinders having more surface area with higher air pressure, whereas higher air pressure is the preferred state due to wheel wear and tear and handling issues that occur at low pressures.
Not to mention cylindrical wheels inherently resist lateral motion, have lower unsprung weights/volumes, and don't have the unnecessary engineering struggles of turning a spherical object into a pneumatic device.
I'm all for trying new things and testing wacky designs, but lots of people have looked at spherical wheels over the past few decades (Goodyear's implementation is a personal favorite[1]) and concluded they're pretty much just good looking, rather than an improvement in engineering over current wheels.
Given how good they look though, I'd love for someone to find a way to make them actually work.
> A perfect cylinder has a line of contact with the road: the width of the wheel. A perfect sphere has a point of contact.
And both have an area of zero. And the area is what matters here.
> but the perfect examples here are indicative of cylinders having more surface area with higher air pressure
This is not true. It's physically impossible. (What you have done is the geometrical equivalent of dividing by zero to prove 1 = 2.)
Weight of car / Contact patch / number of wheels = PSI + strength of sidewall.
This equation is exact. The geometry of the tire makes no difference. You can not create pressure out of nothing. The pressure on the ground must exactly equal the weight of the car.
And the pressure on the ground must exactly equal the pressure in the tire adjusted for the size of the area of ground contact.
Do you see how for any given PSI (including the strength of the sidewall) the contact patch is an exact figure? The forces must all be equal, it's a basic law of physics.
There are certainly engineering issues, I'm not arguing about that. But the size of contact patch is not one of them. Put the same PSI in a cylindrical or spherical tire (neglecting the PSI contribution of the rubber) and the contact patch will have an identical size.
Typically wheels are made of metal wires and are stiff - so they don't like large contact areas because it means lots of flex. But it doesn't have to be that way. You can make a material that doesn't care about flex - if would be harder to make obviously, but it's not an impossible obstacle.
No that's not how it works and you're missing the point. In order to achieve an equivalent size contact patch a spherical tire will have to deform more than an equivalent cylindrical tire. With current materials this means you'll have to run it at a lower inflation pressure in order to achieve the necessary deformation, leading to all the problems described above.
It looks kind of cool, but a bike without spokes is a really bad idea.
Spokes give very high strength to weight ration for wheels. And having cog teeth close to the wheels is guaranteed to get clogged with crap. But it looks kind of "cool" to those who don't know any better.
What if the new car included a compressor that inflated/deflated the sphere as needed for traction control? I just made that up but that seems like it would make the idea a little less crazy.
A team within Titan investigated the possibility of using spherical wheels — round like a globe — instead of the traditional, round ones, because spherical wheels could allow the car better lateral movement.”
Somebody liked the Audi RSQ from Minority Report.[1]
ISTM you could get all the same benefits much more easily using four-wheel independent steering, on regular, cylindrical wheels. The design could also be much more compact by sacrificing fully horizontal motion. (IE if the rear wheels only turned up to +-30 degrees, say.) It could still park very tightly using a zig-zag motion, and in any other situation tighter turning wouldn't be useful.
Porsche (and possibly other companies) are already moving in this direction, with newer models featuring computer-controlled rear wheel steering. At low speeds the rear wheels steer in the opposite direction to the front, and at high speeds in the same direction.
Active rear-wheel steering actually has a far larger history than its recent resurgence from Porsche, actually coming from Japanese manufacturers with mostly hydraulic (not electric) implementations.
* Nissan stared offering it with several 1986 Skyline trims, and would also offer it on Z32 300ZXs.
* Honda starting offering it on the 1987 Prelude, and also on the Accord starting in 1991.
* The 1988 Mazda 626 sedan (predecessor to the Mazda 6) had it.
* Toyota offered it in Japan on the Camry/Vista for the 1988 model year.
* ... and many, many more. From MPVs to pickup trucks.
The modern resurgence started again with Nissan, with several Infiniti models (the M and Q) offering electric versions from around 2006, and it appeared in the R35 GT-R. Though BMW was technically first with the E65 7-series. Porsche got into the game with the 991 911 GT3 (and optional on all 991.2 911s) because it alone hacked 1.5% off of lap times. The benefit of the newer setups is how wonderfully simple it is in terms of parts, complexity, and reliability (and no more hydraulic leaks!)
Having driven both the R35 and 991.2s, the difference is pronounced. RWS is one of the reasons why the GT-R could manage itself (it is approaching 4000 pounds) as well as it could around the track, and why the latest 911s I've driven on track were so eager to dive-bomb apexes compared to any other 911 I've ever driven.
I remember when people went crazy trying to nitpick the probability of spherical "wheels" when "I, Robot" came out and Audi had designed a car with exactly the type of system being mentioned. The general consensus, and even Audi agreed, was that spherical wheels would really only work "in the future" when roads weren't as gritty and mechanical as they are now. They would really only work when roads were smooth and made of some yet-to-be-invented material that wouldn't crack or break in pieces under regular use.
> because spherical wheels could allow the car better lateral movement
uhm, looks more like management entered the project without any real goal or metric for success, throwing ideas at walls just for the sake of budgeting.
Apple is good at taking something that works but in a clunky way, and make it clean and perfect for consumers. Not to be first to market.
There were smartphones before the iPhone, and there were mp3 players before the iPod.
If Apple is to reproduce the successes they had they will release a driverless car a few years after the competitors but it will finally be the one that "just works", without the clunky design and the necessary tweaking and weird options.
>Project Titan looked at a wide range of details. That included motorized doors that opened and closed silently.
Another example of apple putting too much emphasize on fluff... who cares about the door mechanism when the company doesn't know how to build the car it bolts to.
Sounds a lot like a company that wanted to build a new house of the future but found out they prefer redesigning the light fixtures, faucets, etc rather than the house itself. Aka the general UX details rather that would be ideal in a modern house rather than the house itself.
Apple probably would never have developed the smartphone first but they did a hell of a good job at getting all the details right with the iPhone once the bigger picture was worked out by other companies - and general technical progress.
I'd imagine the same thing for the future AI interface. I'd want my AI front-end to be developed by Apple but my pedestrian detection algorithm developed by Google, and my car designed by BMW.
The most important thing for talented people (and by proxy organizations) to figure is what they are best at contributing to the world and focusing on that. Instead of trying to do everything.
"Parkinson observed that a committee whose job is to approve plans for a nuclear power plant may spend the majority of its time on relatively unimportant but easy-to-grasp issues, such as what materials to use for the staff bikeshed, while neglecting the design of the power plant itself, which is far more important but also far more difficult to criticize constructively"
For Apple's task of building a automated car, industrial design is an "unimportant but easy-to-grasp" issue since Apple's expertise is design. They should have focused on the harder core problem of a car that can drive itself.
In fact this seems almost like an archetypical example of bikeshedding.
> Even though Apple had not ironed out many of the basics, like how the autonomous systems would work, a team had already started working on an operating system software called CarOS. There was fierce debate about whether it should be programmed using Swift, Apple’s own programming language, or the industry standard, C++.
Wow. Few things guarantee success like starting off a project with a good old-fashioned language flamewar!
My guess is it wasn't much of a debate and in actuality they used something like Simulink to model the control system and then had that generate the C++ code for the target hardware. I doubt any car control system software is written by hand these days.
And it didn't settle it - I would love to know if they went for C++. It's getting better and better.
Of course, if they wrote it in Swift 1 they would have had pains migrating to 2 and 3, but if they wrote it in C++ then they wouldn't be able to refactor any of the code as Xcode doesn't support refactoring C++....
If you're talking about the actual vehicle motion control systems, they probably should have been looking at what languages avionics companies use, not what their app developers are familiar with.
You'll need languages and operating systems that are battle-tested (literally) in hard-real-time fault tolerant systems.
Swift should never have been on the whiteboard for something like that. It's never been used in that scenario.
Avionics companies have very complex rules. They can use any of the above, but generally a subset.
For example you might use C, but ban malloc, and recursion. There will be static analysis tools that look through your code and calculate exactly how much memory you are using using in the worst case of function call tree, that way they know they cannot run out of memory or stack.
This is a weirdly titled report which implies it just happened. The "Apple scales back" part was already reported first by Bloomberg last year (which seems to be behind a paywall now) [1]. Bob Mansfield was brought on to refocus Project Titan on the fundamentals (being self-driving) rather that producing a car [2]. But both of these reports have the exact same hedging:
>Apple Inc. has drastically scaled back its automotive ambitions, leading to hundreds of job cuts and a new direction that, for now, no longer includes building its own car, according to people familiar with the project.
>Five people familiar with Apple’s car project, code-named “Titan,” discussed with The New York Times the missteps that led the tech giant to move — at least for now — from creating a self-driving Apple car to creating technology for a car that someone else builds.
And that's because the idea that Apple is going to be an auto parts supplier like Delphi that sells middleware to car companies is completely laughable.
There isn't actually much news in this report. The tidbits that the reporter got clearly motivated writing this article but it doesn't actually live up to its premise. In fact, PAIL seems like an expansion of Apple's efforts from what was previously reported.
>“Shelved” is an accurate word, but I think many people have interpreted it as meaning that Apple has given up on designing its own vehicles. My understanding is that it’s more like “Let’s get the autonomous shit down first, and worry about designing vehicles to put it in after that.” Eat the steak one bite at a time rather than all at once.
I don’t get why Apple would do that. They have enough employees who are capable of doing both in parallel. Furthermore, the talent capable of creating autonomous software are not the kind of people who excel at designing the vehicle itself. Apple could easily be doing both so that they have either one ready at the time of the release (and if one team fails, they could buy the self driving part from another company).
> They have enough employees who are capable of doing both in parallel.
Number of employees isn't what determines whether it's deliverable or not. It's likely they're deferring a decision to design the rest of the car until they're certain that they can do autonomous
If Apple were truly serious about building self-driving cars, they would buy one of the big 3 US auto manufacturers. It could buy all 3 with cash and still have one of the largest hoards of cash ever accumulated.
Over the decades I've noticed how businesses need to recognize and focus on their core competencies - if they don't, they die. Everything must feed that core, and undue distractions are lethal. Occasionally there's a need to pivot, which is deliberately stepping from one competency to another, but that is rare and difficult. Apple's core is to build small computers; everything else they do (music, video, cloud services, Siri, AI, AR, operating systems, etc) are all built to draw customers deeper into the ecosystem for the sole purpose of buying more small computers. Electric self-driving cars, while very nifty, are decidedly not small computers (at best being a tiny part of a large product demanding other competencies); to compete in that market requires scale which Apple could certainly buy but would fiercely compete for the attention vs small computers.
I definitely wouldn't call AWS, Echo from Amazon occasional. I think companies come in all shapes and sizes - some focus 90% on their core, some try to spend more time and diverge out to other business segments. Its upto Apple to figure out what to do and what would make it successful.
AWS is an offshoot of building the massive system needed to process the "we sell absolutely everything" goal. Methinks they just got so good at it, cloud services just kinda took on a life of its own and grew from there - but still feeds the retailing monster.
Echo is a consequence of exploring digital appliances as marketing tools. If you're going to build a device which can voice-interface someone ordering 6 bottles of Tide with extreme ease, doesn't take much more to turn it into a nice music speaker and tell you weather & sports & jokes on request. Echo, Fire, etc are just extensions to feeding the retailing monster.
Do notice how Amazon's innovative foray into cell phones crashed & burned hard - despite being lauded as rather a well-built device. That shows how straying too far doesn't work, and that "far" isn't very.
I worked at Amazon for a while and the point to note is that the Fire phone, despite being a public failure, led to a lot of things at Amazon. For ex:
1. The computer vision and machine learning stuff behind the 8 cameras on the Fire phone has been repacked and reused at multiple places. There's also a object recognition service in AWS if I remember correctly.
2. The FireOS, which powered the Fire phone, is being used on all Kindles except the older e-ink Kindles.
While the hardware division was indeed shut down, Amazon did manage to salvage as much as they can.
The cloud service didn't take a life on its own - in the very early days there was just EC2 and S3, nothing else. It took a lot of focused investment, commitment and trust from the management to give the AWS experiment more time so that it could succeed and eventually it did.
Fire phone was one of Amazon's many experiments. It failed sure, but hey you miss 100% of the changes you don't take.
In what way is the billions of dollars Amazon is spending on original content "just an extention to feeding the retailing monster"?
It's easy to point to one failed product as proof that "straying too far doesn't work", if you can do the mental gymnastics required to classify all their successful products as somehow more connected to their original goal.
IMO you do have a good point: Nothing about Prime seems to play particularly to Amazon's strengths, other than the wide reach of their sales channels (but if that's an argument, you could as well have Walmart doing the same). This is especially visible when you compare their software to Netflix. Still light years ahead of Apple though.
I think it's more that most don't see Amazon's actual core competence. Amazon is a logistics business, both information and physical. They do logistics for themselves for various front-ends (amazon.com, echo, video, kindle, etc.) but you can view all of those as accessories to their AWS, warehousing, and shipping business which they provide both for their own front ends and for sale to anyone.
If you define "core competence" sufficiently vaguely then sure, everything can be related to that core competence.
"a logistics business, both information and physical"? Really? Calling their massive retail business, original content, and physical devices an "accessory" to their warehousing is an extremely myopic view of Amazon.
Remember that much of what is sold on Amazon.com is not actually sold by Amazon. Amazon provides warehousing and fulfillment and an online storefront for third party sellers as well as for itself. The tools that it uses to run that online storefront in the form of AWS are used by many non-Amazon websites as well. The Kindle ecosystem helps Amazon sell retail books but also provides a self-publishing platform. It's not unreasonable to say that logistics, warehousing and web services are the real business, and that Amazon's retail business is one of many customers.
Nothing, business. It's a conglomerate. A business that's function is running businesses. A Yamaha piano has nothing at all to do with a Yamaha motorcycle exactly opposite to how all of Amazon's services are related and intertwined.
You are chooosing to ignore the many diversified companies and conglomerates that have done very well, some for more than a human lifetime.
Besides, Apple doing the iPod and iPhone is a counter example to your argument, unless you stretch the definition of the core business of a Y2K computer company to be music players and phones.
No, Apple's strength is refining, polishing, blending, and packaging existing electronic and software technologies.
Cars are more about mechanical engineering than electronics or software. Learning automotive design from scratch when you have no experience and barely any trained staff is not a trivial task.
Worse, a Level 5 autonomous car is not an existing consumer technology. At this point there's nothing to refine, and barely anything that could be bought in to start the refinement process.
Apple might as well go into house building, farming, or food products.
Not well known in the west, but Mitsubishi has been and is active in an insane number of business sectors:
Shipping, motor vehicles, home electronics, bank and finance (UFJ holdings), nuclear power, cameras and optics (Nikon), industrial chemistry, beer brewing (Kirin) and real estate.
Google was a search engine that made money via ads then pivoted into an ad platform that also has a search engine. Android and Chrome are about ensuring they have a seat at the table and don't get pushed out by Apple or Microsoft. The first thing of significance they've done that doesn't fit this is their cloud platform.
Their cloud platform is the same thing: trying to not get pushed out by Amazon and Microsoft.
Google Cloud is about ensuring that those two have competition and can't somehow pull an EEE. Extreme scenario: vast majority of world's online businesses are hosted on AWS and Amazon for whatever reason creates their own AWS ad service and forbids or undercuts Google AdWords for everything hosted on AWS.
Imo modern cars are basically small computers and everything else(seats,doors,wheels)is peripheral. I mean it is 2017 after all, don't you think it's about time we accept that cars are computers? Sure, we used to need humans to "complete" the computer part, seeing as we didn't have motherboards at first. But now computer is the core part of car and even humans aren't necessary. Why even bring your cell phone when your car is a cell phone? It's possible Apple needs the car to compete in a post cell phone world.
They have to focus on their competencies but they also have to completely reinvent themselves every decade or so or they will die. Once the iPhone is gone, Apple will be gone.
When companies focus on just one thing in a vertical, they're incredibly vulnerable. Samsung does lots of things fairly well, with some hiccups, well beyond just personal electronics and home appliances. It's diversification.
EDIT: Samsung does all sorts of things including ship-building, life insurance, construction and advertising.
For example, Apple MacBook Pros have become uncool, expensive, unrepairable and impractical... a giant FU to customers. That business is tettering on failure because they've been hypnotized on elixir of utopian, aspirational design rather than technical, environmental and practical usability. iPhone is the lion's share of
Apple's business, and they're losing ground to Android. That's a problem and most other products have plateaued and aren't anywhere near as dominant-capable or category-defining as the smartphone. That means Apple is a basically a banana republic (pun intended) unless they create or retake a category with a non-incrementalist product.
Disclaimer: I own an A1278 13" from 2013 but refuse to buy a $3000 soldered on RAM and SSD laptop that can't be transfered without proprietary service tools and whose glued-on batteries are a PITA to change. Also the low-travel, flush keyboards are terrible. Looking at Lenovo and System76 machines instead.
Numbers today are all well and good, but goodwill and rate-of-change indicate future trends. People will tire of $3000 laptops with nonfunctional WiFi and Apple Authorized Service Centers voiding their AppleCare warranties.
I mostly agree with this post but the more I type on my new MBP keyboard the more I love it. Was skeptical at first, made a lot of noise, felt weird, but this flipped pretty fast to big appreciation.
There's less affordances for touch-typing based on the shape of keys like Lenovo or older keyboards for boundaries of keys... it just makes typing harder unnecessarily to shave a few millimeters.
Manufacturing scale is not something they need until after they have the self driving tech (and also, I'd just partner with a Japanese or German automaker tbh. Toyota under the current CEO has made moves that hint that it would be open to a joint venture).
The main differentiator of current big auto is the engine and drivetrain engineering, which you can circumvent when going electric.
It's unclear what you're buying with a big 3 company that actually helps with the self driving part of the problem, which is currently a much larger problem than manufacturing scale and quality assurance.
> - a workforce with sunk costs in last generation skills
Often a unionized workforce. You didn't want to use more robots on your assembly lines like Elon Musk, did you? Because these guys are still going to be employed. Period.
I don't think these points are of any relevance. Once you have stage IV autonomy, you can partner with any car manufacturer you want, you have all the leverage.
However, knowledge in cars definitely helps building the technology, since there are so many little variables that you otherwise would oversee.
You can try to partner. However all major auto manufactures are looking at self driving cars. Some are doing it in house, some are having and existing trusted partner do it. That minor auto manufactures have partnerships with someone major and have reasonable confidence that their major partner will provide the technology.
Apple and Silicone valley in general is not a trusted partner, in fact they are the opposite: untrusted. Car manufactures have lost millions of dollars on safety lawsuits. The cowboy coding culture silicon valley has a reputation (not always deserved) for doesn't work, they need controlled processes where they can show the courts they made effort to check everything, starting with the design phase.
Car makers expect that they will be sued over a 10 year old car with some parts failing. They need to show the court they did everything possible to anticipate that exact failure case and either ensure it couldn't happen, or if it they handle it. When someone is dead, "we didn't think about that case" doesn't cut it.
In short, I don't think Apple or google will get anywhere in self driving cars. They have early demonstrations, but that doesn't mean anything long term. It doesn't even prove they have an early lead (though I suspect they do) since car companies might or might not say anything about where they are. In fact in this case I expect them to be very careful not to say anything: if they say to much a lawyer might argue the car should have been self driving and thus the car manufacture is fault for an accident. As such they need to set expectations that self driving cars are a future thing that isn't ready yet.
Why would a high margin, high ROE, low capital requirements business like Apple invest in a low margin, poor ROE, high capital requirements business like a car maker?
Besides being a poor investment that would lock up lots of their capital, it would also create a ton of management distractions.
If they are serious about building self-driving cars, they are probably making a huge mistake. Cars have been a poor business model for quite a long time. Licensing automonomous tech seems like a far better business model.
Electric will drive down the per-mile cost of the vehicles, and autonomous will drive up the per-hour use of the vehicles, which will lead to a larger potential margin.
You can sell a car for a lot more if it's being rented out for 12 driving hours per day. Especially so if it's a high end experience. People have a hard time shelling out $60,000 for a car when they could get something pretty adequate for $30,000, but when the choice is a $2 cab ride or a $4 luxury cab ride, a lot more people will pay the margin.
It won't work that way though. Cities have this thing called "rush hour" for a reason: a some specific times of the day far more people need to get around than others.
Worse, the people who use their car in the middle of the day are the least likely to use shared cars. They are the most likely to need a change of clothing, a stroller in their car just in case. They are also the most likely to run back and for from their car for each purchase at the mall.
What that leaves is people going to/from work, and their lunch breaks. At this point you may as well own your own car self driving car: at worst it is not much more expensive (shared might be 10% cheaper), and you get to leave your golf clubs in the car while at work. At best you can ignore a few tears and keep the car for longer making owning your own car cheaper than a shared car which needs to maintain appearance and cleanliness standards.
Shared cars work well for those people who rarely use a car. However those are the people who already are renting cars, using taxis and the like for the few times they need a car.
My understanding is that it's one of the few markets left that can move the needle. The biggest markets are health care, finance, petroleum, consumer electronics, and automotive.
PCs and phones are low-margin capital intensive businesses. Apple seems pretty good at commanding high margins in such industries.
As for why Apple doesn't license their tech, well, that's not how Apple operates, because then they lose control over the experience. ROKR and the like.
Apple has an easy way to move the needle, return it's profits to shareholders as dividends. They can produce better returns that way then dumping it into lesser businesses.
Apple has made great margins in PCs and Phones because it refused to use commodity operating systems. It's not clear that there is any similar advantage in cars. Everyone will be making autonomous cars, the markets will be highly competitive and they'll still require massive capital investments to make. It's unlikely customers will pay up much for a slightly better autonomous system.
If Apple wanted to go into cars, they should buy Porshe or Ferrari. They actually have brands that make their products difficult or impossible to copy well. Porsche in particular sells cares that are super highly engineered in every area, Apple can't create a Porsche like car business by selling an autonomous car by doing autonomous great, but ride, handling, acceleration, etc just acceptably
Everybody and their dog is trying to develop autonomous tech and license it. Autonomous capabilities used to be regarded as the secret sauce, and if you had it, the future of mobility was yours. This is not true. The ability to mass produce a vehicle is the secret sauce. It's the part that's hard to do.
But as far as low margins in the car industry goes, that point is irrelevant. Robotaxis are a different ballgame.
> Autonomous capabilities used to be regarded as the secret sauce, and if you had it, the future of mobility was yours. This is not true.
I think you're right that when we get self-driving cars it won't be due to a single secret, but rather hundreds of years of engineering time dedicated to getting all the kinks out.
But this is still a super complicated engineering problem, and not all people/orgs will be up to the task, and will not execute on the same timescales.
I think the way this plays out will be determined by how much of a lead the first movers (probably WayMo) will have, and whether companies will cut corners to get something "good enough" out the door, and how the public will react to that.
E.g. I think it's a very different world for automakers if WayMo turns out to have a 5 year lead on them, vs a 1 year lead on them. Cruise certainly looks like they are giving them a good run for their money.
It wasn't true about mobile phones, a business which had what looked like insurmountably dominant incumbents when Apple entered the business. Instead, Apple changed the business out from under the incumbents. Autonomous vehicles will similarly change the vehicle and transportation industry. That's an inflection point where incumbency matters less.
Apple will not buy any US company using it's cash hoard because of tax implications. They can of course raise debt, similar to what Amazon is doing with Whole foods.
A moral of this story is "don't name things 'Titan' or titan-related names". It's asking for trouble - Blizzard's 'Project Titan', Titan A.E., the Titanic. Things didn't end all that well for the titans in Greek mythology either.
A vehicle with a similar external sensor array has been parked in a lot near my workplace every weekday at lunch time for the past several weeks. Given the proximity to AC3 at Central and Wolfe, my coworkers and I had all assumed it was an Apple test of some kind.
Accords with the rumor mill surrounding Apple leasing a former Pepsi bottling plant down the street.
This is the right way. Building a mass market car is an enormous exercise. We have seen this with Tesla, which has thrown money at the problem and will still take 4 years to become mass market (2.5 already over + another 1.5 years). After these 4 years, its unclear what the value add will be.
The Roadster started production in 2008. I don't even know how long it was in development before that. To me, that counts as part of trying to build a mass market car. Yes, it was a niche vehicle, but if you want to point to the Model S as the start point, it's either ALSO a niche vehicle, or already represents success at building a mass market vehicle.
Tesla has built a category from the ground up. That is a very different challenge from replicating an existing business that has gone through decades of refinement.
But isn't what Apple (at least via rumor) was planning to do - build a category from the ground up a la Tesla, even if outright buying the full capacity of a major automotive manufacturer which barely has a grasp on EVs (think Bolt, Leaf, i3, etc)? I mean the OP referenced rumors of spherical wheels and other total revamping/replacing of existing tech plus totally new tech to boot.
If anything, "replicating" (or outright purchasing) what was developed over decades is just entrenching the past. Apple succeeds as it does by practically inventing future tech and making it instant commodities (yes, they're not always first, but hit so hard and go so far they dominate first movers).
"But __our_ai_project_here__ ran into trouble, said the five people familiar with it, dogged by its size and by the lack of a clearly defined vision of what __our_company_here__ wanted in a __our_ai_product_here__. Team members complained of shifting priorities and arbitrary or unrealistic deadlines."
So anyone who has been around for even a few years has witnessed probably more than AI hype cycle. This has been going on since probably the 1960s. While there have been (I'm sure) advances over the years, some no doubt substantial, what's clear is that the big thing that was and is needed is a truly massive amount of computing power.
Now I believe that self-driving cars will ultimately be transformative for society in a way not seen since the automobile itself or possibly even mass electricity generation.
But I just think this is still way further off than the more bullish pundits are predicting.
To be clear, there are two milestones here:
1. Assisted driving
2. Autonomous driving.
It's the second that'll be truly transformative. This is when cars won't be designed to have human drivers at all.
There is a lot of low hanging fruit here like highway driving where basically you need to not hit the vehicle in front of you and you need to stay in a lane at a fairly constant speed.
Assisted driving is the incremental approach needed to prove these technologies and bring self-driving to market (IMHO). This will be gradual and slowly replace some aspects of manual driving. It will probably soon reach the point where the car will intervene to prevent an accident. I expect even this to be cautiously adopted as there is a massive product liability issue here.
A drunk driver drives on the wrong side of the road and has a head on collision and society just tends to write that off as unfortunate, the cost of doing business basically. But as swoon as the car makes a decision that injures or kills someone (and it will) the lawsuits will be swift and massive. That's a problem. In fact, it may be the biggest problem. Nevermind the inherent risk to drivers, passengers and bystanders when you put a meat sack behind the wheel.
But the long tail of this problem is huge, to the point where I'm not sure you can really solve it without having an almost or actual general AI. So much of this is anticipating what humans will do. I mean things like placing a bucket or a plastic bag on the road and seeing what an autonomous car does.
Thing is, people seem to think this is totally going to happen real soon now when we have a long history with this in the form of aviation. People have been trying to automate humans out of flying planes forever. Unfortunately there seems to be an uncanny valley type situation where too much automation can actually make things more unsafe. I'm talking here about incidents where automated systems did or nearly did cause incidents that the humans had problems overriding.
And planes have to deal with probably substantially less situations than cars do.
I honestly don't know why Apple thinks it can compete in this space. It doesn't play to any of their core strengths.
If I had to pick anyone in the box seat here it would be Tesla.
Tesla already produces cars and has a go-to-market strategy. After Tesla, I'd add Google simply because you can never totally discount Google.
I take Apple scaling back as a positive sign here... for the company. I take it to mean that they realize just how far away this is and how difficult a go-to-market strategy is and also that this just doesn't play to their strengths.
> It will probably soon reach the point where the car will intervene to prevent an accident. I expect even this to be cautiously adopted as there is a massive product liability issue here.
Volvo already have this with auto brake and pedestrian protection:
> Collision Warning with Auto Brake & Pedestrian Detection is an aid to assist the driver when there is a risk of colliding with a pedestrian or vehicle in front that is stationary or moving in the same direction. Collision Warning with Auto Brake & Pedestrian Detection is activated in situations where the driver should have started braking earlier, which is why it cannot help the driver in every situation.Collision Warning with Auto Brake & Pedestrian Detection is designed to be activated as late as possible in order to avoid unnecessary intervention
Multiple manufacturers have the technology available in production cars today. Here is a demo involving a Mercedes coupe: https://youtu.be/eMUmI6LeZ_8?t=10m
Lawsuits are a double edges sword. If someone else makes a car where the drunk driver could not kill other people and you don't, then when the drunk driver gets in your car and kills someone you will be sued for not having that in your car.
All the major car makers are working on self driving cars because they know one someone has it they dare not be more than a couple years behind. If their defense to the above lawsuit is we were working hard on it, but it was 2 years away when that car was built they will win. If their defense is anything else they lose a few million dollars.
Call me crazy but why not consider ways to let someone remote drive the vehicle? I'm sure there are all sorts of corner cases (bad signal for one) but it's done all the time with drones.
Theoretically you could find someone far away who will drive cheaply.
Lot of trust in that individual when they too don’t get killed if the car crashes. Also hope you never have packet loss!!! There’s also that pesky speed of light restrictions on low latency, etc.
I think the key would either have them not be far away (so same city), hauling long distance, or even just driver assistance. I'm fully in the free thinking zone here tho.
It's probably not practical but if it were it might make for decent cubicle work for unskilled labor.
They should be more focused on iPhone and related stuff, and invest a million here and there in such self driving companies. One of them is going to be successful, or many. And after car being driven automatically, people will be using smartphone more, hence win win. And with VR, AR, 3D scanning etc, we are very far from reaching epitome of mobile technology anyway.
Tesla and Uber need constant hype to keep investors believing. Even Google needs to diversify away from its desktop ads business, or show it has significant room to grow. For a while last year I was taken in by the hype and thought self driving cars were really a lot closer than I previously admitted, but then I realised there is an agenda pushing these success stories.
Is it that you don't want self driving cars to happen or you don't THINK it will happen? I, for one, am super excited for self driving personal vehicles and will be glad to see the eradication of mass public transportation like trains and buses.
There's a strong case to be made that this isn't a desirable outcome in a lot of areas. Trains and buses are much more efficient at moving people than individual cars, even if they're self-driving. I'm also extremely excited about autonomous cars, but neither desire nor think they will replace mass transit.
edit: As a few people have mentioned, my suggestion that "trains are buses are much more efficient" is dubious. And I certainly don't mean to say they're better in all circumstances. It's more accurate to say that in certain scenarios, it still makes sense to use mass transit instead of self driving cars. Moving inside Manhattan, or commuting from a suburb to Manhattan, are examples where mass transit likely makes sense. With the obligatory disclaimer that I could be incorrect, this is simply my understanding.
I think you overstate how much better mass transit is than self driving cars. Transportation is fundamentally about traversing a graph, and transportation infrastructure is about maximizing the value of the flows on that graph. Mass transit only makes sense when the edges become a certain weight. The vast majority of point to point connections are far too light to support mass transit. Car transit is a bit better for these P2P and near P2P connections, but still pretty mediocre, because of coordination costs.
To a significant extent the issues with mass transit can be remedied by breaking the global graph up into connected subgraphs, and each subgraph can be similarly subdivided, recursively down to the point where the form factors and utilization rates cause the economics to break down. The edges between those subgraphs is mass transit.
Autonomous technologies make both point to point and mass transit transportation much cheaper. But labor (market or not) comprises a much more of car transportation costs than mass transit costs. Eliminating that cost inherently drives a shift from mass transit to car transit. Combine that with an efficient coordination algorithm to increase car utilization rates, and it gets a significant upper hand.
Each approach will still have its place, of course.
> breaking the global graph up into connected subgraphs
I feel like it's too conservative -- and takes "the transportation graph" as too fixed an entity. Consider how much the shape of the U.S. changed between 1917 and 2017 -- suburbs, the Interstate Highways, malls, fast food, huge parking lots, and on and on. The car literally gave us new ways of living with each other, for better and for worse.
So I think we should expect changes at least that radical in the next hundred years -- which suggests that we'll not just divide some abstract, eternal graph differently, but really truly reshape it.
I can't wait for super-fast trains + self-driving cars, AND I can't wait to see what kind of world they create.
That's an interesting approach to breaking the problem down, and a way in which I hadn't thought of it. I can see that I likely overstated my initial comment. I'll edit it to clarify what I meant.
Trains are great at moving people to train stations. Buses are great at moving people to bus stops. Cars are great at moving people to their homes and businesses.
When millions of Americans live in rural or suburban areas, what do you think is easier? Extending rail and bus routes to within walking distance of every house, or convincing everyone to move to a city? The answer is neither, and that's why cars exist.
Here's one that isn't a trick question: is it more efficient to build a rail line to my office and have a train run there or to have individual cars drive there? I don't know the answer for sure, but considering you may possibly need 15 trains filled mainly with people who don't work there converging on one location or 15 cars with one person each who does work there converging on one location, I'm almost willing to bet 15 electric cars would be more efficient than 15 trains.
There's a certain density requirement that mass transit needs that doesn't always exist. That's why we have cars.
And streetcars are great at moving people that last mile.
Take that road in front of your office, and just put rails in it.
If your local government can pay for a road in front of your house, it can pay for a streetcar. This applies to dense areas as well as rural areas. Rail lines actually cost less to maintain than roads, and they cost YOU less because you don't have to buy and pay for a car.
And you don't have to fear dying in a crash every time you set foot inside a streetcar, like you do in a car.
But would a streetcar go past my house? How far do I have to walk to get from my house to a bus stop or train station? Because I own 19 acres and my nearest neighbor is three miles from my house. The nearest town is 20 minutes by car. How would public transport deal with that kind of remoteness? My office is one end of the equation, my home (and the homes of my coworkers) are the other end.
It's surprisingly common when you leave the bigger cities. 90% of the country might live in cities, but the other 10% is spread out across the other 99% of the nation.
The urbanization statistics are also misleading. According to the US census, 80% of Americans are urban. The definition of urban includes the town where I live which has about 7,000 residents and I live on 5 acres and my neighbors more.
The move to cities stats are also way overapplied. College educated young people are indeed moving to a few mostly urban dense cores like Brooklyn. More broadly there's somewhat of a shift from true rural to the suburbs but most of those people will still need cars.
Wait now we're talking median solutions? I thought we were talking about replacing all roads with rails/streetcars? That's what the grandparent comment was saying
So if I don't fit into this world, how do I get around? Obviously we already ruled out self-driving cars, since they'll never work. So I assume I drive my own car? Since I'm already driving my own car, why can't I just drive it to the grocery store? Do I have to drive to the train station and get on a train to get groceries, or are there still parking lots for me? How far am I expected to walk from the train to the grocery store even though I have my own car and could drive right to their door? Or are we assuming self-driving cars work for me but don't work for anyone else? In elementary school I rode the bus for an hour and a half (not even exaggerating) to get from my house to school, am I making that same trip every day to get to and from work? Even though it's 20 minutes by car?
We're talking millions of people across the country here, not an inconsequential number. We're talking about thousands of small towns where trains will NEVER work. Are we just relegating them to second class citizens who have to ride their horses to town? Damn it's so easy for people in big cities to come up with these clever solutions, of course everyone can just take a train or a bus. Except millions of people can't.
Today I learned that poor rural farmers are living lives of luxury. Such a luxurious life in areas with no cell service, no high speed internet, and a several-hour streetcar ride into town to get groceries.
So glad to know that food stamps, welfare, and homemade methamphetamines qualify someone for luxury living.
It's really not. Calm down and don't pick up on one minor point and reply with a giant response. Obviously no one else thinks that cars are unnecessary.
No, it really is. So far I've seen people saying buildings older than "a few decades" should be torn down to move them closer to street car lines, people calling that "urban renewal", people saying that the problem solves itself because all young people are moving to cities as a rule, people saying self-driving cars will never work and every road should be replaced with street cars that lead to busses that lead to trains, but for the rural population the median solution wouldn't work so they'd have cars of course, but you wouldn't need them because you would just tear down your home and move to the city. Oh and also farmers are rich, but at the same time farmers have to move to the city.
Every single person in this thread lives in a big city and never stepped foot on land that didn't have a sidewalk next to the road. We're not talking "minor points" here, we're talking about 46 million Americans who don't have cable internet or cell phone reception, but somehow public transport will work there or we'll just force them to move.
I knew HN was a bubble but god damn, this is some next-level shit if you can just pretend 15% of the country doesn't exist.
No, pretty much all the things you're claiming people have said are egregiously uncharitable readings of their comments.
Someone suggested abolishing public transport might not be the best idea, and you seem to have interpreted that (and all subsequent defences of it) to mean we have to abolish cars instead. No one's suggesting that, they're just saying that we should use more public transport where it makes sense.
> When millions of Americans live in rural or suburban areas, what do you think is easier? Extending rail and bus routes to within walking distance of every house, or convincing everyone to move to a city? The answer is neither, and that's why cars exist.
My generation is moving into the cities where we can live without cars, no convincing needed.
> Here's one that isn't a trick question: is it more efficient to build a rail line to my office and have a train run there or to have individual cars drive there? I don't know the answer for sure, but considering you may possibly need 15 trains filled mainly with people who don't work there converging on one location or 15 cars with one person each who does work there converging on one location, I'm almost willing to bet 15 electric cars would be more efficient than 15 trains.
If your office is in the middle of nowhere, sure, but that's a "don't do that then" problem. If you turn over all the space that's currently spent on roads, road verges, and parking lots to more productive uses, you can cluster a bunch of places within easy walking distance of a train station - offices, restaurants, entertainment, and housing - and then people can live near where they work and enjoy.
Of course people who want to live in the middle of nowhere will probably always need something like cars, but they shouldn't be allowed to spoil it for the rest of us. Charge them a fair market price for the land they use for parking, and a road toll that covers the rent the road could earn if built on, rather than having everyone else subsidise those things.
>My generation is moving into the cities where we can live without cars
If you think that's true for every Millennial across the country, you're crazy.
>that's a "don't do that then" problem.
Oh, okay. Just don't do that. Gotcha. Pretty simple. Just don't have a job, just don't go to work, I'm sure I can afford to move to Manhattan after I quit my factory job in Springfield IL because it was too far off the rail line.
>but they shouldn't be allowed to spoil it for the rest of us.
> If you think that's true for every Millennial across the country, you're crazy.
Of course it's not everyone, but it's the overall trend.
> Just don't have a job, just don't go to work, I'm sure I can afford to move to Manhattan after I quit my factory job in Springfield IL because it was too far off the rail line.
Manhattan is expensive because there's only one of it. If the jobs build around the rail lines, you can save a load of money by not needing a car, and split the difference with your employer. And sure, not every job will be able to do this - factories need space. But that's a small portion of our economy at this point, and getting smaller all the time.
"Trains and buses are much more efficient at moving people than individual cars, even if they're self-driving."
I've said this on here before, but I'll say it again: efficiency is not everything.
Individual houses (or even apartments) are less efficient than having everybody living in barracks, hot-bunking the beds in three shifts, and eating some sort of nutrient-balanced kibble in cafeterias.
Human beings have goals other than efficiency. One ignores this fact at one's own peril.
> Individual houses (or even apartments) are less efficient than having everybody living in barracks, hot-bunking the beds in three shifts, and eating some sort of nutrient-balanced kibble in cafeterias.
Efficient at what? The comment you replied to explicitly talked about what's "efficient at moving people".
Of course some people like cars for reasons other than how good they are at getting from A to B, but is that a matter of fundamental human needs, or something more like fashion? Certainly people who commute by car don't seem to actually enjoy doing it.
Well okay. If you really feel that being able to take a trip to a less accessible location at a few seconds notice at peak times is vitally important to you, then you're still free to own your own self-driving car.
But I think most people would much rather wait a few minutes on those occasions and save their money.
(And FWIW, I think it could be fairly quick, since you don't have to pay a self-driving car to sit around in a small town in case someone needs it.)
Public transit in the US generally fails at the last mile for me especially in the suburbs. Self driving cars would be awesome for getting me to the train station. Currently I'd have to take a bus for that. However the bus stops at literally every block which is insane. Extremely frequent stops are a general problem I've had in both the bay area and the Portland area as well as the few times I've used public transit in LA. I'm more than happy to walk 5-10 minutes but I'm not happy to sit in a bus or train that is stopping all the time and never gets up to speed.
I would love to have reliable and efficient mass transit. However, for most places in the USA, that seems to be politically and socially impossible. For whatever reason, Americans have almost completely rejected public transit.
For that reason, I'm more excited about self driving cars than about public transit.
"Trains and buses are much more efficient at moving people than individual cars, even if they're self driving"
Dubious claim that needs evidence. I think you're underestimating the potential throughput gains from autonomy. As just one example, speed limits can probably be greatly increased when you take the realities of human reaction times out of the equation.
How much energy does it take to operate a train station or get people to the train station? What is the time and monetary cost spent getting to and from a train station and waiting on trains? How many NYC or Paris or Seoul subways run at 3am?
Can't speak for Paris or Seoul, but in NYC probably about helf the lines run 24/7. Of course, that's one of the reasons the system is so hard to maintain.
That would be terrible if it were to happen; it would mean either sprawling, inhumane cities or small settlements that are awful to live in if you don't conform to the norm. Possibly both. Personal vehicles just take up far too much land.
I suspect you would not be so happy when all the people that travel on the more space efficient public transportation systems buy cars and clog up the roads in front of you.
For the "happy path" case, in good weather, etc., sure. But that's the first 90%. The second 90%, dealing with all weather conditions, all traffic conditions, arbitrary road hazards, crazy road conditions, etc., might take a lot longer. To the point that it's not crazy to say "it'll never happen".
That said, I do think we'll get there eventually, as I think we'll get to AGI (or even ASI) eventually. But I can't prove that either. And I can understand a certain measure of skepticism about the whole thing.
There was a day when I booted my computer, I'd have to run a few commands and enter a few keys and insert a diskette. If, at that point, you told me I'd one day have a computer that boots itself and starts programs by itself upon booting to the point where a reboot would be indistinguishable from merely turning the monitor on and off, I may have laughed at you. But here we are, in an era where when my Mac reboots I can open the lid and be looking at the same CNN article as before it rebooted.
I'm not trying to say self driving cars are as easy as building a modern OS, however difficult that may be. I'm trying to say, in the area of how advanced computers can become in a very short period of time, humans have historically been incredibly, actually laughable inaccurate.
Anyone who says "computers will never X" deserves to be shunned into nonexistence. Literally all of the proof is on the other side of their argument. Historically, computers have always been able to do exactly what humans have claimed they could not do. It's only a matter of time.
Throughout all of that development, computers remained remarkably dumb. We still program them manually and they do what we tell them to even if it's disastrous.
Driving on open roads with other humans is going to require elements of real intelligence that are qualitatively different than your OS example where they just did more programming, better, faster.
It's apples and dump trucks. What if computers are just the wrong approach for this problem?
Computers are always improving. Granted. Doesn't mean it's going to be in a direction that's useful for general AI and driving full-autonomous.
On the flip side of constant improvement is are the claims that we'd have full autonomous cars "real soon now" for each of the last 20 years.
In 2017, we're still far enough away no one will give a product availability date. This again points to a qualitatively different challenge than what came before, and the need to develop several new layers of tech (not just integrate what's there) to get the job done
One thing that isn't getting better: humans ability to drive cars. Actually with computers getting smarter, we might even be getting worse at driving cars because we're spending more time on our computers when we should be driving.
Take a modern computer and show it to a programmer from 1970 and try to convince him that computers are still remarkably dumb. I doubt he'd agree. AI always falls into this trap. Once it's been done, it's not AI. It's just an algorithm. AI is something else. And when we do something that only humans could do just a few years ago, suddenly it's not AI anymore either. It's just an algorithm. AI is something else. And when we do that, now it's just an algorithm too. AI is something else.
I have a robot vacuuming my floors right now. I just typed "vacuuming" wrong and my computer corrected me without asking, it just did it. A minute ago I asked my phone, using my voice, to turn off my bedroom lights and it did. Seems pretty mundane, I know. So too will self-driving cars in time.
Alan Turing established a gold standard for what intelligence is quite some time ago. Modern computers still fail the unrestricted Turing test.
No doubt he'd be impressed at the progress, but failing the test is failing the test.
There is a difference between behaviors which seem intelligent (your roomba) and actual intelligence. Seemingly intelligent behavior (like Eliza) only works when your counterparty isn't too probing or discriminating. It's like a Potemkin village of intelligence; looks great, as long as you don't look too closely.
Replacing half of all driving is still a world changing benefit to society.
The self driving technology that already exists could change the world with regards to the trucking industry alone, as trucking hours are mostly done in "easy" conditions on the highway.
Trillions of dollars will be saved even if self driving trucks only ever work in sunny weather on the highway.
What are the margins on making the physical part of automobiles compared to other things that Apple could be doing? Average profit margin is 8% for auto manufactures. [1]
Can the "mass production self driving cars are just a couple of years away" meme finally die yet? Are we ready to admit that maybe this is a harder thing to invent than we've been trying to make ourselves believe?
Given there are auto manufacturers[1] that already exist with self driving cars, I'm going to go ahead and say its not a meme and more just a technology in the process of being fully realised.
Some times, things just take time. Especially when you're trying to create machines capable of not killing the general public.
Tesla's are not self-driving cars in the sense of revolutionizing any driving. You still have to pay attention and be ready to take over all of the time. That means you can't sleep, read emails, etc. on your commute. It's a fancy lane assist that reduces mundane movements you have to make and it improves safety, but it's not resulting in super cheap automated taxis or overnight road trips.
In that case we had self-driving five years ago, I guess OP meant mind-off self-driving. That's the hard part, it could even be an AI-hard problem. Because if you have to pay attention with hands on a wheel, it's not a huge convenience improvement. And there's also the problem that human-take-over situations will be increasingly dangerous as the self-driving software improves.
And by the way, the auto-pilot video is underwhelming. Several companies have more advanced self-driving tech than Tesla, e.g. Waymo is at least 3 years ahead.
What about this article makes you think this? Do you have some insight that all the major automakers are missing when they say they expect to have autonomous cars on the road in the next 5 years?
The article you linked to indicates that places with good weather and good roads could see the technology in 3 years. For all places in all conditions it may take 30 years: "this technology is almost certainly going to come out incrementally. We imagine we are going to find places where the weather is good, where the roads are easy to drive — the technology might come there first. And then once we have confidence with that, we will move to more challenging locations."
Even in the Bay Area, there is periodically bad to less than perfect weather - we had 30+ straight days of rain about 15 years ago in one of the El Nino years, and that would have killed Waymo's steering wheel-less cars' useability. It's almost like none of the people who made that decision were here when that happened.
Yes the Bay Area is probably not ideal, yet still much better than Jakarta or New Delhi.
But even an area that was unsuitable for self-driving cars half the time would see huge demand for self driving cars: half the time the car would drive itself, the other half it would be a regular taxi driven by a human being.
The Bay Area only has a lot of self-driving cars because the engineers are there, note that WayMo is letting people take rides in Phoenix, not the Bay.
Thanks for the clarification. I see them on San Antonio and in out of the way neighborhoods in Los Altos all the time but I guess from this article they are simulating more novel situations for the self driving AI and doing real world regression testing. It was only last year I saw one Waymo slow at every pedestrian crosswalk on San Antonio and there were no pedestrians nearby and the crosswalk lights were not blinking so definitely a necessary step.
Reminds me of a story my dad told about a guy in his village who still drove a horse and cart in the 1960s. He drove it down to the pub where he would get blind drunk but it didn't matter as "the horse would take him home".
How much energy does it take to move one train 500 miles? How much energy does it take to move 10 cars 25 miles each? That's your question.
Why do people always frame public transport in the light of "everyone can just take a single train!"? It doesn't work like that. It never works like that. It's a ridiculous argument barely even worthy of a response. 500 people might take one train in LA or NYC, but how about Greenville, Wisconsin? How about in Bitely, Michigan? How about Linn Grove, Indiana?
Suddenly the argument breaks down, doesn't it? Good luck replacing 500 cars with one train when the town only has 150 people and they all work in different cities. Now suddenly cars are looking pretty damn efficient, aren't they?
We detached this subthread from https://news.ycombinator.com/item?id=15077631 and marked it off-topic because it turned into a flamewar. Please read the HN guidelines and follow them when commenting here.
You raise good points, but they're specific to American urban design, and the long-term solution is probably to redesign and rebuild our cities to move away from those designs.
So the solution is to tear down our cities, abandon our homes, and rebuild everything somewhere else. Gotcha. I mean that's probably environmentally friendly, right?
Thanks for your input. It's rare to meet an anti-development NIMBY on Hacker News, it's always welcome to have different points of view on this website.
Cities and homes should not be expected to last forever; while we shouldn't be rebuilding them every year, doing so every few decades is probably more environmentally friendly than not.
I'm not sure I'm understanding... my home was built in 1953 and is standing just fine. It's got new windows, new insulation, and a new roof. Are you saying I should abandon it and go build a new one? There's a brick building in town that's been there since 1842, you're saying we should rip it down just because it's old?
Has everyone in this entire thread lost their damn minds? First meth-head farmers are "living in luxury", then "street cars will replace every road in the nation", and now "buildings should be torn down and rebuilt every 30 years".
I think we will need roads designed for autonomous cars, to make them truly safe and autonomous. They'll need sensors and digital markers to augment the visual markers. Otherwise, conditions like snow or rain would make it too difficult to work.
This should be a big part of the conversation around self driving cars. If we added some basic markers and beacons to our roads we could have self driving cars a lot sooner. Start with the interstates, we'll save a ton of lives and bring down the cost of shipping.
That's too bad. I was really hoping for Apple to spend all of their resources trying to build a car and then go out of business because IMO they ruined computing for everybody by popularizing walled gardens, anemic UIs and super limited software.
Phones where a walled garden long before the iPhone. J2ME apps sucked, but there where a lot of them.
Calling the iPhone the first smartphone is mostly just marketing and form factor. They got the interface right and built a better browser, but you could use the web, email, apps, take pictures etc on phones long before the iPhone.
There have always been a unlocked phones. But, in many cases these phones did not even have data ports, just the built in connection to a walled garden unless you physically opened them.
PS: I was writing phone software 2004-2006 so really walled gardens where a thing. People would even gasp pay for ring tones.
Good, now if only we can get Musk to stop live alpha-testing his decapitation death code and slow down for a few years, then maybe some actual experts who have working sensors can get this done properly.
What are you referencing here? If you mean the accident that caused a car to drive under a truck, that driver ignored several alerts and warnings from the auto pilot system.
It's literally the opposite of that. They spent billions of dollars on R&D in a new market segment. Just because you cancel the project or decide it's a failure doesn't mean a) you didn't learn anything, b) you didn't get any tech out of it, and c) it's not innovation.
You cannot be innovative if you are not prepared for your efforts to fail. If Apple was "done innovating" they wouldn't be taking massive bets like this at all.
Probably. After all, they're pushing 3bn per quarter and titan presumably lasted a few years. If it was 10% of R&D for 3 years it would be over 2bn according to that graph.
"But people within the industrial design team including Jonathan Ive, Apple’s chief designer, believed that a fully driverless car would allow the company to reimagine the automobile experience, according to the five people."
Ah Jony Ive, first he ruined iOS 7 and now this constant need to tinker with things that work fine. I love the hardware design but please leave the software and HID bit alone... of course YMMV
P.S. Anyone feel iOS usability has been going down with the move to a flat design?
I think iOS usability has become and is increasingly becoming, more complicated and less easy to use. But this doesn't have anything to do with the flat design, but with the many features, buttons, and gestures being added every new release.
Having to teach my dad that buttons and settings are hidden until you tap something or swipe around has proven to me that the new UI is trying to be more clever all while being extremely confusing.
I think it's the new features - but also the desire to make the OS appear simple - so new features get hidden in unexpected places and it feels inconsistent. iOS was a breeze to use up until iOS 6 because it didn't really do all that much and it's much easier to design a small screen interface if you don't have many features.
Nope. Flat design for iOS was Apple's best move. iOS 7 was what made iOS amazing. I have no clue what you're talking about. Full credit to Jony Ive, some of the UI design I've seen.
I wonder if Ive has as much influence as people think. The last few iPhones look horrible with the camera sticking out. And it looks like this will be the case for iPhone 8 too.
I imagine he must not be very happy with the way they look either.
I was looking at an iOS screenshot from 6 or 7 years ago, and was amazed at how the battery and location services and bluetooth icons all really popped in color and texture. No more. Now I have to find a hidden force touch control to do.. well, god knows what.
TL;DR ver:
-> Inconsistent UI within an app
-> Gestures that are inconsistent across apps and within the same app
-> No undo (I mean shake to undo doesn't count)
Apple really is a one hit wonder. Outside of computing devices, phone, tablets, laptops, (let's throw in desktops & watches) They really haven't been able to build and innovate much since Jobs. I was short on the idea when they announced a self-driving car. Without a major change and internal culture shock, they are going to stay on this course, hit peak cash extraction until they start mortgaging cash quickly. The only thing that has been pretty interesting has been AR. Innovation dilemma is strong.
I'm reading it as, "What have the Romans ever done for us? Apart from the sanitation, the medicine, education, wine, public order, irrigation, roads, a fresh water system, and public health."
I literally don't know whether to upvote or downvote you. The first sentence is beautifully sarcastic, but the rest makes me think it wasn't sarcasm at all.
Apart from this, I sort of agree with your view of not having been able to innovate much since SJ, but this is actually evidence of the opposite: not much new has been coming out of Apple, but clearly stuff is happening inside, which sometimes doesn't turn into a product, but their R&D appears to be alive and well.
The team also worked on a new light and ranging detection sensor, also known as lidar. Lidar sensors normally protrude from the top of a car like a spinning cone and are essential in driverless cars. Apple, as always focused on clean designs, wanted to do away with the awkward cone.
Apple even looked into reinventing the wheel. A team within Titan investigated the possibility of using spherical wheels — round like a globe — instead of the traditional, round ones, because spherical wheels could allow the car better lateral movement.”
Very interesting, and one heck of a leak if true.