HNHacker News
TopNewBestAskShowJobs

combataircraft

128 karma · joined January 17, 2012

1630923320
submissionscomments
combataircraft··on Garzik: An Andre To Remember
On the other words: All this software development shits are NOT for EARTH. They are for the price competition of capitalist system and can only impact prices in capitalist cities, nothing more than this. Don't put so much meaning and don't think you're becoming a better person when you commit to a repository.
combataircraft··on Smart Time Ago: a new JS lib to update relative timestamps more efficiently
you guys might be interested at this; https://github.com/azer/relative-date
combataircraft··on Fay -- A proper subset of Haskell that compiles to Javascript
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
combataircraft··on About the future of Thunderbird
@beagle3, I'm not as powerful as Mozilla. They are letting Google occupy whole the internet by not creating an alternative for Gmail.
combataircraft··on Preparing Yourself for Modern JavaScript Development
that's not true. They didn't even experiment CommonJS on browsers properly.
combataircraft··on About the future of Thunderbird
The real question should be: Where the hell is the open source alternative of Gmail?
combataircraft··on Preparing Yourself for Modern JavaScript Development
I'm the owner of both comments and wrote it for two times because I can't see the other one and have very strong opinions about this topic.
combataircraft··on Preparing Yourself for Modern JavaScript Development
here; http://requirejs.org/docs/

you can see all the smelling shit of requirejs there.

combataircraft··on Preparing Yourself for Modern JavaScript Development
I've been following the work on RequireJS for two years and think that it's an evil project that sabotages the rise of CommonJS, NodeJS and NPM by leading client-side Javascript coders to follow a non-standard, awkward way of JS development. From the very beginning, it forces coders to cover their code with awkward code and maintain it manually. It's completely insane. I even think that I'm wasting my time by talking about it.
combataircraft··on Preparing Yourself for Modern JavaScript Development
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.

combataircraft··on Show HN: Joosy, the rails-tied browser app framework
All the JavaScript and templating code should be reusable by other platforms with no effort. It's required for testing, optimization and being able to move from one technology to other easily. This is the challenge programmers should solve. There has been already dozens of very good client-side frameworks that let us create very cool UIs with no effort but none of them is still good enough since the core idea is bad.
combataircraft··on Show HN: Joosy, the rails-tied browser app framework
Github is not a rich web app for me. See Google Spreadsheets to figure out what a client-side framework should be helpful for.
combataircraft··on Show HN: Joosy, the rails-tied browser app framework
What the fuck is going to happen when I need to reuse my JavaScript code on a different platform e.g NodeJS, vert.x etc?

I'm sorry for negative comments but, what ruby and .net communities produce for JS is shit. It's even more harmful then IE6 for our future.

combataircraft··on Show HN: Joosy, the rails-tied browser app framework
yeah yeah, that's what javascript needs! let's make all your javascript code more non-reusable.
combataircraft··on RequireJS 2.0 draft
Here are the core modules it supports; http://news.ycombinator.com/item?id=3915403

browserify-http can be used by OneJS as well but I don't see any point of emulating http module on client-side. I prefer using libraries supporting both platforms, such as boxcars; http://github.com/azer/boxcars

combataircraft··on RequireJS 2.0 draft
Consider OneJS here; http://github.com/azer/onejs

see my comment above for details about the differences; http://news.ycombinator.com/item?id=3915403

combataircraft··on RequireJS 2.0 draft
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.com/2415048

combataircraft··on OneJS lets coders convert NodeJS projects into single, stand-alone files
although onejs and browserify tries to accomplish similar tasks, onejs has some noticeable implementation and concept differences (e.g browserify pollutes global scope a lot and it expects you to provide it a main module instead of a package manifest)

here is the output comparison of onejs and browserify:

onejs: https://gist.github.com/2398843 browserify: https://gist.github.com/2398824

and here is a real world example of onejs;

http://multiplayerchess.com/mpc.js

The second thing is, onejs lets us use the core NodeJS library, too. It doesn't contain it by default but you can install the available modules by typing; "one install assert path util url"

combataircraft··on OneJS lets coders convert NodeJS projects into single, stand-alone files
FOA, "using same code" means "sharing same source code in all JS environments" in this context. "Proxying some server-side JS code to client-side" is totally irrelevant to this topic, as you pointed.

And here are the differences of OneJS:

  - it produces unobtrusive code
  - it bundles any level of dependency properly
  - it's not only for web browsers, but also all JS environments including Node itself
  - it's a command-line tool that doesn't require you to code.
combataircraft··on OneJS lets coders convert NodeJS projects into single, stand-alone files
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

combataircraft··on [dead]
I'm sick of this kind of gay dramas. A political conversation between two JavaScript coders shouldn't be exposed like this. It's not related to JavaScript :)
combataircraft··on Examples of beautiful Javascript
https://github.com/visionmedia/superagent
combataircraft··on Ember.js - Rich Internet Applications Done Right
@silvart19, I was talking about EmberJS' bindings. That's what makes Ember apps crappy. For the mention of MVC, you don't need to use a framework that forces you to live in North Korea.
combataircraft··on Ember.js - Rich Internet Applications Done Right
I'm very happy and satisfied with my current development kits and methodology. I use no framework and don't write any classes.

http://en.wikipedia.org/wiki/Functional_programming

combataircraft··on Ember.js - Rich Internet Applications Done Right
I prefer teaching beginners the JavaScript way of doing things instead of forcing them to write spaghetti code.
combataircraft··on Ember.js - Rich Internet Applications Done Right
Better solutions are already provided by JavaScript itself. Event-driven programming was the idiomatic solution until CPS became the one everybody follows with the grow of NodeJS. See how NodeJS community deal with async programming.
combataircraft··on Ember.js - Rich Internet Applications Done Right
Hey guys, please take a look at the following app: http://editgrid.com/untitled

It's the coolest web-based spreadsheets application built 6 years ago using no library, no framework. I'm a fan of it. It was looking just like this current version 6 years ago and was pretty fast at even IE6. And its 6 years old JavaScript code follows the rules of coding good JavaScript code way more than Ember itself.

Here is another story: I was working for a competitor of EditGrid and built a Microsoft Excel clone with dozens of features in 6 months, using no framework, no library, 5 years ago. We were two guys at frontend and two other guys in at backend. And our source code was almost pure object orient, mixable, reusable and relying on MVC, event-driven programming.

I've been shipping rich web apps for more than 6 years and recently had the chance of working with both Backbone and Ember. Here is my feedback:

The size of Ember library is bigger than total source code (including an AI library) of the last multiplayer game I built.

And both of them solve no problem, simplify nothing. They just force beginners to not code crappy code and that's all. Good JavaScript code should benefit of functional programming very well, like some NodeJS apps and libraries. They got no understanding of FP. Especially Ember relies on a horrible idea that increases the cost of development very huge. Very ironically, ember code is not reusable, not mixable with other web apps. It's not even unobtrusive, pollutes Object prototypes. When you finish your app, you got a huge garbage that has not even one piece of reusable code.

To summarize, there is nothing Ember does right. It tries to solve already solved problems in a very absurd way and is very irrelevant with the new problems JavaScript community tries to solve (such as code-reuse with NodeJS apps, it's partly solved)

It's the new, communist North Korea of JavaScript world.

← PreviousPage 2 of 2