942 karma · joined February 21, 2007
@hellertime
http://www.hackernewsers.com/users/ch.html
(My submissions here are sporadic, and unfocused. I tend to use HN as my set of bookmarks)
We all agree that a null dereference is a bad thing at runtime. I see no advantage for me as a programmer to be allowed to introduce null dereferences into my code as a side effect of "getting things to work" if then when the code runs it doesn't work right. This increases my cognitive load as a programmer, it does not decrease it.
I would argue that you don't think about the compiler anymore when using a language like haskell than you do when using Python. But you do get more assurances about your program after ghc produces a binary than after Python has finished creating a .pyc -- and that is a win for the programmer.
I have this image of a white van pulling up to a curb and out pours a team of technologists in hazmat suits who descend on some hapless computer user's home to forcibly reinstall Windows on their HP Pavillion.
How convenient.
It would seem that if you could normalize, threshold and bucket continuous data than it too would be available for indexing. So while extending his to the entire range of real numbers would not be practical, in some cases a compromise could be found, which makes me want to look further into this.
Is this being released as open source code in the future?
One may be an expert in ones field, and not be a teacher. Saldly one may be a teacher, but over the years we've also gone and built a system which actively discourages teaching.
So the issue isn't necessarily one of money, but of how we approach the problem of building teachers.
An aside, thanks for the EVT reference. Something new to learn.
In general you are going to set up an N+M topology of n servers and n+m agents -- but for a network of 100k nodes does consul scale to 100k agents? Plus what goes unstated is how those 100k nodes are laid out in DCs and racks.
Anyway, this isn't to slag on consul. I think consul is like chocolate and peanut butter.
I use it in my mesos cluster and just am genuinely curious how large it can scale!
Without divilging too many details, what would be the ratio of agents running '-server' to overall agents?
Would it be possible to factor this up into a JSON -> SQL translation function, which could than be used by various backends (effectively consume the JSON and spit out the CREATE TABLE and INSERT statements)?
Certainly that is trivializing things but is this what the notion of the numbers acting random, but clearly not being random implies?
Do you require the customer to size their key services to some theoretical peak, or can you offload so much of the process that the customer just needs to make a one time investment?
(Full disclosure. I work for a competitor, but not on problems like this).
And then, perhaps, used some platform detection to display the more appropriate form by default.
That way less space is used up by the parallel examples.