skysight-inc/HackerNews huggingface dataset:
Boulder Dash was awesome! I had Boulder Dash Construction Kit which I used to make many levels that none of my friends ever wanted to play (They wanted to play NES... so sad)
How can organizations successfully convert big data into real-world decisions?
I fully agree. The crux of my argument is that self-driving cars aren't inherently any more hackable or trackable than existing vehicles with existing available data connections through cell, emergency communications, OTA updates, or usb if local.

One could, in theory, use the fly-by-wire steering, traction control, or ABS systems to simulate a pretty convincing crash. It would be fairly straightforward electronically through the onboard processors in existing cars, and would be practically untraceable.
The "new" Linux interface is roughly comparable to what Windows/Mac users have had for a while now.
The missing energy is evident indeed, but this is not the point. You usually use the missing energy as a proof of a neutral particle, not a fast decaying particle. And you can not say what that neutral particle was because you did not measure anything about it.

More importantly, the particle we are considering, the one that decays really fast, near the origin, will decay into other particles, and those can be detected.
No, that's not how that works.

EEE refers to the times when Microsoft would take an open standard--say HTML, or JavaScript, back when IE3 was actually the best browser on the market--shove in their own, proprietary, backwards-incompatible extensions, and keep calling it the same thing as the open standard.

But MS makes it very clear that TypeScript is a different language. It helps a lot that they don't even have the same name, y'know. Also, it's a system for specifically staying backwards compatible with open-standard JavaScript. Using TypeScript does not replace JavaScript. It supplements it.
Skype hasn't really changed in years now. Linux support doesn't exist despite claims of embracing it.

This is an official sign that it would be strictly in maintenance mode.
React components for Office and Office 365
The Nexus 5 isn't getting Android 7.
When the product began to display connection status at launch, it was a welcome update but it made me wonder why the recent decision to add this to the UI. If things are moving along smoothly, there doesn't tend to be a need to add gauges and indicators to your instrumentation. What is most likely are some backend issues after some migration or update was leading to a lot of inconsistent messaging problems. Adding connection status was a sanity check for troubleshooting these issues. It was one of those improvements that helped explain why things seemed to be a bit flaky recently.

There is a lot of competition in this space and I sort of feel that Skype was a Windows Phone play that didn't pan out for MS after the Windows Phone failed (along side the Nokia deal). Unfortunately for the London office, the product heads are not really sure how to right this ship. Hopefully everyone lands gracefully, whatever happens with the product.
PE is the default of how HTML, CSS and JS work. You have to go out of your way to screw it up. Which is precisely what the whole web world delights in doing now.
…locked in on a contract for 2 years, provided for them by their company, provided for them by their family, etc etc.
We typically run go's built-in server behind nginx. There's no need for something like gunicorn in go.
While networked cars are interesting, there is also a massive security issue here.

Hackers will easily figure out a way to spoof the communication, and could play with traffic.

There are mitigations for most issues, but it's a complex topic.

Just imagine some scenarios:

-) Spoof an emergency break advisory that causes tailing cars to also do an emergency break. (could be mitigated by first observing that cars in front are actually slowing down before breaking)

-) Spoof a command from a smart traffic light at an intersection to stop immediately for police / other emergency traffic. (need to check if traffic light is actually red)

-) Spoof speed restrictions issued by a smart highway traffic jam prevention system.

-) A system for police to force a car to stop immediately and pull over, eliminating car chases. Just spoof this signal and stop anyone you want. (mitigate by checking if there is a police car trailing you, and ignore otherwise).

And so on...

A way around would be to maintain a national database with public keys for each registered vehicle, and make cars only accept those keys. But that would be hard to maintain and still hackers could just get a hold of some PK.

In the end, the driving system will always have to correlate such car 2 car communication with observations it makes itself.

And an autonomous system can react almost immediately anyway.
So coordination doesen't give you all that much.

--
There are some useful ideas though, like:

-) Traffic lights can announce an ideal speed for a route, taking into account traffic and traffic light timings, so you can optimize throughput and minimize fuel consumption
Well, $200K/employee, 4K employees (roughly), and you're at $800M pretty fast.

