skysight-inc/HackerNews huggingface dataset:
> Driving at roughly the same speed as the rest of traffic is definitely much safer than driving the posted speed limit.

Absolutely. I went into some details here:
https://news.ycombinator.com/item?id=15495904
How much is this because of Haskell's build times in particular? Is there a sort of "target build time" that would make you more comfortable with this stuff
> Python, Node and Ruby all have better systems for package management

Maybe they have better tools for managing package dependencies but Go doesn't have to deal with interpreter dependencies, which can be a major headache. Go also doesn't have the problem of conflicting system level packages.

Honestly no matter how good your deployment practices are, if you have to manage an application's deployment long term you're going to have dependency problems of some kind. I'd rather deal with those problems at compile time than hit an edge case during deploy or in prod.
People talking about Stoicism remind me of the end bit of Equilibrium.
Strange. I've found my education has been highly relevant over the last 20 years.
Except Dropbox's Smart Sync has been available for a year already.
I'm willing to wager that this number has dropped in the six years since the article has been written.
That's that hotkey for forwarding an e-mail in MS Outlook, right?
It's kind of rational to do so. I mean, individuals cannot realistically compete with governments who want to oppress them unless they're monumentally stubborn and self-sacrificing, but the various benefits of sharing information on social media has measurable upsides for thema s consumers - they get to meet friends, receive advertising on topics of genuine interest, and so on, which may outweigh the relatively low probability of direct repression.

There's a parallel phenomenon in political behavior that's ably explained in Brian Caplan's The Myth of the Rational Voter.

You could practice really rigorous security culture and avoid creating any digital footprint worth talking about in the first place, but then you'd be socially isolated to a degree that was economically disadvantageous (economically meaning in multiple contexts besides purely fiscal). And to the degree that you can be socially connected, inferences could still be made about you through the behavior of your friends.

As a crude example, recall that Osama bin Laden's hiding place was determined to be interesting because there was physical traffic of people and goods to the residence, but an uncharacteristic lack of electronic communication for the neighborhood it was situated in. What kind of house has a bunch of people living there and regular visitors, but not internet or phone service?

Finally, people have different kinds of risk calculus. Many people know that they're subject to such surveillance and the ramifications that follow from it, but choose to be who they are anyway despite the risks, on the theory that they'd rather live on their feet than die on their knees.
The root of the issue here is that URLs are trying to be human-meaningful and machine-meaningful at the same time, but those requirements are fundamentally incompatible.

Humans work well with ambiguity and context. You know that when your coworker says "Bob's birthday is this weekend" you know she means her husband Bob, not Bob from accounting who nobody likes. And you even prefer that system to having an unambiguous human identifier, even a friendly one like "Bob-4592-daring-weasel-horseradish".

Machines, on the other hand, hate ambiguity and context. Every bit of context is an extra bit of state that has to be stored somewhere, and now all your results are actually statistical guesses - how inelegant!

In the early days of computing, there was no separation between the internals of the machine and its interface. If you worked on a computer, you were as much the mechanic as the driver. We got used to usernames, filenames, and hostnames because they were a decent compromise; they were meaningful enough to humans, and unambiguous enough for machines, so we could use them as a kind of human-computer pidgin.

But we don't need them anymore, and they were never really very good at either job anyway. Google's (probably accidental) discovery was that we were using the web wrong. Everyone was building web directories and portals because they thought that URLs weren't discoverable, but the real problem was that they weren't usable. Search was the first human interface to the web.

So Google's going to kill the URL, Facebook's going to kill the username, and someone (apparently not Microsoft) is going to kill the filename. There'll be much wailing and gnashing of teeth from the old guard while it happens, but someday our grandchildren will grow up never having to memorise an arbitrary sequence of characters for a computer, and I think that's a future to look forward to.
OTOH, if the prima facie limit were followed consistently (or enforced effectively), people would not be exceeding it, and speeds would be more tightly clustered and safer.
Re: Because I can't learn any other language
Not everyone can teach well. I've also found that folks who have never had a good teacher in a particular topic don't realize how much disparity there can be.
As gardnr says, you need to solve this problem by involving the clients. Trying to fix this without some DNS fiddling is going to waste your time and you'll have nothing to show for it.

The world changes, and adaptation requires maintenance. 10 years ago is almost half the age of the web ago. This is more a business decision - do you let those accounts rot - than it is a technical decision. Because the business decision needs to include support time for user interaction.
That is literally the point I am making. You are misunderstanding me completely.

No matter how unlikely an extreme event might be, if/when it does occur it has earth shattering effects due to the complexity of the world. This is why we need to be so vigilant in protecting ourselves against these threats.

