ldlework

12 ms·

31.
by ldlework 12y ago
While I'm not super familiar with the scientific computing field, I can say that Nim needs everyone's help in building the library ecology. Right now, Nim seems to be in the wrap-all-the-things! mode. You can see that most of the
32.
by ldlework 12y ago
Thanks for that explanation
33.
by ldlework 12y ago
As a long time Python programmer who has struggled to cross the gap from dynamic scripting languages to modern statically typed languages Nim is by far the most frictionless language I have tried. Before I found Nim I longed for a language
34.
by ldlework 12y ago
> You mean like the conferences they held before they even had a viable product? The conference was awesome and there was plenty to announce at that point. It certainly helped drive home the conceptualization of containerization for many
35.
by ldlework 12y ago
I run several processes on each VM, each in their own container, and use Docker links which exposes environment variables into each container describing ip/port information for dependent services. It was really easy and works great. Fu
36.
by ldlework 12y ago
Its a flag. There's not much to manage or setup.
37.
by ldlework 12y ago
I don't scale out to a hundred servers and I still use Docker with separate processes because scaling is not the only advantage to having stateless single-purpose containers.
38.
by ldlework 12y ago
I don't think I understand your point. From the Docker Host itself, if you need to manage the state of a container, the intuition is that you need to go into the container (with SSH) in order to do so. But by externalizing your state,