Monday, July 18, 2016

Pressing Save in Blogger doesn't mean it did

You are have been writing the post on and off for the past few hours. You have been diligently pressing save to make sure you didn't lose your magnus opus. Other tabs are opened to access other websites for reference. Before switching between them, you still press save, just in case. Finally, after reading and correcting the post, you are finally satisfied with it. A final press of Save should do it. Then you hit Close.
The dialog box pops up and warns you that unsaved changes will be lost. You press Save again and hit Close. Blogger warns again. "But I just saved! What else do you want me to do?" You press ok and find yourself back in the list of posts. The time and date of the post was just a few seconds ago. You click on the post to add "one more thing".  And half of the post is gone.
Blogger warned you. So far, there is nothing that can be done. Pressing the back button has saved me a few times in the past but not recently. Especially with browsers driving the Back and Forward button into extinction. (Think about it,  Firefox on PCs don't have the Forward button, Chrome on Android don't have the back button). 
So what should you have done? The moment the dreaded "unsaved changes will be lost" dialog come up, press Cancel. Select all the text in your post, copy and paste them to a text edit (like notepad). There is no other way. That post is Titanic. Pressing save doesn't save it. Pressing ok at the dialog will lose the edits but is the only way to move on. Re-open the post and past back the text. And edit the format. And add the pictures again.  If your are wondering why Blogger didn't take over the world, this is one reason.

Lesson:Don't ignore that "Unsaved changes will be lost" in Blogger.
If Blogger overwrote your post, there is a way to get it back.

Monday, December 28, 2015

Systemd is not the end of the world but someone needs to save us from it

This post has been months in the making. I believed I've reduced the rant-iness to a minimum level. It add nothing to the discussion elsewhere on the Internet. It is however, a burden off my chest.
I became aware of systemd as an init system in recent months as it gained traction in Fedora and it's competition with upstart. I didn't give it much of an interest as it primarily dealt with services that are more associated with the desktop: Plug and Play, power management etc. Imagined my surprise when I installed CentOS7 and it was the default init option. And going back wasn't an option.
The discussion around it's adoption has been intensive. This is a website that documents the fallacies in the arguments against for it and the follow-on discussion for a now-dead website advocating for boycotting it.
 My main beef with systemd is philosophical. Systemd's complexity and how it goes against the concept of "many simple programs doing basic jobs well working together" is not where Linux should be going. While many deride this backward-looking, that concept has served us well and has brought us this far. Yes, I do know that not everything that has brought us this far can carry us into the future but that point is evident only in hindsight. We should try new things but not at the cost of what works.  They should also be subject to discussion and mutual agreement. And finally there should be a transition between what is to what will become.
The opposite of this concept is "one big program doing many things complicated things", the best example being Windows. While some point out that systemd is a collection of applications, they are being developed together as a whole and made inter-dependent.
Another beef is the sense of (or lack thereof) of community around the development. The fan-boy-ism around it and the attitude of the developers (e.g the attitude towards corruption in binary logs) is alienating. Although it runs both ways, it is more healthy on the sysvinit side of things. I understand why there is a strong push-back from parts of the Linux community. This is the age-old difference between Linux users that are excited by solving problems and those that like to go home at the end of the day. Systemd is this complicated box / tool that can be used to solve complex problems in a complex way.  

Recently Popular