alexandros

Surely if users are flocking to the 'latest and greatest' you deal with that by gradually reducing the prices of the old servers such that you get natural price discrimination?

Sometimes visualisations are useless overillustrations. Other times, they are enough to put a complex argument to rest. One of the latter ones:

http://www.informationisbeautiful.net/play/snake-oil-supplem...

From an Euler problem (412 IIRC), I had played around with Young's tableaux, counting which also gives rise to the sequence 1,2,42,24024. More numbers here: http://oeis.org/A039622

Am I onto something? Let's see if the next moment is 701149020.

Can't access the article due to database error, but since we're discussing keyboard layout effectiveness for developers:

If we were indeed limited by input, why wouldn't this come up in discussions about languages like CoffeeScript (or even Python/APL) that save keystrokes to begin with? In the case of Coffee and Python, the keys saved are actually the hard-to-press symbols as well. And yet I've never heard the point come up.

Perhaps this is more about our need to feel superior by adopting a routine of cargo-cult efficiency than anything else. In the broader view of productivity, optimising keyboard layouts is more like optimising memcpy() in C. While it may bear some results, it's rarely the actual bottleneck.

Still beats dying.

Oh, I know.

Try to start a project with angular, coffeescript, and requirejs. On top, have the audacity to not want to use array syntax but have ngmin deal with that.

You're in for a world of pain. 4 hours did you say? I've been working on this (in free time, granted) for about a month. It took me a while to believe this isn't solved already. Apparently the angular-seed world and surrounding tooling stil has way to go.

The separate-by-feature approach gets a much better treatment in ngBoilerplate: https://github.com/ngbp/ng-boilerplate

What I don't understand is all the whining about posting slides.

This is fresh off the presses, answers hot questions in the angular community, and obviously people are upvoting it. If you're aware of what's happenning in Angular, every slide stands on its own and has useful info.

Can we please give all the moaning about format a rest please?

Not sure how this is calculated, but you're estimating Instragram at 4B+ and Google (maps, mail, chrome, voice, ...) at 800m? Seems like something's wrong.

It does if you're thinking what OS/market to code your app for.

If Apple doesn't license it's OS to other manufacturers, that's their business decision, but they are (also) an OS maker nonetheless.

It would be good to get Firebase's Angular bindings to work decently well for top-level objects and improve their promise support. I recently worked on http://worldmap.io as a way to test a bunch of angular-related tech and the firebase bindings, while dead easy to start, were a pain as I couldn't resolve them in the routeProvider. Instead I had to do it inside the controller, which forced me to keep a bunch of boilerplate. See https://github.com/alexandrosm/worldmap/blob/master/app/scri...

Still, a great project and concept, just has some more way to go before I'd use it in a real project. I do want to check out https://github.com/marknutter/firebase-resource though, made by a fellow HNer and mentioned last time around.

Prediction:

The much-anticipated convergence of Android and Chrome is near. These new Chrome apps are the programming model for the upcoming native Android webapps

The next milestone I expect to see is V8 added alongside Dalvik as a first-class runtime for Android. Maybe in Android KitKat?

Interestingly, communities like HN and LessWrong have banned political discussion, or tried to, for its particularly deleterious effect on conversation.

http://lesswrong.com/lw/gw/politics_is_the_mindkiller/

Define 'care' when a corporation is involved.

Actually, we're not doing too bad in not killing each other (too much). See Pinker's "The Better Angels of Our Nature: Why Violence Has Declined" and related research. I do hope the trajectory continues though.

Witnessing such an event could help get humanity serious about existential risk, from comets or otherwise. I, for one, am hoping for an impact.

“If you wish to make an apple pie from scratch, you must first invent the universe.”

― Carl Sagan, Cosmos

You could be just as easily be accused of karma whoring for posting this reply. As could I for responding to you like this. But the truth is, you felt strongly enough to post the reply, as did I in responding to you, as did the original posters. Any action in a karma-rewarded community can be brushed off as karma whoring, but that doesn't mean it should.

The problem is that the position of the moving part (the asterisk in your example) is unclear. So effectively the [* ] is not distinguishable from the [ *]. Putting the labels outside won't fix that.

What the article should say to keep the 79% number in place is that '79% of the price was overpayment'. What you are saying is that 'they paid 482% of what they should have'. If they want to keep the structure of what they have written, I think ghshephard's formulation is right. They overpaid by 382%. Aren't percentages fun?

As with SpaceX I think Musk would solve this by designing for humans but testing with cargo.

For all who are thinking about moving to WPEngine:

Your staging server does not use WPE's caching technology, which your production server will use. WPE will not give you details on how their secret-sauce caching works. This means that things that work on staging will break on production. WPE also refuse to turn off their caching on production, but also refuse to turn ON their caching on your staging server. This means there is no real way to test. Things that work with their staging server, and even work with the standard WP caching plugins, will break in WPE production.

Their solution? Buy another production site to test on.

That website is now moving from WPEngine after having its launch botched by the aforementioned issues, and after not being able to make a basic paywall work with their caching. Once they realised the use case, WPE simply suggested moving elsewhere without making any further effort to accommodate.

I had a similar reaction to the post yesterday by asmartbear as Jaques, but he made the extra effort to actually write the blogpost, so bravo to him. WPE enjoys this sterling reputation that misleads a lot of people into using them, but their comfort zone it seems is limited to vanilla WP installs with little deviation.

Fun stuff. How about a RC plane dropping off quadcopters loaded with the payload for the last mile? (the copters can meet the plane on the way back or fly home alone. You get the range + efficiency of the plane with the agility of the copter.

what, nobody for .js?

> I would argue the problem isn't the quantity, rather the quality

But you didn't, argue. You simply asserted. You threw out the article's theory by constructing a straw-man you didn't even bother tearing down, then proceeded to inform us of your views.

I don't think the CoffeeScript step exists in the pipeline. CoffeeScript is the language the JVM is written in, but I don't expect it outputs CoffeeScript itself.

Having 1 VC invest is a problem as the company is dependent on them to invest in the next round or face signalling problems. The VC may use that to force worse terms. Having 9 VCs is less of a problem. Or at least if all 9 VCs that have followed your company since seed round refuse to invest in the next round, you probably have more serious problems to worry about than the signalling issues.

Kickstarter, if you care about your reputation, fix this and make sure it never happens again.

Rulemotion is hiring in Athens, Greece. We're building a cutting edge Javascript/Coffeescript & node.js team, with the best hackers we can get our hands on. We also have opennings for capable Python/Django Devs.

If:

...you are interested in a position with a phenomenal team, the ability to solve hard problems and are able to manage your own time,

...you are entrepreneurial and want to work with a growing startup that appreciates good coders and pays above the market,

...you enjoy working with people passionate about good code, using all the latest tools and libraries, and encouraging open source contributions,

...then I'd love to talk to you! Drop me a line at alexandros [at] rulemotion [dot] com.

Ah yes, the eternal argument by anecdote.

So let's say you've shown that 'Honest People Might Be Dangerous'. How about a few anecdotes where a trivial lie led to a disaster? There, I've proven that 'Dishonest People Might Be Dangerous' too. What does this add up to? The ever-insightful 'People Might Be Dangerous' lemma. Now, given a choice between the 'Honest' and 'Not-entirely-honest' model of human, which one would you choose to work with?