It's amazing how getting scala programmers to care about correct code is so much easier than getting them to care about correct builds.
-
-
Replying to @posco
Is anyone better? Are there communities to a steal lessons from?
1 reply 0 retweets 0 likes -
Replying to @snoble
I guess I mean there is all this moralizing about correctness, but to me it feels largely tribal: they are happy to use knowingly buggy build techniques. The end result is the same: deployed artifacts with problems.
1 reply 0 retweets 0 likes -
I'm rooting for you and look forward to bazel + mypy/typing offering similar gains in Python-land. In the meantime I'll be over here crying about shaded jarfiles, virtualenvs, and all the other accrutrmant that come with not having a devprod team.
3 replies 0 retweets 2 likes -
Have you tried the bazel python rules? The pip support is very basic (and requirements.txt is insufficiently pinned down by bazel standards), but especially in a mixed-language repo I'm preferring it to virtualenv.
3 replies 0 retweets 2 likes
I'm also amused that the pip package that was hardest to get working was tensorflow, which is itself built with bazel.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.