skysight-inc/HackerNews huggingface dataset:
I had a go on a frind's new 15" with touch bar tonight when visiting for Christmas Eve drinks. The touch bar looks lovely, it's a solid machine (literally the trademark Apple solid block of Aluminium) and while I found the feel of the keyboard a little odd it wasn't at all unpleasant. I typed about 300 words and it was accurate and tactile enough to give positive feedback. The large touch pad felt really good. Overall, it seemed like a very high quality product. He needs an SD interface because he takes a lot of pictures for work, so uses a multi-adapter block which he says works fine.

Some of the design choices seem edgy maybe, but nothing that would be a deal breaker for me. I don't need a new machine right now, but when the time comes I see no blocking issues with it and in a few years time when I will be in the market things like USB-C only will be even less of an issue.

I don't for one second buy the idea that Apple is neglecting the Mac. A neglected product doesn't get an entirely new and unique touch interface format that's fully supported by the integrated software from top to bottom, an entirely new keyboard design and a risky but forward looking peripheral port revamp. These are not choices you'd see made by a company treating the device as an afterthought.
Sorry for not bothering to find a source on it in my orig post. Here it is [1].

[1] http://news.softpedia.com/news/Microsoft-Wants-to-Buy-Custom...
There are (roughly) four things that can be done about griefing, cheating, and other toxic behaviors:

1. Design a game where toxicity is naturally mitigated.

2. Create limited spaces where people mutually agree on a code of conduct.

3. Conduct yourself virtuously within your space, to the best of your ability.

4. When someone breaks the code of your space, quietly exile them to the desert.

Ideally everything is possible with point 1 alone, but at scale you inevitably encounter more and more persistent and skilled adversaries. Point 2 helps reduce the scale factor. Point 3 controls atmosphere - if you allow yourself to fly off the handle then you degrade the space. Point 4 is the last resort; you want conduct to proceed along a planned trajectory, but they consistently disrupt it. So the best you can do is remove them quickly and quietly before things explode, because nobody can be counted on to follow point 3 all the time and once it explodes the next hour or more will be spent discoursing over vigilantism and victimization and rights and freedoms instead of whatever you had planned.

The alternative - allow anything to happen and "let people suck it up" - basically encourages Lord of the Flies in microcosm, which is very, very bad for a game. Somehow Twitter has managed to survive with it, though!
I teach high school math, and I incorporate math history informally. I don't teach lessons specifically about math history, but I often use it as context for whatever I'm teaching.

For example, if I'm showing students how to find the area of a circle, I ask them if they know where pi comes from. Many students have no idea that people had to discover the value of pi, and how it can be used in formulas. To many students, pi and formulas are just things that have been around forever, that they have to learn in school. I draw a square around a circle and ask what the area of a square is. I draw a pentagon and a hexagon, and ask them what will happen if we keep adding sides. Students spend most of their time focusing on the practical aspects of math, but they come away with an understanding that math has been a human endeavor of discovery, and that many of the pieces fit together in beautiful and surprising ways.

When we have a little time at the end of class, or during transitions, I pull up little snippets of math to show them. Math videos are great; for example, I love showing students that ∞ + ∞ = ∞. [0]

There are lots of little things we can do to make math more alive for students, and sharing some math history is certainly one of them.

[0] https://www.youtube.com/watch?v=faQBrAQ87l4
Researchers Send Information Using a Single Particle of Light
When I learned calculus in school our teacher took an hour to describe what the problem was and how people over history had solved these problems before calculus came around. This made the topic much more interesting to me. You probably don't need detailed math history but a few minutes showing that things like calculus have not always been around and how they were discovered is pretty useful.
I've been following Rust since way before 1.0 and one of my fears when 1.0 was announced was that it seemed rushed. On the other hand, I completely understood the need for stabilization for people that actually use Rust in production (i.e. not me).

People aren't building castles on foundations of sand. They are building sandcastles, experimenting and building along as the language and ecosystem evolves and matures. Every nightly-only crate should be regarded as highly unstable and experimental. If a lot of people are building sandcastles surely that means that the language wasn't yet ready for that particular castle being made of stone.

