eta_carinae

You have to get used to the idea that Google is the kind of company that has a different sense of priorities than most public companies. For starters, they prioritize employees over shareholders, which is why the food over there is still free despite costing them hundreds of thousands of dollars every day in food alone.

But more than that, Google is philanthropic, humanist and a scientific activist. Don't invest in them if you are not comfortable with these ideals.

> And the fact that it's missing exceptions seems like a win because I much prefer dealing with errors when they occur.

This person doesn't seem to have much experience with error handling.

You shouldn't deal with errors the way you prefer it, you should deal with them the right way. Sometimes, it's where they occur, but very often, it's somewhere up the stack.

We learned this lesson in the 90's.

> Scala really makes Play2 shine.

Not really. Scala has a lot of good points but it's very ill-suited to web development because of compilation times.

Play1 could compile templates in a few tenths of a second while it takes 7-10 seconds for each template in Play 2, which is unacceptable when you do this all day long.

I predict Play 2 will not be around in a year from now for this reason, there are just better and faster ways to do this.

Stop paying attention to trash patents that get filed every day (too many to count and of little consequence) and start getting outraged at companies that actually sue based on trash patents (Apple is the #1 offender here, but sadly not alone).

> I don't mind writing code.

You should mind writing code that the compiler can write for you, which is exactly what you do when you don't have exceptions (you simulate bubbling up the error manually).

> In Go the code does what it says. The error is handled or it is not. You may find Go's error handling verbose, but a lot of programmers find this a great relief.

I'm sorry but you are on the wrong side of history on this question (and I happen to think you're also wrong in your characterization of exceptions).

Forcing callers to deal with error numbers right here right now only gives you the illusion of clarity and robustness but it gives you neither.

Every Go program I read is littered with "err,ok := Foo(); if err {}" every ten lines or so. It's brutally verbose and hides the intent of the code.

And it also forces callers to handle error codes that they might not be able to, while a caller a few stack frames above would do a much better job at it.

We learned all these lessons in the 90's, pity Go chose to ignore them.

> Go is so small you could hold the spec in your hand and it's going to be faster and more efficient than python as well as safer to modify thanks to type safety.

I think it's very naive to think that the value of a language in a corporation is limited to its syntax or compilation speed.

> What it says is that he finds writing containers like lists of ints and maps of strings an unbearable burden. I find that an odd claim. I spend very little of my programming time struggling with those issues, even in languages without generic types.

Rob Pike seems to be doing a kind of programming unlike what most developers do. I fill, empty, filter and analyze values in containers all the time, and I suspect I'm not the only one.

> C++ programmers don't come to Go because they have fought hard to gain exquisite control of their programming domain, and don't want to surrender any of it. To them, software isn't just about getting the job done, it's about doing it a certain way. > The issue, then, is that Go's success would contradict their world view

I'm disappointed that the only justification that he can find to explain why C++ programmers are not embracing Go is "C++ programmers don't get it".

> Disadvantage is more verbosity

Type inference cuts down the verbosity tremendously.

While this is theoretically correct, it goes against the principle of the web.

Write the content, provide some structural guidance (paragraphs, item lists, etc...) and let readers decide how to render it.

> I'm keeping an eye on Haskell for iOS.

Really? Is that even possible? Can't imagine Apple being okay with that.

The advantage of statically typed languages has a lot less to do with tests and everything to do with tools. IDE's can do very little when no type information is available, and most automatic refactorings require human supervision when performed on dynamically typed languages (read this for details: http://beust.com/weblog/2006/10/01/dynamic-language-refactor... ).

Never take GUI advice from a web site that hardcodes the width of its paragraphs to 600px.

Seriously, who does this in 2012?

> Although I don't necessarily think it will be because of war, I can see a potential future where people/persons decide democracy is a less effective system because it's holding back the decision making process

That's something Darth Vader could have said.

Oh, wait, he did :-)

> The report goes on to convey the truly heartbreaking image of a hopeless RMS sitting at the university staircase, crying.

Words fail me.

> Despite his controversial views on a variety of topics, his evangelism work all over the world is a true inspiration for countless people

I disagree, I think his evangelism is dangerous and offensive. He goes around telling programmers that they should give their code for free and he belittles anyone who doesn't follow his advice.

> If Hollywood made this exact same product but with pay buttons, why would I as a user choose it over movies.io.

Same reason you buy stuff instead of stealing them?

> Polymorphism in this instance is simply allowing you to call the same function with an integer and string respectively.

Er... no, that's not polymorphism, that's overloading.

The name is unfortunate, especially when the documentation sometimes omits to capitalize "Loop", which introduces even more confusion than there already is.

There is no evidence in this article that

1) this approach is better than A/B testing. 2) it doesn't suffer from the the Heisenberg principle

Also, the call out box at the top is obviously an ad but it's not marked "Sponsored link", which is really scammy.

It is cheating.

Interviewing is different from a real job. You need to show you can do more than look up solutions on the web.

I can't blame you for trying to cheat your way into a job and I certainly blame the interviewer for not seeing through your cheat, but make no mistake: you cheated.

Note: the interviews are for an intern position, which are very different from software engineer positions.

Brain teasers of this kind were banned at Google circa 2006.

> Not sure if I'm more amazed that Oracle thought deleting the evidence from their website would stop non other than Google from finding it.

That's not the first time they do this, they deleted Jonathan Schwartz' entire blog in the days that followed the acquisition.

They were certainly right to think that this blog would hurt their case, but they obviously didn't realize that Schwartz' testimony itself would align with Google.

Fun times.

Correct. "To marry" is actually one of these rare verbs that can be both transitive and intransitive.

And like somebody pointed out earlier, it can either mean that the subject is the one getting married or that they are performing the ceremony.

> it's unbelievable how many people are leaving.

Where have you been? Yahoo! has been in limbo for half a decade, there has been a constant brain drain for all that time. The only engineers still working at Yahoo! are probably there because they can't find a job somewhere else.

I wonder why Crockford stayed there for so long, to be honest.

> Hey, I'm the author of the article and I don't really have an agenda in the Android/iOS platform debate.

Either you are being dishonest about this claim or you are simply a bad reporter who wasn't able to convey her intention in her writing.

Your article is clearly biased against Android, whether you meant it this way or not.

This is nonsense.

Yes, fragmentations make it a bit harder on developers, but that's why we get paid the big bucks.

Choice is good for users, you won't hear a lot of Android users complain about fragmentation.

Here are a few more pull request tricks:

http://beust.com/weblog/2010/09/15/a-quick-guide-to-pull-req...

> I believe in civility and courtesy in many areas, and Linus doesn't phrase things exactly as I would.

And a few messages down, he proceeds to say "You are a moron".

Not exactly a role model of civility.