I finished with "But September 11th came along and changed the West and Middle East for decades." That is the point. 9/11 was tragic enough, but it triggered an avalanche of death and trillions of dollars spent. These sort of attacks have non-linear effects that cannot be predicted.

You originally stated you are more likely to die falling down the stairs therefore "Bomb attacks are not something you should be concerned by." My response is that terror attacks are like what we see in 9/11. Considering that event resulted in hundreds of millions of death due to the complexities of the world AND the risk distribution and magnitude is completely incomparable to known risks and their distributions, it is nonsense to dismiss the risks as you are more likely to die falling down the stairs.
Twitter was not made for blog posts.
Did you just read 'What Happened'?
So Perl was built because Sed/Awk had "whipupitude", but fell short of being a real application language like C which was great and fast to run, but slow to develop in. Perl was the middle ground which took the power of Sed/Awk/Bash and made it faster and more respectable and added a huge module repository. Of course take this with a grain of salt.
I think by the standards of history, that letter would be deemed kind.

Keep in mind that often times wives were essentially viewed as property, and subject to extreme (physical) abuse.

And of course that hasn't stopped.

I'm not supporting that behavior, of course.
i agree it's not scummy but it's far from nice...see Chicago
Python was my entry into the programming world, and I've been an evangelist ever since... Or I was until I ran into distribution and parallelism. Since then, Nim has been my go-to language of choice. It is all that Python was, plus unbelievable speed, compiling to shippable binaries, and some other cool language features that admittedly, are still beyond my scope of abilities. Still quite lacking in libraries compared to Python, but after a few attempts (perhaps halfhearted), I never felt "Go" was a suitable replacement.
That entirely depends on who you ask.

If classes and inheritance aren't a form of OOP, then what are they?

Also, Smalltalk had classes and inheritance, whatever Alan Kay had to say on the matter.
301 may be dangerous, because browsers cache them.

Suppose the client follows a link to old-slug after the slug has been changed to new-slug. The server responds 301 → new-slug. The client caches that redirect, so that if you request old-slug it will immediately take you to new-slug without querying the server.

Then the object’s slug is changed back to old-slug (perhaps the change was made in error). Now a request to new-slug produces a 301 → old-slug. This likewise is cached, and a client may new be stuck in an infinite redirect loop.

I’m not sure if this is actually what browsers do; they might detect the loop and decide to throw away their cached redirects. I haven’t tested it; but I wouldn’t count on it.
Male mosquitoes feed on flower nectar and don't bite so I'm not sure why you would think residents would be annoyed at the "Google mosquitos" unless they like to spread nectar on themselves.
Thinking Like a Mountain: On Nature Writing
For me the part that I'm saying nix-env -i rather than editing a config file and nix-whatever --read-the-config-file-again isn't really a big deal. It's just a cute tool to author and maintain user environments, I'm sure I could, like, define a single package that just depends on and exposes all the packages I actually want installed and call that my declarative user environment but I'm not sure what that's actually gaining me.

Declarative or not, I'm still gonna get the advertised benefits of Nix like, say, having some confidence that I got all the dependencies specified properly if my stuff builds, easily customizing packages by overriding specific bits, and coping with arbitrary version requirements really easily.

I'm sure someone who's more used to configuring homebrew has a different perspective there, but it definitely seems preferable to taking over /usr/local and rotating things in and out of there as I switch between projects or w/e.
No, it still wouldn't be if he were. This is just about being dismayed by revelations about people whose fans used to look up to them.
>Reason 3 – Developer Productivity & Not Getting Too Creative

There is a time and place for these tools. A part of managing a team is ensuring there are good practices around "getting creative" and that there is a clear rationale. Python's metaprogramming came in handy for helping us provide a high level syntax to work with our data model.
Mårten Mickos and 2 Hackers on Hackers Solving Security Issues
Something was bugging me about this, but I had to think hard to figure it out.

The article is largely based on a misguided premise: the idea that URLs should be conceptualized as either names or identifiers. URLs are neither: they are addresses of web pages. The things located at the URL may have names or identifiers, but by design of the web the stuff located at an address is mutable while the address is immutable.

This is an important point because it breaks the analogies to books or bank accounts. A physical copy of Moby Dick is a thing that may be located at a given address, or not. The work of fiction "Moby Dick" has an ISBN number, but the ISBN number is metadata, not an address. A bank account number is also metadata, not an address.

So I get the feeling that URLs should be conceptualized as addresses first and foremost. This isn't a magic bullet for the problem the blog post addresses (how to design URLs) but I think it gives some perspective:

* If the "thing" at the URL will always be conceptually the same "thing", but its name or other metadata may change, it makes sense to assign that thing a unique identifier and use this as part of the URL. (Because the thing with this ID will always be found at this address.)

