skysight-inc/HackerNews huggingface dataset:
You don't think conflicts of interest can create perverse incentives or be problematic? Conflict of interest != criminal conspiracy
tell me about it! Or, heaven forbid, just make the user get the entire html page rendered from server after every click like it's 2003 or 2004!
Some of her concerns do make sense, but the using, “a lot of our users stil use python 2.x” as a justification, in 2019, is ridiculous. Those same users had years to adopt/change the code base.
Bedbugs Menaced the Dinosaur Age Before Moving into Our Mattresses
If "Rails it not your application", why use Rails then ?
Yup. Media will be signed cryptographically and your belief in the media will correspond to your trust in the signer. It will destroy the usefulness and damage of anonymous publication of recorded evidence. Bad for transparency, good for privacy.
Have you been to Shenzhen lately? You must swipe your ID card before buying a train pass, mandatory random police checkpoints, tens of thousands of cameras+facial recognition laser scanners. All in the name of "reducing crime". It's complete bullshit. Crime stats are pumped up and these measures are slowly introduced with little to no pushback from citizens.
Reagent is probably the best UI dev experience I’ve found yet.

A quick blog post explaining why for anyone curious about reagent: https://www.mattgreer.org/articles/reagent-rocks/
Ted Nelson pointed out that knitting (or was it weaving?) is one of the most popular programming languages back in 1979.

https://m.youtube.com/watch?v=RVU62CQTXFI

Edit to add: I wouldn’t be surprised if there are more knitting programmers today than all computer programming languages combined. Just the size and pervasive presence of Walmart or Joann’s yarn and fabric sections makes me almost certain.
Rich Singapore-based parents get their kids into elite US unis
But ideally Congress forces states to make their tax systems easy to comply with in return.
dont put all the blame on users. there's a ton of software that is python 2 only, for example gyp.
Yeah doing a lot of anaerobic activities when on a zero or Ultra low carb diet will tend to wear you out quicklydue to glycogen depletion.
If you value build size you might want to take another look at Svelte. Build size is one of its strengths. For example, the Svelte implementation of RealWorld is roughly 10% of the size of the React/MobX implementation:

https://medium.freecodecamp.org/a-realworld-comparison-of-fr...

Edit: Confused the React/Redux implementation with the React/MobX implementation the first time around.
It doesn't matter what OS I run. My "modern", and apparently buggy, CPU runs arbitrary systems that I know very little about, and I have little to no control over.

Since 2008, it's been a dramatic departure.
Sounds like the real problem is your company, not python. I work for a very large bureaucratic company, but even they don't restrict us from installing software on our dev machines. If you install a torrent client they might ask you why, but that's the extent of it.
That is sort of like the old "Scotty with the phaser" explanation for transporters.

FMRI extraction of text has already been performed in a controlled setting. No one has demonstrated it with an adversarial subject in the open literature, yet.

An interesting consideration for the extraction of cryptographic keys is that the extraction could be very noisy and yet still be a massive speedup for a search. If the attacker can try a billion combinations per second they may not need to get that many bits of search space reduction from the subject.
Has anybody here migrated a UI from React to Svelte? How did it go?
As far as I know, there isn't any good reason not to. So indeed people should, if they can.

(IIRC, posix_spawn was introduced relatively recently, so most old software wouldn't use it).
You don’t have to use Facebook. There, moderating solved.
I already did Rust.
I'm surprised gulf war syndrome wasn't mentioned in the article. What ever ended up being the consensus on that?
As is stated on their homepage[1], vaccinepapers.org takes the position that no currently marketed vaccine is acceptably safe for use because of long-debunked concerns over aluminum adjuvants causing autism.

[1] http://vaccinepapers.org/about/
This is an interesting conundrum. The govt can't outright pay media to spin a certain narrative (...obviously this happens but it has to go thru abstraction layers to get around laws) meanwhile a foreign entity doesn't really care and can just buy them out.
If he's really serious about making a dent in expenses, he should definitely consider hiring outside of Fremont, CA. There's much more cost effective labor outside the bay area, up to 1/3 cheaper in the rest of the US and even cheaper outside the US. I understand, factory jobs can't be outsourced since people have to use the factory in Fremont, but software engineers, web designers should be remotable.
> 1. Changes to the DOM cost a ton more than executing JS code.

The point of the article, and of the performance problems that people actually have with React is that this might be true for a small number of JS operations, but that

1) Tree diffs are computationally complex operations that add up for real-sized apps
2) The diff is actually unnecessary if you simply take into account the structure of templates, so diffs are pure overhead.

