weareconvo

Or just "heavy flagging"... it's a little ridiculous to claim that everyone who hates Microsoft is a Google fan. Microsoft did enough to earn my eternal contempt before Google even existed.

You are most definitely the only one. And judging from your comment history, you also like Windows 8, so rest assured that your opinions are far, far outside the mainstream.

True, but in this case, they were, because she was blowing something up... not conducting a science experiment. Which was the point of his post.

Okay, as much as I hate syntactic sugar... that's pretty freakin awesome.

List comprehensions as a programming technique are incredibly useful, don't get me wrong. I am just not a fan of syntactic sugar in general.

EDIT: On a more elaborate note, I think that the extreme variety of programming styles enabled by Haskell is more of a weakness than a strength. True, defining your own abstractions and operators is part of the fun, but seeing declarative style (pattern-matching in function defs, where blocks, function args on left-hand side, guards), expression style (let blocks, lambda abstractions, case statements, if clauses), applicative style (<$>, <* >, <$, <* , * >, <|>), and arrow style (* * * , &&&, ^>>, ^<<, >>^, <<^, <+>, +++, |||, >>>, <<<) all in the same file can get pretty overwhelming even if you're already pretty fluent in the language.

We don't need any help being confusing, people. We already have Monads, for god's sake.

Haskell person here... I personally find Haskell list comprehensions to be ridiculously ugly, and are an unnecessary bit of syntactic sugar over the List Monad.

No, but I would like to hastily assure you that it is solely because I am a coward when it comes to NDA issues.

Absolutely the best questions to ask in interviews, in my opinion, are open-ended questions. The problem with those, however, is that the interviewer himself has to know enough to be able to correctly judge whether the candidate's answer is a reasonable one.

Not only that, there are fewer language barriers when asking some canned binary tree bullshit. So a Chinese programmer doing an interview who barely speaks English can still proudly ask the candidate some crap about Heapsort and feel like he's done his job well.

Did interviews for 5+ years at Google... the real problem is that there's no uniformity to the hiring process. I was allowed to just make up my own questions and judge candidates based on those. And I did so. And admittedly, the questions I asked were so difficult that I seriously doubt I myself could've answered them when I first got hired.

But I didn't give a crap, because hiring is something you're kind of coerced into doing (it's not technically required, but not doing interviews looks bad at promotion time). And I hated doing interviews with a passion, so I'd just give them one impossibly hard question, which is easier than asking a bunch of questions.

Maybe they feel that if they sue enough people, they'll earn enough money to stay afloat for another year.

What's the full story? Why was he detained? Is he actually a terrorist? There can't possibly be absolutely no other side to this story.

Maybe they really hate exercise.

That's a good point, though protocol buffers aren't used for everything. There's more tightly-bound systems stuff going on, plus libraries and so forth. Which is to say, I have no idea.

In addition to the difficulty of rewriting existing code, even when you program something new at Google, you'd be a fool not to leverage what infrastructure already exists. If you try to do that while at the same time writing the new project in Go, you run into weird interoperability issues.

> Do you work at Google?

I did for over 5 years. While I left before the Go programming language was released, I seriously doubt they've transitioned much of the codebase to it, for one simple reason:

The Google codebase is fucking massive. I simply cannot describe how unbelievably huge it is, and while I don't doubt for a second that Go will be used for some of the systems-level projects (some of which Rob Pike is directly involved with - how's that for vague), you simply don't transition that big of a codebase to a new language.

It would basically be impossible... unless you're Jeff Dean.

Go is not some side-project started by a mid-level engineer. This is Rob Pike and Ken Thompson we're talking about. They're demi-gods, even at Google.

Maybe some bitcoins being shuffled around in the exchange?

You guys nailed it - Mitch's joke was indeed what I was thinking of when I wrote the comment.

Quite a few of the transactions on bitcoinity are actually cached mtgox pages pulled from cloudflare, which accounts for the fake $180 fluctuations.

I mean... where else is the data going to come from? The future?

I didn't mean legally, I meant morally. Don't her complaints about having her work co-opted by Disney when that work co-opted Alice wholesale ring a little false to anybody else?

And didn't she, in turn, steal the idea of Alice from Lewis Carroll?

Maybe they were buying a news story.

> Kobo says American startups like to develop products without the "impure" influence of monetization, "but [in China] the development of a good product isn’t even thought of in the beginning," he says. "Chinese web companies have a totally nonchalant attitude towards creating the actual products. They are just a lot more focused on ways to make money from the outset.”

...because they know that, due to their country's non-existent respect for intellectual property, they can just rip off the product itself from something created in America.

I can't even count the number of times I've attempted to block every variant of "w3schools".

Right, but the great thing about a compiled language like Dart is that it can detect at compile-time which modules aren't being used and then exclude those from the js output. Except, it doesn't seem to ever do that.

EDIT: Well, technically, Dart is actually designed to be interpreted (or JIT compiled, or what have you) by the Dart VM, so calling it a "compiled language" was incorrect on my part. However, dart2js is a compiler, so, it should be doing compiler-y shit.

Okay, but um, why did minify not get rid of the module i wasn't even using?

> You don't say if you used the 'dart2js --minify' setting

I did. I'm no stranger to Closure Compiler, and even after fiddling around with ADVANCED_OPTIMIZATIONS for an hour, those ridiculous $variables persisted. What was even weirder was, just as a test, I imported a module I wasn't even using at all, and for some reason, Closure Compiler still refused to remove its code...

Yesterday, I rewrote one of my JS modules into Dart, and it ended up being about 10 lines of code with only two modules imported. Then I compiled it to JS, and it was over 120k. I tried for about an hour to get that down to a reasonable size with Closure Compiler/Uglify, but the names were too wonky.

I'm sure that, given enough time, they'll solve these problems, but as for right now... it isn't ready for primetime. Not by a longshot.

You mean to tell me that even in the Functional Programming world, there are still tradeoffs between memory and performance to consider?