EvenThisAcronym

One thing that I think doesn't come up very often when discussing BI is the fact that many other laws will have to dramatically change to make the experiment successful. Just imagine the enormous increase in things like contribution to open source, creation of art and culture, etc. I don't believe that the current environment of hyper-strict IP and patent laws can continue if BI were to be implemented, as many more people would use their increased leisure time to create. Today we can already see conflicts between big IP companies and individual creators, and if BI is introduced it will get much worse.

People on HN refer to it as an "intellectual community". That should be you all the answer you need.

I feel like internet news sites and comments sections have become bizarre parodies of themselves.

The null coalescing operator is nice, but it can be overused. I recently saw some Swift code that was riddled with question marks everywhere, which()?.made?.the?.code?()?.very?.difficult?.to?().read.

> Henry Ford introduced the 40-hour work week in 1914 because he saw — through research — that workers on five eight-hour shifts kept up the highest sustained levels of productivity.

Why does this ridiculous meme keep popping up? The 40 hour work week was a long and hard-fought battle, full of blood, tears and sweat. It was an uphill slog against the most powerful corporations in the world; lavour unions fighting tooth and nail for every minute of time away from work. It wasn't some flight of fancy by Henry Ford because it made his workers more productive, or so they had more time to buy stuff, or whatever other pieces of false history have been dreamt up.

From the very first line of the article:

>Over the course of the past few months I’ve been using Go to implement a proof of concept program in my spare time.

It's almost as if, like most people who post on Hacker News, you took a cursory look at the title, wrote some inane comment that supported your point, and squeezed out a reply.

The Higgs VM is part of Maxime Chevalier's PhD work.You can find her blog here: http://pointersgonewild.wordpress.com/category/higgs/.

Popular culture and the mainstream media, as both tend to do, have turned trolling into a meaningless word, and now nobody actually knows what trolling is anymore. Taunting someone whose father has died, however, is definitely not trolling.

I'd say that the series as a whole is just ok. I did enjoy both books, but they didn't stick out in my mind as amazing.

>there isn't enough there to the spittle-flecked, cheeto-dusting link...

Why, exactly, did you use this particular choice of words?

That doesn't make any sense. "Some people said before that Gamergate was about harassing women, I guess this woman must've been harassed by Gamergate as well, although there is no proof, and Gamergate supporters decried the threat and reported it, which is all they could do."

An entire article about the rise to popularity of bacon and not a single mention of the Atkins Diet or Epic Meal Time.

I'm a member of that generation myself, and I agree with a lot of his points. My generation is one that can't take criticism, and requires constant positive reinforcement. Any negative opinion is dismissed as "trolling" or being a "hater". His claims are not contrary to the truth in the slightest, they're descriptive of a failed generation.

Are there any plans to add named arguments a la C# or Python in the future?

I think you've been using a different C++ than I have, then. Numerous implicit (read: invisible and unexpected) conversion in C++ account for a large swathe of bugs. Sure, it's deterministic as to which function is called, but throwing a die is deterministic as well, as long as you know about every variable that affects the roll.

His advice on the use of auto seems perfectly sane to me. The first time I learned about a language with type inference for local variables was D, and coming from C++/Java, I had the same reaction. I absolutely hated it. However, the D community seems to overwhelmingly prefer auto/const/immutable/etc. (any of these can be used in place of an explicit type declaration in D), and over the years as I've worked with other languages that have adopted this convention, I find that I now cannot stand any unnecessary explicit type declarations in my code.

Nearly 100% of the time, you know what the type of a local variable is (otherwise people would be unable to use Python/Ruby/Javascript/etc.), so it's no great harm to readability. Furthermore, you are probably already working with an IDE that can tell you the type of a variable when you hover over it, anyway. I think that it also leads you to think more about interfaces than specific types.

Minecraft was started as a clone of Infiniminer.

Neat, I bet you could prove just about any point by fabricating a fictional character and attacking their constructed ideas. I'll have to give it a try sometime.

That @auto_closure annotation seems to work exactly like D's `lazy` keyword, transparently wrapping the passed-in value in a closure. Pretty cool that more languages are getting built-in support for laziness.

    def compare(a: Int, b: Int): Int

    This one has not only 232 possible results, but an incalculable (232)264 possible implementations. Even if we are generous and only allow the inputs to be 0 or 1, we still have 2128 implementations. If the only meaningful return values are -1, 0 and 1, indicating “less than”, “equal” or “greater than”, then why would we embed them like specks of dust in a big desert of undefined behaviour?

I don't agree with this. This is not a "big desert of undefined behaviour". The behaviour is defined along the entire spectrum of Integer values. "Less than" maps to all values <= -1, "equal" maps to 0, and "greater than" maps to all values >= 1. There's no undefined behaviour here.

> He will manage, no doubt. He will not die poor. Maybe not a billionaire, but no one’s entitled to that. What’s with all the unending sympathy for rich people in public positions with lots of power making stupid mistakes and having to face the consequences for those?

Because he was judged in the court of public opinion. You may point and say "What this man did was obviously wrong! He deserves everything he gets!" And then someday, maybe you make one small, innocuous mistake. One off-the-cuff comment taken out of context. And the internet lynch mob will come for you.

(Please understand that I'm not saying what he did was said out of context or could be misinterpreted. It was pretty obviously a dumb thing to do. People have been "executed" in the court of public opinion for infinitesimally smaller gaffes, and it is this we must work to stop.)

Is there a reference anywhere for the utility stuff that comes with Vibe.d, or are we expected to read the source on Github?

On the bright side, if Node.js is adopted for "enterprise programming", all the hipsters that write blog posts about how great Node.js will abandon it overnight.

Only someone who hasn't played Minecraft would be surprised at this. Altering the scenery is half the fun of the game, anyway (the other half is building cool stuff).

Expose? This is something we all know. It's no secret.

>Even so, we work in a world where inequality exists by default and we have to overcome that. Bullying, intimidation, and harassment, whether illegal or not, are absolutely unacceptable at GitHub and should not be tolerated anywhere. GitHub is committed to building a safe environment for female employees and all women in our community... I'm sorry to everyone we let down, including Julie. I realize this post doesn't fix or undo anything that happened. We're doing everything in our power to prevent it from happening again.

Why the apology on Github's part after it was concluded that there was no gender-based harassment towards the engineer in question? Is this apology pertaining to the other issues?

The number of times you'll wish you had a generic red-black tree or linked list in your life: many, many times.

The number of times you'll need a generic map or fold algorithm to operate on those structures: many, many times.

>Does Andrei have a sticky D button on his keyboard?

Well, it is written in D. Walter (not Andrei) is talking about how he leveraged D's features to his advantage when writing Warp.

The stuff you can do at compile-time in D is just mind-boggling. Lisp and C++ are the only languages that really compare.