skysight-inc/HackerNews huggingface dataset:
There's a high performance asm.js implementation of WASM (converting WASM to asm.js at runtime). ie if a browser didn't implement WASM, but had a JIT which executed asm.js at high speed, it could execute WASM at high speed
Teslas generally don't charge to 100% at a supercharger -- it's much faster to charge lower and more frequently.
Yeah, good point. I presumed it would be a pain, but I never thought to see if someone actually tried it.

Though you shouldn't be compressing things over TLS. I think the only proper solution is to pad out all articles (and images) to the nearest 2kB or something so that you can't figure out the length (randomness can be thwarted by forcing refreshes).
> I guess I should have added the caveat that I want to be getting eight hours fairly consistently. How often would you say you have less.

Right now, I'm sleep training a baby, so less. My goal is 7 hours and I really enjoy 8. And I can get this consistently.

> When doing heavy weight training, it's more or less a necessity.

I've been a gym rat for many years and I can attest to this. Not enough sleep and your tanks are empty, no power.

> (No kid at this point, I'm sure that will change things once I do have once)

Kids make you focus. You cut out things you wasted time on and you're back to where you were. Less time wasty, more family and relationship. Works out well.
Well they do have a search that works reasonably fast, so they have the infrastructure already. It's just not that good. It's a algorithm/methodology issue. I can understand if they were still in startup mode or it wasn't 2017. I'm not saying the method I mentioned would be a solution for something on reddit's scale but we live in an age of readily available data analytic solutions and open-source search engines. An open-source solution like Solr would work, I just don't think reddit has any motivation to solve the issue.

Edit: Found this on reddit's wikipedia page:

"On July 21, 2010, Reddit outsourced the Reddit search engine to Flaptor, who used its search product IndexTank.[91] As of July 12, 2012, Reddit uses Amazon CloudSearch."

It seems to be an implementation issue, not a technological one.
Millennials are less keen than previous generations on illicit drugs
I assume once Robinhood's compliance team finds out about this, his account will get shutdown, or maybe he'll be asked to collect KYC information for all the people trading on his account.

Maybe it helps that users vote instead of directly invest.
Neat.

::clicks on a random word::

"We couldn't find any sentences for the word centripetal."

So... Why is it one of the chosen few?
For Modern Astronomers, It’s Learn to Code or Get Left Behind
The pendulum has swung back to just a straight caloric deficit as the cause of weight loss (so yes, 1800 calories of sugar when the body expects 2000 calories causes weight loss). His hypothesis isn't panning out..

The NuSI experiments that were suppose to prove the insulin hypothesis but showed no metabolic advantage for low carb/high protein/fat diets.

The one advantage the low carb diet does appear to have is satiety; fats just leave you simply feeling fuller longer. But there's nothing metabolically magical about them.

https://www.youtube.com/watch?v=MiUyjMjuLl0&t=674s

The low fat/high carb group actually gained a longer-term metabolic advantage vs the low carbers..
New discuss forum for LXD, LXC and related projects
https://discuss.linuxcontainers.org/

We've recently started a new discuss forum to better connect with the community. It's available under the link on top of the post. Here you can get updates on new features, what we've been working on and plan to work on and also get help from us devs and other community members. :)
One thing that bothers me is that people tend to expect miracles. I usually tell them it will take as long as it took to fuck it up to fix it. But that doesn't mean that you can't have some initial results to point the way in a short time. It's more about establishing a process and showing that there is a way out of the swamp than that it is something super tricky or difficult. Just follow the recipe, don't let yourself be distracted (this can be really hard, some management just can't seem to get out of the way) and keep moving.
> I'm assuming this is just temporary and eventually it's just smooth sailing and you get sleepy?

After reading this again. Yes, the goal is a habit that puts you into a rhythm. The place you want to be is to not need an alarm to wake up and to wake up with light (natural or not). Now I like sleeping too much for this to work. I'll happily stay in bed for 10 hours. More than that and my body starts hurting...

( Artificial: http://www.usa.philips.com/c-m-li/light-therapy/wake-up-ligh... )
I've also thought it'd be nice to have a way for repo members to quickly send a warning to someone without spamming the thread. In this case, it'd be nice to have a way to put a specific person into a cool down period.
The problem is that everyone does that slightly differently.

Having a stdlib function makes for an easy "let's just use this everywhere" answer.
Steve Omohundro has written on this topic, predicting that a certain set of features (termed Omohundro Drives) will appear in all sufficiently advanced AIs.

https://selfawaresystems.files.wordpress.com/2008/01/ai_driv...
My home ISP can not see my DNS packets. Those are the adversaries I am defending against specifically. All DNS packets on my home ISP are encapsulated in a VPN to my VPS nodes. I also pre-cache popular requests via cron and via settings in Unbound.

From there, for sure, the risk increases. I am not sure I trust DNSSEC to help me much. That said, I rotate through many local recursors at each location, so they have to rewrite my traffic right as it leaves my node. That is doable, but that isn't really what I am defending against. Anything I care about, I validate in a script and write into /etc/hosts.

You are correct, there are not that many recursors that support TLS.

Beyond that, things like software updates I don't trust DNS at all and certainly not public mirrors. I validate packages with GPG signatures. Even that is tricky, because chicken+egg, so I validate the GPG sigs from trusted sources.

On a funny side note, you would be surprised how many people rely on trusting GPG keys that are contained in a package, signed by those same keys, in the same repo.
This website doesn't work in Safari. Google Chrome is required. Back to IE6 age...

UPDATE: Nevermind, it started to work after couple refreshes.

UPDATE: Actually, 'home' section started to work, 'phone' section still doesn't work in Safari.
The comparison you appear to be hinting at is poor. A better fit:

Suppose the Holocaust had gone down a tad differently. Instead of a German army sweeping across Europe, the German Nazis had simply migrated to neighboring countries. Let's say that Poland was mostly Jewish, and that German Nazis generally agreed that German Nazis shouldn't convert to having Polish/Jewish culture. So the immigration happens, and the Holocaust follows. Would it have been wrong for those Polish Jews to build a wall or impose a German Nazi ban?

Similar cases have actually happened. Consider the North American aborigines (American Indians, native Americans, etc.). They did not prevent immigration from Europe, and they paid dearly. Consider the Christians in Lebanon, frequently slaughtered by those who have immigrated in the last 70 years. All the world over, since the dawn of time, things have often gone very badly for those who failed to defend territory and preserve it for their own group.
Deprecating it in the browser will kill any developer ecosystem. No one will write Chrome Apps anymore.
Perhaps you have never seen the trails of broken dreams leading out of introductory proof-based math classes.
New Shadow Brokers 0-day subscription forces high-risk gamble on whitehats
It was a great technology fun bit of history my company was in a bidding war with Computer Associates for it when SGI decided to dump it, sad part was we where a profitable CBT company that had the extra development capacity to support it. Sadly we did not have the pockets that CA had and therefore where outbided, we knew it was the death of Cosmo Worlds and had to adjust course pretty rapidly, sad part was there really was no competitor for real time web based 3D at the time. VRML had a chance until Cosmo Worlds died. We ended up moving all of our CBT to the unreal engine and retreating back to the desktop. Back then I wrote a pretty popular collision detection library for VRML.
Yeah, doesn't Google have something like a 6.7% stake in Uber? Even with share diluation by half, at a $60bn valuation that's still $2bn. Do we really think Google can win much more than $2bn in this Waymo lawsuit?
How Physicists Used Science to Beat the Odds at Roulette
Synology uses btrfs by default for a NAS product, and I find it hard to believe they'd pick that for a product whose explicit goal is reliable storage if it were full of dragons.

Once something gets a reputation for having issues that reputation tends to stick pretty much forever. I'm thinking maybe older versions of btrfs were problematic and the FUD has never gone away.
Bakers Are Cashing in on Instagram’s Cake Obsession
> The way things are, right now, Chrome is much better at protecting apps from each other than my Linux desktop is.

I have a hard time believing that. With a ton of stuff all running inside of Chrome, it's much easier for them to access each other's data than if they were standalone apps. Further, since Chrome is such a huge attack surface, I would expect it to be less secure than a smaller, more specific application.

On that note, I can go look at my Linux distro's security and bug tracking systems and see all of the known security issues and bugs affecting almost all of the software on my system. Does anything like that even exist for Chrome Apps?

> If, for example, the Cleanflight or TeamViewer apps were regular apps, a bug in them would fully compromise my account.

Isn't that the case whether it's a Chrome App or not? Chrome has a huge attack surface, so it seems there's an even bigger chance of hitting a bug or being affected by an exploit.

The bigger problem seems to be that you're running apps that you don't trust, while I can trust my Linux distro to have safe software in their repositories. Barring bugs, I generally don't have to worry about installing malicious applications.

I'm not sure Google does any kind of vetting for Chrome Apps, but I'm not sure I'd trust them even if they did. They are the largest ad tracking company in the world after all.
Creepy Text Messages – THE ROAD TRIP
Any video editors got a few minutes?

There's an open video stabilization request here: https://www.reddit.com/r/ImageStabilization/comments/6e1mgj/...

So far there's https://streamable.com/lrkhg which sorta gets partway there.
Edit Fraps Videos in Davinci Resolve Without Hassle
I hope your insurance is up to date. That sounds like a trip hazard litigation waiting to happen.
An unofficial WWDC app for macOS
A Puzzle of Clever Connections Nears a Happy End
Are you aware of something similar for Biblical Greek?
> If the cost is less than the savings, the business should see this as a no-brainer, and the only restraint would be scheduling a time to get it done. (Not having it might cost more, but it might not cost as much as failing to get other necessary work done.)

And that's the crux of the problem. The business invariably mistakenly believes that piling more features onto the steaming pile of crap that is the codebase is the better solution. Add on to that that some mid-level PM promised feature X to the C-level in M months, where M is such short notice even a engineering team with cloning and time machines would be short-staffed, and was chosen without even asking the engineering staff what their estimate of such work would be.

To the business, the short term gains of good engineering practices are essentially zero. The next feature is non-zero. The long-term is never considered.

I've had multiple PMs balk at estimates I've given them. "How could internationalizing the entire product take so long? We just need to add a few translations!" No, we need to add support for having translations at all, we need to dig ourselves out from under enough of our own crap to even add that support, we need to figure out what text actually exists, and needs translating, actually add those translations, and we need to survey and double-check a whole host of non-text assets because you mistakenly believe that "internationalization" only applies to text. Next comes the conversation about "wait, you can't just magic me a list of strings that need translating? I need that for the translators tomorrow!" No, they're mixed in with all the other strings that don't need translating, like the hard-coded IPv5 address of the gremlin that lives in the boiler room eating our stack traces.

Then, later, we'll lose a week of time because the translation files that engineering provided were turned into Word documents by PMs. One word doc, with every string from every team, and then those Word docs got translated. So now we have French.docx, but that of course only has the French. So now engineers are learning enough French to map the French back to the English so they know what translations correspond to what messages.
> I would argue that getting everything to build on a central system (some sort of CI) is usefull as well, but before changing, testing, db freezing, or anything else is possible, you should try to have everything you need on each developer's machine.

I'd extend this and say that the CI server should be very naive as well. It's only job is to pull in source code and execute the same script (makefile, whatever) that the developers do. Maybe with different configuration options or permissions, but the developers should be able to do everything the CI server does in theory.

A big anti pattern I see is build steps that can only be done by the CI server and/or relying on features of the CI server software.
Don't know about you, but I won't get out of bed for any less than $500k
They can do demographic tracking, brand tracking and other retargeting type advertising.
That's a dumb reason to drop the "v". smh
Actually, the AOT optimization path for asm.js has been supported by Internet Explorer/Edge for quite some time. Chrome also supports AOT asm.js path now through their wasm implementation[1]. Before that Chrome and Safari did optimizations that just happened to make asm.js faster ;)

It's likely that if WebAssembly didn't happen everyone would've implemented AOT optimizations for asm.js and all the new features (shared memory threads, simd, 64bit int etc.) would be targeting that instead.

[1] http://benediktmeurer.de/2016/12/20/v8-behind-the-scenes-dec...
> EVs have all of those things, and they suffer no less wear-and-tear than ICEs.

Brakes suffer less wear and tear.

Water pumps may be present, but they are not for the engine. If present, they are usually for an actively cooled battery. They are needed mostly for charging operations and do not run all the time. Meaning less wear and tear on them. They are also electrically operated, so there's no belt wear and tear.

Batteries very seldom suffer catastrophic failures, as opposed to, say, a transmission.

EVs can be much simpler than ICEs. Currently some of them are not, but they can be. The list of things that EVs do not have is even larger than the things they do have in common with ICEs.

Anyway, I will concede the point as being generally true – there are lots of other things that may break and are shared no matter how you power the car.

However, there's something that's harder to measure: everyday annoyances caused by parts that are "working", but not as well as they should. Engines with low compression, faulty spark plugs, or partially broken sensors feeding incorrect data to the engine's control unit. Things like that make the car feel "old", cause multiple annoying trips to repair shops, and lead people to replace their cars. Modern AC motors will run much longer, and just as well as when they were brand new. They are certain to outlast the battery that feeds them.
By that point "the site delivered an average of 100 million video views per day". Otto never delivered anything.
There are many factors in this, such as proximity to the blast, elevation of the nuke, surface shape and soil/sand content, wind direction, ambient temp, humidity levels, your age, your pre-existing health condition.

There are way too many factors to generalize any proper response. If you are too close to the blast for the filtration in a car to be of use, you will probably be in a state of shock anyway, so just get in, drive away, go to the closest convenience store, help yourself to water, food, etc and drive away as fast as you can. Otherwise, if you are in a busy city, ya, yer pretty much out of luck.

Oh and this is just a guess, but save up on bottle caps.
My commute is really short. I don't drive long distances very often, so I think it would make a difference.

Another way to look at it is if I could get one extra kWh per day from solar and can go 3.3 miles per kWh, that's about 100 extra miles of range per month. I typically drive maybe 200 or 300 miles per month, so that's a pretty big reduction in total plug-in power that I would need. (In our Oregon winters it might not help so much, or if I can't reliably find sunny parking spots.)
Aren't entrepreneurs already a class of outliers? I'd be interested to see if there's any research on productivity and how it's related to self-reported relationship with ones work or product and occupation.

Probably the most proximate and salient example for me is mathematicians. A lot of them seem to have an almost monkish devotion to math, and breaking their brain day in and day out with little reprieve doesn't seem to bother them at all.

Although entrepreneurs are probably not nearly so eclectic, I don't think it's strange to think they might be somewhat exceptional in this regard.
There isn't such a polyfill. There is currently no good tool to translate wasm into asm.js (or general JS) on the client. The best that exists is to run the wasm in a wasm interpreter, very slowly.

In theory a translator could be written into asm.js, but there would still be wasm code that won't run fast, such as 64-bit ints, unaligned loads and stores, bitcasts, and other operations.
One of the nice things is that you can just let async functions fail and they won’t throw asynchronously and kill the process. So no, error handling isn’t important to include in a small example.
I remember reading on http://reddit.com/r/talesfromtechsupport some time ago (I unfortunately don't remember what thread) about someone who decided to move their server rack. Said rack had a UPS, but no wheels.

The 10k HDDs in the blades didn't really like it...
On what grounds do you consider a claim "remarkable"?

This also isn't a standard of admittance that would work terribly well for minorities.
It's definitely a challenge trying to balance portability with support for platform specific features but I'd be a little hesitant to draw general conclusions from the two big examples since both Adobe and Sun were notoriously negligent platform maintainers addicted to haring off after some shiny whim before fixing what they had already built. Even simple things like if Sun cared about non-server performance in the 90s or if either of them had figured out how to properly package and ship updated before the 2010s could have improved their reputation immensely.
Which makes it a much tougher problem, therefore harder to have as much impact as on a truly neglected problem.
A more in-depth explanation of journaling vs soft-updates:

https://www.freebsd.org/doc/handbook/configtuning-disk.html
What you said is true, however...

I am referring to the initial offering of Native Client for inclusion into FireFox.

Since this did not happen, Native client did not see the uptake it needed— and the team was destaffed.

Since it was a working platform that actually existed and let you use a modified version of LLVM, it was quite usable.

We could of have powerful native sandboxed apps quite a long time ago if FireFox became PNaCl compatible.

Instead, Mozilla envisioned that the JIT could eventually bridge the native performance gap.

Mozilla defended this ideas such as ASM and emscripten.
And now Mozilla is coming close to a more open and performant web.
Can I still install and use via a nuget package? It looks like it's integrated with all those crazy npm tools now but I'm not sure if that's just for development nor usage.
It would be humorous, but instructive, to have something like this for Java that parses it and dumps out metrics about the tree size for a project - AST node count and static depth, where possible to tell.
Thanks! And I suppose I can't really argue with that.

I mean, I could, but not with any conviction; on the one hand, I opted against college and found my early adulthood less circumscribed in some ways thanks to an absence of terrifyingly sizable debt - but on the other hand, I'm not about to try to pretend it's anything other than the clear partiality of almighty God, or if you wish a frankly implausible degree of good fortune, that's made it possible for me to build, on the strength of a high school diploma, even something vaguely resembling a software engineering career. Were it not for so many things going my way that sometimes it keeps me up at night just with the thought of how things would be if even one of them had broken differently, I'd be doing well to make $15 an hour in a job that prompted daily fantasies of suicide. So any criticism I might presume to offer, of the fashion in which you've achieved all that you have, would I think have to be pretty laughable on its face.
>and oil change costs about $50, once a year - if you're actually urban, you might not rack up 5k miles in a year, and could get by on a single oil change

Um, that's a really bad idea. Even if you are using 5k rated oil, you should get your oil changed every 2.5k or so if you are always in city driving.

Why is that?

Severe conditions. Pretty much every oil bottle and car manual says change your oil more often in "Severe conditions". Of course most people think of severe as stomping on the gas and going 100mph, or driving in mud and deep water, or something else just as crazy. Of course that's only part of what your manufacturer calls severe, this is also called severe conditions

* Driving repeated short distances.

* For extended periods of idling or low speed operation.

* More than 50% of driving in heavy city traffic in temperatures above 90°F.

* If using brakes extensively.
Uber's board to receive Eric Holder report on Wednesday
What is amazing is how cool are the people in the video. Instead of running out screaming they calmly do their job.
Have you ever tried to run more than one operation at once and collect the results?

(There are lots of other reasons to use the promise abstraction – having a type that can be transformed is extremely useful and natural – but that one’s pretty significant.)
If he is looking to protect his reputation, AND he is actually innocent, even at the expense of the money he should be wanting to tell his side of the story despite a lawyer telling him not to talk.

My, admittedly cynical, take is much simpler, his lawyer sat him down and said something along the lines of: "screw the 250 million, keep your damn mouth shut if you want to stay out of prison".