> > There, I clearly and repeatedly mentioned, Smart city, Smart home and > > Smart Society, Smart Car and many other things which are related to the 4 > > th Industrial Revolution, Internet of Things, Cloud Computing, etc as the > > business case and the market for the LSB.
The cloud runs on source code. IoT generally doesn't care about ABI because you don't link third party binary only blobs any more. Even when you do modern IoT is running as fast as it can from C and C++ because of liability law, support lifetimes (six years mandatory from the last sale in some countries) and the cost of security compliance. Nobody gets up in the morning and says 'lets launch a big new C++ project', or if they do their security compliance team explains to them why it's a bad idea. >From an application perspective the world has solved the problem of compatibility in at least four ways 1. There is far better consistency between the Linux vendors now just down to commonality of what is shipped and also the much lower rate of evolution in the C/C++ space 2. Disk space has become so cheap that stuff can be packed with its additional libraries (and it's now a security problem instead) 3. Virtual machines 4. Languages define their interfaces strictly and carefully in the first place (as most post C++ languages have mostly done), learning from the past So LSB really has become a legacy project for a legacy language. It's not about whether ISO is good or standards are good. It's time has gone. It's about as useful as a new updated standard for a steam engine. Alan _______________________________________________ lsb-discuss mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/lsb-discuss