So _do_ feel bad when you have a no-op render() in React at least, because the resulting VDOM diff just chewed up CPU and battery for no reason.
A Dispatch from the Fast-Paced, Makeshift World of High-End Catering
1934 Betty Boop cartoon banned for drug use (nitrous oxide for tooth extraction)
Xpath’s relationship to XML is like CSS to HTML: its natural domain—and most common use—is XML. However, it is a general path selection/query mechanism with a UNIX-file-path-like syntax.
Don't presume to speak for victims because you're painting with too broad of a brush. My sister's killer was convicted and sent to prison. Justice may have been served but for me the day after his conviction was the same as the day before: she was still dead and nothing can change that.

There are too many downsides to putting causal DNA collection into the law enforcement toolkit. Starting with the fact the frankly anything given to law enforcement is often abused and used out of context to the fact that a false positive means anything from financial ruin to possibly a plea bargain for a crime the person didn't commit due to the abusive charge stacking prosecutors use the days.

And although it may feel righteous to you to punish the guilty it should never been done at the cost of due process. We really can't afford the erosion of any more civil liberties, IMHO.
Composable, yes, but functional as in functional programming, no.
>Obviously it doesn't apply to everyone, and it certainly doesn't apply to most startups or open source developers, but I spent most of the last 20 years working in environments where you have to get permission for every third party library you bring on to the network.

Situations like this will really make you appreciate "batteries included". I think this particular issue is fairly revealing of the attitudes common among programmers of different languages. I think it's a good thing to be skeptical of a program pulling in a bunch of standard libraries over the Internet. It worries me when I find something on Github I want to try and I can't download and compile it without it pulling in 30 or 100 other libraries that I haven't looked at or decided to trust come along for the ride. I don't like that way of doing software, and unfortunately it's the norm in node and starting to become a norm in Rust as well. Real security fails have been caused this way in node's case at least.

Even in cases when Python programs depend on external libraries, I usually don't need to use pip for anything because Python programs will pull in dependencies provided by your distribution just fine. (My distribution doesn't even have any Rust libraries, so even if dynamic linking is possible in Rust not many people are shipping software that way.)

"Download by default" is a worse way of doing things, and it makes me sad to see newer languages like Go and Rust embracing it.
Well, they say that they did not invent it, they have just implemented it as defined in ISO/IEC 9075:2016 standard [0]

It is entirely possible that ISO design is based of Goessner’s work, but unfortunately it is just history at this point. Unfortunately this is what standardization often does - the work becomes attributed to organization, and individual authors are forgotten.

[0] https://modern-sql.com/blog/2017-06/whats-new-in-sql-2016
Forensic testing of DNA looks at 13 positions. 9 out of 13 is considered a match.

When you match against a very large database using such a small number of polymorphisms, you get many matches.

Detectives then take that list and look for people who lived sort of in the crime area. The matches who don't happen to have an alibi they can prove for a crime sometimes decades ago are then deemed "guilty".

It's complete pseudoscience.

If they did a full DNA sequence and matched that, sure. But they never do.

Also there is the problem that many DNA samples contain DNA from multiple individuals, in which the match can be assembled piecemeal. This completely destroys the statistical validity.

DNA forensics are absolute pseudoscience. Any court case relying on DNA should be discarded by the jury.
If you had shit on your arm you'd just scrub it without water?