And this is a good thing! AFAICT without nightly-only crates being so pervasive due to compiler plugins, Macros 1.1 wouldn't be so close to stabilization. Isn't that exactly what nightly is for? If some nightly feature is used a lot, that means it should promptly be polished and stabilized.

At such an early stage in the language's life the evolution is mutual. The development team responding timely to such issues is just another sign that Rust is a healthy (even if in its infancy) language.

Stable Rust is dead, long live Stable Rust!
Why Smart People Support Trump (And Why They’re Wrong)
It was all abandoned, but many similar features made it into CM. Things like separating the seeding passphrase/PIN/pattern for FDE from the lockscreen and lockscreen PIN randomization were once features in CyanogenMod.

The former, FDE key separation, feature is gone and you'll need to either use adb or a 3rd party application [0] to achieve it.

It shouldn't be too hard to pull kernel patches from CopperheadOS and apply it to a clean AOSP tree for different devices -- this is obviously after they have done all the heavy lifting.

0. https://github.com/xmikos/SnooperStopper
Except you equated that pattern with crowdfunding which is rather untrue. Several examples were provided of successful games which delivered exactly what they set out to do more or less.
Pure Randomness Extracted from Two Poor Sources
Here's the important piece of information, from the conflict resolution page:

"Compare their string values with JSON.stringify, choosing the greater of the two."

In other words -- don't ever use this database in production.

on edit: Here's why. CouchDB, which is also an AP database, puts conflict resolution into the hands of the user, but each document contains a revision, including information for the user to determine which is the correct revision. Many times, it's just "the correct one is the most recent one", but that's done in the user's code.

Making this kind of assumption (stringify and string comparison) for conflict resolution is dangerous because there will be scenarios when you will lose data no matter how many times you post to the database, guaranteed. Yes you can't be consistent, but you need to tell the user that there's a data conflict and have them deal with the logic.
Not IPSEC in itself, but the full stack (tunnel+encryption) implementation in (for example) macOS is completely closed. You could go for something like StrongSwan, but then you lose the advantage you mentioned, namely OS-integration.
Well all experiments have been near large large objects so far, so if such a force exists nothing is being said about it being faster than light.
I maintain a dozen or two Rust libraries and programs, and close to half of them are real-world production code.

Exactly one of them requires nightly Rust, and that's because it uses a feature (Macros 1.1) scheduled to show up in stable in just under 6 weeks.

There are two reasons not to use nightly:

1. Stuff breaks. I remember the bad old days before Rust 1.0 and its iron-clad stability guarantees. I spent my time fixing a endless stream of GitHub issues reports across a half dozen projects. Modern nightly isn't so bad, but I'm still guiltily sitting on a PR about nightly breakage (as usual). But something that works in stable Rust just keeps working.

2. Stuff goes away. Nightly only features do get removed, and then you're stuck only building with an ancient nightly build.
I've always wondered: has any computer ever come with a "dock" that actually contains its own CPU+GPU+RAM+disks+etc, such that, when you plug the "computer" into the "dock", you're really telling the "dock" to boot and parasitize all the "computer's" PCI-E peripherals into its own address-space?

Sort of like an iMac's Target Display Mode, but in reverse: instead of the "guest" computer doing the work and the "host" computer acting as a dumb frame-buffer, the "host" does the work and the "guest" acts as a Thunderbolt hub.
58335 - North East
>> I doubt these people know the inner workings of computers

> ...wha...? This is so ridiculous of a claim that I can't even think of how to respond...

GP probably means that while these pioneers might be aware of, might have tinkered with the nuances of processor design and syscalls and nitty-gritty details of TLB's and interrupts and stuff that, say, a kernel-level or SSD firmware guy might deal with regularly, it's highly unlikely that they would know their way around these like they know their way around the algorithms that they deal with on a regular basis, which exist at a much higher level of abstraction.

Take everything with a grain of salt.
"Arrays of sizes from 0 to 32 (inclusive) implement the following traits if the element type allows it:

