skysight-inc/HackerNews huggingface dataset:
https://github.com/cockroachdb/cockroach

which was inspired by this paper:

http://research.google.com/archive/spanner.html

which google made available for all in form of it's cloud datastore:

https://cloud.google.com/datastore/

"We believe it is better to have application programmers deal with performance problems due to overuse of transactions as bottlenecks arise, rather than always coding around the lack of transactions." [1]

[1] http://highscalability.com/blog/2012/9/24/google-spanners-mo...
I can get behind this.
> 2. The iPhone becomes the new ultra portable desktop computing device. You plug it into a dock (maybe backside of an Apple 27" monitor) and boot up an ARM version of macOS from your iPhone.

Why would they do that - Apple is very profit oriented and if they can sell you Apple monitor, Apple iMac, Apple iPhone and all the dongles to connect them together, that maximizes their profit.

Plugin your iPhone into a monitor is not a good way to extract maximum profit - well maybe if it'll only work with Apple monitor and nothing else.
Ask HN: Best MOOC or Tutorial After Reading Nate Silver's Signal and the Noise
Just finished Nate Silver's Signal and the Noise and thought it was a great read.

At the end, Nate suggests to dive in and start doing your own statistical analysis.

I'd love to find a MOOC or good tutorial that can guide me in a more structured way as to how to get started. Maybe a tutorial that provides a good data set and some challenges to get started on.

Anyone have some suggestions...?
Homebrew router faces better tests, tougher competition
I'm replying to you rather than making another top level comment to prevent sprawl, but I'm adding a different way the effect changed for me. (I'll probably try yours later, when I'm done playing with it, lol)

For me, holding a "picture" of what the picture is in my head and trying to heat map where I think my view is spotting the dots changed it from seeing about 4 (in a triangle or box) to about 6 (in weird squiggles). I think that actively trying to see it changes how my brain caches information as it moves the eyes' focus.
Does this 'News' article contain any truth?
Show HN: Directory Tags for Lazy Programmers
Ok, I've juste discovered that in the html5 specification you can omit tags. I've always been reluctant to push Jade to my coworker but it makes much more sense now.
A relatively small part. Apple computer sales are not that impressive. They may be a large individual conntributor, but they alone do not sell enough to make a big difference.
I think what you're looking for is wisdom, not smarts.
What are you hiring programmers for? A science project, or a company which has to meet business goals?

If the former, by all means, pick some esoteric language. If its the latter, more mundane issues like existing codebase, skillset and, I don't know, perhaps using the right tool for the job? C# can do things Python cannot and vice-versa.

Learning Scala to show off and fit in Graham's paradox is silly and doesn't prove that you are a smarter programmer. A smart programmer is someone who comes up with smart solutions; you can write crap code in any language.
As somebody who does a lot of xml, I'm weirded out by the idea that the root tags are optional. I mean, get certain child elements and attributes being optional, but the parent ones? That's.... hard.
I thought it was one of those stupid 'satirical' articles but reading the comments, it seems that no one is calling it out.
10 ft fence.
The conclusions of this article have far more implications for the future of blockchain technologies than for the future of databases.

Bitcoin and Ethereum and their ilk have, out of necessity, valued ACID qualities above all else- including availability and responsiveness. Does it make sense that completing a $1 transaction would require the same amount of resources as a $100,000 transaction? The traditional banking system has the flexibility to expend fewer resources on the $1 transaction, but Bitcoin does not- by design.

Interestingly, I think it is the inconvenience of the traditional banking system that gives it this flexibility. If financial transactions were something that could be done instantaneously, by a computer, without having to provide personal information to set up an account, then stealing money in 100,000 $1 transactions might be easier than stealing $100,000 in one big heist. Add a little inconvenience to each transaction and this problem goes away.

Unless blockchain transactions are extremely cheap, it will limit their competitiveness with the traditional banking system for this reason.
In-spec or not, I don't like it
No, you missed my point. I'm perfectly clear why Jonathan Blow made it's own engine and why anyone who's capable of that would want the same thing. I was talking about the article and about some members of the game community and for that I have two criticisms

First: in the article she says that they struggled on one very complex project while using Unity. And then she says (or that's my understanding) that she made a completely different project on her own engine. That's why I said apples and oranges. I can't build unity, u4 or frostibe from scratch but if you want Pong or a simple platformer, sure, I can do that from nothing. That would be me saying: "well I had serious problems recreating the Witness in Unity but look at my space invaders which i made in Elm for browser without an engine".

The second problem I have is with some members of the gamedev community. Feel like a lot of people are ready to jump on the "I wish the source was available" train while very few of them (or at least that's my perception) know what to do with the engine source. Actually I could extend this point to a lot of advocate of the open source community. There is this false perception that anyone can fix anything that's broken because the source is available and yet a lot of those apps are sadly still very much broken and sometimes the authors of those apps have difficulties in finding people who might help them. But if you read any post about it online it's usually "closed source sucks and open source is brilliant cause we can always fix that anytime".

Sorry, this is a lot of generalization and obviously not everyone is like that but I tried to make point clearer this time 'this all.
Usually, though, there is a continuum between the "code a well known and well understood problem quickly and maintainably" and "figure out the math/algorithms to do do it in a new way". If you can stay closer to the latter, that is a competitive edge too. (Provided you don't bungle the basic stuff in its pursuit). I remember this thread from a few days back when I asked about Mathematica:

https://news.ycombinator.com/item?id=12473688

A relevant section from PG's How to make Wealth [1] essay:

"Use difficulty as a guide not just in selecting the overall aim of your company, but also at decision points along the way. At Viaweb one of our rules of thumb was run upstairs. Suppose you are a little, nimble guy being chased by a big, fat, bully. You open a door and find yourself in a staircase. Do you go up or down? I say up. The bully can probably run downstairs as fast as you can. Going upstairs his bulk will be more of a disadvantage. Running upstairs is hard for you but even harder for him.

What this meant in practice was that we deliberately sought hard problems. If there were two features we could add to our software, both equally valuable in proportion to their difficulty, we'd always take the harder one. Not just because it was more valuable, but because it was harder. We delighted in forcing bigger, slower competitors to follow us over difficult ground. Like guerillas, startups prefer the difficult terrain of the mountains, where the troops of the central government can't follow. I can remember times when we were just exhausted after wrestling all day with some horrible technical problem. And I'd be delighted, because something that was hard for us would be impossible for our competitors."

[1] http://paulgraham.com/wealth.html
indeed, with the small caveat that you now need to know the database's IP address, thereby introducing a failure point / master IP point. My solution is completely IP address agnostic. Indeed you could run my version even with DHCP for all nodes.
Great points here! I agree with you that there are people who chase after novelty and don't complete most of what they start. If the person is naive about it then I would be weary about hiring them, but it depends on the persons motives.

If they are doing it to experiment with a new library/framework then finishing may not be the point; it could be to see if the tool is worth the hype or if it adds unnecessary complexity.

This exploratory tinkering has been good for me personally because it has developed my sense for parsing out the bullshit used to market new tools.
I am very fond of pushing as much validation into the database as I can, so I use `NOT NULL`, foreign keys, `CHECK` constraints, and whatever I can to let the database do the job of ensuring valid data. All of us make mistakes, and making sure there are no exceptions is just what computers are good at. I think you're right about "a lot of developers", but I find data modeling, including finding the invariants, pretty satisfying actually.

Reading your comment reminds me of ESR's point in The Art of Unix Programming that getting the data structures right is more important than getting the code right, and if you have good data structures, writing the code is a lot easier. The database is just a big data structure, the foundation everything else is built on, and the better-designed it is, the easier your code will be.
Nvidia Debuts New Graphics Processors for AI to Compete with Intel
It reminds me, and not favorably, of all the old laziness that made browsers' DOM parsers such nightmares of special cases upon special cases, and all the extra effort to deal with that which was so much the norm last decade. Perhaps this isn't a regression, but it certainly feels like one.
Do you have any examples of this, or how to get in touch with someone who is doing this?
However weird it feels, this makes sense. Why did we ever have do things like use an HTML tag immediately after declaring the DOCTYPE as HTML anyway?
The way the eye interfaces with the brain never ceases to amaze me. Another fun fact is that it even has it's own error correction mechanisms, one of which you can intentionally miscalibrate in order to see colors that aren't there for days, weeks, and sometimes even months after doing the calibration (which is acheived by looking at a very specific image pattern for a long time). I would not recommend actually doing this, as those who have have reported back that the illusory colors become quite distracting and actually cause a bit of emotional distress after many months, but it's crazy that the brain has this kind of chromatic abboration error correction programmed in in the first place. https://en.wikipedia.org/wiki/McCollough_effect
For one, they haven't made it clear that they need to take them down; they said they are going to do whatever they can first, but leave open the possibility that they will be unable to meet the regulations and would need to remove the content.

I understand your argument, but if you only have to say "I can't afford to support disabled people!" in order to not have to be in compliance with the ADA, then the ADA becomes meaningless.

The answer of "we can't afford it" is always about priorities. They could choose to spend money spent on other things to make this content accessible; it isn't like they are spending their entire school budget on this. It is ALWAYS going to be cheaper to NOT provide accessible content, so this argument could happen in every single instance. The resources spent making content accessible could always be spent on making more stuff for non-disabled access. However, as a society we have decided, no, it is unfair to choose not to spend those resources on accessibility,so we mandate it, because we know a pure utilitarian action will leave disabled people always getting the short end of the stick.

Yes, this means that non-disabled people will lose out on some stuff (and maybe this content is one of those things). That is a price we as a society have decided to pay, and I think it is a worthy one.

Think about it; the same goes for handicapped ramps and the like. If businesses didn't need to pay for those, they could use the money on other stuff. Prices would go down. So yes, we all have to pay a little more so everyone can enjoy the same access (or at least a certain level of access)
>If you only need a small amount of relatively simple code and the license allows it, then just copy that code into your project.

I disagree with this. With a good dependency management system, this should almost never be done, even for the most trivial code. If you find it somewhere else, and it's published as a "dependency" (module, package, etc...), you should install it as such.

Lock the version, vendor your dependencies, keep a copy of the full source, but don't just copy it into your project.

Even trivial code snippets "decay", and being able to look at a piece of code that "decayed" and see that there was an update 6 months ago that fixed the problem will save time over trying to follow code copied into your code base, a possibly out-of-date comment saying where it came from, and the chance that anyone could have modified it from it's original without updating the comment in the meantime.

I think of a dependency is "copy-paste with metadata", and throwing out that metadata seems like a bad idea.

Is there something I'm missing or have completely wrong, as I seem to see this being advocated for more and more, especially in the javascript ecosystem?
> cluster failing with some network issues we had with Rackspace

Were you using Zen Discovery at the time?

I haven't kept up with ES development in the last year so maybe they fixed this, but a flaky network can cause a cluster using Zen to freak out a lot.
The rules are really complicated here. It's best to do this using a minifier instead of through hand-coding.
This should be an optimization step performed by a tool anyway.
Apologies, I didn't mean it as a critique of your post. What I meant was that its often used as a strawman example of why you don't need consistency[1]. Bank transactions are extremely simple compared to the majority of things we build on top of databases.

[1]: http://highscalability.com/blog/2013/5/1/myth-eric-brewer-on...
That's the styleguide that Flask and other pallets docs always had for many years already. People keep opening pull requests to change it and are always surprised when I point ou that it's not only not wrong but also by the spec.

If you consider how the parser for HTML5 actually works many of the closing tags you would encounter don't actually add any value unless you have some trailing text that should be attached to the parent node.
I've read that a good codebase is supposed to look like it was written by one person, no matter how many people have contributed.

I know that doesn't sound fun but it makes maintenance so much easier.
A lot of big tech companies aren't building their products on .NET, for a variety of reasons that mostly boil down to it not being the right tool for the job. Recently the .NET web dev situation has improved. (Whether it has improved relative to the alternatives is arguable.) But when those companies were getting started the original iteration of ASP.NET was the only game in town, and it was very much not something you'd want to use for what any of those companies do. Nor was it intended to be.

.NET's always been more of a player on the in-house enterprise dev front, and probably always will be. (That might change with .NET Core, but it also might not.) Which means that you're not going to see much about .NET on TechCrunch. Inventory & financial management for Fortune 500 companies might be the silent majority for software development work, but it's rarely newsworthy.
>In my professional experience, people that are always learning new languages or are constantly using new libraries and frameworks are never the ones who accomplish the most.

There's a huge difference between chasing fashion and seeking out what is new that is actually better.

I agree that those people are usually worse. The ones that pick up on new stuff that isn't necessarily fashionable, assess it intelligently and balance the trade offs of the good vs the bad - those are the better programmers.

IME scala programmers are better - mostly because they tend to be programmers who got frustrated with java's shortcomings and realized scala solved many of those shortcomings, not because it's fashionable to learn scala.

IMO people who chased mongo, on the other hand, demonstrated a responsiveness to large marketing budgets rather than critical thinking skills.

You don't have to try out every new technology either. There are some that you just have to read a bit about to know enough to dismiss them.
I didn't say the people were weird. But the climate is unpleasant, and you can drive for miles and still be in the same state. And even "northern" california (I believe SF qualifies) is pretty far south, so it hardly ever snows. And all the landscapes look pretty ordinary, and then you suddenly see a palm tree (although that's more LA than SF).

And I do love Cambridge. Why? Bookstores. Bookstores everywhere. If you're looking for a book, and you can't find it in Cambridge, than you're probably not looking hard enough. And there's the MIT Press bookstore as well: Their CS section houses SICP, EPL, TAPL, The Little Books, and countless other excellent books on one row of shelves. If that's not awesome, I don't know what is.

I know that as a Cambridgeite, you know many more reasons why Cambridge is cool, but frankly, having a lot of bookstores is pretty high on my list of ways that places can be awesome.

And yes, it totally sucks that so much talent is on the other side of the country. Living in the New Haven suburbs, I can say that it's hard to get a good pizza most places. And that's the least of the reasons it sucks.
This blows my mind. Can't wait to bring this up in a code review.
Top Programming Language in the 21st Century – Naijafixer – Programing
Hrm, is anybody else's browser not navigating to the "Optional Tags" anchor?
The $14M advance is still a rumor AFAIK. It's not much of a record either as Bill Clinton received a $15M advance in 2004 dollars.
YC's Xerox Alto restoration Part 7: disk exerciser trial [video]
Uhh... I wonder how large the percentage of users is that see a broken site if you strictly adhere to that principle.
> Yeah. Reducing expenses is the goal.

I feel like you may have overlooked some of the nuances in my answer, because I've already specifically pointed out how the robo advisors can be cheaper than buying the indexes directly for a lot of people.
My views on the Motley Fool are complicated.

They are a "diversified financial brand" which does a lot of e.g. telling people to get out of credit card debt (a good idea!) and save for retirement (a good idea!). Then they also tell people that "with just a little work, you too can read company numbers and outperform the stock market" (a really bad idea!) and "if you want to do less work, buy our newsletters and we'll give you picks which mumble mumble maybe mumble mumble will make you into Warren Buffet" (a really bad idea!).
Carefully read the author's bio and decide for yourself what biases he may have.

The author says that a pardon decision hinges on what is good for society. So, the question is: does the benefit of the disclosures outweigh the costs?

I considered the pros and cons and decided to sign the pardon Snowden petition, for what little that is worth.
We are also working on a congestion avoidance for a UDP based protocol - our goal is to share large volumes of data over the Internet but have high throughput for high latency links and support NAT traversal. So no UDT. We're using a varient of LEDBAT (utp/micro-torrent). What are your negative experiences based on?
Maybe it will make more sense once it fully sinks in, but I think in general it is a mistake to make developers think about when and where certain things can be omitted. It's more straightforward to simply do one thing, consistently, following the "explicit is better than implicit" mantra.

What happened to optimizing for mental overhead instead of file size? This simply should be a build step, part of your minification and concatenation dance, not having to consider all of these when trying to decide if I should close my <p> tag or not:

A p element's end tag may be omitted if the p element is immediately followed by an address, article, aside, blockquote, details, div, dl, fieldset, figcaption, figure, footer, form, h1, h2, h3, h4, h5, h6, header, hgroup, hr, main, menu, nav, ol, p, pre, section, table, or ul element, or if there is no more content in the parent element and the parent element is an HTML element that is not an a, audio, del, ins, map, noscript, or video element, or an autonomous custom element.
Knowing the scale of corruption in Nigeria, Mark doesn't need to do anything like this to buy his way through.
scripts in <head> tag works perfectly as well as long as you position scripts above elements you would put in the <body> . I will start doing this!

demo: http://jsbin.com/duqonahiyi/1/edit?html,console,output
Maybe after SF is underwater rents will come down.
Movavi Video Converter 16.2.0 Crack and Activation Key Free Download
Well, the HTML tag is older than DOCTYPE. Andin SGML and, later, XML, the document must contain a single root element.
To me it makes total sense.
I mean why would you have a root tag? You already know it's an HTML file due to the mime type. It's redundant information with no meaning.
For those with knowledge of the genre: What are the better, traditional roguelikes that you can recommend? I've only played Elona so far and quite liked it.
This problem can't be solved. No politician who advocates the sort of changes required will be reelected. There is no way to enforce international agreements.

Probably the best idea is to start thinking about risky geoengineering remediation techniques.
I suggest talking to a women in business or politics.
I'm pretty sure what applies to Scala vs. Java programmers applies to F# vs. C# programmers.

Existing code bases, etc. don't matter so much when you're sharing the same ecosystem, and the good programmers from that ecosystem will certainly choose the best language that they can within it.
> We run an average of 14k logs/sec through a two-node RMQ cluster

How many MB/s are you indexing?
I agree with you on people who are constantly chasing the ball, but I also think that's a false dichotomy. To me, if there's someone who can demonstrate a deep understanding of the features that lend merit to newfangled tech, _and_ they have a track record of delivering well architected, appropriately engineered products, that's a win all around.

It's pretty easy to find people who use "boring tech" and still fall prey to the hazards of overengineering, slow delivery, etc.
but I think in general it is a mistake to make developers think about when and where certain things can be omitted.

Yes, sometimes it is better to make developers think about when and where certain things are required.
Being outside of MIT, I don't exactly know what you're talking about, but it doesn't sound good.