Letters to the Editor
I always look forward to reading my issue of LJ each month. Great magazine; thanks.
The reason I am writing is to share a concern regarding Linux API stability. I enjoy system work too, but the fact is my company sells applications, not operating systems. If I am to produce shrink-wrapped applications, user and kernel APIs must remain stable. I just worked my way through our several drivers to get them from 2.0.* to 2.2.* series kernels, and now I see the driver API is changing again in 2.3.*. It is a terrible temptation to keep improving, but if it works, let's leave it for a while. And maintaining old APIs is not a long-term answer either—that's what makes UNIX systems so fat, all the baggage they carry around.
Thanks for listening.
—Elwood Downey ECDowney@ClearSkyInstitute.com
|PasswordPing Ltd.'s Exposed Password and Credentials API Service||Apr 28, 2017|
|Graph Any Data with Cacti!||Apr 27, 2017|
|Be Kind, Buffer!||Apr 26, 2017|
|Preparing Data for Machine Learning||Apr 25, 2017|
|openHAB||Apr 24, 2017|
|Omesh Tickoo and Ravi Iyer's Making Sense of Sensors (Apress)||Apr 21, 2017|
- Graph Any Data with Cacti!
- Teradici's Cloud Access Platform: "Plug & Play" Cloud for the Enterprise
- The Weather Outside Is Frightful (Or Is It?)
- Simple Server Hardening
- Understanding Firewalld in Multi-Zone Configurations
- Preparing Data for Machine Learning
- Server Technology's HDOT Alt-Phase Switched POPS PDU
- Gordon H. Williams' Making Things Smart (Maker Media, Inc.)
- IGEL Universal Desktop Converter