Clone (only if T: Copy)
Debug
IntoIterator (implemented for &[T; N] and &mut [T; N])
PartialEq, PartialOrd, Eq, Ord
Hash
AsRef, AsMut
Borrow, BorrowMut
Default
This limitation on the size N exists because Rust does not yet support code that is generic over the size of an array type. [Foo; 3] and [Bar; 3] are instances of same generic type [T; 3], but [Foo; 3] and [Foo; 5] are entirely different types. As a stopgap, trait implementations are statically generated up to size 32."

from the rust docs. https://doc.rust-lang.org/std/primitive.array.html

i sort of leapt to the conclusion that these traits couldn't be implemented because generically because the type system requires them to be implemented for each size of N, and they provide the first 32 as a nicety. the similarity to the situation with tuples in haskell, (http://stackoverflow.com/questions/2978389/haskell-tuple-siz...), and the fact that rust doesn't have dependent types and so a type couldn't depend on a value, and i just kind of guessed at a possible reason.
I understand your reasoning, but it is based on incorrect assumptions.

The first assumption you make is that we actually know how pre-18th century music sounded like. We have guesses, some better than others, but we know that we are likely wrong.

The second assumption is based on the idea that music somehow improves in complexity and quality. We have many scores that have survived the test of time, but these provide a huge selection bias. Only scores that were popular, widely copied and preserved due to timelessness are currently available. Musical ideas that could not be expressed using the scoring techniques didn't survive. Nor did musical ideas that didn't mesh with following eras. Therefor, what we see is a pattern of scores that are popular (of low complexity), easy to write (of low complexity) and similar to following eras (of lower or equal complexity). See the selection bias?

Lastly, and more concretely: 18th century musicians didn't suddenly start caring about bending time. They started caring about sharing musical ideas outside of their direct sphere of influence (printing press), so they understood the need to add extra markings on sheet music, such as rubato and accelerando.

And saying you try to understand jazz is akin to saying you try to understand philosophy. It cannot be done, too much has been written and one cannot understand all standpoints simultaneously. Try to understand a specific era, like Bebop, or a specific musician, like Chick Corea.
But then the confusion with TrueOS (prev. PC-BSD).
Times like these i feel like the only runner who doesn't experience any sort of clarity of mind or runner's high.

I run five days a week. After a hard run i feel tired. If i made a good time with a low heart rate, i feel slightly happy about it. I don't feel anything i could ever describe as a runner's high, and never have on any type of run.
Exactly. When someone changes their name, we don't hold a funeral.
Best of all, it is offered as a 1-click-install on Vultr.com VPS.
I can't find any evidence that Powerwall, for example, has any rare earths in it.

Can you?
Please stop trolling and read my actual post.
Beta is almost exclusively used by Travis CI and other automatic builders, as far as I know. But a huge number of Rust projects are built against it on every commit.
Midpoint displacement is mentioned in The Science of Fractal Images (and the Beauty of Fractal Images), and also in Mandelbrot's book Fractal Geometry of Nature.

From a phone, sorry about upside down: http://m.imgur.com/JGCpnIu

A snippet from "Science of Fractal Images"
Eh what, on the mob branch? Master untouched for three years.
"Completely closed"? Isn't it still raccoon?
The comments on /r/rust are worth reading

https://www.reddit.com/r/rust/comments/5k4sep/a_tale_of_two_...
Physics and chemistry are usually taught from an historical perspective and I found this to be very helpful for it fires the imagination. We humans seem to love learning by stories. The hero strives to solve an important problem, fails a few times and eventually suceeds. Learning in ths fashion seems to enabler the learner to better integrate new knowledge into mental representations that are more likely to be recalled at the appropriate time when solving our own problems.
Math is unfortunately not taught in this fashion. IMHO this is why so many kids have the same complaint: "when am i ever going to use this?"
I don't do graffiti often, but when I do this is what I write:

∇ ‧B = 0

I love the simplicity of the equation, and the implications that come from it.

