3 ms·
The issue, as I understand it, is not so much path-dependency per se, but the long lead times involved in the manufacture of new hardware at scale. Software ha
by cs702 14y ago
The issue, as I understand it, is not so much path-dependency per se, but the long lead times involved in the manufacture of new hardware at scale. Software has path-dependency too, but changing source code to modify a new software product is faster than changing physical machinery, processes, materials, suppliers, and logistics to modify a new hardware product.
- 001sky 14y agoThis is a good comment, and sheds more light on the subject. The long lead time is a question of agility. This is subtly but importantly different that path-dependency (considered more of a lock-in to an existing technology). The link is that the ways of making the company more agile (investing in specialized manufacturing/prototyping and/or inventory) tend to create a more path-dependent trajectory (or opportunity set). So, perhaps this is better said that HW has 'interial' dependency on initial trajectory if not true path dependency per-se. Even provided that the startup is low-capital/outsourcing model. I hope this does some justice to incorporating your point.
- deleted 14y ago[deleted]
- tty2020 14y agoNice comment. I think there is indeed an inherent "inertial" in hardware business. A software/website service can have different usage. Users may prefer to use a smaller part of the service, or using the main service for purposes not originally conceived by the creators. In this way there is a chance of pivoting. However a piece of hardware has a very focused usage. All parts are integrated to provide a single function for the user. Also, unlike software, there is no straightforward way to collect real-time data on how a user uses their hardware.