skysight-inc/HackerNews huggingface dataset:
Ask HN: Most powerful, smallest, mini-ITX PC build?
I tried this on Reddit, but just got 'buy a laptop'.

I use my own laptops all the time when I'm working for various companies. I usually use their monitors and peripherals. Common in the UK.

Desktop CPU power is fairly affordable. Equivalent mobile CPU power not so much.

So, why not build the tiniest Mini-ITX system possible? This would be much cheaper and faster than a top-end laptop.

The dream: Portable 2.5l desktop PC with ~100w TDP CPU.

I found a tiny case that suits the idea - Mini Box M350. It's 2.5litres. http://www.mini-box.com/M350-universal-mini-itx-enclosure

But, getting a Skylake 91w TDP 6700K CPU into a 65w TDP case is the real challenge. And I know little about dissipating heat other than finding good fan placement.

Is this a realistic idea?

I'm dreaming of an ultra-powerful tiny computer that can be extended (thunderbolt) with a powerful GPU sometimes.

Thunderbolt 3 is going to make the USB 3.1 Type-C connecter unbelievably useful by being able to carry 40gbps of thunderbolt data with HDMI, DP, PCIE, USB 3.1 etc.

I'd love to stick a 6-core i7 5930K in that case, but it is hot and lacks integrated GPU.

Other skylake chips should be announced end of this month.

But, how to cool this thing?
Yes, exactly. The essay is attempting to tie the moment of creation for a concept to some event in the real world. Certainly there is something physical going on which we call a "discovery" or an "invention", but it gets fuzzier the more you look at it.

We can objectively say that 1492 was an important year of first contact and we should talk about what happened. But it wasn't "discovering the New World" from the Native Americans' point of view.

Both in science and math, publishing a paper can be an important event and it's a physical process. But the first math paper published may not correspond to the first time someone had an idea or made an observation. If we're going to talk about a concept as a thing that exists in time and space, we need to take into account that ideas may be created, shared, and forgotten many times.

Perhaps we can think of Platoism as a way to avoid getting bogged down in the history of an idea by declaring it irrelevant for our purposes.
> I’ve commited a grave statistical faux-pas in this article. Did you spot it? I showed that the number of votes a Hacker News story gets is correlated with the time it is submitted. Then, I told you that submitting your story at a particular time will cause it to have a higher chance of success. Correlation does not imply causation, however, so this is unproven. It is entirely possible that stories submitted on the weekend have simply been better than those submitted on weekdays, or that weekend readers are “vote-happy”. However, my intuition suggests to me that it is most likely that there is true causation here.

You probably should have led with that caveat. Ignoring it completely for the sake of an argument is misleading.

Relatedly, "what if I told you I found an easy way to increase your story’s votes by 172%?" is flat-out wrong. That metric implies an average behavior, which is not the case here.
> There’ve been week­ends when I haven’t opened my work com­put­er.

This makes it sound like most weekends he does open his work computer to do work. I imagine this is pretty similar at any of the top tech firms though?
>So what hap­pened? · I mean, how is it that The Times por­trays a hell on earth, a cul­ture that would drive me to quit­ting in about fif­teen min­utes?

There's a reason for the disconnect for some of the employees who don't see "hell on earth".

If you do meta-analysis of the mainstream media's coverage of Amazon, a few patterns emerge:

-- The NYT almost always has a negative bias about Amazon. Even before yesterday's article about Amazon being a "bruising workplace", they ran numerous articles about Amazon and book publishers renegotiating their contracts and the stories were always biased towards the publishers.

-- articles from Wall Street Journal and Harvard Business Review are not as negative. Unfortunately, they have smaller circulation numbers, and their articles are more heavily blocked behind paywalls. Their articles are not as widely accessible and therefore not as easy to share. As far as "dictating the narrative" and "shaping public perception" about Amazon employees, NYT drowns out WSJ & HBR.