Still an astounding number.
Maybe next time just email them before issuing a DMCA request, and assume charitable behaviour before evidence dictates otherwise? edit I was wrong, see below.
Hi anotheryou,
For full disclosure, I'm one of the Devs that worked on this project though these opinions are completely my own. We agree that the ugly red X is ugly, it's just part of an old design, that will still be around for a bit, but not too long. We actually used to have a zoom, the problem is that unlike Artsy, we do not have the full rights for these images, even though MoMA might own the artwork. Image rights for modern art are complex, and we removed it not to long ago. We legally can't put out images larger than 2000x2000, so we decided to use tiling to get around that. That was until people started to paste them back together and got a very high res image, so we took it down (for now).
In the end, this was an archives project, which means dealing with a lot of old material. We are the first (or at least one of) that opens up our archives in such a way. And as it should be with big IT projects, this was an MVP of course.
I really wish I could have been there to take a picture with Audrey Hepburn and a banana for scale :D
Edge cases. When something "works" it handles the requirements of your customers in the normal case, but may misbehave in edge cases. When it is right it won't.
From an outside perspective, it sounds like Microsoft finally decided to merge various "Skype, but not efforts". There's the obvious in that Skype has had a bunch of different platform clients that were never quite all aligned and is now trying to merge everything into a single UWP client.

But it also sounds like Microsoft is also finally slowly starting to merge in the efforts from the business side (Yammer, Skype for Business aka Lync) and unify those communication efforts a bit more than just how Skype and Skype for Business share a brand but not much else. (All of this in an effort to present a more unified front versus Slack, HipChat, and others currently eating into the enterprise space and Whatsapp, Facebook Messenger, and others into the consumer space.)

From that perspective it's easy to imagine there have been quite a positions that have been redundant between the various teams.
As you can imagine, the long-lived particles can have "any" lifetime. Since the lifetime is unknown, it makes sense to probe many lifetimes. The experiment being suggested by Lubatti and his collaborators probes lifetimes on the order of 10^5 - 10^7 m. There aren't strong constraints on this range, which can appear as missing energy in CMS or ATLAS (or not). CMS, ATLAS, and LHCb are giving constraints at 10^-6 to 10^2 m. Interestingly, the different experiments are probing mostly different ranges.

To correct something in the grandparent (?) post, the LHC experiments do not know the incoming energy. Even though the beam energy is 6.5 TeV on 6.5 TeV, the collisions are only a fraction of that. We only know that the energy has to balance in the perpendicular direction. However, if a collision produces two invisible particles that balance each other, it would appear that there is no missing energy. In many of models, pair production of new particles is preferred, so if the particles are long-lived, they can be hard to find.
I haven't put Linux on it myself yet, but how about the Surface Book? Keyboard, screen and touchpad are all wonderful.
Auto-Scaling Kubernetes Cluster on AWS EC2 with Supergiant
The JS build system ecosystem could definitely use some help along the whole "reasonable tools I can expect to work together well" front. I swear, 30% of my time is spent fighting the build systems and their plugins that hate each other.

EDIT: to add, I think the TS team has done such a bangup job on Typescript that I would love it if they could create a build system as well. Some things that would be nice to have:

* Build-time loading of static resources (.json into js objects, html into strings, etc.)

* File watching and processing for more than just .ts/.js files

* Optimization. Not just tree-shaking and minification, but you could actually get a little more advanced due to the static types and ES6 modules.

* Environment-dependent compilation (compile these files in this way, inserting these static values where ENV variables are used in the source, etc.)

* Target capabilities analysis (ie. for this set of browsers and versions, what is the Lowest Common Denominator for browser capabilities, and ergo, what babel transforms and browser shims should be included?)

* Integrated contracts testing with test elision (ie. run these tests in these (karma? selenium?) environments and if failing, throw a compilation error or warning, and if passing, strip the tests from the compiled source).

* Source packaging (gzipping, etc.), and deployment plugins (ie. deploy compiled assets to S3, package for NPM, etc.).

All of these are pain points in Typescript projects, and all of them touch TS projects in such a way that it makes it even more painful in existing build systems.
Oh god, so now I have to charge my shoes as well?
If done well, formal verification of kernel level services and how these use runtime protection built in hardware can absolutely reduce the attack surface of application level code. The key is to move critical services that attackers would wish to exploit into a formally verified sandbox. That is the real power of systems like seL4, even though seL4 isn't itself really geared toward the sort of chipsets commonly used in consumer grade IoT products. However, a system _like_ seL4 can absolutely improve application level security, as long as the application is constrained by the architecture of the OS.
Exchange by itself is absolutely not secure from an audit trail perspective[1]. I've specifically had this come up where an employee edited an e-mail to try and CYA.

Even if you are using journalling, an administrator can open the journal mailbox and edit messages. If you want/need a reasonably secure audit trail, you need a 3rd party product in addition to Exchange.

[1] https://www.msoutlook.info/question/edit-message-and-subject
Does it really matter in practice though? If someone else is driving your car without you in the vehicle you can still be liable. Car insurance for autonomous vehicles will be dramatically cheaper and will still be required (someone can ram into your autonomous car as Google has proven many times!) which can surely cover the liability for edge cases.
I think an auxillary testing group is a good idea. Someone who tests all the components as a cohesive whole. Ensuring it acts as expected in terms of businesss expectations.

