Making Sense Of When To Use Open Source For EVs
Unless you’ve been off the grid, the latest debate these past few weeks have argued the idea of using Open Source for electric cars, EV. While the idea of Open Source is not new, it flourishes very well in the Linux and other Unix world where it brings you a timely constant stream of improvements, often time for free. However translating it to an industry as intricate as the manufacturing of automobiles based on a more closed source system poses huge challenges, although, it isn’t without rewards.
Open The Source, The Pros. The idea makes sense, at least on paper and ideologically. A shared platform of chassis, controllers, battery management systems where companies could chip in with their expertise and use the overall package. They could then rebadged the product, even go as far as continue to engineer the car or tweak them to suit their specific market needs. You would have an EV that would use a huge community of savoir faire and input at a fraction of the cost any single company could develop. If the pros make sense at first, a closer look reminds us of the dangers of adopting this way of building an industry, especially in the case of making cars that go fast and carry human lives.
The Darker Side Of Open Source. When to comes to cars, you need a strong series of quality control if you don’t want your cars to crash in flames and ruin your company. You don’t need to think too recently to remind you of cars hastily brought out only to have early adopters find computer glitches rendering them inoperable. In this instance, the closed source system, such as what Apple has delivered means their splendid machines work out of the box. In this instance and at this stage of the game, closed source is the best way to introduce EVs, at least for now.