* If the name of the stuff located at the URL is never going to change, it makes sense to use the name as part of the URL. (Because the stuff with this name will always be found there.)

* "Search results" as discussed in the blog post are a special case of the previous point: if a URL will always contain search results for a certain query, it makes sense to use the name of the query as part of the URL.

* There are also URLs that fall outside the name or identifier paradigms. http://www.ycombinator.com/about/ is the address of a bunch of stuff, which is not necessarily a single coherent thing with either an ID number or a name, but is a very reasonable address at which some content may be located.

Maybe this is all obvious, but to me it really helps think about the issue whereas the blog post confused some things for me, so I thought I'd share.
It costs more to insure obese people. For example, performing surgeries on obese people is much more time consuming and risky. This doesn't seem like something that should be subsidized. Too bad obamacare was about politicians choosing the kind of insurance you can buy instead of actually providing care. Missed opportunity.
My university (in the United States) had a course code like this, except that it was allowed to be repeated so you could take it a number of times under the same course code.
Hevelin Collection: 800 fanzines online and counting, 1930-1950
Mark Farber does not understand that the geography of the United States gave it a unprecedented geopolitical advantage more than any any nation to date. From the farmland to abundant water, to the Mississippi acting like a virtual "freeway" from one end of the country to the next. It made the USA "empire inevitable."

https://worldview.stratfor.com/article/geopolitics-united-st...

Africa on the hand has more surface area than a Pluto and nearly as much as the moon including dangerous terrain.
I'd expect you list installed packages by pointing your text editor at the file where you defined which packages you want your meta-package to pull in, no?
Popularity of ArXiv.org Within Computer Science
> Another great aspect of concurrency in Go is the race detector. This makes it easy [emphasis mine] to figure out if there are any race conditions within your asynchronous code.

Am I reading correctly?
Increasing the incentive to catch every last one, presumably?
I feel like... I'm actually OK with this?

Social media is public. It's intentionally public. That's really the whole point. It's your choice to post things to Facebook or Twitter or Snapstergram.

Of all the privacy issues that we should be worried about it feels like this should not be one of them. If you don't want your social media info used... don't post it to social media!
Re: frameworks

My experience with the language (building multiple production systems) is that the language itself is sort of it's own framework. You don't need to add much to build an application with the standard library. Which is a huge plus and makes things simpler.
My immediate reaction was: "oh god eyecandy + broken features". I felt the same way with Inbox (which, thankfully, was not pressed onto users). They seem to make cosmetic changes (IMO material-UI is clunky) which in turn make things harder to use, or they just straight-up remove stuff on which one relied previously.
Ketone salts enhance fat burning but impair high-intensity exercise performance
A nice write up generally. I just feel he should also mention the classic static vs dynamic typing thing. From my perspective, teams switching to Go — from dynamic typed language such as Python — really appreciate the additional compiler help it provides ;)
I would agree with some of the points - speed (which is stretched over two points), concurrency, and the ability not to do magic as easily, but several of the points (compile time, available developers, strong ecosystem) are not a "versus Python" at all but rather against other languages.

Personally, I see a language like Go and Python as solving different spaces. I wouldn't write a lot of website business logic in Go, and I wouldn't write a low-level TCP redirection daemon in Python.
I have been using Nearley.js [1] and have had a lot of fun using it. I actually quite liked being able to mix in the JS post-processing with the grammar definition in Nearley but could be convinced of the advantages of keeping the separate (checking out your paper on DSLs now).

How would you compare it to Nearley? Can Ohm handle ambiguous grammars?

[1]: http://nearley.js.org
Over 40, sometimes engineer still. First job was Delphi 2, but moved quickly to Delphi 3.

My stack now is... diverse. Python, Spark, Java, React, Node, PyTorch, Scikit and occasionally R.
Unless he was an alien.
That’s a good data point, though it doesn’t preclude the people in that Gallup poll being a different population than those making large investment purchases in the story. Those workers don’t own a grocery stores.
Somebody who never robbed a bank did not become a Georgetown law professor.

Was he the most "qualified" candidate for the job or was he the most "interesting" candidate? Would "interesting" candidates enhance the institution/world more than a less "interesting" but more "qualified" candidate?

---

Edit:

I'm not a domain expert on what makes a strong Georgetown Law Professor. It seems like he has some publications to his credit.

https://www.wikiwand.com/en/Shon_Hopwood
This has been a massive win for us vs languages that require you to haul around a runtime and other dependencies.
Did she not write one for him?
I used it to show the edit history of forum posts until I found out the hard way that you're not to store long strings in Datomic.
So what? That's how the world works. You don't get a free pass because you can code.
The problem for me is, if they were a violent criminal, is your conviction that they are a changed person strong enough to override your fear that they are not a changed person, or that they might revert back to their violent tendencies at a later date?
This has always proved to be unstable.

