skysight-inc/HackerNews huggingface dataset:
I wouldn't put it quite so strongly, but yes; go makes design decisions that are addressing non-obvious problems that the designers encountered over several years of software development in other languages.

Consider the block against unused imports. Now consider an application made of hundreds of .go files, that relies on hundreds of libraries, each of which could itself be made of hundreds of .go files---all of which changes frequently enough that a total recompile may be necessary often (which might sound like a code-base you can imagine Mr. Pike would be familiar with). It's actually a non-trivial amount of work to churn through and ignore all the unneeded imports.

"But that's sacrificing developer prototyping velocity to solve a problem that most developers never see; at most, it should be a feature toggled by a compiler flag", one might argue. Well, sure... Now consider how many C / C++ libraries cannot be compiled with -Wall -Werror because the original developer had the option of building the library without those flags enabled and not enough people want to learn all the subtle details of the languages they use, they just want "the code to compile and be done with it." Now consider what that does to the problem of trying to build larger projects from these tiny pieces that were never actually sanitized for unneeded imports... Which will inevitably happen to code that works well enough, etc.

It's a line drawn in the sand, but it's a line drawn in the sand from hard-won experience with how little projects grow into big projects.

Besides, the language is so small that it's not very hard to write wrappers for IDEs that can quickly identify and kill unused imports automatically (probably also add them when needed, like the most common "oh GOD I need to put 'fmt' back in just because I'm pen-testing the outputs in this code I'm debugging").
> It's hard for a lot of people on here to imagine dealing with 100k+ other coworkers but at a point you oftentimes have to abstract away what makes people human to work in most large corporations.

Working myself for a company of 150K+ employees, I can confirm this is totally true.

I hate a lot of high-level business speak like "resources", but what I've come to realize is that one cannot think of 150K people as individuals. It's too much for the human mind. If you see this as an indictment of large corporations, I wouldn't blame you. Just realize it's a reality of operating inside them.
Yes, the semantics of ":=" for the multiple-variable case are just weird. You can create one variable and assign another, and it's invisible what's happening. Not too good.

Variable shadowing is probably a misfeature anyway. If shadowing were an error, sometimes you'd have to change a local variable name. No big deal. An amusing alternative would be to require that any name imported into a block must be at least 3 or 4 characters long. You don't want short global variable names anyway; if "x" is a global variable, something is wrong. Then short local variable names could never clash.
I wish the author would have taken a little more time to polish this and be a little more respectful.
"Its amazing NASA got away with this crap for so long."

This is unfair. The popular article we're talking about is trying to dramatize a milestone, but it does not say that his retirement threatens the spacecraft. It's being managed by training someone new. When you retire after many years of service, people will make laudatory comments, say you will be hard to replace (which will be true), and then move on.

Incidentally, I believe he's not fully retired, because he's still listed in the employee directory here. Maybe it's set for the current work week, which for him, ends Friday.
Getting rid of the driver doesn't get rid of physics. You can't make the car taller or wider or heavier without impacting fuel economy and stability. You can't get rid of intermittent stops for cross-traffic and pedestrian crossings. And you will never be able to match the smoothness of a heavy rail vehicle with a lightweight road vehicle.
Anecdotally, there are cartels of authors that fail to be sufficiently critical in the literature. This is undisputed. However, quite a large (sometime overwhelming) amount of criticism and scientific conflict operates in the daily practice and presentation of science that occurs outside the formal literature. Within the primary literature, variation in results or technical questions about methods are often not cited in a manner that is overtly "negative" from the perspective of a field outsider, but those in the field will understand and recognize the conflicts. These inconsistencies or disagreements in results are most often made explicit in review articles. A broad analysis of this sort is unlikely to grasp these kinds of subtleties in scientific practice.
The behaviour you are talking about isn't anything to do with :=. It's just how scoping works in Go. := is just syntactic sugar.

http://play.golang.org/p/bh6pm_8s9S
Oh. That's unfortunate. Do you have a better article than this one? I'd like more info on this, and this article is lacking a little.
Want to buy an elephant whistle?
yea, the Sense browser plugin has made my life a lot easier, but i agree that a relatively sophisticated query/filter + aggregation can be quite a load
> don't call Go or any other popular language "poorly designed" with a short blog post. Instead, say "it doesn't fit my current needs."

that's not what the author wanted to say though. very, very often someone says "this is bad" when they actually mean "this doesn't fit me". in this scenario, I think the author made a very good case for "it's poorly designed".
Assuming a .onion's key were to be bruteforced or stolen however, you would also need to steal the SSL private key in order to continue to appear authentic.

I'm not saying Tor doesn't cover authenticity, but that SSL provides an additional authenticity check on top of that.

edit: On the topic of bruteforcing, the linked Stack Overflow post leads me to believe it's not terribly infeasible.

