This whole systemd fiasco has caused a boatload of infighting, dissension among what should be cooperative members and teams, and it makes the process of administering Linux systems that much harder.
There is no need for a Microsoft conspirator to produce this outcome. The linux community, filled by zealots who *believe* in "Right Things" is completely responsible for its fate. Any change to core components will result in a mess.
Extremely good changes will cause little problems (only some whining) ; reasonably good changes with little drawbacks will cause havoc. And instead of working together with authors to improve shortcomings, they will just waste their time (as well as the time of the authors) to troll, because that's what they like : discussing about what is the Right Thing (that will get them go to Unix Paradise at the right of God RMS) instead of doing real stuff to move forward and improve the code base.
I'm no dev guru or Linux wizard, but even I know that swallowing stderr messages and mucking with long-time, well-established syslog formats is a Bad Thing.
Well, dev gurus and Linux wizard are not necessarily the persons to listen to when you want to make changes. They are guru of the *old* thing, so any change will lower their guruness (or need them some effort to keep them afloat).
All that said, I don't like Unity nor Gnome 3 and miss my old sawfish.
But back at the article, I love apt-get and dpkg. I like the fact that a .deb file can be done with simple tools like tar an ar. Apt-get has been the first system to manage dependencies and that was a huge thing. But I can understand when people complain that you need to type apt-get install and apt-cache search. And frankly, since snappy commands are pretty logical (install / search / update), we should adapt without any effort.
Snappy categorization in framework/apps/... is also interesting for security and for me, it really makes sense.