-- the readership for NYT (more workers) is different from WSJ & HBR (more managers). Therefore, articles about sweatshop pressure at warehouses and white-collar burnout in the corporate offices will resonate with NYT readers. Even if the senior editors at NYT privately don't favor bashing Amazon repeatedly, one can't blame them for always running the stories because they know what their readers like. In the comments section, NYT readers continue the pile on of scorn. It's the same situation with NYT running negative articles about Marissa Mayer at Yahoo and her "unfair" personal baby daycare, eliminating remote workers, etc.

The negative effects at Amazon mentioned by NYT can be true while simultaneously, employees like Tim Bray don't experience it. However, NYT is not interested in running a story that interviews a bunch of "Tim Brays".
Technically, the lower bound is log2(n!), which is slightly less than n * log2(n).

According to the table of experimental results, the algorithm described in this paper and two of its competitors can all do better than n * log2(n) bits.
Re ceteris paribus, I address simliar criticism here: https://news.ycombinator.com/item?id=10064126. The key point is that the original post I was critiquing was already implicitly keeping all other factors fixed. And I only aimed to critique that post's reasoning, not the conclusions it made.

As for imperfect competition (which I'm also familiar with, I have a PhD in economics), I see you mentioned it above but I still don't know why. Even if not sellers were a monopoly or oligopoly, everything I said above would apply, at least in very broad terms. You could probably come up with some demand function such that increasing input costs of a monopolistic producer resulted in an increase in production, but I don't see why you would think that actually applied here.
Yup, I do agree that some things were really funny, but it felt like the audience started laughing no matter what he said.
I bet you're fun at parties.
There have been short-term booms and busts, but the long-term trend looks like this: http://cdn.cstatic.net/images/gridfs/54aadb0df92ea1558800c86...

Imagine a version of yourself in 1987 waiting for the bubble to burst.
I wrote a tutorial for this too which includes c++ source code that's been used in some succcesful video games and thereby tested by millions of people http://heyes-jones.com/astar.php
I get the sense that people feel entitled to live in whatever city they want, and SF is clearly the cultural center of Northern California.
I've never kept one, but from what I hear, they're extremely good at getting out of their cages... especially into nearby tanks full of fish.
I think there is something to that.

Product marketing is really hard. I heard about the culture at Proctor and Gamble and it being really hard as well - a lot of burn outs but also a lot of people saying that the challenging culture taught them a lot that was useful later on.

But AWS is a tech place and not really expose to the same type of pressures.
No, you're correct...these exercises were deliberately kept programmatically simple -- e.g. single loops and conditional statements -- ...not everyone student had much CS experience, nevermind web scraping. In cases where JSON is being parsed, it's usually because that's the easiest way to access the data...but the "skill" in the exercise is recognizing when a website feeds from such an API...and then go direct to that source.

For example, usajobs.gov is a consumer-friendly jobs search site. You could find the number of librarian jobs by manipulating the web form...or you could do a little looking around and see that there's an API:

https://data.usajobs.gov/Rest

And just as importantly, there's an official taxonomy for federal jobs: https://www.opm.gov/policy-data-oversight/classification-qua...

So being able to look at a website and deduce what might be behind it is good enough...and is actually what I would do in a real-world situation rather than just trying to reverse engineer a site.

And there's the increasingly common situation in which the website loads data client-side, such as analytics.usa.gov...and so inspecting the network traffic and working with the JSON files is the only way to collect the data displayed on the website.
It makes it harder to make changes. The story you start telling is not what you end up with later, after you've completed all the non-trivial features and major assumptions have fallen through. Going back and fixing the story as you go along is expensive. Writing the story after it's done is too late - the business value is in the product's shipped functionality, not in the development artifacts.

We have an alternate method of understanding how software developed, which is to look at revision control commits. This method falls more in line with the techniques of development and the genuine evolution of the codebase. Recall that revision control methods were still being improved well after Knuth wrote about literate programming, and the available systems, where people used them(and a lot of shops didn't), weren't nearly as fine-grained back in the 1980's.

Personal experience: I tried using "Leo", an outlining and literate programming text editor, for a project. Although the documentation capability was nice temporarily and gave me an additional method of structure and organization, the hooks messed around with some formatting and refactoring operations, and most of the time, the benefit wasn't clear. The time I spent on the documentation could have gone - from my current perspective - into making the code smaller and simpler. At the time, I didn't know how that would be possible, thus I focused on defending against the complexity by adding more.

A lot of our preconceptions about what makes code both look good and behave well are temporary. That makes it hard to come up with a sensible system of organization, as we'll put effort in to enumerate and categorize only to discover that it falls apart.
Wonder what happend to +Mal and others +HCUers now. Probably still in reversing business .. Good ol' days
> Guess that the only way out is to wait for the next big one.

Maybe I'm reading it wrong, but that seems like a pretty gross sentiment. "I hope a natural disaster gets these old people out of their homes so me and my hip friends can move into our favorite city." I know you probably didn't mean it that way, but I feel like I see a lot of similar animosity towards the longstanding residents (or as you put it, "entrenched interests") of SF.
I've found it cleaner and easier to track changes to your model data and let the view be a declarative representation of said model. YMMV though.

I'd much rather punt the ball into a stadium with some properties/parameters than run the logistics of a game myself (security, ticket sales, refereeing, etc). It's saved me gobs of time as a developer. Again YMMV.
This sounds like something out of Mike Church's blog.

In the real world, I knew plenty of people who switched teams. Sure, there are pathologically bad managers and it may not be possible all the time. But it's definitely the rule, not the exception, for internal transfers to be possible.
Just visit any mainstream AI conference like IJCAI. You will see many things in AI out of reach of current ML. ML is just one track.

http://ijcai-15.org

Also, even in things like question-answering, pure ML is not the state-of-the-art. E.g., IBM Watson had a bunch of different algorithms.

http://ieeexplore.ieee.org/xpl/tocresult.jsp?reload=true&isn...

We will eventually get there with a pure learning system, but not yet. Till then, we need less FUD. :)
That list doesn't include all the new studios being built:

Pinewood: http://m.pinewoodgroup.com/our-studios/usa/pinewood-atlanta-...

Third Rail: http://clatl.com/freshloaf/archives/2015/04/07/film-and-tv-s...

Tyler Perry's new facility: http://m.clatl.com/freshloaf/archives/2015/06/29/tyler-perry...

This is just three of about ten studio facilities being built in the area.

I believe three of the Marvel films have been filmed in Atlanta. These have been recent enough not to be in that list.

I know this is anecdotal, but if you were living in Atlanta you'd get a sense of how much growth is occurring in our film industry.
I agree with the principle of your comments but not with the wealth aspect. My experiences have told me that the world of traveling is restricted to those with the right passports, i.e., North America, Europe, Australia, New Zealand, Japan, and a few other countries considered privileged. If your passport is from the wrong country, like mine, throughout your travels, you'll come across incredible barriers irrespective of how much money you have. You'll constantly be reminded that you don't "belong" in the club of travelers.

If you have travelled to enough different countries, (60 for me and counting), you will have several instances of being detained by immigration, yelled at by consular officers, beaten up by border guards, have your passport flung at your face by police, and several such adventures. The fact that you went to great lengths to get the right visa papers (which could involve filling lengthy forms divulging every aspect of your finances and your life till date and wait months for a decision granting you permission to visit a country for a week) doesn't count. The fact that you have a PhD from a US university doesn't count. The fact that you have a great job at a fortune 5 firm in silicon valley doesn't count. The fact that you make a high income and have a lot of savings doesn't count.

In fact these could count against you, because immigration / consular officers will think someone with your passport is obviously making it up. That you are just trying to sneak into the country to get an under the table job washing dishes. This happens even when the country you are trying to enter gets a massive amount of financial aid from your own country.

So it's not a rich vs poor aspect. Traveling is a type of large-scale consumption that re-affirms self-worth through having the right passport.
Looks like you can get "1800 Mechanical Movements, Devices and Appliances" by Gardner D. Hiscox at:

http://www.pdfarchive.info/pdf/H/Hi/Hiscox_Gardner_Dexter_-_...
You're not converting between data structures in your example, you're mutating a stateful system. Moreover, I'd rather leverage a library so that I don't have to manually do everything myself.
Beneath The Ink
This guy makes $10,000 a month sending potatoes through the mail
I don't know how SF can call itself a city and not allow greater than four story buildings for most of its area.
> Canonical did not hide what they were doing,

Did Microsoft? This is news to me if so, and I'd be interested in reading up on any sources for this you might have.

> and enabled an option to disable it in the first place.

Microsoft added several options to disable things. While I certainly agree that those options have some gaps and/or are outright bugged, I'm not convinced there's any difference in intent or motivation, which is the bigger factor to me when it comes to trust of character.
Honest question:

Why does anyone still care about root escalation on workstations? When do we stop pretending our MacBooks are multi-user UNIX mainframes?

App sandbox to full user privilege escalation may be scary. But if someone can run arbitrary code as my user, then by all means, have root as well.
By "y'all" are you referring to the people who moved to San Francisco in 1981 and "destroyed" the city by making all the changes this article describes?

Or are you referring to the gays and hippies who did the same a decade earlier?

Or do you mean all the civilians who destroyed what used to be a nice military town?

Or do you mean the soldiers who ruined a nice Gold Rush town?

Or do you mean the 49ers who destroyed a Mexican ranching and missionary outpost?

Or the Mexicans who spoiled a charming Ohlone village?
Warning: very little knowledge of Rust and Iron

Can someone explain why there is an extra Ok(...) in this? (I want to call it a function, but I'm not even familiar enough with Rust to be sure that it is a function).

Is it something that could be removed? Right now it just looks like boilerplate.

Edit: Thanks everyone! Ok is similar to a Right or Success of a Either/Result type of object.
Generally, I agree with what you are saying. However, there is one example of someone speaking to the opposite view which I also agree with: Marcus Zarra: https://vimeo.com/97058344

I think the key there is that he is in somewhat of a niche: client-side iOS programming. By limiting the set of problems which he is reimplenting "from scratch" again and again, he has some hope of getting very efficient at the "from scratch" approach (he becomes an expert in that approach). I also think this approach is probably only realistic for very small slice of people (top-level talent whom are also lone-wolf contractors (no oversight, no collaboration)).
You can disagree without calling him names.
I find The Han Solo Shot First Issue very interesting because it plays with how significant Star Wars is.

At this point, no one can be surprised by the movies. In particular, everyone knows that Han Solo is one of the good guys, from the beginning.

That wasn't true when it was first released. At the point of the encounter with Greedo, the audience doesn't know if Han is going to be a traitor. Chewbacca is more menacing than ever on his first scenes, and Han is definitively a shady character.

Now, all that doesn't make sense. We know Han (and Chewie) to be the "good guys", even if we never saw the movies. We can't be surprised by then...

Similar stuff happens with Yoda appareance and Vader revelation. They are plots that we know in advance, effectively changing the movie experience...
Island ECN 10th Birthday Source Code Release
Go, the game... Not the programming language as I expected on HN...

But some of its ancient Japanese wisdom is timeless ;-)

'Basically, I don't provide answers to problems because you will eventually find them by yourself after retrying many times.'
All networks are hostile, not just the internet or "external" network.

Google's BeyondCorp [1] initiative recognizes this and treats the internal network as untrusted.

Instead of trusting a privileged network or VPN, securely identify devices and users assuming untrusted networks.

[1] http://static.googleusercontent.com/media/research.google.co... [PDF]
I had an offer from Amazon after grad school. There was only one reason I did not accept it: I had heard first person stories from a couple of my friends who were working at Amazon. And it did not make any sense to me to join such a work environment. One of them left Amazon to join Google, and is thriving at Google, which works well for him and his company. While at Amazon, he was constantly cynical, negative and it felt that the work environment was affecting him personally. As a developer, I need to be happy and stress free to provide good quality, thoughtful solutions (I'm sure not everyone is like me, and many would certainly thrive at Amazon). I couldn't see myself doing that at Amazon.
Same story from 6 hours ago, this time with '#hn' added to the URL https://news.ycombinator.com/item?id=10068983

If you found the solution when/if a story gets picked up by time-of-day then why submit it again? (I'm making an ironic joke)
Prof Eric Demaine – Data Structures
Just wait until you get to the "megademo". :)
All these lists of what we have and haven't seen are merely anecdotal. That Tim Bray (and others in the last thread) has not seen it does not mean it never happens.

Conversely, while I have seen people crying and get a superficial 7-day PIP so the boss can rapid-fire someone litigation-free, I know that doesn't mean it happens everywhere. Likely all this has happened at MS/Goog/FB as well.

So is the culture toxicity level here above industry average? I think it is slightly, but it's not a huge deal if you're competent; those who are mediocre performers will be impacted most.

The "frugality" is annoying though. Total comp is comparatively low, we pay our own parking $250/mo (and you still might not have a spot!), no free snacks or even soda, and until last year, we had to steal a monitor from ex-employees just to have a 2nd.
My friends answered immediately: «Saying that Scala is a gateway drug to Haskell is like saying that poor-quality heroin cut with speed is а gateway drug to LSD».
Because hello_world returns an IronResult, which in turn is just a simple Result type from Rust. Note that the status::Ok is different from the Ok(...).

Iron::new expects a function that returns a Result type, so it has to be there.
I think this critique can be rephrased as saying that the anthropic principle is equivalent to saying that the relevant probabilities are not the "raw" probabilities, but the probabilities conditional on the existence of a conscious observer. Such conditional probabilities only make sense if you assume many possible universes, one of which we happen to inhabit.

If you are a Christian, then you most likely believe in a single objective universe, which is the one we live in (I'm not a Christian so I won't go as far as saying that a Christian must believe this, although many theologians do).

If you are not a Christian, you might have more flexible beliefs that allow for the anthropic principal.
Are there that many situations where you can't just put a SSL proxy in front of a standard HTTP server, and keep the application itself simpler?

If I were a sysadmin in charge of just keeping in-house applications running, I'd really hate it if some SSL layer bug meant I had to figure out how to recompile some custom application - especially one using boost! - not to mention figuring out how to update certificates and that sort of thing.
It is needed because the handler doesn't return a Response, it returns a Result that wraps a Response if there isn't an error. This provides the means of error handling.
The advantage of the bay area is your improved chances of networking. If you are well connected enough as it is, chances are you'll do better elsewhere, maybe even doing remote work for bay area companies. There's people here that could pay for a 4 bedroom house in full every year if then wanted to, just by abusing that pay differential.

So why would we move there, if we can get paid pretty much the same with a much cheaper cost of living? The extra connections are not worth going from 1K a month mortgages to 4-5K.
Also, because it is a Result it forces the caller to either handle the error or explicitly panic on it, right? They can't ignore it? (which is awesome!)
Many of those scripts will most likely fail within a few weeks, as their data extraction logic is way too simplistic and based on unstable and non-semantic HTML structures (i.e. doc.cssselect('small a')[0] ).
It does survive, in a certain sense, in scientific programming and data science. Both iPython notebooks and Rmarkdown are a sort of literate programming, although with the emphasis on the text more than the code. In that setting, the executable artifact is not really more important than the explanation of why the code does what it does, so the extra overhead is justifiable.

Rmarkdown example: http://kbroman.org/knitr_knutshell/pages/Rmarkdown.html

iPython notebook example: http://nbviewer.ipython.org/github/empet/Math/blob/master/Do...