PyPy.js: Now faster than CPython
It has been the better part of a year since I first started hacking on PyPy.js, an experiment in bringing a fast and compliant python interpreter to the web. I've been pretty quiet during that time but have certainly been keeping busy. Some of the big changes since my previous update include:
Hasnain says:
Yo Dawg, I heard you like JITs, so I put a JIT in your JIT so you can trace while you trace. (https://rfk.id.au/blog/entry/pypy-js-poc-jit/resources/yo-dawg-jit.png)
Posted on 2014-05-06T17:19:57+0000
How to talk to an open source software project as a large scale or otherwise interesting user
The very short version: if you contact an open source project anonymously, you may not get the best help. Feel free to also reach out privately and share that your post from gmail.com is actually (...
Hasnain says:
"In fact, next to development resources, a great community and funding, having impressive deployments is one of the most important things for an open source project."
Posted on 2014-05-06T17:18:31+0000
Observations of an Internet Middleman - Beyond Bandwidth
We received a lot of positive feedback, as well as a lot of questions when Mike posted his recent story, Chicken. Many of the questions asked for more spec
Hasnain says:
"That leaves the remaining six peers with congestion on almost all of the interconnect ports between us. Congestion that is permanent, has been in place for well over a year and where our peer refuses to augment capacity. They are deliberately harming the service they deliver to their paying customers. They are not allowing us to fulfil the requests their customers make for content.
Five of those congested peers are in the United States and one is in Europe. There are none in any other part of the world. All six are large Broadband consumer networks with a dominant or exclusive market share in their local market. In countries or markets where consumers have multiple Broadband choices (like the UK) there are no congested peers."
Posted on 2014-05-05T23:09:35+0000
Doctors flunk quiz on screening-test math | Science News
Many doctors, and the news media, don’t understand that because of the statistics of screening tests, a test with 90 percent accuracy can give a wrong diagnosis more than 90 percent of the time.
Not Your Father's Java: An Opinionated Guide to Modern Java Development, Part 1
Despite it assosiation with large, bureacratic, and slow enterprise shops, and big, unwieldy frameworks, recent additions to the Java language, tooling, and libraries, combined with more lean programming styles, have turned programming Java into a rather pleasant experience.
Featherweight Musings: Rust for C++ programmers - part 4: unique pointers
I'm a research engineer at Mozilla working on the Rust compiler. I have history with Firefox layout and graphics, and programming language theory and type systems (mostly of the OO, Featherweight flavour, thus the title of the blog). http://www.ncameron.org @nick_r_cameron
Click to view the original at featherweightmusings.blogspot.com
Hasnain says:
Rust looks very exciting. The ownership semantics and low-level memory access may finally allow it to become a competitor to C/C++ for "systems" programming, which would be a huge plus.
Posted on 2014-04-29T17:09:32+0000
Fifty Years of BASIC, the Programming Language That Made Computers Personal
A celebration of one of technology's biggest, most underappreciated revolutions
C&C - Leaving Go
I’ve been using Go since November and I’ve decided that it’s time to give it up for my hobby projects. I’d still be happy to use it professionally, but I find that programming in Go isn’t “fun” in the same way that Python, Haskell, or Lisp is.
Some Thoughts on Go and Erlang
I'm going to attempt to leave out my subjective opinions for disliking parts of Go, such as syntax or lack of pattern matching, and explain objective reasons for the language and runtime not being ...
Hasnain says:
This is a really good writeup that discusses the pros and cons of both languages.
Posted on 2014-04-29T02:03:48+0000
Follow up to the investigation results
Last Monday I published the least open and least transparent blog post GitHub has ever written. We failed to admit and own up to our mistakes, and for that I'm sorry. GitHub has a reputation for being transparent and taking responsibility for our actions, but last week we did neither. There's no exc…