So, nothing “hard”, really, you just have to do the work again (and prepare to support two versions for a long time, instead of virtually only one).
1,173 karma · joined July 26, 2011
So, nothing “hard”, really, you just have to do the work again (and prepare to support two versions for a long time, instead of virtually only one).
But if you have complex bugs to track, the integration of Python in GDB alone is worth the hassle, I think.
Which makes me agree very hard with your first point, btw.
The alternative logos are in SVG, so that's great.
Try WHOIS, you'll hopefully reach someone tech-savy enough to discuss with.
I trust them even less to not put Google+ inside this, which for me is more or less the same thing as shutting the service down, since I really don't want to use Google+ (I mean, really), and I don't want people I share photos with to be forced to use it (I mean, really). You seem to be sure they wouldn't do this, I think the exact opposite. Well, future will tell us.
Now, you're right in that they have a excellent history of allowing their users to get their files back. This is something I definitely trust them and thank them for a million times. Now, a photo service isn't relevant without a sharing feature, and if the service is shutting down, no backup that I can think of backs the sharing up.
I'm still using GMail and Android, but I'm not happy with how their UI change, and with how the latter puts Google everywhere (it's a bit better with Cyanogen, but still).
Maybe I'm extrapolating, maybe not. The only thing I'm sure of, is that when trust has been lost, it's very hard to get it back.
While bzip2 is faster at compressing and has lower memory requirements, LZMA can beat it at decompressing speed by large margins.
This is of course nowhere near LZ4.
Some did not like Gnome 3, they created MATE. Some found GCC was too conservative, they created EGCS. And MariaDB. And LibreOffice. And ffmpeg… And…
That's how you guarantee software will continue to fit your needs in the future. It's not paying for Microsoft Works that made people able to open *.wks files with Microsoft Office when Microsoft discontinued the former office suite (though they are some converters available). But it's open-source that made people able to open TrueCrypt files with CipherShed when the developers gave up.
Even at my level, I'm able to tweak the tools for my needs. The last version of zsh is not available on AIX? I can build it myself (and send the fixes upstream). Vim doesn't provide the feature I want? I can add it (and who cares if it's not yet merged upstream? it still does what I want it to do, now).
And it's really not about money. I'd be happy to pay a developer for some tool I use everyday if asked for. I already pay for music under CC or FAL.
Actually, I used to generate rules using gcc -MM which does pretty much this: track dependencies in sources files using #include directives.
Nevertheless, I'm happy to see that the idea of automatically handling dependencies is still being worked on. I'd be so happy to trash all this scons config files we have to maintain on a near-daily basis.
Do you mean that you run bash -c in zsh, or that you run zsh -c ?
I'm very happy I almost never have any problem with OVH (I've two DSL connections with included Hubic accounts and a few web hosting with included domain names), because the support is not great at all.
I guess my submission would be dead too if I were hellbanned.
Anyway, it's not a big deal since the comment is just a tl;dr, but I've no idea why it isn't visible.
Maybe this thread? https://news.ycombinator.com/item?id=6143244