11–20 of 188 posts
It looks like jobmachine is a private repo, maybe don't include the url in your blog post :)
I don't think there is any harm done in putting it in there. All GitHub urls follow a standard schema, so if you wanted to you could anyway guess it. The point of the code snippet was simply to highlight how nice the Haskell build tools are compared to Python's.
The comparison between Stack and Python build tools is striking: > No messing around with virtualenvs and requirement files. Everybody builds with the same dependency versions. No more “works on my machine” and “did you install the latest requirements?”. I wonder why the Python ecosystem, which is much more mature, doesn't provide a build tool as delightful as Stack (which is less than 2 years old).
I hope I'm not being too pedantic but Python's ecosystem is much larger than Haskell's, it isn't really more mature. Haskell and Python are very similar in age as languages go.
In the 1990s I did research on the efficacy claims of object oriented programming versus procedural programming. This article bares a striking resemblance in the claims. Case study after case study showed that object oriented code had less bugs due to compilers catching bugs, etc. However, almost every study was similar to this report: it was a re-write from procedural to object-oriented. There exists strong evidence…
I'm guessing he is a Python developer and likely he is no longer the lead.
Earlier quoted context omitted.
I don't think there is any harm done in putting it in there. All GitHub urls follow a standard schema, so if you wanted to you could anyway guess it. The point of the code snippet was simply to highlight how nice the Haskell build tools are compared to Python's.
I couldn't help but try to see if they were nice enough to opensource it, though, hah.
In the 1990s I did research on the efficacy claims of object oriented programming versus procedural programming. This article bares a striking resemblance in the claims. Case study after case study showed that object oriented code had less bugs due to compilers catching bugs, etc. However, almost every study was similar to this report: it was a re-write from procedural to object-oriented. There exists strong evidence…
Do you have anything published? I'd be very interested in reading.
The comparison between Stack and Python build tools is striking: > No messing around with virtualenvs and requirement files. Everybody builds with the same dependency versions. No more “works on my machine” and “did you install the latest requirements?”. I wonder why the Python ecosystem, which is much more mature, doesn't provide a build tool as delightful as Stack (which is less than 2 years old).
Probably for the same reason I greatly prefer cabal to stack. Stack assumes it knows better than me. Cabal just does what I tell it to do. As a domain expert, I greatly prefer the latter. It does what I want, nothing more, nothing less. Stack is a mysterious "solution" to a problem I don't have that works by doing everything differently than I do. Stack was created because not everyone is a domain expert. A lot of pe…
> Our lead developer Robert usually comes in a bit later, so we had about an hour to build a working prototype. I'm guessing he is a Python developer and likely he is no longer the lead.