Filipino uses a system called tabo, or sometimes a hand hose bidet (I call it the bum gun). If the pressure of bum gun is strong enough, well, it's like a pressure gun. You shoot it at 45 degrees angle (cause 90 hurts lol).

If the pressure is not strong enough, then use it like tabo. Tabo is a water scoop. You water your hand, you water your butt, then you soap both of them, and wash it out. It's a shower but just for your butt.

This sounds a little bit weird and disgusting but it is the cleanest since it's like a shower. Nothing beats a soap and scrub.

If there's tissues, take a tissue, pat down your butt so it's dry, put it in the bin.

Hope that explains it!
Can you explain that more?

I'm not sure what you're saying is true with lit-html. You don't have to quote attributes with single expressions.

html`<div class=${myClass}></div>`

is perfectly fine.
The tech giants (or other corps) have spread the fantasy that if you piss one of them off then everyone up there will know and black ball you. Basically unless you don't do anything super illegal the odds of fucking over your employer coming back to haunt you are relatively small. But the fear that it will keeps people in the order the corps want.
I quote an Angular contributor

> If you call something "view" and diff it, then it's Virtual DOM.

> If you call something "view model" and diff it, then it's Dirty checking.

(Angular uses the latter.)

https://github.com/angular/angular/issues/22587#issuecomment...
I don't understand. Are you saying that it's wrong for the state to grant search warrants in the course of investigating murders? Because it seems to me that the alternative is that then all one needs to do to never be convicted of a crime is to just not consent to being investigated. So which is the lesser problem, invading privacy with a warrant or never being able to prosecute any crimes?
I'm on FreeBSD 12 now. No it doesn't. And vim is not vi but vim doesn't do that either.
How often is diff done against the DOM? My understanding is that it’s done against last valid vDOM instead.
Dan Abramov has a great thread about this here: https://mobile.twitter.com/dan_abramov/status/11209717954258.... In particular, I find this argument really persuasive:

> Time slicing keeps React responsive while it runs your code. Your code isn’t just DOM updates or “diffing”. It’s any JS logic you do in your components! Sometimes you gotta calculate things. No framework can magically speed up arbitrary code.

In my experience, as your app grows, the amount of time you spend on dom reconciliation becomes negligible compared to your own business logic. In this case, having a framework like React (especially with concurrent mode) will really help improve perceived user experience over a naive compiled implementation.
I was not a CS major but I had a number of friends that were CS majors and one of the courses used a book written by the professor, who is also the department head. The book cost like $200-$300. It was a shitty rewrite of the Sun Java documentation with a few added exercises and some reworded bits.

Fucking racket. Also something something cheating and plagiarism is bad unless you're the head of an academic department.
What "conduct"? It's a simple disagreement, not some big dramatic fight.
Both those mentioned had more than one deal-breaker issues. The jumpiness (at maybe 5 hz) was ElementaryOS IIRC. No doubt the fact that there are a "crap ton" is the underlying evil.
It says industrial and automotive all over the page and mentions how wide an input voltage it takes and that an extended temp range will be available later.

Definitely not targeting hobbyists.
It is, but I'd be shocked if it were involved, I've tried to keep it out of the mix with Linux.
The price is not attractive
The range is software limited.
I'm not sure if it's still an 'interface' since it's compiling another language to imperative code which operates DOM API. So it requires other platforms implements a similar
imperative API surface as DOM.
Sorry, you're correct for React, and for most VDOMs, though some do diff against the DOM.

The point is that the diff isn't sped up by using immutable data. The app data is only used to generate the vdom tree, and the diff is after that.
When engineers quit did they just back a van up to the building to remove their property?
I went 6/8.

However, I call shenanigans. Some of the real clips were him reading from a script for the advertisements at the beginning of his show. Joe has a really flat/unnatural delivery when he's reading from a piece of paper.

