twerquie

Scala seems roughly similar.

What you describe as "ceremony" I take to mean socialization, that you are shopping with the public in a market atmosphere and I think that's something absolutely intrinsic in all human cultures and isn't going anywhere. The mall is the perfect style of market for shopping for clothes, media, fast food, housewares.

Heatman would never do that. Heatman honest.

You're thinking of "modern man", not "the modern man".

For what it's worth, I've also had a hard time recently understanding what the Wolfram Language and associated products are outside of the marketing bullshit.

You're probably about to discover that the data is also not free.

Put a reverse proxy server such as Nginx in front of your existing Rails 2.3 servers as well as a new Rails 4 app server. Slowly, route by route, port controllers over to the Rails 4 application and map traffic there using Nginx rules. This method is completely safe: If you notice discrepancies, you can point traffic back to your Rails 2.3 environment while you improve the behaviour of the Rails 4 replacement. Lather, rinse, repeat until it's all ported over.

But that's exactly what the article is suggesting Apple creates.

What a great post, please share it with more people. I agree 100%.

MDN publishes correct polyfills for ES5 Array functions like map, reduce and forEach. I think it's worth shipping those and using them now.

Ultimately though, wouldn't you want to use a js preprocessor that lets you write full spec ES6 and compiles down to ES4 or whatever your runtime target is? That's available today, and it doesn't confuse the meaning of class, fat arrow, variable scoping, etc.

CoffeeScript played an important role in the development of ES6, but looking forward, it seems to have a same-but-different set of features vs. actual JavaScript, which may doom its future.

Generally speaking, in dynamically typed languages, unit tests are the replacement for compile-time type checking. Type safety should not be a goal, duck typing is embraced and the correct behaviour is verified.

I suppose. For me music is like fashion, it is in and of a moment. It is inspired by what came just before it, and it inspires what comes directly after it. Beyond that it takes on some sort of historical context.

http://www.youtube.com/results?search_query=cover+teenage+dr...

Why wait until the copyright has expired?

And how is value determined (hint: it's not subjective)?

Pitch correction is unable to change the timbre of a voice. If you can't easily recognize different people's (auto-tuned) voices, you would be in the vast minority of humans who lack this basic skill.

That Adele album was brilliantly written, you should go listen to it in its entirety if you haven't already.

Great username, great band.

Most of the singers MM writes with contribute the lyrics. Hip Hop works almost the same way with their producers essentially writing the "song" structure (beats and loops).

Katy Perry's Teenage Dream album was largely written by MM, I'd say it's both one of the most important pop records of the last decade and MM's best work. It smashed all sorts of chart records, in total it had 8 top-three singles on the Billboard Hot 100, and 5 number one singles.

It's absolutely destined to be a classic album in every sense of the word, and I find it funny that most music heads I know can't see that because (imho) they are too afraid of being seen as someone who enjoys Katy Perry. Oh well, the kids who were 12 at the time will grow up appreciating it. I suppose it's for them anyway.

I've got a feeling we're going to look back on this era of music with wide-eyed wonder and recognize many of his pop hits as the masterpieces they are.

Unfortunately, social norms prevent us from listening with our ears.

No surprise they often work together.

I'm a big fan of ORMs in other ecosystems (Rails and Django, for example), but in node I like to write more functional-style code, composing small modules into larger applications.

For this, check out the fantastic node-postgres adapter from brianc as well as his node-sql package for authoring SQL statements.

https://github.com/brianc/node-postgres https://github.com/brianc/node-sql

I feel you - I recently started a node project on LevelDB and ultimately switched over to an SQL database. The difference though is I went for Postgres 9.3, which has incredible native JSON support, allowing you to slice parts of your JSON data out as a record set, join them against tables, as well as other crazy things like partial indexes on deeply nested JSON values which may or may not be present.

I really think Pg is starting to blow Mongo out of the water.

I think you completely missed my point. "Byte size" in javascript is an analogue for slow app execution (page rendering and code paths), not slow downloading or bandwidth costs.

Also, I'm not suggesting we "re-invent the wheel" or code everything from scratch. I'm an advocate for composing your app from small modules. Modern js is incredibly good at this.

Comparing images and javascript in terms of payload size is apples and oranges. Images do not block the rendering of a page, are trivial to decode and display, and do not have long execution paths for the duration of their life.

I'm not following, is this just snark or am I missing a point?

What if, instead of needing a framework, we just wrote tiny modules of functionality and composed them into an application?

This is how the nodejs guys are doing this via npm and I must say, it's staggering. The core node "framework" has a tiny API, and the heart of it is simply require().

It can (and should!) be written more elegantly

[5, 10, 1].sort(function(a, b) { return a - b })

Or, in ES6:

[5, 10, 1].sort((a, b) => { a - b })

That's starting to look pretty nice if you ask me.

True, JS doesn't ship with a large standard library. But that has turned out to be one of its greatest strengths and a key reason for it's runaway success.

AFAIK Dr. Dre hasn't done a stitch of work for or with Kanye in any capacity.

http://en.wikipedia.org/wiki/Watch_the_Throne#Personnel