My experience though has been counter productive though. I expect a bit of lead time, introducing them to the code base. But I had daily meetings covering the code base, and what it was delivering. Then several weeks of meetings mapping out test cases into a spread sheet, with the various results.

There is a fine balance, but when executed properly they are worth it.
To be clear, we’re not doing that work. We’re helping the departments build their own services with both patterns and standards, and assess each service before it goes live for quality. You can see what you need to do to meet the service assessment standard at https://www.gov.uk/service-manual/service-standard
But capabilities do solve real application security problems, and this capability system is proven correct. You can get the same thing on Linux [1], but there is no guarantee that it can't be circumvented or broken.

[1]: http://www.cl.cam.ac.uk/research/security/capsicum/
Using containers? Let's reveal the truth about app testing. Take the survey
Chrome gives some ssl-shaming for this site that I haven't seen before. An angry red warning and text that says "This site uses a weak security configuration (SHA-1 signatures), so your connection may not be private."
One small quibble, if you are going to take the time to implement progressive enhancement, why serve up incredibly large images?[1] Even sitting on a MBP with a high speed connection, the initial download took some time from across the pond.

[1] https://gdstechnology.blog.gov.uk/wp-content/uploads/sites/3...
Making hacks for Jedi Knight.

Really enjoyed it so I started going to summer camps for coding. Then took classes in highschool, and college. But eventually senior year of college as a C.S. major with high marks on projects and tests I realized I had no idea how to code after a failed internship.

Then sorted stackoverflow by votes and read and tried to understand the first 1000 questions.[0] By the end the change in my coding style was like night or day.

0 - This was before stackoverflow decided to cripple it's usefulness by eliminating open ended questions, so you can't repeat this today.
> String theory has so far failed to live up to its promise

(emphasis mine)

How long should we wait? There should be a Samuel Beckett adaptation...

Valdimir: "Should we start work on some other theories?"

Estragon: "Yes let's"

(They continue adding dimensions to make their predictionless theories internally-consistent)
Per the previous article linked at the top, they tried that: https://www.scrollytelling.io/al-jazeera.html

"In addition we contacted you directly too. After waiting patiently we received no response. After many tries through your editorial office we got hold of an editor who promised to return our call. This never happened either. As a final measure we sent you a DMCA takedown request and waited patiently. No response."
Gotchas and Common Mistakes with Closures in Go
Nike: the battery would last about two weeks
Well... how much should the author assume you already know? I think you'd agree that this would be tedious if he started with a few hundred pages describing calculus - preceded by another few hundred describing algebra. At some point, it's reasonable to assume that the reader has a specific background and that readers without that background aren't your target audience.
Applications of the Vector Dot Product for Game Programming
I know right! I have in my space time actually played around with something similar for this project, and at least for some exhibitions this is something that could be done in the future. Maybe some next incarnation might include this ;)

ps: For full disclosure, I'm one of the Devs that worked on this project though these opinions are completely my own
Yeah this outcome should ensure that no outlet will publish with the proprietary platform again, and that there are controls in place to ensure that it is not available for that to happen.

The "guilty" party in this scenario also seems to be EJC for not properly licensing the original content.

Edit: It also seem very reasonable to think that AJ thought scrollytelling was simply a host of the opensource resource, and removed all links backs except the CDN file that was obfuscated.
Why not the 1541?
I'm worried about the following: Hapless Joe buys a nice, well reviewed, good looking and performant self-driving car. He enjoys it very much for a year, goes for all the required maintenance checks. Then suddenly as he is taking a nap on his usual daily commute the car swerves onto the sidewalk and runs over my wife. Turns out there is a very rare race condition in the path finding algorithm, which makes it do that with astronomically low probability. What I don't want: I don't want Hapless Joe's life to be ruined, he did nothing wrong. I also don't want my wife to become just a statistics. What I want: A crack team of industry veterans get to work. Both engineers from the self driving car company, and independent experts. Since accidents of this kind are so rare they have ample amount of resources to overturn every rock, develop new investigation techniques if must, and nail down all the nodes in the causality chain. Then they disseminate their findings and make all cars on the road, as well as the industry best practices, so much safer.

Is this how you mean the owner's liability to work out? Because then I agree with you. If you want to punish Joe. Take away his savings, possibly his home. I don't see a point in that honestly.
Personally I think they were forced to do it from the games industry, just like it happened with Windows Phone 7, which only allowed pure .NET applications.

However the Android team, which is composed by quite a few ex-Sun Java team members, seems to not share the same love for C++ as Microsoft or the even their own Google clang team do.

While I appreciate the safety we get from Java as the Android main language, Symbian, iOS and WP all managed to have native sandboxes.

> I think it's misrepresentative to try to characterize this as 'just for games'...

