skysight-inc/HackerNews huggingface dataset:
100 basic words (the corpus of the study) is such a small subset, especially if you posit very strong correlations among subsets of those 100 words most likely to be used in the first year of life.

And especially considering that the researchers "reduced all sounds to 34 distinct consonants and 7 vowels." (Consider that the more we reduce and simplify the vocalizations the more likely we should expect correlations. For example, if we simplified all sounds to grunts we should expect tremendous overlap.)

The correlation of the corpus of 100 words isn't particularly surprising given what we already know about language development. The null hypothesis was that there'd be no correlation whatsoever (i.e. the sounds would be completely random), which I don't think anybody could reasonably expect.
You can use * on each side of the text for italic quotes.

Good work on the screw research. Having read it and thought about the mechanics of pulls along the axis of the screw as opposed to loading such that shearing through the ice plays a role, it makes intuitive sense that a screw placed at a positive angle should indeed hold better, but only in ideal ice conditions - that's the big qualifier. Of course determining what constitutes "ideal ice conditions" is the art and essence of placing ice gear. I felt you made this clear in your article. My personal conclusion from your tests is to place screws at a positive angle when I feel the ice is 'very solid'. Obviously some rather ill defined terms in that statement! 'Very solid' will remain an intuitive assessment.
it seems like the only recurring revenue they might receive comes from publishing books
GSB-47:+How+to+Flip+Gas+Stations+for+Profit
I tried to start another project in Go instead of Python/Flask. I never really started.

If you want to learn, Go is a good choice. If you want to get things done, use what you already know.
It's just not skype, even Skype for business (former Lync) has gone down the drain. It still baffles me why I can't paste 10 lines of code. Copying is wonky, messages go to wrong computer. Calls barely work. Don't even get me started on the UI.
Ruslan Spivak: Let’s Build a Simple Interpreter. Part 11
Angelina Jolie to divorce Brad Pitt
Open source machine vision board and robot kit run Linux and Arduino
Seems totally reasonable, also I don't know about the US but in other parts of the world there are other kinds of staff related costs you have to consider too like fringe benefit tax etc. Seems like let's encrypt is a great meaningful endeavour that produces good results for the world on a pretty elegant idea and lean implementation.
Well then the spec isn't just a spec. It is a programming language in and of itself.

And how do you prove that THAT spec is correct?

It is turtle specs all the way down.
Polyglot is here. It creates opportunities for a lot of folks. And it creates a lot of headaches for others. The open source NoSQL analytics project, SlamData, will reduce a lot of the friction described in these comments. I work on the project.

Three things to know:

1. SlamData is souped-up SQL + data viz platform.
2. SlamData send analytics to the data (computation happens in-database)
3. SlamData connects to MongoDB, Couchbase, MarkLogic, Spark and relational stores.
4. You can do JOINs across data stores

Four things, sorry.

If you want to know what's going on across a polyglot business or application... it's exponentially easier now. So go ahead and use the new technology -- the overhead isn't nearly as much as it was. I think this materially changes the conversation.
to add to this, I want to compare to the source image! You should definitely link to the original.
Throwing an error doesn't make a function impure. If the calculation is erroneous then the expression sum() has no value which could replace it. I.e. the definition of pure being that we can replace sum(a) by its value without changing the behavior of the program, simply doesn't apply. The exception is effectively equivalent to the situation of there not being a value.

As for this:

var a = {}; a.valueOf = Math.random;
var fn = x => x * 10;
fn(a); // 5.107926817373938
fn(a); // 3.4100775757245416
fn(a); // 5.1903831613695095
// Same input, different outputs!

Calling that "same input" just because it has the same syntax "a" is just ... plain silly. It's obviously "a" that is impure not the "fn" multiplication function. "a" is behaving like a macro which denotes the retrieval of a pseudo-random number.

It's simply not reasonable extend the definition of a functions' purity to include *the behavior of the expression(s) which are evaluated to provide its arguments.

