phadej

6 ms·

1.
by phadej 7y ago
I probably don't say it in the talk very explicitly (or do I?): the target architecture is web = JavaScript.
2.
by phadej 7y ago
Are you confusing Oleg Grenrus (OPA) and Oleg Kiselyov ( http://okmij.org/ftp/ )?
3.
An example of functional design (in Scala)(futurice.com)
10 points by phadej 12y ago|0 comments
4.
by phadej 12y ago
Good comment! I did make a too quick judgement there. It turns out you can't easily see how popularality of CoffeeScript has changed. It is surprising to see CoffeeScript in this list as a language compiler should be mainly
5.
by phadej 12y ago
I corrected the jasmine stats. The right package is `jasmine-node`, not `jasmine`. Sorry for my mistake. Though there are now much more users, there are still less than of nodeunit or mocha.
6.
by phadej 12y ago
Wow, someone had time and motivation to write all of that boilerplate there. Yet e.g. the license parsing is very naive: compare https://github.com/npm/npm-www/blob/99020b5b3e21607dab24cd69... and https:&#x2
7.
by phadej 12y ago
I like the minimalistic nature of npm packages. It also encourages people to publish own packages. If you create an useful test assertion library, you don't need to turn it into full blown framework with all possible bells and whistles
8.
by phadej 12y ago
Short version: node.js of course! A bit longer one: One can fetch `jsverify` package metadata from http://registry.npmjs.org/jsverify and all current packages are listed in http://registry.npmjs.org/-/a
9.
by phadej 12y ago
It was enough to fetch only the package metadata for the analysis in the post. One could fetch the actual packages too (e.g. the smaller ~20k package set). But there should be more motivators than just counting the amount lines of code :)
10.
NPM registry in numbers(blog.futurice.com)
65 points by phadej 12y ago|36 comments