Monthly Archives: June 2015

Why can’t a Browser run Python Instead?

Pierre Quentel

Billy Earney

Brython supports most of the syntax of Python 3,
including comprehensions, generators, metaclasses, imports, etc.
and many modules of the CPython distribution.


It includes libraries to interact with DOM elements and events,
and with existing Javascript libraries such as jQuery, 3D, Highcharts, Raphael etc.
It supports lastest specs of HTML5/CSS3, and can use CSS Frameworks like Bootstrap3, LESS, SASS etc.


Brython is designed to replace Javascript as the scripting language for the Web. As such, it is a Python 3 implementation (you can take it for a test drive through a web console), adapted to the HTML5 environment, that is to say with an interface to the DOM objects and events




Be Mindful. Pluto Live in July! How Close Will We Be?

The structure of Pluto is not very well understood at present. Nevertheless, spectroscopic observation from Earth in the 1970s has revealed that the planet surface is covered with methane ice. Surface temperature is -230 degrees C, and the frozen methane exhibits a bright coloration. However, with the exception of the polar caps, the frozen methane surface is seen to change to a dark red on the basis of observation of eclipse by its moon Charon.



Because astronomers discovered the dwarf planet in 1930, they have seen only part of its 248-year path around the Sun, and they don’t know exactly where Pluto is. And New Horizons is so far from Earth that it takes 9 hours to send and receive a signal, making the spacecraft hard to direct in real time.


New Horizons is now deep in the encounter, and already seeing just how interesting Pluto and Charon promise to be. Mission PI Alan Stern writes that there’s only one Pluto flyby planned in all of history,…

SaaS Shopping List

stackTechsCode inComplete – SaaS Shopping List

I wanted to also take a moment to recognize the growing number of 3rd party SaaS vendors we depend on in order to build out our own platform, and the increasing amount of time we must spend on evaluating and integrating all of these pieces into a (hopefully) cohesive whole.

Generally speaking, for a lean startup we should be spending our resources on the core product features that are central to solving our particular business problem. I should not be spending time on peripheral concerns that would be best outsourced to a company that has already solved those particular issues.

I want to Build only if it’s core to the problem at hand, and Buy if it is secondary scaffolding that I just happen to need in order to support my core feature set.