I don't think so, because although we are able to use the NDK for coding apps, that is clearly not what the Android team wants to allow us to do, given the list of official APIs, which are all to game development related, even POSIX is only partially supported.

Now in Android N there are changes in place to prevent linking to platform libraries written in C or C++ like libpng and Skia.

It is ironic that we are forced to use JNI to make calls into those platform libraries via their Java bindings.

Also I don't believe that if Jetbrains hadn't decided CLion would be a worthy product, the Android team would have spent any effort to improve the life of NDK developers stranded with their decision to drop Eclipse CDT without any alternative.
And when you call up Oracle for support, they laugh and tell you to GTFO...
Question: why should we take your declarations of who is and isn't a scientist more seriously than the scientists themselves?

Lets take a typical cancer drug. It goes through safty, dosing, and efficiacy clinical trials. In lucky cases, it will show efficacy in a multi-year clinical trial across many geographic locations with hundreds of patients.

If the trial is successful, the FDA will eventually approve the drug, the drug can now be prescribed. The FDA mandates that follow up study is done continuously to learn more about the drug; better indications for use, contraindications for when it won't work, etc.

Where does "replication" come into any of this? Why in the world would somebody replicate a dosing study and generate the same data? That would be unethical, dangerous, and counterproductive. At best, one would throw out bad data that was improperly collected. At worst, one would just abandon the drug and move on to a different candidate drug.

When it comes to human studies that come at real cost to human life, not using all the best available information is unscientific, unethical, should result in civil penalties, and should probably result in criminal penalties as well.

This is the situation that the parent was asking about; by making short blanket statements about what a scientist is and is not, without considering the real issues at hand, makes it seem like you're not engaging the issue.

"Scientists replicate data" is a simple thing to say if you're looking at stars or running a particle collider or working on a new synthetic compound; taking that simple minded attitude is not appropriate for much of the most expensive research out there.

The question of what to replicate and when is a difficult one; it's the tradeoff between new discovery and making sure you're on the right path. If you can make a new discovery that simultaneously proves or disproves that you're on the right path, that's a smarter move, but it's not "replication."
That's correct, that would be misunderstanding. No offense, I'm actually quite a fan of your blog, but this one explanation was easy to misunderstand, in my opinion. I didn't even quite understand, what we are trying to achieve here, and suddenly found myself reading about Perron-Frobenius theorem. Compare it to the explanations at stackexchange, especially this:

> The way MCMC achieves this is to "wander around" on that distribution in such a way that the amount of time spent in each location is proportional to the height of the distribution.

In fact, yes, I read the fifth paragraph, but didn't quite recognize what I proposed as a "solution" earlier before you pointed this out.
> If you're starting with a language that's 2-10x slower you're always going to be behind the curve.

I got involved in a huge discussion about optimizing a web app recently. Things that were learned from the conversation?

1) It turns out moving more frequent cases to the top of an 'if-else' chain in JavaScript offers a greater speedup than I expected.

2) It doesn't matter if you shave 4ms off a request by optimizing your if-else chain if a little later in your code you make 27,000 database queries when you could have made 2.

Knowing how to write a performant app will always be better than writing sloppy code in the fastest means possible.
> Which only goes to say that you can have bad teams anywhere.

Oh totally - much harder to find a good team in India if you are just another corporation looking to outsource. But if you are Microsoft, Google, Twitter or any other well known product company they have no trouble hiring the best and it usually speaks for itself.

I wanted to point out that you can do acceptably well with offshore teams by doing your research, hiring right people, doing proper planning, getting used to more communication than usual and encouraging the team take up authority. Most of these apply to any team but the communication part becomes of more importance when the team is offshore.
At DefCon, someone did a talk investigating the wireless security of some drones. Some of them had a TELNET port open for anyone to log in. The problem here isn't a lack of formal verification, it's a lack of people caring.

There is only one thing that will fix the problem, and that is when corporations get hit in the wallet for having security flaws, see for example: https://medium.com/@xParXnoiAx/irresponsible-disclosure-52d0...
Are you in the US? Google has this terrible system where they "geo IP" then return nonsensical results.

Travel with an Android phone, and watch the Play Store go bilingual, mostly in English, with random parts showing up in e.g. Spanish.
I looked for that on the site and didn't find it. Would you mind linking the page with this statement? Thanks.
SSF one year later: cross platform shell, proxy support and new features
Why is a class in Animation and CGI Motion part of the curriculum in the Artificial Intelligence micromasters program?
A Skype write-off is probably coming in the next 2-3 years, along with many more layoffs. Microsoft will never make its $8 billion back on Skype.
Oops. I’ll see if I can get that fixed.
Previous discussion: https://news.ycombinator.com/item?id=12512618
I'm now wondering a world without left or right turning wheel. Maybe even a right handed UK ?
Why is that? I can see why there would be regulations on brick quality, but why color?