In addition, if they were including the advertisement reading in the training material, that would definitely mess up the final model. Advertisement Joe doesn't like Joe.
Honestly, if outside speculators can wreck your housing prices, then your local government ducked up zoning and development laws really badly.
There are large parts of XPath which are XML specific, like attributes or namespaces or node names (JSON’s arrays of arrays have neither). I am sure with enough effort one could use Xpath for generic JSON queries, but this will require non-obvious redesign of the language.
Currently trying to find a new framework to do a front-end with because the company I'm currently interning doesn't allow React :^)

Looking at angular code, it's pretty ugly. What would be the next best thing to look at? Vue?
Weird. I feel like clenching my teeth using JSX and a compilation step when a function suffices.
Seriously doubt there are 300lb dudes running many ultra marathons. I recently read that book by the ex marine dude who did them. He was a freak in the low-mid 200s and he talks about how he destroyed his body pushing thru it. On top of it runners have sugar and whatnot they eat on the way, so op was making a conservative estimate.
I asked you about the paper specifically - why do you consider it pseudoscience? And long-debunked? There is really recent research about the dangers of aluminum as an adjuvant. What safety studies of aluminum as an adjuvant are you aware of? I haven't found any really.
I have seen many women win overall races, at distances from 5k to 200 miles. But what is always left out of these articles is the relative talent and fitness of the entire field. Elite-level women can beat 90% of all men. So if a male in the top 10% doesn't show up to race, elite women can win the overall. This is what is happening in all of these cases. I love to see women win the overall, but even they would say it depends entirely on who shows up on the start line.
Whether you gave him the most succinct demonstration up front or not, it doesn't excuse Guido's behavior and dismissiveness towards you at all. Guido should have found a way to be patient with you and ask for additional information if he felt he didn't have a clear enough explanation, and should have taken the time to prove his hunch (which turned out to be wrong) that the problem was on your end.

I did observe that you first provided a "fairly detailed repro recipe", and then after he rebuffed you, you provided a "simple, 20 line piece of obvious code". What Guido should have done was ask you to make the extra effort to provide the latter case if the "recipe" you provided was in fact too much effort for him to look at, for something that didn't seem to be a bug to him. That is, he wanted you to "spend the time" as you said, and if he had more experience with this kind of thing perhaps he would have known to just ask for it rather than dismissing the whole thing.

What happens to me, at least, a lot, is I get bug reports that are like "here just unzip this 10M attachment, install theses libraries and datafiles and then watch the log output for the thing I spent five paragraphs not really describing". These are not coworkers or customers of mine, for whom I might be obligated to go through all those steps for, they are regular users who have downloaded my software for free (as they should), and likely saving their company thousands or even millions of person-hours of work by doing so. The thing I ask these people in return is that they A. report issues to me and B. do as much work as they can to help me fix the problem - I'm not a concierge, the help process is more of part of how the give and take of open source software is supposed to work between parties.

I encourage these people to please pass along an MCVE, e.g. the most succinct demonstration script possible, and quite often when I get the sense that they don't really have the experience to know what I'm looking for (despite my sending them the link to what an MCVE is), I will often read their verbal description, then write my own MCVE in about one minute that shows what they are asserting is not true, and then I paste that into the issue; I have a Python fragment script that I use as a starting point for writing 90% of these test cases. I ask them to please modify the MCVE to show the thing they are actually trying to do. That's how I get them to send me a succinct problem description that isn't a huge waste of my time.

I understand this is likely not at all what happened in your case as you were both at Google and I'm sure folks there are more sophisticated than this. I just had the thought based on how you had sent two versions of the issue.
Stadia Streaming Tech: A Deep Dive
Impressive stuff, and this is only 2019 tech. Now, imagine this kind of technology in 10, 20 or 30 years. Things will get weird for sure.
I'm glad Windows 10 has OpenSSH now:
> Microsoft Windows [Version 10.0.17763.437]
> (c) 2018 Microsoft Corporation. All rights reserved.
> > ssh -V
> OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
I personally enjoy using Angular, but yeah, Vue is your best bet!
A lot of this is side effects of the Python 2 vs 3 schism imo. If it weren't for that situation, practically everyone would on be 3.x, and supporting older versions wouldn't be important, so package maintainership wouldn't be as difficult.

