Python 2.7.7 is out, including 'HTTPS is now used by default when connecting to PyPI.'. Hurrah!
miniblog.
Ooh, it's also neat to see that @CoverallsApp comments on pull requests regarding coverage changes:
Landing arbitrary size integers to Trifle Lisp's master branch!
Ooh, nifty Emacs trick of the day: in eshell, just enter `magit-status .` to open a magit buffer for the current directory.
I'm coming to the conclusion that good collaboration tools are the most important part of a technology toolset.
Continuous Deployment is the 'put your money where your mouth is' of software testing.
I think there's a corollary of Zawinski's law: "Every program attempts to expand until it can read PDF files."
Blogged: Trifle Lisp: Designing a Numeric System: http://t.co/Oy0eC67yjP
I've seen Emacs being used as an init process, but this is something else: http://t.co/xboo7xLdUR Squeak Smalltalk as an OS!
If you ever try running code that's syntactically invalid, you probably need a better editor.
Pharo is a lot of fun, but it doesn't seem to have a convenient npm-style package manager as far as I can tell. Shame.
I am impressed the I2P package on Arch Linux has the option of building it by fetching the source over I2P!
1. Find some known-good code you trust and measure coverage. 2. Find a few missing coverage lines. 3. Write tests. 4. Find bugs!
It's really easy to set up a Twitter account that reports on commits on a project! I've set up @TrifleCommits to keep on top of changes.
I've walked past my first store that accepts bitcoin! Old Street, London. Seems appropriate.
Showing 691-705 of 1,323 posts