onejs

This weekend; 7min.io MultiplayerChess.com github.com/azer/boxcars github.com/azer/onejs github.com/azer/shell-jobs github.com/azer/fox

Most of the stupid ideas like semicolon insertion are not major deal breakers [1]. Yes, they are annoying, but nothing that can't be fixed with a lint program. You can treat your lint program as a stricter replacement for a syntax error checker. Class-based OO is implementable with prototype-based OO (with some exceptions such as "protected" which are mostly unnecessary when first class functions are available). In practice, this means you need to learn how to use it (unfortunately the quirky way its implemented in JS doesn't help this at all) CommonJS provides quite excellent namespacing and modularity - its only a hack because it doesn't work in browsers [2] The standard library is admittedly lacking but there are many libraries that cover this gap, some of them being de facto standard. Development environment support is pretty good for

Very cool except it has no NodeJS example. By the way, JavaScript does not suck. It has module and package systems, check out NPM, and OneJS for using all NodeJS utilities in client-side; http://github.com/azer/onejs

both RequireJS and Browserify are not good options. Browserify's implementation is awkward, incomplete and pollutes global scopa a lot. Check out OneJS: http://github.com/azer/onejs It's the only tool that lets you structure your client-side project as a CommonJS package and produces unobtrusive code mixable with anything in same global scope.

Consider OneJS here; http://github.com/azer/onejs see my comment above for details about the differences; http://news.ycombinator.com/item?id=3915403

RequireJS is very expensive and it's NOT CommonJS. It claims that CommonJS is not-optimal for browser and offers you to put your source code inside of an awkward container for optimizing. It's not smart. Let me introduce you OneJS: http://github.com/azer/onejs It simply converts any CommonJS package into a single, stand-alone JavaScript file. It means, you can structure your client-side project just like a NodeJS project and you can convert your NodeJS project to a single file just like a client-side project. Unlike Browserify, OneJS is unobtrusive [1], provides an accurate implementation of CommonJS specs [2] and the output it produces is suitable for splitting and having async dependencies. [1] A chess website built with OneJS: http://multiplayerchess.com/mpc.js [2] ExpressJS built with OneJS, with all dependencies: https://gist.github.

A bundle file OneJS generates contains only a tiny CommonJS implementation and a simple "process" object ( use "--noprocess" option if not needed). You can browse them here; https://github.com/azer/onejs/tree/master/templates It doesn't contain the standard library of NodeJS by default but you can install the available modules like assert, path, url etc.. by doing: $ onejs install assert

That approach may fit the need of a modularity but it doesn't solve the remaining issues. To me, the most important issue is to make both backend and frontend dependencies same. I haven't documented yet but there is something I'm working on for a while, OneJS. It generates a single, stand-alone JavaScript file, not requiring coder to make any change on a CommonJS code. The built file it generates can be run at any platform that doesn't support CommonJS, such as web browsers. It means that we can use the great dependency mechanism NPM provides in our frontend apps. For those who wonders, OneJS; https://github.com/azer/onejs Example project; https://github.com/azer/onejs/tree/master/test/example-proje... Output of the above example project; https://gist.github.com/1286969 A relatively larger example; https://github.com/azer/multiplayerchess