It will always result in revolution. The 90% will demand an equal share.

The sad bit is that the revolutions seem to destroy the robots, not share the wealth. The 90% elect a different 10%, who then build more robots. See Animal Farm for details.

The 10% have to share the pie, at least enough to prevent revolution.
Not allowed to have more than one per their rules? Obliged to provide a photo to confirm a new account these days?
The Nirvana sounds so utterly bizarre to me - I suppose because I don't hear the original as tonal to begin with.
Not personally tried these but...

https://weblog.west-wind.com/posts/2016/feb/22/using-lets-en...
A New 95
Did you read the article? It is pretty clear he is quite competent..
This is the future and a good reminder to all the Millenials who will be replaced by the GenZ soon enough.
Bower deprecated in favor of yarn, webpack, and npm
I'm sooooooooo sick of this argument. It's not that it's incorrect from a probabilistic point of view, but it shows such an indifference to the facts of how humans actually are rather than how they should be as ideal rational actors.

Look, what are the odds of being killed by a spider? tiny. And most spiders aren't even poisonous. But lots of people have an irrational phobia of creepy crawly animals, perhaps due to some unpleasant childhood experience. If someone is afflicted with such a phobia, maybe therapy can help them, maybe they'll grow out of it, whatever, but standing around saying 'it's very irrational of you to be scared of this probably harmless spider' is no help whatsoever. Either get rid of the spider for them or leave them alone, because when someone is freaking out they're not able to process information rationally.

We know that people don't react rationally to real risk probabilities, some are irrationally risk averse and others are irrationally risk tolerant. We know that such irrational cognitive behaviors are often exploited by unscrupulous actors to manipulate people for financial, political, or strategic gain. We know that the externalities of such exploitation impinge upon our economy, liberty and so so on.

Endlessly repeating an argument that people are already demonstrably indifferent to isn't getting us anywhere. Education is one long-term approach to alleviating that problem but it's very slow and expensive and outcomes are hard to predict and to measure. It has consistently proven easier for politicians to spend money on security services (both pragmatic and theatrical) than it has to raise the intelligence/wisdom of the public at large.
Corrupt Hillary Clinton;

>They also obtained an eyewitness account — backed by documents — indicating Russian nuclear officials had routed millions of dollars to the U.S. designed to benefit former President Bill Clinton’s charitable foundation during the time Secretary of State Hillary Clinton served on a government body that provided a favorable decision to Moscow, sources told The Hill.
you could have something like the rehabilitation of offenders act from the UK. After sometime old convictions are spent and don't need to be declared to potential employers, even if they ask about them.

http://hub.unlock.org.uk/knowledgebase/a-simple-guide-to-the...

https://en.wikipedia.org/wiki/Rehabilitation_of_Offenders_Ac...
Which reminds me of the 'Paperclips' game:

https://universalpaperclips.gamepedia.com/Universal_Papercli...
"Code quality" is, in my experience, usually highly subjective. It's strongly dependent on the fads of the time, and strongly dependent on the preferred style (oop, fp, procedural) of the person being asked.
You know there are but that's the end - still not easy to reason about them haha!
> Our largest micro service written in Go currently takes 6 seconds to compile.

What's the biggest, beefiest real world program yet written in Go, and how long does it take to compile it?
When “fake news” turns real.
I'm not sure I see the difference?
One reasonable perspective is they will be successful until there is a market correction so large it can't be hedged against. World War Three, global warming societal collapse, popular revolution, or massive antitrust activity.

As they say, "in the long run we are all dead."
I actually thought Inbox was a refreshing change for email management, particularly snoozing, but I wish they would port the rest of gmail to it. It's a horrible UX to have to switch from Inbox to gmail to manage filters and anything else that even remotely caters to a "power user".
Their query language is based on Datalog (a non Turing complete subset of prolog.)

I can't think of a job where I would pick it over a SQL database. Maybe if you were already using Clojure, since there would be less impedance mismatch.
As to other ways to avoid lifetime employment denial, a lot of places are forcing at least public sector places and many private sector employers to "Ban The Box" [1] that is to say remove the initial questions about criminal history. They are still allowed to ask at a later date, but the idea is that the people just won't be completely culled without care (which is technically against US employment law anyways).

1: http://www.nelp.org/publication/ban-the-box-fair-chance-hiri...
> The root of the issue here is that URLs are trying to be human-meaningful and machine-meaningful at the same time, but those requirements are fundamentally incompatible.

The TLDR of TFA is that an API can support both human-meaningful and machine-meaningful URLs.
Why Usability Is the Foundation for Delightful Experiences