One of the problems with code bloat is creeping featuritis, and adding code for "it works" but not great code. Also there is the "you weren't asked to do that..." mentality of managers. Once I had to maintain a legacy tool that pumped data in real-time into a database. For fun I optimized some of the routines (it was written in C/C++ cross-platform for Linux/Windows) so in the next release there was a humongous speed-up...my team lead was not pleased. Hard lesson in first job out of college: Hoover vacuum cleaner principle about code--if it sucks don't blow it.

What about Rust? It was oxidizing its way to the top, and was most loved....while it was not widely used. EL.

Tencent is the new march of dimes to nothing. Not even worth ten cents. Ellith.

This is like hotdogs. Do we really want to know how they're made?

LG *might* sell iPhones after abandoning Android. A Hobson's Choice, or like Henry Ford said about the Model-T coloring scheme, "You can have any color so long as its black." Ellith.

Hey JoshK, don't forget their maxim "Our fingers are in everything." Here's a blast from the past: https://entertainment.time.com...

"Microsoft blamed the accidental server exposure on misconfigured Azure security rules it deployed on December 5, which it now fixed," adds ZDNet. The explanation is laughable. Consider re-phrasing for the Titanic disaster: "The White Star Line blames the accidental sinking of the R.M.S. Titanic on a miscommunication in ice warnings and telegraph distress signals utilized when it sailed on April 10th, which has now been fixed." adds the New York Herald Tribune.