1,054 karma · joined November 21, 2014
I just can not remember where I heard it (some podcast maybe), but is my understanding that the Go Team hinted the possibility of something like JMX coming to the Go runtime.
They don't want to try solving a problem they don't really have. As RSC says:
> the community understands and encounters these problems more than we on the Go team at Google do.
1) as others are suggesting, they'll adopt Apple's versioning model putting everything under the windows 10 umbrella.
2) they are setting the table for a rebranding/replacement of Windows in the same fashion as they are doing with IE.
Of course not, software is about trade-offs, and every company has different use cases. Is it their primary datastore? if they lose data do they lose some data samples for a recommendation engine? or someone's money? I wouldn't assume "if it works for them it works for me".
> Trying to solve hardware issues with software is bound to lead to misery.
I strongly disagree with that, I believe exactly the oposite.
> If aphyr's post is the ultimate rating, why would anyone use anything thing else he's written about?
He does not judge the system's usefulness, throughput, etc. But he's a good benchmark for distributed system's reliability. While he might not test every possible scenario, if he says software X loses data on conditions Y, I do believe him. It's still up to me to decide if that matters for my use case or not.
Consider that if you have not experienced any issues yet it might say more about your network stability than aerospike. Of course you can chose to ignore it, but network partitions eventually do happen, and when it does I hope your data is not mission critical.
The argument from the issue https://github.com/golang/go/issues/444
> It would be much easier to port preexisting code if you could just copy your time formats over.
It's not really much of an argument, since transforming the sprintf format to Go is a trivial as printing an specific date.
I'm with you here, at first I didn't understand the alarm but now I'm starting to see the danger of this trend.
In Go that's certainly the case and in my experience it's a great thing, only time will tell if it will end up suffering stagnation like maybe happened to python.
Can someone well informed about Rust give some impressions on the standard library? It is as comprehensive as in python or Go for example?