For those of us who are starting to look into Twitter Bootstrap 3.0 for new projects and possible migration of old projects from Twitter Bootstrap 2.3.2 to 3.0, I found a couple of good resources. Firstly, this very brief StackOverflow discussion on what has changed between the versions. And secondly, this really nice migration guide.
If only there was an automation tool that works for me… A few were mentioned in this StackOverflow discussion, but none did anything sensible on my projects. I guess I’ll have to roll out my own, or use some manual labour in combination with powerful search-and-replace tools.
As you might have noticed, all sites that I was hosting had a bunch of problems recently. Mostly, they were very slow. I’ve spent some time tracing the issue with the technical support of my hosting company, but we were unable to pinpoint what was the exact issue. The slow downs were coming and leaving randomly, they were not limited to any specific website or browser or network or time of the day.
Finally, I decided that enough was enough and that something has to be done. So I arranged for another hosting. For the last couple of days I’ve been moving the websites to the new home and now I am almost done. As you can, hopefully, see, the new place is quite a difference. Everything is flying fast and I have plenty resources still.
The works aren’t completely finished yet, but most of the stuff is moved and the dust should be settling now. If you notice something that still misbehaves, please let me know and I’ll jump on it.
As some of you know, I’ve almost abandoned my Flickr account. I haven’t uploaded any photos there in the last couple of years. And I’ve also voiced my increasing preference of Google Picasa on several occasions. I’ve even started re-uploading all my pictures to Picasa and tagging people in it. Which is how you probably know about it, since that stirred a massive wave of notification emails.
Anyways. There has been a sudden and unexpected development in this area, which I want to share. Google replaced Picasa link (‘Photos’) in its navigation bar with Google+ Photos. And while Google+ Photos is an improvement over Picasa in some areas, it is an inferior product at this stage. And that was done when I was almost done with my Flickr-to-Picasa migration. I felt it was a blow below the belt. And that gave me yet another opportunity to reconsider my reasoning for the move.
These, to the best of my memory, were my reasons to move from Flickr to Google Picasa.
- Uploader. This was one of the main reasons. Back a couple of years ago, Flickr web interface only allowed me to upload 5 or 6 pictures at once. If I had to upload much more, the only option was to install a browser addon or a desktop client. Which I tried too, of course. But all of them sucked in general. And required constant permission fiddling. Google Picasa had an excellent web uploader. All I had to do was drag and drop a bunch of pictures into my browser.
- Mobile integration. Google Picasa had a client for my Android smartphone since the day I needed it. Flickr was a different story. A different story with Yahoo authentication on top of it.
- Price. Flickr’s Pro account is $25/year. Google Picasa uses my extended Google disk space, for which I pay $5 / 20 GB / year. But those are magic Google gigabytes. Somehow I can fit 40 gigabytes of laptop’s disk space into about 11 Google gigabytes.
- Image editor. Google Picasa had a built in editor which I could use to do minor editing like rotation and cropping. FLickr didn’t have anything.
Of course, these weren’t all my reasons, but they were the most significant ones I think. So, did any of that changed during my inactivity on Flickr and during my Google Picasa migration process? Yes. Let’s have a closer look.
- Uploader. Flickr now features an excellent batch uploader. I tried it and it works very well.
- Mobile integration. Flickr recently released Android app, which works pretty good. It’s not as useful as the Picasa one yet. But it covers the basic needed functionality and I’m sure it will improve in the nearest future.
- Price. That is always something to consider. In relative terms, Flickr seems to be 4 times more expensive than Google Picasa. But in absolute terms, $25/year is really nothing. $2 or so per month won’t make much difference to me. That was a stupid argument on my part.
- Image editor. Flickr now has one too.
So why would I want to move to Google Picasa now? There is really doesn’t seem to be any good reason right now. On top of that, Google Picasa is being phased out and replaced by Google+ Photos in which I don’t have any confidence yet.
Therefore, my thinking now is that I shouldn’t really move. Not at this stage at least. I will upload pictures from my camera to Flickr. I will take a bit more time to figure out what I want to do with my mobile pictures – either keep them in Picasa, or upload them to Flickr, or just use them in my blog only. But other than that, I think, I made up my mind about the move now.
What do you think? What is the best photo hosting/sharing option?
There is a lot of noise going about these news:
The Foreign Ministry is migrating all of its 11.000 desktops to GNU/Linux and other Open source applications.
That’s good. Both the noise and the news. But it’s not the first time that we hear about this or that government office moving to Linux desktops. It happened before. What I am more interested in hearing is the “after” life. Something along the lines of “Look, we moved to Linux desktops one year ago and we are doing better than ever. We are happier and we also spend less money”. How many of those moved roll back to what they had before? Why did they roll back? How many stay? How many of those who stay are more satisfied? How much cheaper it is for them?
That’s what I’d like to hear.
I’ve been a bit quiet for the last couple of month. That’s because I was leading an ambicious project at my new job – migration of a Microsoft Dynamics CRM version 3 to SugarCRM Community Edition version 5.0.0. There were only three people involved, non of us could afford to work full time on the project, and we only had three weeks to do it.
Read on for a story on why it took us longer, how we did, and if it was a success at all.
Continue reading Migrating MS Dynamics CRM to SugarCRM