(I only write it in places where graffiti has become acceptable, like some hike-in cabins. I also occasionally leave it in small writing in the corner of random whiteboards.)
Because it doesn't display the same signs as CIG. Zero executive turnover. Much lower employee turnover. Steady revenue.

I feel like I'm talking to an aquarium.
I'm trying to make a similar for python, I knew it will not be as easy to start, Go standard libraries are more featured that the ones in python for the Web.

https://github.com/mariocesar/wiki.py
Doesn't want to see logo again... posts base64 version of it to preserve it forever :)
I'll take your word on that one. I've been more of a movie/docu person, and have seen a movie based on that story, Argo [1]. The movie was good. Non-fictional, based on the real story, slightly romanticized/more suspenseful.

While I'm trying to steer more towards reading books I made the rule to not watch a book of a movie I've seen. It just doesn't work very well for me (other way around seems fine).

So yeah, the movie spoiled it for me...

[1] https://en.wikipedia.org/wiki/Argo_(2012_film)
I strongly believe they should.

I've learned much more about math by looking at its history. Then again, I've simultaneously had to learn a lot of applied math quickly, so I have skipped the historical perspective on many things too.

I think the way I learn best is simply try to apply a concept first and struggle until I become deeply frustrated. Then I backtrack and try to learn the fundamentals that influence the most current tools and methods of application.

Part of understanding these fundamentals is understanding the history of an idea and how it evolved.
True, that was wrong, it should have said we learned of it 3 days ago.
I did the same and I'm also sticking with El Capitan. I have no use of Siri, Sierra broke Karabiner (Karabiner Elements mappings are not sufficient for my keyboard), and mouse scroll was also behaving weird on Sierra. f.lux is showing artifacts with fullscreen video. It feels like this will be my last Mac, which sucks because I bought my first Mac three years ago and completely stopped using Windows last year. It might be time to embrace Linux for desktop when it's time to replace the 2015 MacBook Pro.
Because clicks.
There's so much incorrect information in this post that I almost know where to begin to refute it. An RFC to stabilize extensions was accepted literally last week. The vast majority of code that is only on nightly is because of unstable deriving, which will be stable in less than six weeks. The community is emphatically not embracing nightly, exactly the opposite. A Python scenario is impossible because stable is a strict subset of nightly, and even using unstable features on nightly requires explicit opt-in. And so on.
Why should he be any different than the rest of the industry?
There are ways to ask questions about restrictive clauses in licences that don't cause shitty threads, which is something that almost always happens when US politicians are named.
Why would anyone run an authoritative time service on a virtual server in the first place? My experience is that system time suffers greatly from noisy neighbor.
Most of the time octal causes me pain, but octal is definitely the way to understand Intel instruction sets. In hex you can sort of see some patterns, but in octal things are trivial.

The octal encoding goes back to the Datapoint 2200, which use BCD decoder chips (7442) for instruction decoding. These were used to decode three instruction bits at a time, so the instruction set of the Datapoint 2200 (and thus the 8008) was based on groups of three bits. Among other things, that's why the 8008 has 7 registers (A, B, C, D, E, H, L) - the 8th value was used to indicate a memory access.

Also see "x86 is octal": http://www.dabo.de/ccc99/www.camp.ccc.de/radio/help.txt
Reduce inefficiencies in waiting times on C2B sales through GPS tracking (pretty hard to explain without mentioning the domain).
He has some good content here https://www.youtube.com/channel/UC8gjB1PSXv_oAUSAQ16S0fA/vid...
Well, speak for yourself!
You can't use the CJ phrase - it autokills your comments.
AWS-3 is B66, NOT 62. They also still have 'legacy' AWS-1 which MANY "mainstream" devices support.
Leverage from Being Small
> Anyone developing their library as nightly-only should expect to see little adoption.

As evidence of this, it hasn't been so long since 1.0 that anyone's forgotten that "I don't want my code to break" was, in polls, the absolute #1 reason for people not using pre-1.0 Rust, by leaps and bounds.
You have correctly framed this situation. The linked article, however, was a complete misrepresentation as it declared,

