Oh, so you're an Android developer and an iOS user, huh? That's quite the rare combination. I'm sure you're very knowledgeable about both platforms, but that doesn't mean you have to be so condescending.
If iOS is so unreliable and unpleasant to use, why do you keep using it? Maybe you're just a masochist. Or maybe you're just afraid to admit that you're wrong.
> Android developer and an iOS user, huh? That's quite the rare combination.
It’s not. I am in the field and it’s totally not so, especially if you are talking about USA. Besides de-facto dev machine (in android dev world as well) is a Mac, so probably that’s a contributing cause, but anyway I have no large scale data on this.
> I'm sure you're very knowledgeable about both platforms
Really? Why would you have that doubt? I use both the phones extensively for multiple hours a day - at least every working day. I read about the feature set, releases, read dev docs etc of both the platforms regularly - and also do extensive discussion among team (the mobile team) as well how our competitors are using the mobile ecosystem.
So yeah I actually know what I am talking about. And you? That I am not sure :)
> you have to be so condescending
Ah, I don’t think I was. Apologies if it came across that way. It was just a knee-jerk of a shitty response to a very similar comment and I am totally fine with that. If I have to reply to a similar comment in future it’d be in the same tone or mo response at all; I should have gone for the latter.
> Maybe you're just a masochist.
See, now you are being an idiot. God, HN is full of us ;-)
> Or maybe you're just afraid to admit that you're wrong.
Awww. What an insightful twist of a comment. Genius
Because we don't want to use 20 IPv4 addresses for the cluster of 20 nodes, when we only have so much addresses assigned to our institute. We could have gone the NAT route, but then we'd need to have some router. And if we designate the head node as router, all traffic would not go through the switch directly, but first through the head node and then out. This would mean that the nodes are less independent, as they have this one additional choke-point. Our university gave us a /64 for this network, so we just used that and it worked flawlessly, also for university-internal distro-package fetching and host-cluster connections.
Also, research software is usually working nicely with IPv6. If we encounter something that would really need IPv4, we could update the thing and give it some local subnet - but currently we were lucky.
