smanuel

- Google is afraid of Facebook

- Google wants more users in Google+

- People don't care about Google+

- This doesn't change the fact that Google is still afraid of Facebook and wants more people to use G+

- Google will try to do everything it can to drag you into this service which you won't use anyway

What's so strange about this?

> Jobs wasn't talking about aesthetics; it is true of pretty much everything from Microsoft. From UIs, to development frameworks, to tools, to shells and even APIs. Back then, having "no taste" was totally fine because people communicated far less.

I think that the main problem is the MS has always tried to make things appealing to a certain crowd known as "VB developers", "drag and drop developers", etc.

I've heard too many times "You can do this with almost no code" with our cool new "Microsoft Foundation For Next Big Bullsh Blah Blah". And this is presented as a good practice. And the whole army of evangelists starts touting and praising the next BS framework. People start adopting it, other people start building other things on top of it, until everyone realizes it's BS and such practices, proclaiming "you'll write less code" lead to a pile of bad design decisions that you will later deeply regret.

Japan is big.

Agree, the more data points we get access to, the more correct analysis we'll produce at the end.

It's a pity knowing that there's a lot of information stored already in systems like 23andme, practice fusion, healthtap, etc. but I guess getting access to this data to aggregate it and analyze it would be... mission impossible.

I, for one, do Not believe this study. Decline of serial killers!? What would they say next? That Dexter is not real?

Which reminds me of this article:

http://www.digitaltrends.com/mobile/why-you-shouldnt-fall-fo...

and the most important advice: "Ask yourself why you're upgrading"

"the assembly language for the web" just got renamed to... "the assembly language". Very cool.

Well... everything could be achieved with JQ. Usually with 1 line of code. But that library is 2.7k and you're working directly with the DOM elements and not with wrappers. So I guess it could come handy for smaller projects where you wouldn't need the full JQ power and 10 JQ widgets.

Web Tracing Framework a.k.a. WTF. Looks cool btw.

I'm not sure to what specific beats you've been listening to but they surely did "work". I listened to a few hemi-sync beats some time ago (http://www.hemi-sync.com/) and they've brought me the worst nightmares I've ever had. On the next they I got sick. I've also talked to people who said they've had OBE (http://en.wikipedia.org/wiki/Out-of-body_experience) after listening to those beats. This never happened to me though. Just the nightmares. I guess it really depends on your current state, in what frequency these waves put your brain in, etc. So it's highly individual.

It's custom code which pulls the latest commit when github hook hits the endpoint. It's... a few lines of code.

It's only me working on this so I run the tests before each push but I guess running the tests on the staging env will be like a few more lines of code. I s'pose at some point I'd want to keep test results and I'll need a build server. May be.

Forgot to say that I also deploy everything on heroku (for free) as a staging environment (before pushing to production).

heroku + mongolab + redis to go.

ah yes, and new relic for monitoring what's happening on live.

Hosting everything on Linode.

nginx as a load balancer (running 4 node processes on different ports as upstart scripts with respawn) and for serving static files.

Express + Jade (but I do most of the things on the client - calling REST API)

redis as a session store: https://github.com/visionmedia/connect-redis

DB - MongoDb (I also use Mongoose: http://mongoosejs.com/)

I also host most of the static resources on S3 and they are served through CloudFront CDN. At first I used this module (for easier deploying the resources to S3): https://github.com/niftylettuce/express-cdn but later I had to rewrite most of the things to handle my specific requirements (using knox).

Tests (client and server side): Mocha + sinon + chai

CSS: Less + less-middleware

JS: UglifyJS + express-uglify

I'm also running a worker process and a scheduler process. For communication between the worker, web and scheduler processes - RabbitMQ.

Deploying everything with git push in master (custom github post push hook). No build server. Have nothing to build.

Client side: jQuery (of course) + AngularJS + custom code for bootstrapping the SPA.

KnockoutJS - Naaw.

Hope this info helps.

P.S. Authentication: http://passportjs.org/

I would rather use a lemon battery. It lasts longer and I won't have to think about redundancy for a few... seconds.

Looks like a great start, that's sth I've been waiting for a long time.

It would be great if it supports adding more instances (dynos?), balanced through ELB. And... worker instances. And... Some configuration management.

The potential is huge!

I've always seen Yeoman (and hence Bower for package management) as The standard. I've never used Ender and can't comment on it but AFAIK it uses Bower underneath.

I would add iwantmyname.com to the list.

I'm not sure "native apps still reign supreme over HTML5" on the monetization front (the app stores) because we have hybrid mobile apps for that (e.g. PhoneGap, Titanium, etc.).

For a brief moment I read the title as "Seamless and GitHub to merge" and was trying to imagine what they could possibly deliver together.

Whenever I feel this way, I just open http://programming-motherfucker.com

And I just start writing code.

I'm using PhoneGap and I'll use it again.

Yes, a PhoneGap app may never run as smoothly as a native app but I'm not ready to sacrifice the advantages that PhoneGap approach brings:

- Using HTML/JS/CSS for all platforms - I can strip all PhoneGap related calls from my app and have a mobile web app (which can run as a full screen web app)

And there're various tips and tricks to help you achieve almost native experience with PG (http://coenraets.org/blog/2013/05/top-10-performance-techniq...).

Imagine doing this in: - ObjectiveC for iOS - Java for Andriod - C# for WP - HTML/JS/CSS for having a mobile web app

Sacrificing some performance suddenly starts making sense.

Thumbs up for Gitchess. Just brilliant. Idea pitch - Gitateka?

An integration with Jawbone's Up / Fitbit's One would help a lot.

The tl;dr part should just say "If you haven't started coding yet, then you shouldn't bother much about unit testing" which is.. well... common sense.

They forgot to mention the best new feature - changing the code name from Nadia to Olivia. Olivia sounds much more... stable. On the other hand whenever I read support for HTML5, CSS, JS, it's like... something dies in me. So, will be staying with Nadia for a little while longer.