Put another way, the whole Python universe from my point of view has become a cautionary tale about breaking changes. Given Python's popularity, this might be an unpopular opinion, but I have yet to find someone who loves Python who still loves it as much when they discover other newer languages (I'm sure you exist, I just haven't met you!).

Python is having its time in the sun really because it is a default install for most unix distributions, so even people stuck in government labs can use it because 2.7 is already installed. Even apt depends on it via the debian software-properties package, so it isn't going anywhere any time soon.

The real question is how many people would use Python if it was as little known as, say, Elixir.
Probably a hold over from goats mowing the grass, or was that NS?
Turns out that the most serious file name issues are mostly down to disagreements between Linux and Windows about what characters are kosher - Linux allows a finger-slip to insert characters in folder and file names (such as a forward slash) that cause windows to crash out of copying tasks without specific explanations. It's taking me more than a week to isolate and fix these issues one by one in a large file system. Dead lost time. Extremely expensive. Some file issues appeared to be one Linux vs the other Linux, earlier, however. It wasn't just Windows operations crashing.
I noticed that, and also that the spacing in words was too uniform.
I was trying to find a year on it and couldn’t, but agree it seems newer.

FWIW, it’s not required to be able to run any setup code in the child to do arbitrary setup. For instance, WinNT makes that very hard, but has a larger syscall interface to compensate, so it’s actually more general. An alternate design of running all code in the parent can be made work if the kernel supports passing a pid handle to every syscall: https://lwn.net/Articles/360747/

On the other hand, this is perhaps a bit more complex in some ways? or at least just different.
They'll learn the lesson to introduce more variance after the first big incident, if it happens.
I think this article - and many of the comments on this thread are forgetting the context of how DOM manipulation was typically done when the virtual DOM approach was introduced.

Here's the gist of how folks would often update an element. You'd subscribe to events on the root element of your component. And if your component is of any complexity at all - first thing you'd probably do is ask jQuery to go find any child elements that need updating - inspecting the DOM in various ways so as to determine the component's current state.

If your component needed to affect components higher up, or sibling to the current instance - then your application is often doing a search of the DOM to find the nodes.. and yes if you architect things well then you could avoid a lot of these - but let's face it, front end developers weren't typically renown for their application architecture skills.

In short - the DOM was often used to store state. And this just isn't a very efficient approach.

This is what I understood the claim that VDOMs are faster than the real DOM meant - and the article is pretty much eliding this detail.

As far as I'm aware React and its VDOM approach was the framework that deserves the credit for changing the culture of how we thought about state management on the frontend. That newer frameworks have been able to build upon this core insight - in ways that are even more efficient than the VDOM approach is great - but they should pay homage to that original insight and change in perspective React made possible.

I feel this article and many of the comments here so far - fail to do that - and worse, seem to be trying to present React's claim of the VDOM faster than the DOM as some kind of toddler mistake.
There's two aspects to a joke that are equally important: one is being clever, the other is reading the room. A witty remark delivered in a snide tone followed up with a hot punchline is good for some lulz, but it's kinda like making a joke at the expense of the bartender who works at the comedy club every night.
I love Vue.js. I've never really caught onto the JSX stuff. If you have ".Vue" files then you get nice separation of the template html, methods, and the scoped styling. The Javascript syntax is pretty straightforward, and the templates just add nice directives like v-if, v-for, etc. I think it look pretty clean and is fairly easy for JS developers to pick up. Integration into a project is pretty straightforward as well. We have a webpack installation that pulls in the Vue files and bundles everything and it is quite clean.
Curating packages for quality across multiple versions and architectures is hard work. In addition to Enthought (mentioned earlier), Anaconda maintains a curated set.