Additionally, stealing the .onion's key would likely expose the SSL private key as well (as you'd likely have access to the server at that point), unless the .onion's key is exposed due to misconfiguration or another form of human error.

I also think, lastly, that the point about the browser understanding its dealing with a secure connection and enforcing general browser SSL rules has merit.

edit 2: Forgot the link - https://security.stackexchange.com/questions/29772/how-do-yo...
Ceylon also has excellent Java/JVM (and JavaScript) interop. You should try it :)
Sometimes all you need is 3 cards and your phone
Meh.

1. How often do you insert into a slice? You know that's a O(n) operation, right?

2. nil is typed, I'll grant that it's not the most obvious part of Go's type system.

3. Meh.

4. This is type covariance. It's complicated and hard to get right. The Java Generics FAQ looks like this: http://www.angelikalanger.com/GenericsFAQ/JavaGenericsFAQ.ht...

5. I like by-value loops. Everything else in Go is by-value.

6. Yeah, fuck everything we know about parsing, let's make whitespace significant, then we can declare slices like:

x := []int{
1
-2
+3
}
len(x) == 3
y := []int{1 -2 +3}
len(y) == 1

7. Meh
> The writer of that article and the pseudo-science "doctor" can go eat a dick.

Please don't.
I often prefer to use lambdas as (named) inline function definitions:

auto lessGold = [](const Hero& h1, const Hero& h2)
{
return h1.inventory().gold() < h2.inventory().gold();
};

std::sort(heroes.begin(), heroes.end(), lessGold);
Tonight by midnight pt
Fixing Bugs Driven by Tests in Swift
If we actually do break down barriers and correct our gender biases as a society, what is to stop us from continuing this "special treatment" at the expense of men? When do we say "mission accomplished"?

Case in point: "Black History Month" wasn't supposed to be permanent. We still celebrate it though, as if black history were distinctly different from American history. It started off with good intentions, but it continues to this day as an unnecessarily divisive holiday. How much "black history" is ignored 11 months out of the year just so we can celebrate it in February (the shortest month of the year)?

Sexual discrimination is sexual discrimination, regardless of context.
Whether or not it's constructed from protein is irrelevant to whether or not it can be eaten. There are many proteins that can be eaten but are not (or poorly) digestible or convey no meaningful nutritious benefit. And for that matter, one can "eat" anything.

The germane question here is "does this have nutritional value"?; the answer is almost certainly "no".
This is more interesting as a list of "what is Zuckerberg reading", than a list of things anyone should care about reading.

His reading and takeaway of Orwell's Revenge, for example, is astounding in the context of Facebook. You really start to wonder how self-aware old Zuck really is. Or isn't.
> I've marked ~80% of emails reaching my inbox from Mailchimp as spam because they were sent without my permission.

I think the status quo has grown to tolerate unsolicited email and accept that their inbox isn't the same property as their physical mailbox.

edit: Oh! Much like your physical mailbox, unless you host your own email, your inbox isn't your property either ;-).
Ceylon has an IntelliJ plugin in the works that builds on the solid foundation of the Eclipse plugin, so it's picking up features really fast. It should be out in a few months.
I love Python, up until I remember that I can't make any guarantees of program correctness until I have 100% coverage tests on every line of code because the language is so flexible that it can't tell if a random identifier refers to a variable name that might exist at runtime (but is not determinable to exist at compile time), and therefore most of my variable-name typos that would be compile-time errors in another language are runtime errors in Python.

So great for prototyping, not so great for large projects and maintenance (as I've just put the floor of my unit test cost around a factor-of-2 more code).
To be honest most of Homebrew stuff is "bottled" IE its pre-builts most of the time you no longer have to actually build it from source... So its not even really a difference any more!
Natural processes can include earthquakes, volcanoes, viruses. Its often random. Plenty of reason to think these species have something to offer in the present day.

I think of it like publishing an old book, or seeing an old movie. It is being a good steward of a legacy in a sense.
The simplest to use is HTML/CSS. This video might just help you :) https://www.livecoding.tv/video/beginning-a-site-htmlcss/
It isn't my opinion.

http://www.npr.org/sections/money/2013/02/19/172402376/why-b...

http://www.americanbar.org/publications/franchise_lawyer/201...

What bugs the hell out of me is that on HN - rather like on reddit - there are often comments that make lipservice to an abstract concept of quasi-erudite fairness, saying "well if we don't have all the facts, how can we judge!?" well, two responses:

1. You are literally already on the internet. Use google for like, 30 seconds.
2. Oftentimes, those facts are actually in the underlying link.

