Charles Kincaid (4/29/2015)
So many things here. Where to start?
Ah, Charles, glad you've got some stuff for me.
Steve, I thought that this was 29 days late (as I'm reading it). Recently on the news there was a piece about classrooms replacing desks with exercise bikes that have screens over the handle bars. They are doing this to improve reading scores. Testing showed that it worked. Unfortunately they do not have generators on these things so are not capturing all of this motion as power. That is short sighted. So I almost bought into your editorial in part about the intrusion of healthcare everywhere. It could happen.
I have a few friends with treadmills below desks. I've thought about it. Certainly capturing the energy isn't a bad idea. At scale, that could add up. I'd think health clubs should be doing this, but perhaps the interconnects are more work than value?
As to the missed extra word "does" in the original it was sort of missed twice. One way to avoid that is to use a screen reader to have an article read aloud to you prior to posting. What the eyes miss the ears might catch. It works for me. But then I'm an audio oriented brain anyway.
I usually catch lots of typos when recording the podcasts. See things I didn't when editing. Not sure why I didn't get this one. Too busy. I could try the screen readers, but the ones I've heard before (my wife worked in text-to-speech) drove me slightly crazy.
One of the models that a company that I worked for used is the Software As A Subscription thing. You paid a low entry fee and a monthly per user service fee. Upgrades were both free and mandatory. For my company I am using a different model altogether.
For some things I like SaaS. Email, no brainer. I'll never set up an email system again. For Salesforce/CRM, quite a few apps, I like it. Office, I'm there. I like that model.
The platform, SQL? Not sold. There are issues. Overall I like PaaS, but certainly some maturity needed from MS and others.
It takes a lot of folks to properly support as many versions as Microsoft does. All of those folks have to eat. Bodies are expensive.
I would agree, but the feature list from version to version continues to shrink. Lots of bugs don't get fixed, and even carry into new versions. SSMS feels abandoned. I don't mind the short product cycles, but the support is lacking.
As far as the upgrading path you might find an analogy helpful. Often we see humorous articles about how it would be if Microsoft built cars. But then seriously look at that. You can't take your car back for an upgrade. You replace it. Yes there are after-market parts but you still don't see air bags on a '34 roadster. (There is also not much of a market in used software.)
Except if cars fundamentally have issues, they have to be fixed by law under recalls. Software can have egregious issues and be left alone.
The car analogy isn't good, but I do think the car people tend to test more and stand behind their systems better. OF course, a car is a fraction of the complexity of SQL Server.