1 karma · joined December 4, 2019
My use case isn't anything fancy. I just want to understand what tail is doing behind the scenes with inotify so that I can implement it in another language but I haven't found a rigorous enough outline of tail in pseudo-code to translate it. So now I'm just fighting with it in Vim and VSCode to strip away all the baggage that C forces onto a problem to get to the meat of the actual solution.
I think we all gain when code is more understandable and don't have to individually reverse engineer things to transport the lessons from one code base into another. I thought crowd sourcing the annotation process was an interesting take by Omniref. Maybe it was ahead of its time.
No one knows how the brain computes and the current hardware models are very poor approximations as the article outlines. Stacking more silicon is probably not the way to do it.
In fact, the model is lower bound approximation to the real thing and if the approximation has certain complexity then the real thing will be much worse. That is the whole point of having a model. You approximate reality with something simpler and hope the solution to the simpler model problem is close enough to the solution of the real problem.
So what real world problems are you talking about? I'd say much of engineering and science is coming up with these solvable models for real world phenomena and so far no one has cracked the nut on coming up with a simple solution to problems that have complicated models. You might argue AGI is not one of those problems but that's a different argument.
What does being in a savanna have anything to do with population densities and intelligence? The article doesn't really say. The only pertinent point seems to be about collective problem solving and intelligent people needing less help when it comes to solving problems. Which is kinda a tautology. The article then goes on to conclude that being in dense urban environments and being a loner are correlated with intelligence which seems like a non-sequitur.
Another competing packaging format. Why?
What is the value that Elsevier is adding to have the de-facto monopoly on the entire enterprise of scientific publishing in so many scientific disciplines?
I don't think the answer is yet another variation on the same theme. The design space for such tools is pretty well trodden and they are all lacking in one way or another. This blog post does not say what exactly about ansible needs to be fixed and what their plan of attack is. It just sounds like the author would like a more responsive set of developers which is a social problem more than a technical one and writing yet another configuration management tool is not the right solution to that problem.
Some interesting variations on that theme are http://babushka.me/, http://larsyencken.github.io/marelle/, https://github.com/brandonhilkert/fucking_shell_scripts, and http://palletops.com/. I also have a variation in mind but every time I sit down to write something I remember that there are already way too many of these and instead just write another shell script.