(I would say that it's still not reasonable even under non-strict evaluation.)
A Lisp interpreter for Raspberry Pi in a single ARM assembly file
Ah ok so 3rd party software not yet ready for new kernel. I thought apple dropped support for pptp or something of the like, esp with the IPSec comment in the thread.
The result of this thinking is when I press the back button, I have to refresh the page manually because the data is stale.

My daily use case for this is Github Issues. Simple repro: Click an issue, make a change, press back.

Now the list view is out of date and doesn't show my changes. So I have to refresh.

I think a background XHR request is the best approach (until browsers fix this issue for real). On page load: pull latest from server (if network is down, then no-op). If no changes, then don't change. If there are changes then replace inline without a new page reload.
This isn't an all-or-nothing issue. The author generalizes that developers and users today use browsers/html differently than they did before, but what I'm hearing is actually a new way to use the word/button for "(go) back".

The back button has not changed functionality--it still works as expected on all non-webapp webpages.

From my perspective, I think the author should be asking for browsers to implement a new button that follows his desired "load previous URL" behavior.
Indeed. Especially when the article gives us this: "...the team found a lot more consistency across languages than they had expected." What does that mean? Were their originally expectations reasonable, or did they merely re-discover the birthday paradox?
>What is it about the Commodore/AmigaOS brand that is worth resurrecting?

Nostalgia, and you can't really resurrect nostalgia. I loved my Commodores when I was growing up, but times have changed. The BBS software that I ran and modded are long gone, the friends I would post with are long gone, the doors would be fun for about 5 minutes.

It was great, but it's like meeting a great childhood friend that you haven't seen in 20 years. Most of the time, it's fun to reminisce, but there's nothing new there. We've both changed.
I take Uptake (Chicago industrial IoT unicorn, http://uptake.com/) as a positive case of Chicago's tech scene embracing the area's manufacturing strengths.
Hype or not, I inherited a project that had CouchDB baked into the bones. While I found its disk space usage and its time to reindex large databases frustrating, I did appreciate REST-like queries, how it just saved whatever you wanted and how the map/reduce queries could actually be quite powerful for ETL and reporting (though it took a good while to index every time we had a change). We abandoned replication early on as just too chatty over high latency networks.

I love the CouchApp idea because it's a natural extension of "save whatever you want." As long as we're saving json, why not save static files too? It lets you prototype quickly and, in our case, let us develop and test out specific features for clients by quarantining risky crap code on the fly into one database. I like to think we're beyond that stage, but at the time it was invaluable to keep multiple versions of our app running concurrently.

I have 3 solid years of experience working with CouchDB and in the end I find myself longing for PostgreSQL with one bson column for the unknown or "volatile" attributes. Our data was semi-relational, as I would argue is most data. Meaning there were honest to goodness has-many or belongs-to type queries that could have been simplified and easier to maintain outside the application code.

I know that's just a style, some people would use key-value stores for everything with no validation on anything. If you're not that far gone and you still like freedom then CouchDB might be for you. As for me, I wanted an error from my database if my application code asked for something or tried to store something invalid. But for rapid prototyping for us I don't think we could have gotten a better database.
Microsoft announces qtr dividend increase and $40B share repurchase
Elaborate a little bit. I read it, and I'm not sure what to take from it. I feel like I need a bit more context.
> I'm surprised they didn't go by the UIAA standard

... for testing dynamic ropes. That's because they weren't testing dynamic ropes. All the other UIAA standards—the ones for harnesses, nuts, camming devices, static ropes, and so on—tell you to apply a set force, usually 10kN, and see what breaks. To be pedantic, all this stuff is specified in the CE standards that the UIAA ones incorporate by reference.

If you're in a lab, you apply 10kN in a precise way that uses a whopping great hydraulic ram. If you want to avoid hauling a whopping great hydraulic ram halfway up an ice cliff, then you improvise, but the aim is still to control the force acting on the gear and measure what happens. I'm using "control" and "measure" in the technical sense here.

Dynamic ropes are different because they determine the forces that act on everything else. In a dynamic rope test, the conditions of a fall are controlled as well as possible, and the peak impact force it generates is one of the variables to be measured. If you did that in the ice screw tests, the results would depend on which rope you used, and that isn't what you want.
10 Ideas to Help You Sell UX Work
Microsoft announces Project Bletchley reaches version 1
Similarly in english we use "yappy dog" to describe little chihuahua like dogs. You can drop dog, or substitute it for a superlative of your choice and everyone will understand what you mean.
I notice that they explain the purpose and benefit to the organization of every single category of employee - except the executive director.
I have to imagine that it's more better accurate to get raw numbers at the transfer point rather than browser-reported ones. This also allows them to get stats for no-js browsers, too.
My thoughts exactly. I'm not sure who CouchDB is supposed to be for anymore. The original developers who fell in love with it are moving on. Who is the audience for 2.0? Who does IBM hope to reach with Cloudant?

BTW, you are spot on about continuous replication. Try using continuous replication on Cloudant and you will end up with a fat bill.
80% of my browsing is in a browser that has had doubleclick blocked for years.
That's a fascinating assumption.
Can I get a digital version on floppy disks?
Do you know of any mainstream language that has been "removed"?
Comparing Confluence to MediaWiki...

Confluence lacks categories. You are stuck with hierarchy. It's more like filesystem directory structure than tags. This gets awful once you have a lot of stuff.

Confluence does not provide direct wikitext access. You might not think you need direct access, but then one day you want to turn a bunch of data into a big table.

Confluence, obviously, doesn't scale as well as MediaWiki. Nothing does. You'd hate to find yourself needing to migrate from Confluence's closed ecosystem over to MediaWiki once you hit the limits.

Confluence lacks the familiarity of MediaWiki. Pretty much everybody has seen MediaWiki in action on Wikipedia. This is comforting. People know what to expect from MediaWiki.
I generally want a back button that rewinds time (server side be damned).

usually I'll right-mouse-button click + open in new tab on any link instead of just clicking on it.

Eventually, like garbage collection, I'll stop, go back to the start of the tabs and close a bunch of them, then go back to what i was looking at.

And if I'm on a site that doesn't allow right clicking on a link? well the site had better be important otherwise it's gonna get closed.
That was a great book that got me into CouchDB. I think the original authors of that book, primarily Damien Katz and J. Chris Anderson, left for Couchbase. Today's CouchDB has different motives than the one that book was written for. Couch Apps are no longer the killer feature.
Guilty as charged - and worse: all I cared about was the source of the 280 years figure, as used in the disingenuous and clickbaity phrase "280-Year-Old Algorithm." I was being all meta.

Edit: Also a variation on the TSP was part of my senior project so I am forever traumatized.
Considering our nearest ancestors don't have complex language I'd say convergent/parallel evolution is a much more reasonable conclusion.
Pick up a copy of The Algorithm Design Manual or CLRS, they're great! MIT OCW also has a great deal of content covering algorithms. https://ocw.mit.edu/courses/electrical-engineering-and-compu...
JetBlue Makes Biofuels Deal to Curtail Greenhouse Gases
It's hard to take this seriously because the page itself does not work correctly w.r.t. the back button.

For example, if I click through to the http 1.1 spec in the first paragraph, then hit "Back" I see the scrollbar shrink as new content is loaded and uBlock's block count increases as new content loads.

If I scroll to the bottom of the page, click a link, and then click back, I don't even go back to the same spot - I'm at the end of the article and content loads below it...

My expectation as a user, regardless of the spec, is that I should see exactly what I saw when I was just on the page. Render to a bitmap, and when I click "back" display the bitmap. If going back to the page requires any network requests then the page is doing it wrong.

The exception that proves the rule would be streaming content.
It's even worse than that. The search results on Google scroll with one "weight", then when you tap the AMP link and all of a sudden it scrolls differently. Keep in mind that your address bar says "google.com" the entire time - this is inconsistency within the very same site.
Yup, works flawlessly on both, although I just got the 15 and haven't messed around with switching between GPUs.
Link please? From reading, it sounded like Elizabeth Warren spanked him.

And how can you not love Elizabeth Warren? <3
In my experience, the new IE is Safari.
For me, SeL4's verification is important because it can actually provide formal real-time guarantees. Before SeL4, if you wanted to write a hard real-time system, you pretty much had to either forego an OS, or forego formal verification (or, usually, both). Having the option to write a RTOS without also writing a bunch of boilerplate (and probably incorrect) scheduler / resource allocation code, or dedicating a core to a task because you couldn't reason about resource consumption otherwise, is pretty exciting! Sure, it may not help much with securing normal userland applications, but in many embedded systems meeting deadlines is more important than any security functionality could be; the confinement properties are in some sense just consequences of having to reliably hit deadlines and isolate resources.
What I really love about most of Stripe's landing pages is that they tend to use tastefully designed vector graphics (SVGs), gradients, and animations over photos (or even worse, videos).

A high resolution photo can easily take up Megabytes of bandwidth, and could still look like a blurry mess on an even higher resolution screen.

Vector graphics can scale to any resolution and remain as sharp as it could possibly be, and often come at a tiny fraction of the size of a similarly-sized photo.

The largest SVG in the new Stripe site, by the way, is only 10KB. Which site would you rather visit on a mobile data plan?
Sure, most of humanity participates in a religion of some kind, but they're all just fools getting taken in a con. I get that there are some well established problems that come up in conjunction with religion, but perhaps there's a little bit more to it than that, no?
Well, he said he will accept what the board says. If the board doesn't tell him to return his bonus, they should get sued by the shareholders.
The traveling salesman problem comes up quite often when programming. I'm actually surprised how well written Cristoferides's algorithm was on this blog post. Usually most algorithm explanations are super hard to follow.
Thiel prides himself on iconoclasm. He really likes to ask people, "What important truth do very few people agree with you on?" For that reason I'm surprised about his attitude towards Chicago, and the non NYC/SF USA at large. I think there's a lot to be gained by shrugging off the accepted wisdom that anything of ambition must be done in these two places and embracing the unique opportunities in a great city like Chicago, Columbus, Nashville, Pittsburgh, etc..
Considering what this team is doing, creating, and providing to everyone free of charge-- especially keeping in mind the scale of it, and the magnitude of it's impact on the entire Internet-- I'd say pay them more than $200k. They maybe should offer top tier salaries, in order to attract and keep top tier talent (not meaning to disparage the current team in any way, they could be best in show for all I know -- what they've done thus far is pretty incredible and they're just getting started)
I read trips in the title as a verb.
Likewise, if the random component could be removed, it might make for a very nice video encoding.
In one of my Engineering classes back in the day, our prof told us about the Euler algorithm and that it was impossible to stay off the island in the middle if you could only cross each bridge once and if there were an odd number of bridges.

Someone in class responded immediately: "Build another bridge."

The prof congratulated him on his lateral thinking.
This is similar to something I created a while back: http://codegolf.stackexchange.com/questions/50299/draw-an-im...

Drawing a target image using a voronoi diagram.
Ok, I don't think you meant you need the book just for the admin interface, I just made a jerky comment.

I was, however, under the impression that you actually needed a book for a lot of things and I didn't like that feeling.

However, now that you explained, I understand how good can a good book be. I also read that CouchDB book almost entirely before going on to use the database, before thinking about it, or having a need for it, and that made wonders to me. I had forgotten about this fact of my life. Thank you for reminding me.
There are people who like it.
Early CouchDB contributor here. I agree with much of your write up, but I think the picture for apps built around replication is brighter than it seems. PouchDB has crazy momentum. Couchbase Mobile is getting baked into the next generation of infrastructure at places like GE and big airlines.

If you want filtered replication, we designed Couchbase Sync Gateway because we thought db-per-user was to heavy. What's fun is to think about the options for mix-and-match across the stack.
I'm not sure how this is non-standard.

On iOS, there are various conventions that apps generally follow. On a list item you can swipe from right-to-left to bring up a Delete option. On a list of stuff you can tap at the top of the screen to scroll to the top. These are standard things in the iOS ecosystem.

A good parallel outside of iOS would be the pervasive use of right-click to bring up a context menu in Windows or the convention of having "--help" show help text in Linux.
The human cognitive measure for egregious pay is not: Pay > Marginal Utility to Humanity, otherwise there's millions of jobs that provide Pay > MuH or even where Pay > 0 > MuH, and I don't hear people complaining about that fact very often. If you look at it through this assumption that compensation should be provided in exchange for providing a benefit to the world, complaining about LetsEncrypt dev salaries begins to look ridiculous.
What I find cool about this is that I ran it on my profile pic, and when Facebook shrinks it down to the micro size image, you can't tell the difference between the primitive version and the original.
The BeOS file system: an OS geek retrospective (2010)
You might have to wait a while on the encoding side. It's taking a minute a frame to encode here! :)
But not specifically a job title's internal expectation of fully-loaded cost or willingness-to-pay. You can find salary and benefit aggregates, sure, but that's not the same thing.
Pair programming: Absurd or nah?
This is how photography nearly always worked. I think there's some early photo tech that did only result in one image, but all of film photography produced 'prints'.

Although I remember growing up with one print that deliberately had a fold in it, made by the artist as part of the art.
An upgrade card with a 20Mhz 65816 and 16MB RAM was actually sold as a product: https://en.wikipedia.org/wiki/SuperCPU, but it didn't really make anyone happy. The C64 purists stuck with the 6510 and those looking for more power just switched to modern architectures.
It all depends on the purity of the underlying computation. If you're multiplying XXL numbers together, that's different than accessing a database with dynamic or variable data. Math is totally pure. But you'll have to evaluate the constraints on the purity of that database access.
Always nice to see success from startups outside of the SF/NY hotspot.
I'd agree. The truly evil characters are barely present in the books; the stories are much more about how the rest of the world reacts to the threat.

Saruman, Denethor, Boromir, Theoden, the elves choosing to largely stay out of the war...these are people facing hard decisions with limited information and no expectation that victory is possible.

How many of us would make choices in the face of the end of the world that an outside observer would call unambiguously good and wise?
see this thread I posted last week
https://news.ycombinator.com/item?id=12489839
In fact, most of this background material only became available ~20 yrs after this article was published.
Shippey's "J.R.R. Tolkien: Author of the Century" is a very good read.

https://www.amazon.com/J-R-R-Tolkien-Century-Tom-Shippey/dp/...
The revenue part is coming under a lot of scrutiny recently, since it's being proven to have very regressive effects. The Federal government will make it more expensive than the revenue they generate from it.
Wish they'd put a bit more time into editing this OCR scan. So many typos, it gets quite distracting.
A bit off-topic: Is possible to use React-Native without the whole npm non-sense? Like with normal javascript you get the scripts at that is all?
> “I do not feel any pity for Gollum. He deserves death.”

> “Deserves death! I daresay he does. Many that live deserve death. And some die that deserve life. Can you give that to them? Then be not too eager to deal out death in the name of Justice ... even the wise cannot see all ends.”

Remains a very good, concise argument against capital punishment.
It reminds me a little of the way in which airbags are always described as "SRS" (for "Supplementary Restraint System"), to try and make it clear that they're supposed to be used with seatbelts, not instead of them.
BaycloudSystems Joins EFF's Do Not Track Coalition
Just merge AmigaOS with Linux the same way Jobs merged Classic MacOS with BSD Unix.

Make new video and sound chips based on SVGA and Soundblaster chips to run Windows if the user wants. Make the Intel the main CPU and add in a 68K chip and PowerPC chip that can run old code in a Window. When not running legacy software the 68K and PowerPC chip can be used for coprocessing. Add in an ASIC Bitcoin mining chip as well to mine bitcoins.