skysight-inc/HackerNews huggingface dataset:
Yes. I don't know but I assume for reasons of DRM:

https://help.netflix.com/en/node/23742
Entrepreneurship course: Ideation
Antibodies are too large to pass through the filter in the kidneys. Lower molecular weight fragments of antibodies are usually reabsorbed in the proximal tubule of the nephron.

Their fate mostly lies in catabolism, i.e. they are broken down and the components reused. Biliary excretion accounts for a very small amount of the elimination of IgG antibodies.

[0] "Pharmacokinetics of Monoclonal Antibodies" http://onlinelibrary.wiley.com/doi/10.1002/psp4.12224/pdf
Chinese crypto industry undaunted by crypto ban
I'm well aware, and really happy about the work the EU's competition commission is doing. Unfortunately, for US-based corporations, global change is unlikely to happen until the US steps in.
1) A new dependency to install on every build server and dev's machine unless you're a 'nix only shop (e.g. not in gamedev) and sometimes even then (yes, I've had to apt-get install make) - at the very least this is a boatload of new setup/install instructions, in practice this also involves coordinating with IT, and heaven help you if you let your less programmery coworkers build from source too.

2) Which version of make? I have detailed instructions at work about which make to use with which makefiles such that all the stars align and the OS vars and other gnu tools line up such that our upstream Makefiles work without modifications (well, usually.)

3) Given the complexity of 2, what I'm actually going to do is automatically invoke make from whatever build system we're using internally.

4) Now that I have two sets of build configuration, I have a continual maintenance burden as conflicting dependencies and incompatible build settings need to be resolved. Since I deal with C++ libs and tools, sneezing too hard will cause incompatible libs. In practice, the Makefile will hardcode CCFLAGs, sometimes CC itself, and things like building with/without RTTI will cause incompatible libs I can't link without more Makefile tweaks.

5) When I get sufficiently fed up with the state of affairs in point 4, I'll integrate the tool into our own build system such that we have a single unified build system again and I don't have to make the same change in 5 places (our codebase + a measly 4 dependencies in this example.)

At this point I'm no longer using make and wondering why I didn't just skip directly to step 5 in the first place. Make is simple - so simple it doesn't address my needs nor solve my problems.
Yeah, but we mention 4G, pressurized cabins, what-have-you.

My point is that of all the futuristic fictional technologies that ST presents and deals with: teleporters, replicators, phasors, warp drive, etc... they never ever even mention the artificial gravity. (Spoiler alert: There is one part in one of the movies where the bad guys turn it off on a ship during an attack. But still no one actually talks about it.)

Arguably, gravity control would be a huge thing (Larry Niven has a book where one of the characters has developed g.c. and done spectacular things with it.)
A fair number of people are already running the Chrome NaCl client in their browsers but it is CPU only.

http://folding.stanford.edu/nacl
No.

The problem is that people all too often see the passing tests and think, "Great, I'm done!". They don't take the time to evaluate whether they have thought of all cases.
It's a shame that Netflix is not allowing to download everything in their catalogue like Amazon Video does. A lot of movies and shows are not downloadable in my region.
As a systems engineer, I struggle with this virtually every day. We're called 'DevOps' by most and anytime we encounter a new problem, everyone invariably screams for containers. Containers aren't a magic bullet.

My favourite example is when our AWS TAMs offer a solution, knowing we have ZERO pipeline/infrastructure setup for supporting containers. They always push containers. We don't use containers, stop forcing them down our throat. We've tried, we've been burned, VMs work for us. Stop!

When did containers become perceived as the end-all solution? I see their value and uses but they don't meet ours so why have we started ignoring the right solution for the job? I see this everywhere I go.
HC 508 Amiga 500 accelerator available at Alinea Computer Shop
Some tests on my system: including everything at the root of /usr/include: (intel 4770HQ)