> Stable Rust is dead. Nightly Rust is the only Rust.

Many people and orgs are using Rust stable. In production.

Nightly is a playground.

We shouldn't misinform those unfamiliar with the language or give them the opinion that Rust isn't well managed. Doing so can steer new talent and interest away. We are all relying on newcomers for more widespread adoption and faster growth of our community.

The author probably didn't mean any harm, but I feel like the article is disingenuous and should have a retraction before it causes any confusion.
Low correlation of predictions and outcomes is no evidence against hot hand
What a load of garbage. The reason Trump and other politicians attack "technocrats" is that politically they are overwhelmingly unrepresentative of the population they're meant to serve. Combine that with little accountability and the ability for regulatory bodies can make new law on the fly, and you have a recipe for corruption, disconnect and resentment.

Case in point, Clinton got 91% of the vote in DC:

http://www.nytimes.com/elections/results/district-of-columbi...
Photon rockets are not actually reactionless, because the emitted photons carry momentum and energy out of the system. This makes conservation laws to hold for such systems, cf. https://arxiv.org/abs/1506.00494

Now, the emdrive people are apparently claiming that it is truly reactionless. If so, you can build a perpetual motion machine of the first kind (produces energy from nothing) out of it --- which should demonstrate the degree of plausibility of such claims.

For photon rockets, there's apparently a hard upper bound on the efficiency, which limits the practical usability.
I had a roommate named John Edward Smith III. Aside from the III, this is basically the most common name in the US. There were 3 people with exactly his name (including the III!) in the University of Virginia database. If you're going to change your legal name for privacy reasons, it's a good choice.
He has done us all a service. The real problem is not the jacking up of the price of some obscure drug that almost nobody uses, but the constant yearly 10% to 20% increases in the blockbuster drugs that billions are spent on. By dragging the activities of the pharmaceutical industry into the light he is helping make change possible [1].

1. I do have some sympathy for the pharmaceutical industry as it has through its greed managed to get itself caught in the vice of rising regulation and safety requirements and payer (insurance) coverage restrictions. If only it was pharma management rather than the scientists that are being crushed.
Shkreli is my hero. Inspired me to start studying economics.
> The reason we call inverses “arcsine”, etc. is because originally these were written as quasi-sentences, and the concept of a mathematical function was not well developed. So sin⁻¹ x would be expressed as something like: arc (sin. = x).

Any pointers to resources about those "quasi-sentences"? I'm interested in language, broadly speaking, so info about how mathematical notation evolved is interesting to me. The rest of your comment is great to, I'd love to read a book about stuff like this if there is one!
Yes, people did. Lots of people didn't like that Macbook keyboard, and this new one is supposed to be better and improved.
>Shkreli, a former hedge fund manager who posts on Twitter frequently

This is terrible reporting. Donald Trump posts on Twitter frequently. Shkreli's a veritable memelord.
Principles of Programming Languages (2011)
This library does more than "random" testing: when it finds a failure, it will try to reduce the input (called "shrinking") to report a minimal example. Here are some similar tools for other languages: http://hypothesis.works/articles/quickcheck-in-every-languag...
I am a computer professional. I never even considered using the low end MacBook. I imagine all other professionals also disregarded it. So, I don't think this is a reasonable argument. Now that the second generation is being used on a computer for professionals, professionals will start noticing the flaws and voicing their complaints.
I'll ask for a citation for "a lot of people". The only evidence given is a single web framework that was announced 24 hours ago, by someone who up to now is entirely unknown in the Rust community. The only two projects in Rust that run on nightly are Serde and Diesel, and those do already also run on stable, thanks to deliberate effort from their authors, and they will both be completely stable as of Rust 1.15 in February.

(And for the record, I think Rocket is the perfect sort of project for helping us get experience with using unstable features, and helping us prioritize which should be stabilized first. I don't want to knock it just for using unstable features! People are too eager to forget that, as of two years ago, every Rust project was de facto unstable, and we've been making steady progress toward a majority-stable ecosystem since then, as expected.)