8 ms·
One of the side effects of software eating the world is that the world becomes more exploitable. I expect that over time we may see the emergence of general 'so
by ChuckMcM 13y ago
One of the side effects of software eating the world is that the world becomes more exploitable. I expect that over time we may see the emergence of general 'software building codes' much like there are physical building codes, and more importantly liability associated with failing to provably meet such codes.
The current 'random person implements firmware that controls the this chip' practice and the 'no warranty etc etc' disclaimers will, I predict, be replaced by manufacturers who are willing to warrant their code.
- fjk 13y agoExtending that metaphor, a profession could evolve around zoning for permissible uses of code based on types of software and intended audience, much like urban planners do with zoning codes and city master plans.
- eurleif 13y agoI can't tell if you're pointing out the problems with regulating software, or seriously suggesting this idea. That's scary.
- im3w1l 13y agoI think it is a consequence of the fast improvements in functionality made. People would rather be on a feature rich beta branch, than a safe stable branch. I also expect this to change as the industry matures.
- csmuk 13y agoActually I find its broken down into two camps: Consumers want the latest. Companies want the most stable. After some particularly huge disasters I've had to deal with coming onto new projects and with general consumer electronics, I'd go for the latter every time both as a consumer and company these days. Time is valuable and losing it to a feature packed unreliable mess is a big risk to that time.
- blowski 13y agoYou're right - there is a tradeoff between features and stability, but "consumers vs companies" is an oversimplification. It's about the probability of something breaking, and the consequences of what happens when it does. For a company with a large workforce, the probability of something breaking is higher - many different machines being used in different ways, and the cost of a botched upgrade can run into millions, with people losing their jobs, and legal action being taken. For consumers, the risk is typically lower and less costly if it goes wrong. If a Facebook upgrade causes the app to crash repeatedly, it means I can't post for a while, so I'll just upgrade and hope for the best. But if a personal finance or medical app goes wrong the consequences could be extremely serious, so stability is more important.
- alandarev 13y agoExcept that baseband is both not feature rich and stable.
- frozenport 13y agoThese already exist, for example it is very difficult to build biomedical software that gets hooked up into a living thing - even if you use it only for research. In practice such a hard realtime guarantee can only be met by a devices like an FPGA. All of this is in a code. Real issue here is why such codes don't exist for for this particular problem.
- informatimago 13y agoYou can code bugs and security failures into a FPGA as well as in software.
- klez 13y agoYes, but you depend less on bugs caused by levels of abstraction below your code, such as runtimes, OSes etc.
- nilliams 13y agoOnly a win if you have some reason to believe your code will be any less buggy when you inevitably start on your own ad-hoc reimplementations of those abstractions.
- bri3d 13y agoBetween writing and formally verifying HDL, logic synthesis (often using third-party or vendor-provided blocks or soft IP, mind you), behavioral and logic simulation (software!), layout, MDP, and building test harnesses that actually test the final hardware, I would actually trust a lower-level language compiled using a well-known compiler and running on a small RTOS on a proven CPU more than I'd trust a new design synthesized into FPGA or especially ASIC form.
- gngeal 13y agoIn practice such a hard realtime guarantee can only be met by a devices like an FPGA. There have always been fully deterministic CPUs around for that purpose. The simpler the system, the better; just hook a Forth chip to a memory without caches and you're set.
- frank_boyd 13y agoFirst of all, all that code must be open-sourced. It's so obvious that it really hurts. Next, hardware needs to become "open-source", too.
- kabouseng 13y agoThats easy to just say, but how wil you financially protect the company developing the software / hardware, if their competitors can just copy the work. Or stated the other way round, how will you keep companies encentivised to develop new software / hardware?
- fpgaminer 13y agoActually quite the opposite. If legislation were passed that required an entire industry to open source their firmware (automotive, voting machines, medical, etc), it would provide better IP protection. Did company A copy company B's code? Well it's open source ... go look! As opposed to being able to hide things in binaries. But yes, this only applies if the competition must also open their kimonos. That seems practical for industries where regulation is required or provides reasonable benefits to society (automotive, voting machines, medical, etc).
- davidw 13y agoYou are making the mistake of equating 'visible source code' with 'Open Source', which has a fairly precise meaning, which explicitly allows copying: http://en.wikipedia.org/wiki/The_Open_Source_Definition http://en.wikipedia.org/wiki/The_Open_Source_Definition Making the source code visible would probably be sensible in this case though, so I think the idea is a good one even if you need to be careful with the terminology.
- fpgaminer 13y agoSorry, I forgot to put the necessary disclaimer in my post stating my intended meaning of open source. You're right, I used it in the 'visible' sense of the word, not 'libre'.
- ivanhoe 13y agoThis is very unlikely because such embedded software operates on extremely low level and it's completely dependent on a particular hardware design (not just the chip, but the whole architecture). It's extremely hard to make that portable enough to make it sellable, especially with the speed of technology advances today.
- pjc50 13y agoPossibly; there are already standards in certain areas. But it can greatly increase cost and time-to-market, so even when there are codes corners will be cut. See the Toyota lawsuit at the moment. Oh, and applying pretty much any "software building codes" to the web app industry would probably kill startup culture entirely.
- blowski 13y ago> applying pretty much any "software building codes" to the web app industry would probably kill startup culture entirely. Not necessarily. To use the analogy with the building industry, there are different requirements depending on what the building will be used for. Startups holding or processing financial information might have one set of regulations, whereas those hosting cat pictures might be less rigorous.
- zarify 13y agoBut at the same time, the consequence for access of account information for cat pictures site on the site holding financial information shouldn't be discounted (passwords, social engineering info etc). To continue the (somewhat stretched) building analogy my house falling down doesn't affect yours, but someone stealing my access codes from my poorly secured building potentially could affect the security of yours.
- bazzargh 13y agoPCI compliance already exists, as a counterexample.
- davedx 13y agoIndeed, and one of the most successful YC startups (Stripe) is based on providing PCI compliance as a service.
- madaxe 13y agoThere already are such things - see COBIT.
- ivanca 13y agoWe are truly the generation where the mediocrity and corruption of the human race becomes digital.
- penguindev 13y agoI am getting tired of seeing physical building codes thrown around in comparison to software. I've looked at residential building codes, because I've done my own work like building a deck, framing and finishing my basement, and researching how to build concrete & steel suspended floors, or wood floors - seeing what their spans are - seeing how lightweight steel framing vs wood framing works - it's quite fascinating. (I was considering designing my own house, but the wife shot that down) And there is simply NO COMPARISON in complexity to software. In physical building, you over engineer and get redundancy. You also know that almost everyone builds plumb and level, rectangular rooms, with easy span and shear calculations. You also know that wood follows a predictable strength pattern. So you put in enough nails of the right length, to enough wood of the right thickness, and you're good. How much intelligence do you think you need to follow a building code? Building materials and techniques change GLACIALLY compared to software. (A good thing!) Whereas in software, one single bit flip will just fuck you up.
- ewbuoi 13y agoThe complexity of software doesn't preclude standardized "building codes." Obviously the codes would have to be just as complex, but software could be used to check that those codes are met. It wouldn't be perfect, but current building codes for physical buildings also have their flaws (every building [vs design] needs to be physically inspected by a person [much easier to exploit than a machine]).
- gwu78 13y ago"The current practice... will I predict, be replaced by manufacturers who are willing to warrant their code." You should run that prediction by some of your friends in the legal department and see what they think.