So just now, following the theme of trying new technologies and seeing how they work, instead of blindly choosing Git I thought about picking a different VCS for a new project of mine.
So I stumbled upon this post. It’s quite long, however it is worth a read.
I’m kind of sad for Bazaar, even though I’ve never used it seriously (I’ve dabbled around long before I had any reason to). From this post it certainly seems superior, however choosing it now would be not quite wise, since it doesn’t seem to be alive enough. Perhaps people would call this state “stable”, but Git is currently both more performant and promising in the future. So I’ll be sticking to Git for this one.
There is some stuff I don’t 100% agree with, however most of this is reasonable and should be incorporated into your own coding guidelines.
That’s actually not just an emoji problem, but a problem with Android in general. Although it would be nice to have a mechanism for decoupled emoji updates just like there now is one for system apps and the Chromium web view.
Okay, so this started as a Google+ post (sorry, limited) which was intended to be a status update but turned out to be a mini-rant-slash-excitement-expression. So here I come to rewrite it as a proper blog post.
We live in interesting times, and I don’t mean that in a negative way.
The march for HTTPS isn’t slowing down any time soon, and that’s a good thing.
I must admit I’ve caught myself guilty of this occasionally as well. For example, there already exist a couple of Telegram’s API wrappers for Node.js, however I’ve written my own each time I tried to finally get that tgfr shipping. I’m still stuck at the last rewrite (0.11 hype!), and I agree that I have my own way of doing an interface to an API.
But that’s reinventing the wheel. We don’t need any more of that, there’s already plenty in open-source.
Anyway that article’s great. Take it and think about it next time you do a side project.