tferris

What's the fastest templating engine for Go? And how does it compare to respective implementations in other languages?

Some nice thoughts but dcurtis missed the point: people do not criticise the concept or idea of Google Glass -- they sneer at the implementation. Once we have mores subtle devices or even contact lenses with embedded screens we'll see a breakthrough of this new medium but until then it's more kind of a R&D thing with a use case for just few niches.

Definitely the best browser multiplayer game ever.

And nice to see that it's build on Node (among other tech).

Weird question and the answer is, don't plan for the next five years, plan for the next week, develop an MVP and when it's deployed think about the next step.

Node + Express

> why people still use Java

I am not into Java but I'd rather prefer using Java the next 10 years than Ruby 1 month. At least I get a perfect language implementation (the JVM) with Java.

> It's nothing but flame bait

Why? I am damn serious about every point: Ruby/its entire ecosystem/Rails/DHH is outdated/becoming obsolete/so 2005.

Thanks, corrected.

> 1. Probably 75% of new startups are using rails, and rightly so. You'd need a good reason not to use it. "Rusty slow legacy systems" - what nonsense.

75%? Evidence? You are the one who is talking nonsense, sorry to be direct and getting on Reddit level but you started.

> 2. If there was a better language, they'd probably learn it? Or are you trying to insinuate Ruby programmers are dumb/lazy?

Do I really have to tell you? Instead of doing some research Rubyists still defend their old tech (like you do now).

> 3. If you are blaming your slow web page on Ruby, you're doing it wrong.

Yes you are right, and now get back in your comfort zone and code some slow web services.

> That is not the right way to start a healthy/useful discussion.

Maybe you are right but I am just fed up that on HN the forefront of new tech still such old slow technology gets upvoted on a regular base mostly by people fearing their go to tech is vanishing away. Ruby/DHH/its entire opinionated ecosystem is so 2005.

Today, I'll lose at least 50 karma points, but it's worth:

Why people still use Ruby?

1. Because they get dream day rates for maintaining rusty slow legacy systems

2. Because they do not want to learn new languages and can stay in their comfort zone

3. Because they think it's still 2005 and nobody cares about slow server response times

And now Ruby lovers, click on downvote or give your reasons why you still use Ruby.

Very good point and I forgot to write it. You are totally right women usually won't get it when you talk about let's say business related achievements because they are often not interested and don't get it AND MUCH MORE IMPORTANT: because you are qualifying in that moment: you send the signal 'hey look, I am doing impressive stuff, I am special, please like me' which makes you again needy and unattractive -- now we are knee deep in PUA stuff -- that's too obvious and women aren't stupid, you have to learn how you transform the energy you got by your achievements into your general self-confidence. Telling that you are an entrepreneur who makes tons of money is the wrong way. You will signal this automatically without telling anything about your startup life. When I peaked in my professional life I told that I am a "grocery bagger" and I converted 100% to the next step while converting 0% when I told the truth.

Then, when closed and in later stages your startup life gets more relevant since it shows that do stuff that matters and it helps transforming an one-night-affair into a relationship.

Guys, if you haven't done this before, now is the time, get PUA stuff and learn this like you'd learn Go or C++.

> make me want to cut off my penis and write "Eunuch" under "Sex" on my ID.

Just getting your testicles removed would do the job too -- but seriously, please get some advice before doing anything.

> I'm a rich startup guy in NYC and I can't get a date.

This is weird as long you got rich by your own startup/achievements. Then, you really need some help. As cheesy it may sounds you should get quickly some PUA resources and/or training. Getting laid and the SO is 70% about self-confidence and having state and 30% about tactics/getting reframed/brainwashed which you get from PUA's. Do this today. Every men should once get into this stuff.

> How about we all just chill the fuck out?

That's no option. At least for men.

Men are restless hunters and highly competitive creatures. Men thrive when taking risks, when being in a fight and when they finally won and dominate their peers. As sad it sounds this is what we need and make us happy. We can have breaks from time to time like working as dull office drones avoiding any risks and watching Youporn before bedtime but we degenerate when this state of boredom sticks for longer time. Even if Zuckerberg, its Facebook and the constant flow of successes of peers on the FB news feed drives many into depression, men need this to get out of their comfort zone and start fighting.

(Besides, I think that the original article is crap as many lifestyle advices)

> Silicon Valley is filled with rich startup guys who can't get a date.

You didn't get the point, it's not about being rich. It's about having a life and having achieved something, you don't need to be necessarily rich, you need self-confidence to approach women. You can train self-confidence and fake it until you make it with tons of PUA books and resources BUT building self-confidence by starting something is much easier and more effective.

Saw this thread when it had just 2 points and hoped it won't get upvoted since it's just -- sorry to say -- a useless post full of misinformation without delivering any message. I highly doubt the author has enough experience with building relationships, getting laid, get the right one and so on:

Now, since it's on the front page my view. You have two options:

Either you spend your time in your early 20s chasing women and spending all your time on building relationships and getting laid or:

Start at least 5 startups until you are 25 and hope that one of them gets kind of profitable or even better and you do an exit. Starting later is getting harder and harder, you are spoiled by high salaries and laid back office work and suddenly you have a child and it's getting to risky to start anything. The experience you make as an employee hardly help you as an entrepreneur but you need to fail often as an entrepreneur -- every failed startup brings you tons of experience and closer to a successful company.

Back to the girls: if you got successful with your startups you don't have to think about relationships and girls -- you'll send so much self-confidence and they're will be tons of opportunities. And even if you still do startups which didn't succeed you have much more to tell then any office drone. You'll have much more opportunities than those who desperately looking for the SO without having a life or anything to tell. That doesn't mean that you should omit any social life or getting laid while building a startup, it just means don't focus on this, focus on being an entrepreneur.

If this had be done by any Tom no one would have upvoted

Great having one bringing a balanced view on Go and showing that Go is still not ready for production when used with external libs. A refreshing take in this overhyped thread.

fyi, in the replies of the original post someone got totally different results. with v0.6 it was significantly faster than Go and with 0.8 was on the same level

I find this post paired with this thread confusing. Yes, Go is tempting and I'd like to try it since a lot of people get quickly into flow with Go, the "package manager is so great" and "everything is just a breath of fresh air".

But what I don't like: the negativity against Node and omitting some facts. In the replies of the orignal post a guy tested two (!) times Node and once it was significantly faster (v0.6) and once it had same speed (v8.0). So, why has mjijackson such different results in this thread at the top?? And maybe we should test it on real servers and not on a MBA. Moreover, we have here some micro benchmark which possibly doesn't reflect reality well. Don't get me wrong, I appreciate any benchmarking between languages but then please do it right and make no propaganda out of it. Further, Go's package manager seems to be nice but it does NOT have version control. How do you want to use this in a serious production environment. Maybe version control will come (but then tell how without loosing its flexibility) or not but this is something serious and definitely not an alternative to any server environment except for some mini services.

EDIT: downvoting is silly, propaganda and won't help the Go community in getting more credibility, better do some further benchmarks; otherwise this post/thread is full of distinct misinformation and should be closed

How long does take the compile time with a medium sized typical web project. Something which gets annoying or still bearable?

HN's karma system already makes reputation often more important than the actual message. I think an HN AMA would strengthen this, so I'd suggest to stick to good contents and not focussing to much on the author's identity (since the best contributions come from anonymous accounts).

what's the best way to have hot fail over?

I totally agree, this new machine is so fricking responsive that I still think bare metal rules but I am just so afraid of the system operations of such a machine. But maybe Paul can give us some hints and why it's still worth to go the bare metal route.

EDIT: since Heroku fooled Rapgenius and us all it would be one more reason to get into system operations again and host on bare metal.

Saturday, I thought: "This guy (PG) is really brave, everybody is nowadays using virtualized server environments on mulit-core machines and PG just gets some bare metal and puts his app on one core and one thread. WTF, this guy is a genius, single-threaded apps on bare metal FTW, this is so great and I am doing this too."

After seeing this thing down for several hours -- and Google hate downtimes, they punish you instantly -- I think: "Maybe not."

However, happy to hear what went wrong and why we still should go for the bare metal thing.

- No proper packaging/namespacing

http://nodejs.org/api/modules.html

- Completely idiosyncratic results when operating with mixed data types (10 + 'p' = '10p', 7/0 = 'infinity' and all that)

I wouldn't call it idiosyncratic but just use Underscore and you are fine.

- Variables default to a pseudo-global scope

just use 'var' when declaring them

- Prototype based 'inheritance', while cool, is just cumbersome and inelegant compared to languages that have proper object oriented language constructs

Any OO is cumbersome and should be used only when it makes sense. If you don't like prototype based inheritance you can still use traditional OO with extra libs.

- Take all those and a syntax that was partially taken from Java, and you end up with verbose code jumble that is way more difficult to read than equivalent Python/Ruby (even C#)

Sorry to disagree again but there are many people preferring bracket based languages over those omitting them. You can quickly identify blocks and navigate through the source. And JS isn't verbose like Java.

JS has its quirks like any other languages but these are just very few and you get tons of amenities in return.

JS is a modern and beautiful language, comparing it with PHP is bold. People fighting Node are just afraid to change and to start from zero again, they fear the truth.

No other language offers C-class speed, that rich ecosystem (which is fully async) paired with such an easy approachability plus the best and most modern package manager around. Speed is not everything but users won't tolerate unresponsive web services based on sluggish language implementations and cumbersome frameworks anymore, it's not 2005.

Why do you think did Airbnb, LinkedIn and many more choose Node in production for high traffic apps?

Don't get me wrong, Python, Erlang, Haskell are great languages, I love them all but since V8/CrankshaftJIT/Node, JS is playing in a different league with an amazing cost-benefit ratio and I am confused by people ignoring this (however, I see rather Go and Clojure as real contenders to JS since they offer modern language concepts too paired with speed and real concurrency but they are again compiled and deploying JVM based stuff (Clojure) is no fun at all).

As good as pypy is it's no replacement for python yet.

http://stackoverflow.com/questions/12867263/why-wasnt-pypy-i...