Hey Alex, there's the same holywar in Java world about Checkstyle. And btw, the error caught by the jshint there should be really caught by the 'use strict' and some unittest (mocha, for instance, catches mem leaks even w/out 'use strict').
Guys, again - that's really a sample of node.js layers; client is just showcasing the way restlike APIs may be easily exposed and the tech stack which allows for quick creation of such APIs. I should have given more stress on that in the original email, sorry. Code styling really is an opinionated stuff, I know people totally nuts about Coffee and its haters. And yes, I can understand both of them :) So let's keep this idea-centric, not whitespace. Btw I also had that feeling that Jade is rather for serverside rendering than for client-side. Anyway, if we do client rendering with it we'll need something to plug in for the MV* (backbone?). Cheers, Alex. 2013/10/29 Alex Kocharin <a...@kocharin.ru> > 29.10.2013, 13:05, "Floby" <florent.j...@gmail.com>: > > Thanks for your inputs alex's. > > In my book, jade sucks ass, as does any templating on the server-side. > > > Yep, that's what I'm talking about. > > Jade can be used quite well for hybrid approach, by which I mean creating > the same templates on the server-side and updating them on the client-side > without reloading. > > But a lot of the people think that it's a server-side only engine, and > that's exactly why people need to teach about its possibilities. > > That's why angular.js sucks by the way. You can't use it on the server > side, so it is useful only for a few web applications where client-side js > is an actual requirement. > > > > So you see, opinions infer. My suggestion to use javascript MV* frameworks > is in fact because they are so hip. Alexander is trying to gather interest, > this is probably the best way. > > for code formatting, just feed your code through jshint or jslint. This is > the standard for javascript. > > > Jslint is an opinionated crap. Jshint is better, but only because you can > configure it properly. Default codestyle imposed by both these engines is a > crap. > > I actually tried to use jshint for a while. And just once in all the years > it successfully catched an error for me. I still remember that one case, it > was like that: > var something, > foo, > bar; // <-- this > baz, > qaaz; > > I avoid semicolons since, but I still remember that case for some reason. > > Anyway, running jshint to fix an errors in the code isn't really worth it. > Running jshint to check your codestyle is just plainly wrong. It is NOT the > standard. > > > > > > On Tuesday, 29 October 2013 07:33:32 UTC+1, Alexander Cherednichenko wrote: > > Hello Alex, Floby! > > Thanks for your participation. > > As for UI - Totally Agree, capitalized. We had extjs as a requirement back > then, and really only used it to illustrate node's REST API services. Will > defo switch to something fancier later. We are not really happy with Ext in > any way, especially after working for a while with it. > > > Grunt, deployment descriptors to NodeJitsu and Joyent - yeah, great idea. > If we add a couple of description pages on how to fire up the application, > developer-in-study could have their app running in the Internet in like 5 > minutes, mostly spent for account creation on hosters'. > > As for indentation - we'll look into that; really have to comply with all > the projects' guidelines (which tell to use 4-space), but I also felt > that's a little wider than it should be. > > Thanks all, > Will keep posted on significant updates to the app -- anyway we were > planning to plug in fancy testing of everything (just as an illustrative > setup) next. > > Good night, > Alex. > > On Monday, 28 October 2013 12:58:23 UTC+2, Alex Kocharin wrote: > > > On Monday, October 28, 2013 2:10:03 PM UTC+4, Floby wrote: > > Hey, really interesting stuff here. > > I like how you tried to keep the dependencies minimal. However, here are > my thoughts for what, in my opinion, could make this better > > - Use something sexier than ExtJS. Like Angular.js or Ember.js. Better > yet, all 3. > > Better yet, Jade. Simply because nobody seems to understand how to compile > templates and use them on the client side. > > I don't know about Ember.js, but Angular.js is largely overrated. I'd > avoid that for a long while... > > > - Use Grunt for front-end assets management > - Add necessary files for deployement to Nodejitsu and Joyent in > addition to Heroku > - Use 2 spaces indentation for javascript > > Use tabs, pleeeeease. I understand that spaces is preferred in large > projects because stupid developers don't understand smart tabs, but why do > you suggest teaching beginners the wrong things? > > > IMO, this could become a great example app. > > On Sunday, 27 October 2013 20:03:27 UTC+1, Alexander Cherednichenko wrote: > > Hello! > > Me and team at my company (logicify, software consulting) have started > node development around a year ago. We had then created a really simple app > showcasing the tech stack, and now, after that year, we would like to share > it with the community. > > This is a really simple but fully-functional application featuring data > storage (MongoDB), search (Elasticsearch), cloud deployment (Heroku), > serverside JSON API (node) and client-side UI (very basic extjs 4). Totally > a work in progress rather than finished product. > > I think it may be useful: > > 1. For learning - just get a grasp of the code in a bite-sized chunk > (s). > 2. Sample for integration of technologies - it has quite full a stack > though very small domain (books). > 3. Seed, or archetype app - we have been already seeding it twice as a > skeleton for real-life application > > So, the links: > > 1. Github, code https://github.com/Logicify/nodejs-sample-task > 2. my blog, motivation (why we needed that and how we use it?) > > http://lexaux.blogspot.com/2013/10/nodejs-elasticsearch-mognodb-extjs-and.html > 3. and as a bonus - 2 slidesets from local meetup me and Pavel Knorr > had last Thursday in Kherson (Russian language!). Just in case :) > > http://lexaux.blogspot.com/2013/10/two-talks-at-local-software-development.html > > Thanks, and good night! > Alex > > > -- > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nodejs+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. > > -- > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > You received this message because you are subscribed to a topic in the > Google Groups "nodejs" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/nodejs/yjyHVWlDPjU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > nodejs+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- Alexander Cherednichenko [ the only way out is the way up ] -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
