Announcing the first release of batman.js • Hacker News Board

Re: Announcing the first release of batman.js

#71

Post by Pickels » Thu, Aug 25, 2011, 1:29 PM UTC

transition wrote: post #68

nciagra wrote: post #38

Earlier quoted context omitted.

A number of Shopify future products are being/have been built from the ground up using batman.js :)

Much like the description of the framework i think people are looking for a more specific answer to this question. I'm starting to think you are a super hero yourself. Captain Vague we'll call you.

I mostly try a framework to see what it can do. Looking at the documentation it seems like they are good enough to get me started.

Not sure what all these negative comments are doing here. Feels like half the people are asking for somebody to hold their penis and the other half is crying because they can't read Coffee-Script.

Re: Announcing the first release of batman.js

#72

Post by pandeiro » Thu, Aug 25, 2011, 1:40 PM UTC

edwardog wrote: post #51

dstein wrote: post #39

Earlier quoted context omitted.

Shouldn't it be named batman.coffee?

Haha! Yes! Good call. The first version of Batman was written in plain Javascript, but Shopify has really been falling in love with CoffeeScript, so we decided to rewrite it before it was released. Batman.coffee is more correct but sure doesn’t have the same ring to it…

Same problem as Spine."js", playing hide the salami. Most JS devs still think JS means ECMAScript. Call it what it is. Python packages compile to C but they don't call themselves names like "Django.C", that would be disingenuous and obnoxious

Re: Announcing the first release of batman.js

#73

Post by thesnider » Thu, Aug 25, 2011, 2:30 PM UTC

pandeiro wrote: post #72

edwardog wrote: post #51

Earlier quoted context omitted.

Haha! Yes! Good call. The first version of Batman was written in plain Javascript, but Shopify has really been falling in love with CoffeeScript, so we decided to rewrite it before it was released. Batman.coffee is more correct but sure doesn’t have the same ring to it…

Same problem as Spine."js", playing hide the salami. Most JS devs still think JS means ECMAScript. Call it what it is. Python packages compile to C but they don't call themselves names like "Django.C", that would be disingenuous and obnoxious

In fact, Python packages do not compile to C, so calling Django Django.C would expose a complete lack of understanding of Python. In fact, batman.js is closer to a Jinja template being named with a .html extension.

Re: Announcing the first release of batman.js

#74

Post by sunchild » Thu, Aug 25, 2011, 4:12 PM UTC

chrisbroadfoot wrote: post #34

sunchild wrote: post #31

Earlier quoted context omitted.

CoffeeScript compiles to Javascript. Batman.js can most certainly be a Javascript framework and give examples in CoffeeScript. Many people prefer CoffeeScript for a variety of reasons, including readability. Also, you aren't entitled to dictate instructions to other people who are giving you the benefit of their hard work. It's rude and obnoxious.

Your strawman argument that I'm dictating instructions is rude and obnoxious. Read my post again.

Mea culpa, and I'm truly sorry. I mistook your plea for a demand. Seppuku at dawn?

Re: Announcing the first release of batman.js

#75

Post by pandeiro » Thu, Aug 25, 2011, 5:05 PM UTC

thesnider wrote: post #73

pandeiro wrote: post #72

Earlier quoted context omitted.

Same problem as Spine."js", playing hide the salami. Most JS devs still think JS means ECMAScript. Call it what it is. Python packages compile to C but they don't call themselves names like "Django.C", that would be disingenuous and obnoxious

In fact, Python packages do not compile to C, so calling Django Django.C would expose a complete lack of understanding of Python. In fact, batman.js is closer to a Jinja template being named with a .html extension.

Sorry, my bad, but you can replace Python with some Scheme implementation or anything else that compiles to anything. The point was "compiles to" != "is".

Re: Announcing the first release of batman.js

#76

Post by exogen » Thu, Aug 25, 2011, 7:40 PM UTC

Pickels wrote: post #64

exogen wrote: post #49

This looks fun. We (at BigDoor) have built some of these same pieces using Knockout ( http://knockoutjs.com/ ) as a starting point. I'll be trying this out for comparison in some prototypes for sure.

I also use knockout.js for a project and batman.js looks like it has some similarities but it seems to be filling some holes that knockout.js leaves you to fill your self.

Which, I think, is not a huge deal with Knockout, just a difference. In our case we're using it for widgets included on other people's sites, so it's not a conventional web "application" with "pages" (I don't think we'd use the routing bits of batman.js at all, for instance).

Re: Announcing the first release of batman.js

#77

Post by [deleted] » Thu, Aug 25, 2011, 9:17 PM UTC

nciagra wrote: post #15

bprater wrote: post #6

From the site: "It gives us great pleasure to finally announce the release of batman.js to the JavaScript community today. This release represents the first code dump of something we’ve been working hard on at Shopify for a long time, so we’re very excited to get it into your hands and see what you do with it." I got zero value out of this lead. When you launch a product like this, please tell us why we'd want to use…

Sure, I'll break it down: batman.js is a JavaScript framework for rich JavaScript applications. It's designed to make development as fast and as painless as possible for developers and designers while giving them lots of power. We designed everything around a number of primary goals such as convention over configuration, HTML-based views, and the principle of least surprise. This is something we're using at Shopify i…

[deleted]

Re: Announcing the first release of batman.js

#78

Post by southpolesteve » Sat, Aug 27, 2011, 5:58 AM UTC

This seems like a horrible way to do things. I really don't want to throw a ton of loop logic (data-foreach?) and other data attributes in my HTML.

I think all of the JS MVC frameworks will be short lived. Someone (hopefully) will develop with a real soup to nuts solution that will make writing a front end heavy app simple. In Rails, I can see it being as easy as "act_as_front_end" somewhere, and the app automatically serves up your JSON to a generated frontend that mirrors your Rails app. I know that would be a hard thing to make, but this is where things should converge.