In this case, it is self evidently true that the laws that were passed to prop up car dealerships came about in an era without mass marketing, but, very importantly, and self-acknowledgledly, these laws existed to prevent the manufacturer from undercutting prices offered by dealers - under the theory that dealers were of critical importance to customers for servicing and selling cars. Which is a combination of circular and dumb. And even if it was once true, because people could not comparison shop without the internet, it is now no longer true, because people can comparison shop with the internet and can visit manufacturers directly for servicing.

These laws are literally anti-competitive monopolies that, if they never existed, would not need to be invented now to protect consumers. Instead they operate as enforceable licenses, dividing the country up into fiefdoms, in which each little fiefdom the local car dealer is the ensconced baron, operating with a monopoly on all original cars sales from that manufacturer in that territory - and if another dealer tries to sell new cars from that manufacturer in that territory, they can be stopped by the state and sued out of existence.

That, dotcomrade, is a load of bullshit. And easily discoverable with a 30-90 second google search.
> any example using a lambda in C++ I find to be 10,000× worse than the functional equivalent.

> I naïvely assumed that the keyword `lambda' was involved.

I don't understand how this two sentences co-exist. If you are unfamiliar with the syntax, surely you can't have a well informed opinion on which usage, in practice, turns out better?

I am assuming "functional equivalent" means the old named functors of C++03. And yea, you are likely super alone on that opinion. I normally say lambdas in C++11 mostly-obsolete (at least as the default) a huge class of the old ways from functors to bind/placeholders and friends. I don't think I've ever heard someone pining for the ol' days on this one.
Funny how this reminded me of the recent discussion about facebook reactions: https://news.ycombinator.com/item?id=10355556 (with a difference that in this context people would seem to need, not wanting though, a dislike button).

Maybe a system providing private dislike function would yield a balanced solution?
Many of the issues here--for example, the set of built-in slice primitives being inadequate--have ready solutions in other statically typed languages (in this case, generics). These are not problems fundamental to static typing.

(For the record, I disagree with some of the criticisms here, for example the slice-of-interfaces type coercion criticism.)
Right, a waiter could do all sorts of things to contaminate food but doesn't require licensing. Regulations and investigation are sufficient. The same could easily been done for barber shops. Enforcement can also be done via torts. Insurance also requires certain base level of employee training. There are many ways to try and prevent and remediate problems other than requiring a license.
I think part of the challenge is actually showing damage after an information breach. It can be difficult to connect a particular breach to a particular harm: the harms are often hidden until much later, at which point the same data may have been contained in several more hacks.

We need an avenue of recourse that doesn't rely on showing actual damages if we want to address the current market failure.
Probably not. Your hair and nails are made of protein and they're not very digestible.
Also https://news.ycombinator.com/item?id=10466518 and https://news.ycombinator.com/item?id=10466507.
There seems to be something being missed in this thread with the back and forth of effective tutorial screens:

What if we created UX that didn't require explicit hand-holding?

I'm sounding snarky I'm sure, and maybe that's because this is kind of a snarky comment, but as someone who makes mobile apps for a living it's a position that is surprisingly infrequently considered.

Yes, I know it will look really cool, but do you really need to break platform conventions (that users have already spent a lot of time learning) just for your one thing?

Maybe instead of pointing an arrow at a hamburger button and telling the user what's under that button, we should consider something less insanely vague and useless as the hamburger button?

Having built a pretty large number of apps so far, my position right now is: if you find yourself building a tutorial screen/mechanism, you have already failed, and the only good you're doing for your UX now is controlling the degree of failure between "mild" and "utter".

My experience with tutorial screens - not just on the implementation and UX side, but also where they seem to come up during the product development process - suggests that they are at least a bit cargo-cult-y. People suggest them because other apps have them and it's at least a superficially sensible thing to do.

A lot of projects start with the fundamental premise that tutorial screens will be necessary, and when these projects inevitably run into conversion/completion barriers because of the tutorial screens, attempts to mitigate rarely involve completely removing the screens. It's as if the presence of tutorial screens is fundamentally non-negotiable.
I have no problems using Weather.com. I just type in the url, they've got my locations of interest up at the top, I click on one, get a quick forecast and can drill down into different segments like "The Weekend" "10-Day Forecast" and easily get the "Map-In-Motion" doppler.

Any extraneous stuff I notice but filter out automatically. I love the site and don't have any of the sort of issues you've described. I do seem to have a higher tolerance for the minor inconveniences of life when I compare my experience to those of the people who surround me, so maybe I'm just lucky. I think you can develop this attitude though, and it sounds like it would help ease your way through the world.
Nifty new workstation lets you lie down on the job
But this isn't the same thing. The GA is general availability and not a release candidate. The OP link has more relevant data.
I've been enjoying Edward Snowden's comments about this on Twitter. One great retweet by him from @droosien:

"Runaway surveillance blimp" is the perfect metaphor for the military/intelligence industrial complex. And the perfect mascot.
am i the only one thats nervous or what?
The species for which revival is technologically plausible are those with well-preserved frozen specimens, mainly pleistocene (mega)fauna like mammoths and the lions presented here. They lived at most a few tens of thousands of years ago, which is geologically barely worth mentioning, and the atmospheric composition hasn't changed much since then, or not in ways relevant to animals.
What does it mean to "break 2 primes"? Is there some prime number that's calculated secretly but somehow unknown?
There are also RSS feeds one can collect.
Because the people in charge of the program at the CIA were fans of abstract expressionism.

To put it another way, they were using tax dollars in a very weird way to subsidize the kind of art they liked.
Yeah, exactly! The saddest part of all this beautiful discovery and imagery is that we are about to be thirsty for more, and there are hardly any new robots in the pipeline. So sad.
See the original article: https://freedom-to-tinker.com/blog/haldermanheninger/how-is-...
https://twitter.com/bcrypt/status/659448608362663937

I find bcrypt's response and selection in hashtag (#BlimpinAintEasy) is the most appropriate.
Aren't bruteforces of .onion plausible in the mid-future by powerful actors?
It's Ember.js on the front end talking to an Algolia API. It's all proxied via CloudFlare, so very few requests hit our server (at Heroku)
Sales Tax/VAT is probably the bigger reason, though.
If you're making the decision just for the sake of Swift Programming. Don't. Not a great idea to spend a lot to shift to Mac for that reason alone. That being said, there are lots of other reasons why Mac works great.

I was a PC User for as long as I can remember. I used windows since Windows 95 and all the way up till Windows 7. I got a chance to buy a MacBook Bro when I joined college. And then it suddenly flashed how I wasted all my childhood with windows. Linux at least would've been better. The reason I say this similar to that of other people who made the transition.

The whole OSX ecosystem is very user friendly. The learning curve is shallow and once you get used to a Mac, you'll really start questioning how you did things on your PC before.

I'm both a designer and a developer. And my Mac gives me the best of both worlds. I can both develop freely with no worries on my mac with no terminal or bash problems(unlike the command prompt). Also, all the designer tools run very smooth on a Mac. There's a reason why all professional artists use Mac.

The popular saying goes "Once you go Mac, You never go back". You really don't.

The decision might seem hard with so much to cost on a product. One thing I can assure is that it's worth it.
You can take the leap.:)

P.S. There are some shortcomings with the latest OSX releases, but I think Apple will fix all of them eventually making for a better user experience.
Well, we can be sure folks will bring it up again. Nobody is ignoring this issue, especially on internet comment sites. But for now, the status quo is unacceptable and special treatment is called for. Doing nothing is tantamount to acceptance of the unfair situation.

Here's an idea: lets reverse things for now. You lose your job, along with most other men, and women are put in their place. That's millions of people changing jobs. How long before men start complaining? How long before 'special treatment' begins to look good to them?
Ubisoft's largest development studio is in Montreal, Canada... but their headquarters is in Montreuil, France.[1]

So it's fair to say Ubisoft's products are French (from France, not the language) products.

---

[1] https://en.wikipedia.org/wiki/Ubisoft
Well, that's in the Confirmed Hoaxes section of that page. :)

The N1 rocket (USSR's workhorse for their Lunar space program in the '60s) never worked well. Chief Engineer Korolev (the Russian counterpart to Wernher von Braun) dying in the mid-60s certainly didn't help. The project suffered from "financial malnutrition" for a long time, due to political infighting within the top levels of the Communist Party.

The N1 test launches were all rushed, improvised affairs that failed, sometimes spectacularly. https://en.wikipedia.org/wiki/Largest_artificial_non-nuclear...

The way the project operated was, basically, "we don't have enough money to run horizontal burn tests properly, so we'll do it live, with a full-scale vertical launch". The results were what you would expect.

Main point is, the Russians didn't have a properly working vehicle in the '60s to reach Moon orbit. They were starting to figure out the issues with the N1 towards the end of the decade, but then Armstrong set foot on Luna and the rest is history. The N1 was cancelled quietly in the mid-70s.
Genetics as a Social Network – A Data Scientist's Perspective
Gizmodo article is actually decent: "While helium doesn’t appear to be a problem at the moment, deflation is. ABC27 reports: “Authorities said it is equipped with a device to slowly deflate it, but it apparently is not working.” Whoops. If you see the free-floating balloon on the loose, call 911. Do not attempt to engage."

http://gizmodo.com/theres-a-runaway-defense-department-blimp...
That's what my 'mostly' meant. You can simply pay a 12 month fee and buy it 'in advance' and just use what you get, vs thinking about it as "I'm losing bug fixes". I'm still using PHPStorm 7.1 from a couple years ago, and it still works. Same concept would apply going forward, but... I still think they handled this wrong.