$ for file in /usr/include/*.{h,hpp} ; do echo $file | awk '{ print "#include \"" $1 "\"" }' >> /tmp/test.cpp ; done
$ (laborious step consisting in removing headers that don't play nice with others... in the end there are still more than 1425 base headers, which end up including most of Qt4 & Qt5, boost, etc)
$ time g++ -E /tmp/test.cpp -fPIC -std=c++1z -I/usr/include/glib-2.0 -I/usr/include/qt -I/usr/include/glibmm-2.4 -I/usr/include/glib-2.0/glib/ -I/usr/lib/glib-2.0/include -I/usr/include/gdkmm-2.4 -I/usr/include/gdkmm-3.0 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/atk-1.0 -I/usr/include/qt4/ -I/usr/include/qt/QtCore -I/tmp -I/usr/include/qt/QtWidgets -I/usr/include/qt/QtGui -I/usr/include/KDE -D_FILE_OFFSET_BITS=64 -DPACKAGE=1 -DPACKAGE_VERSION=1 -I /usr/include/raptor2 -w -I/usr/include/rasqal -I/usr/include/lirc/include -Wno-fatal-errors -I/usr/include/lirc -I/usr/include/gegl-0.3 -I/usr/include/libavcodec -I/usr/include/freetype2 -DPCRE2_CODE_UNIT_WIDTH=8 -I/usr/include/python3.6m -I/usr/include/libusb-1.0 > out.txt

1,82s user 0,18s system 99% cpu 2,013 total

out.txt (the whole preprocessed output) is 710kloc and 23 megabytes.

With clang:

0,72s user 0,08s system 91% cpu 0,875 total

so I'd say that in general, preprocessing time is fairly negligible. A few template instantiations will take much more time to compile.
> A similarly powerful IDE better integrated with the rest of the system would be better

Does one exist? (I'd preach vim to you but I don't want to perpetuate editor wars.
Sure, if you day trade. But if your timeline is 20 years, none of this matters. If you believe the market will be here in 20 years, index the S&P and get a good nights sleep. If you don't, invest in guns and ammo.
Some ripping groups (particularly Russian ones) have started putting ads in front of the videos, and super-imposed logos in the corners.

Pretty brazen, if you ask me.
Shouldn't I be able to edit this for a little while? Strange, only two minutes later and I can't edit. It had no replies.

I tried adding this quote from the linked paper:

> Thus, IgG elimination occurs mostly through intracellular catabolism by lysosomal degradation to amino acids after uptake by either pinocytosis, an unspecific fluid phase endocytosis, or by a receptor-mediated endocytosis process.

Explanation of two words in there that maybe not everybody knows:

pinocytosis: The ingestion of liquid into a cell by the budding of small vesicles from the cell membrane.

endocytosis: The taking in of matter by a living cell by invagination of its membrane to form a vacuole.

EDIT: I can still edit this comment more than five minutes later, as expected. Hmm... why could I not do that with my first comment...?
A Detailed Timeline of the IMAGE Mission Recovery
You need containers to run on Kubernetes my dude. And running on Kubernetes is critical.
Why is the patent office approving so many patents on non-novel things? While we don't get as much visibility into what they're rejecting, it seems like they're a rubber-stamp factory and are offloading their job onto the courts.
On HN, could you please not conduct arguments like this in the flamewar style?

Making this about "young" people who come from "web dev" is flamebait, which predictably takes the discussion into inner circles of hell. That's just what we don't want on HN.

You've done this kind of thing more than once before. That's bad. If you'd (re-)read https://news.ycombinator.com/newsguidelines.html and take the spirit of this site to heart—intellectual curiosity and thoughtful conversation—we'd appreciate it.
The other mistake that Sun made with Java was its linguistic supremacist "100% Pure Java" propaganda campaign: you should rewrite all of your code in Java instead of expecting Sun to provide you with easy seamless interoperability with existing languages and libraries.

So Sun's JNI and applet web browser integration languished while Microsoft integrated COM and CLR for seamless interoperability with the web browser and other languages like C++ into Java and CLR.

Sun also had an unholy obsession with code generation, since their attitude was to breed as much 100% Pure Java Code into the world as possible (see AspectJ, JAXB, etc). While C# took a much better approach of supporting code annotation and metadata and reflection and bytecode generation at runtime so you didn't actually have to generate and compile a huge pile of boilerplate source code (see PInvoke).

https://docs.microsoft.com/en-us/cpp/dotnet/how-to-call-nati...

http://www.pinvoke.net/
Threema appears to optionally do the exact same thing. Signal eschews the flexibility to ensure more universal usability by being able to assume that anyone who uses signal can be associated with their phone number. An assumption that holds for the vast vast majority of potential users.
Marvelous Designer 7 Full and Crack (Win and Mac OS X)
Both. WSL works by translating Linux calls into appropriate Windows calls under the hood. The Windows file system is already comparatively slow, and the interfaces aren’t especially similar, which means that you end up using a not-fast translation of a medium-fast filesystem implemented on top of a relatively slow file system.
LT-STIB = Linear Transformations w/ Soft Thresholds In Between
I am a paying customer for Netflix and Primevideo and I just had to pirate the Altered Carbon tv series because I play it on a ultrawidescreen monitor (21:9, 3440x1440) and the Netflix web player is putting black bars all around the videos (horizontal and vertical black bars). This is because the video is supposed to be played on 16:9 with horizontal black bars only.
With the pirated version I can just tell MPV to apply an autocrop script and use much more space on my monitor.
Excessive DNS queries for NTP pool addresses
Please make your comments civil and substantive.

https://news.ycombinator.com/newsguidelines.html
> Health - beyond the obvious effects on the emergency room, what else? Ambulances willl quite clearly be affected. Why would someone wait minutes for one to arrive when they can just hop in an autocar to go the hospital? Or would the entire emergency room itself be on wheels? (Less likely.)

Well, the car can't go through red lights or overtake in certain locations to get to the hospital more quickly. That could be an easily ignored issue in some cases (if traffic is light or if it's easy to get to the hospital from your current location), but good luck if there's a traffic jam or the car needs to ignore certain laws to save your life.
I like ideas. It's a shame idea threads are not a good fit for HN.

Where is a good place to talk about random ideas?
I still don't understand the fear of the Windows dos prompt. In the terminal section [0] he suggests Hyper:

> it is an Electron based app and it’s a bit sluggish but works well, scales well and looks like it’s 2018.

Electron? Would anyone in the Linux world accept an Electron prompt?

All you need is Git + clink [1] and you get a ton of GNU tools + readline/history. Then it's as fast as possible and you get sharper and clearer fonts than all the other pseudo windows terminals. This is the stuff that's really important to me.

I couldn't get console to handle vim colours (although 32-bit colours is supposed to be there now) which is a real shame. Plus certainly there's no bold / italic.

[0]: https://cepa.io/2018/02/10/linuxizing-your-windows-pc-part1/...

[1]: https://ianchanning.wordpress.com/2014/10/29/dos-command-his...
If you don't consider an OS process a sandbox at all, why are even talking about security here?
As an aside (and since you brought up snapshots), mobx state tree https://github.com/mobxjs/mobx-state-tree seems to have combined the ease of use of Mobx with the power (and beyond) of Redux and its ecosystem.

I watched a video about Vuex last night, and with mutations, it seemed more convoluted than mobx state tree.
Marcus' article mentions Hinton's recent misgivings about backprop:

"Perhaps most notably of all, Geoff Hinton has been courageous enough to reconsider has
own beliefs, revealing in an August interview with the news site Axios 16 that he is
“deeply suspicious” of back-propagation, a key enabler of deep learning that he helped
pioneer, because of his concern about its dependence on labeled data sets.
Instead, he suggested (in Axios’ paraphrase) that “entirely new methods will probably
have to be invented.”
I share Hinton’s excitement in seeing what comes next.
Each Hacker News commenter believes that the exact set of topics that they are knowledgeable on are requisite to be a software engineer.
I second Gajim especially 1.0.0 version that looks good. There is also https://dino.im but that's still in alpha.
>We know how human beings are supposed to live to be happy: small communities of stable relationships, with a lot of face to face time, ideally spending some of it outside doing some sort of physical activity.

That's how we used to live, in small roving bands where all males are close relatives. Total lack of privacy. No dentists. Parasites. Obsession with the spirits that apparently lived in trees and rocks, also the evil spirits which brought disease and thunderstorms (cholera not having been identified). Endless wars with other tribes...

https://images.huffingtonpost.com/2015-04-28-1430240960-5078...

Now, obesity has replaced malnutrition. Distraction has replaced boredom. Social media has replaced gossip. These are better problems to have and they're solvable in turn. Then we'll see what the next problems are.
> Somebody (Geoffrey Hinton, Andrew Ng, I don't remember exactly) made the point that neural networks were in a pretty moribund place, until the confluence of three things came along: more compute power, more data, and algorithmic improvements. Given that, one wonders what other older ideas are waiting to be resurrected by a similar confluence.

Andrew Ng says something like that on his deep learning Coursera course.

Also, Animats mentions perceptrons. A neural network is a generalized (combination of) perceptron(s) on steroids. That ceiling was basically removed again with the advent of the above-mentioned improvements. Similarly, the gradient descent used to optimize a neural network resembles hill climbing, as well.
What are people doing abut this?

https://www.wired.com/story/self-driving-cars-power-consumpt...
Reminds me of this: http://www.mongodb-is-web-scale.com/

"Docker, docker, docker!"

Edit: I'm not knocking either of these products - I actively use Mongodb in production. I like docker/containers/Kubernetes and have used them for various projects. I just take offence with how people have started ignoring common sense, like: we don't have the tooling in place to support this product, or: it doesn't meet our business needs.
"There are growing concerns the cyber-attack was Russian in origin, and was a response to the fact the Russian Olympic committee was banned from the games in December – along with nearly 200 Russian athletes – because of state-sponsored doping at the games in Sochi in 2014."

Sounds like paranoia.

"Pyeongchang 2018 spokesperson Sung Baik-you refused to confirm the country behind the attack but said: “There was a cyber-attack and the server was updated yesterday during the day and we have the cause of the problem."

Why not give the proof to the people?

"“We are taking secure operations and, in line with best practice, we’re not going to comment on the issue because it is an issue that we are dealing with,” he said."

Wait, didn't they just say it was Russian or not?

"“We don’t reveal details in public because actually at the moment, we are making sure that our systems are secure, which they are, so discussing details is not helpful,” he said. “But we will have a full report and, I guess, it will be made public.”"

Okay, I'm still confused, they don't give out details but told us it was Russian? Who is lying here? Do they think it was Russian or id the media just jumping to conclusions like usual?
I agree except for the "greater extent than is traditional".
Otherwise than the statement implies, there isn't one, single, traditional attitude towards weirdos that would be shared across different civilisations.
Indeed, some cultures eg. held the mentally ill in certain reverence (native Americans, Russians and "yurodivy", etc.)
Yeah, the best way to handle this is with a version in the path and then the host can knowingly/willingly upgrade the library version and SRI hash at the same time.
Derailment of a passenger train near Wimbledon, south-west London, 6 November 17
Asciinema version 2.0.0 was released
Dan Brown has donated €300,000 to digitize 4,600 ancient books
There is/was discussion in the standards body of using the SRI hash for exactly this purpose. It sounds really promising but iirc there was a privacy kink to work out.
Nice to see something I wrote 7 years ago hasn't gone entirely to waste. Spot the 'ancient' technologies like Solaris and perl mentioned there...
It's easy to jump to conclusions on why you'd post this quote here.. Instead, maybe you could expand on what this quote means to you (in this context)?
More or less, yeah..
That's not even true, though. The highest concentration of Scandinavian-Americans is is in North Dakota, where they make up 1/3 of the state's population, and have a poverty rate that is significantly above zero.
The problem is not the label "ritual", it's the way the word shuts down all further discussion.

Why? "Ritual." Done.

But that doesn't actually answer "why" it just gives it another word.

Another example in the same light: "How was the world created?" "God" vs "How was the world created?" "Big Bang".

In both cases you have answered nothing. You just used another word. "How was God created?" "Don't know", "How was the Big Bang created?" "Don't know".

Using a scientific sounding word does not actually answer the question, anymore than using the word "ritual" answers the question.

Instead the lack of knowledge should be made explicit, and not hidden behind a "comfort" word. (I.e. a word used to make you feel better about not knowing.)
> Vue [...] works with Typescript too.

It """works""" with it. React's story is much better on this front. I set up Typescript with Vue at work and:

1. Setting it up and getting it to compile was hell. The documentation was incredibly poor (often out of date on several options) and I often had to try several things just to get it to compile.

2. It was slow with Webpack - far, far too slow to start up (what was once 10 seconds to start up easily was taking 45+). tslint was a no on top of that. I looked into various ways to speed up Webpack, wasting hours trying to parallelize things with various plugins, and found almost everything would just refuse to work with .vue files.

I got this fixed, thanks to fork-ts-checker-webpack-plugin - which didn't actually have .vue support at the time. I ended up having to use a fork by the amazing David Graham [0] which thankfully has been merged now.

3. Vue's "support" for TypeScript isn't there yet. It's maybe 80% there. Vuex isn't typed - which, at least for my company's SPA, kills half the benefits of type safety and requires a lot more type annotations than is pleasant. (Yes, I'm aware you can get Vuex working with some serious hacks... but this isn't documented, and I found out it was possible from GitHub comments. It did not look easy enough for me to do without an hour of pain, so I have yet to try it.)

Also, you can't strongly type props in both directions using the standard template language. In fact, I'm not sure you can strongly type the things you give to a component, only the things you take in... if you use a third party library [1], which modifies an official new way (ES6 class syntax) to declare Vue components.

You could use JSX - which Vue supports - but again, you're going off the beaten path and aren't really writing standard Vue components. Swapping to JSX was not possible at my company - requiring developers to learn an entirely new templating language when they already know Vue components is a no. It's a wonder we're okay with ES6 class syntax.

All this is to say, standard Vue components can't be fully typed. Not only do you have to use a new way to declare them, you have to use a third party library to get proper typing for props and more. And it's still not enough unless you swap to JSX too. (I'm not even sure if JSX would end up working for full type safety, either - Vue might have some stupid thing which screws it all up.)

---

Compare this to React, where because of JSX you get strong typing on literally everything without special hacks. They're not the same here.

Vue is moving very nicely in the direction of more and more TypeScript support - I'm a huge fan of that. I'm glad we swapped over at work. But right now, claiming Vue supports TypeScript is misleading. It's a second class citizen. You're not getting the full benefits. This seems to be changing, but glacially.

(Am I allowed to say that something which might take less than a year is glacial? I guess this is just how web dev is.)

[0] https://github.com/Realytics/fork-ts-checker-webpack-plugin/...

[1] https://github.com/kaorun343/vue-property-decorator
> On one hand, when many sites use jQuery (for example), there’s huge benefits (bandwidth, speed, etc) in having it loaded from one location relatively infrequently and cached for many pages. This is exactly the promise of shared libraries, just on a much wider scale.

This is an interesting comment.

So, packing all the JS into one file + optionally removing unused symbols would be similar to statically linked binaries. If optimized well, this would be the smallest amount of code / binary a system has to load to execute the program, but if you have multiple binaries, you might load the same library code multiple times. And security updates of libraries require you to recompile everything. But, in this context, you have to trust basically one JS-file from the host you're accessing.

On the other hand, dynamic libraries minimize the bandwidth / memory required to hold the code for a set of binaries, because libc/jquery/... just gets loaded once, instead of once per application. And, technically, shared libraries simplify security updates - update openssl, restart services, and hope that RHEL tested well so you don't end up with a mess. This would be really cool, if you think about it. Depend on magic-js-provider.acme.org/jquery/2.1.x.js, and get security fixes like that. Except the testing would be a nightmare.
Just don't use redux. Maybe one day there will be a decent, ergonomic framework on top of the flux architecture, but redux ain't it.

Try mobx state tree for all the benefits that redux has without the pain.

Vuej seems nice enough (especially for migrating server side tech apps), but I'm still not digging the templating engine. I've seen the way you can use JSX in Vuej, and I don't like it.