skysight-inc/HackerNews huggingface dataset:
I think attacking one problem at a time is the best way to go about (at least for me). I noticed that many people try to make drastic changes all at once and then fail at all of them. I'd recommend trying one thing and just doing that one thing above all else. IE, don't try to exercise and diet at the same time. Pick one and when you've firmly established the habit, start the next change.
Great work! I love multi-accounts containers on desktop. Is it coming to the Android browser as well?
Ah, I see. I was reading it as two axes, not a product.
I am actually surprised by that number, in that I expected it to be a lot closer to 100%.
> (if anyone does)

There's no doubt that if it is established that APIs are subject to copyright, then someone owns copyright to the C standard library APIs. It's not old enough for copyright to have expired, and nobody has ever released the APIs to the public domain (because nobody ever seriously thought that such a thing would be necessary). Establishing API copyright as a real thing without broad fair use rights would throw into doubt the copyright ownership of a large portion of all software ever written.
React is such a mess.

> These lifecycle methods have often been misunderstood and subtly misused; furthermore, we anticipate that their potential misuse may be more problematic with async rendering.

I hate it when library authors blame users (consuming developers in this case) for their blunders. Almost all lifecycle methods in React are confusing and contrived. The state mechanisms are becoming so convoluted (and overly generalized), no wonder we're ending up with gobbledygook like "getSnapshotBeforeUpdate(...)."

It's also pretty funny (or sad) to see no mention of SSR. Just a few months ago I spent literally weeks trying to figure out how to do server-side rendering with React. I ended up populating data via componentWillMount on the back-end. Terrible solution, but hey, it's the only one React has. Now, they suggest moving data-population in componentDidMount.. but guess what?

This will not work on the server-side because technically components never mount when doing SSR.
presumably an inactive repo suggests they arent spending the money on development
It stuns me that any extension would be so critical as to keep one away from Quantum! (But then, I suppose I also don't understand why one would stay back with Windows 7 when 10 is out there either.)
It hides it from _your_ timeline, but the backlink to your profile still remains. You have to actually untag it.
> I don't want to be unreasonable, but Google used to at least generally support the idea of the open web.

This is a Machine Learning product, I don't think anyone at Google, at least as part of this team, is trying to "get you" or destroy the open web or something. This isn't even a case of Google using something non-standard -- WebComponents is part of the standard, you can even see it in Mozilla's MDN [0]. Firefox, Safari, Edge, et al simply haven't implemented it yet (or landed in stable). Is that somehow also Chrome's fault?

Filing a bug report is good, but ranting on HN about how this is a sign of Google trying to steal the open Internet is at best unnecessary, and absolutely unreasonable.

Coincidently, I'm working on an application that uses complicated SVG with CSS animations, and I've spent a ton of time optimizing it. I've never tested it outside of Chrome before today. To my surprise, while everything works fast in Chrome, in Safari it's bearable, but in FF it's simply too laggy to use. Now, I probably won't ever get to fix the performance issues in FF and Safari, simply because I don't have the time. Am I also out there trying to destroy the open web? Maybe I'm just bad, not evil.

[0]: https://developer.mozilla.org/en-US/docs/Web/Web_Components
Linux kernel developer here. I don’t know know how MS’s Meltdown solution differs from Linux’s, let alone whether I should hate it.

MS (I think) uses IBRS to help with Spectre, and IBRS is not so great. Retpolines have a more fun name at the very least :)
Beeminder comes to mind when thinking about losing money when you don't hit your goals (goes to the company). I've been too afraid to try since I'm a student with loans, but maybe it's time.
Why not just help with some tips here?
Elm: De-throning the List
Why not? Google started out as a software company and now has plenty of different hardware lines.
Well it's not like they made a booboo, and some bugs caused some inconvenience to a few or many people. Someone died.
How a Thermostat Heat Anticipator Actually Works
Snowden tweets about Facebook
Which lawyers in what context do you see providing that nuanced human perspective?

Corporate law? Their job is keep us from getting sued.

Family law? If you're advocating that human perspective for the opposing party, are you failing your duty to your client?

Prosecutors? Not sure they have that discretion.

General legal services, probate, etc. Doesn't seem that applicable.

Intellectual Property? Human perspective? Unlikely, except maybe the "hard-working inventor" angle.

Defense attorneys? Sure. That could be a good angle - along with any possible opening to exploit.
So now we have to go back to every site/service/app including unchecked but mandatory tick boxes about agreeing to their terms and privacy policy in the checkout process, thus both annoying just about everyone and potentially reducing conversion rates while making no practical difference to anything whatsoever? I guess we can file that with the "cookie" law and the consumer protection rules that say if you want to download any digital content you just bought immediately instead of waiting 14 days first then <insert scary legalese about losing a right to cancel under some law you never heard of here>. I think they're under "well intentioned but utterly lacking in practical understanding".
It would be involuntary man-slaughter at worst. Hard to prove right?
No, and I'm pretty sure the parent commenter doesn't either. It's why I put "deleted" in double quotes, as the above comment did.
The initial pitch barely mentions the part of the game that makes it so ~~much fun~~addicting: You get to beat on pinatas until some loot pops out. Then collect the loot and/or convert it into in-game currency.

Diablo was one of the earliest games to start exercising those little dopamine hits of microjoy when the monsters go pop, hoping for just one more bit of treasure/xp/whatever.
I don't think we disagree on that, since he explicitly mentions event loops and essentially claims they are generally slower. Which is nonsense.
I agree with you on all points. Should Uber continue their self-driving efforts, I hope they take both public safety and passenger safety more seriously.
Is anyone getting the sense that Palantir, Cambridge Analytica, and Facebook aligned on a rather coherent political axis, with Google and Apple staking out an opposing axis, and Amazon is staking out a sort of arms-dealer neutrality?
Why? The car should have all the logs, shouldn't it? It's won't be 100% an account of what happened, but it should be pretty close - unless neither Uber's lidar nor radar was functioning, in which case that could ironically save the company.
Thiel is not a true Libertarian. But he does like to disrupt the system. That is why he did PayPal and funded micronations.
Here in NYC, the mortgage on a taxi medallion costs a lot more than the total salary of all Uber developers divided by the number of Uber drivers.

There are other costs that go into taxis that Ubers don't have. Taxis have back-office support staff too (the people you call up to order one to you).
I've always wonder why no C or Java code formatter tool allows me to use Lisp-style formatting. It's clearly superior, and the popularity of Python should prove that people are OK with not having closing braces on their own lines:

void foo(int x) {
if(x == 0) {
bar() }}
Criminal negligence statutes (I don't know Arizona law in particular) virtually always have a "gross negligence" requirement. A reasonable person would have had to have known that the action was likely to cause harm. It's not enough just to make a fuckup.

That just doesn't seem to apply here, absent evidence that we don't have (e.g. Uber knew the LIDAR was being ignored, something like that). This was just a software bug. You don't throw people in jail because they wrote buggy software.
Not all organisations are required to have a DPO under the GDPR.
Labor is probably not fluid enough. I expect people to value steady income very highly. That might change if basic income was a thing though.
The Know-not-all Developer
I was going to say that I couldn't even imagine the selling point of this to the average consumer, but I'm not someone who uses my Echo for social uses (i.e. calling, or sending/receiving messages). For the FB/Instagram-addicted crowd, I guess I could see the appeal of being able to do voice-activated messaging, and to look at photo albums. And it's not something FB should want to give API access for to Alexa/Google/Siri.

That said, I think as popular as Echo devices are, people already have a bit of paranoia about them, and that's before considering the controversy FB is now undergoing. Unless the hardware is best-in-class, hard to see how this will fare any better than Facebook's failed attempt at its own phone with HTC: https://en.wikipedia.org/wiki/HTC_First
To be horribly utalitarian - every week you set back the development of self-driving tech, you're 'killing' future people who are involved in human-at-fault collisions. Counterintuitively, it is the most ethical choice to continue to accelerate self driving car development even if it is sometimes conducted in an unsafe manner.
How to build a calculator from scratch (part 1)
Are you too old to learn to code?
This is frustrating, and we've just begun seeing these fatal car accidents done by self-driving cars.

These things and liability should have been decided before the cars were allowed on the road. But when Congress deregulated them at the federal level everyone hailed it as a good thing and completely ignored all the potential negatives of that.

Now, even if Uber is found guilty, it may get away with it, because there may be no law clearly attributing guilt to a self-driving car maker in case of accidents like these.
Over what? Correct me if I am wrong, but the car had the right of way and the person illegally crossed. Regardless of any improvements in what the self driving car/driver could/should have done, it seems clear cut to me that the root cause lies with the person.
That’s cool and all, but doesn’t really work if you’re trying to, say, stop being anxious on public transit.
It's a little more setup, but I believe you can accomplish that in Multi-account Container extension by setting "Always open in <container>" for the Google domains.
> in view of the fact that copyright explicitly allows clean-room type reverse engineering.

The legal status of reverse engineering is not at all clear-cut. There are many nuances depending on the circumstances, and much of it is determined by case law rather than statute. There's no clear basis for you to make claims about how this new class of copyright (on APIs) will interact with reverse engineering. However, it is much simpler to state that if APIs are a work subject to copyright, then it must be possible to make derivative works of APIs that are also subject to copyright absent any explicit exception or fair use right.
(Someone went to jail for VW and there was no death directly as a result of the emissions cheating.)

That was an instance of deliberate fraud.
Copying an API is what software developers call "implementing an API"

When you create your own USB cable, or electric plug, you aren't copying the API specs, you're implementing them.
Used that maybe 50+ times, it NEVER gave me anything remotely accurate.
Did you see the video?

Imagine if it was just a person at the wheel. Would a person have gone to jail for hitting that person, in the video?
Just because you have right of way does not allow you to murder someone.
> To be clear: there is nothing wrong with my iPhone vs anyone else's iPhone

That doesn't mean that there isn't anything wrong with your iPhone. There very clearly is.

> understand you're going for the "lawl iPhone sux" kind of thing but it's really not appreciated.

I am doing no such thing.

There is a major UX bug on iOS that showed up today. It is a local bug that exists in local code running on iPhones that causes unpleasant, unexpected, intrusive and possibly scary popups to frequently interrupt users. To deny that is insane. It is a simple fact.
Human Scale Autonomous Race Car
If that’s what he meant that’s what he should have said. Using terminology that can be even the least bit confusing never helps any discussion.

BTW, the link mentions trans people too. Stallman was using it as a catch all term. Again, don’t think he meant anything by it (that is another way of saying: “I am not personally offended by the words themselves because I understand and acknowledge the context and intent of them”) but words matter when you are trying to make a point.
Probably smart -- cause Facebook listening to what goes on in your house is a sound idea.

Then again why does any one trust the companies who provide this service at all?
Nothing sounds more invasive than a Facebook created in-home, always-on device.
I like photoshop and haven't found a good replacement. when muscle memory is built up, it's really difficult to learn and switch to a different tool.

I have been searching for photoshop alternatives. but so far I haven't found any. For me photoshop is too expensive.

I have even considered to implement my own (I only need a portion of the photoshop features)

https://affinity.serif.com/en-us/

is what I found recently, it looks nice, but I can't get used to it.
I agree the people wanting a PowerRPi aren't relevant, bit if IBM wants to compete in high-end (not specialty/HPC/AIX) servers, they need an entry level server like an HP DL360 or Dell R300 to get people in the door. That's a sub-US$2K item.
Which is it? You're saying we don't have enough details AND that it's just buggy software.
I don't get it. They admitted the methods were confusing and then made them more explicit. And all you have to add is that they're blaming people for being confused?
Many do but not all (I have a Samsung which does and an Acer which doesn't).
> the behavior has always been

The ECMA spec only defines Javascript 1.3 and above. See this description for logical operators for Javascript 1.1: https://web.archive.org/web/20060318153542/wp.netscape.com/e...
Is there an online equivalent course?

This one seems to be in person only.
Is he really wrong though? What purpose does artificially created diversity serve? Shouldn't we always be looking for the best qualified individuals?

The goal should always be equal opportunity, not equal outcomes.
Doesn't uber use nvidia? If so, this doesn't bode well for nvidia, it implies a link between the crash and nvidia's piece of the rig.
Well they better not, they have lost almost all consumer trust at this point. They need to rebuild that, maybe for years to come.
It's not a unique situation. Developers are responsible for software that kills.
My mission is to eat tacos. As many as possible.
You can see Wells’ genius even in such a short clip. To think he was only 20!
We do this! You can even do it without opening an Amazon account. https://zincapi.com/

Disclaimer: I work at Zinc.
This is comparable to prosecuting the developer who works for a gun manufacturer when a new type of digital "safety" fails.
It would be utilitarian if we knew that self-driving tech was the best outcome out of all potential alternatives. We don't.
No Michael Bay?
> You don't throw people in jail because they wrote buggy software.

That depends upon the application.

Too many programmers think "Meh. Bugs are no big deal." because their code doesn't interact with the real world.

The problem is that the useful code that doesn't interact with the world has basically all been written, code is now starting to interact with he world by default.

Hang on, programmers, this ride is about to get bumpy.
That amounts to "the ends justify the means." Some people go for that, some don't. Personally, I usually don't.
If Uber is not found legally at fault which seems likely given the circumstances and based on opinions from people with legal expertise in these cases, I highly doubt they will let themselves got derailed completely by this. Too much money is at stake.

Further, we don't stop using trains, or buses when a pedestrian makes an error and gets killed because they "could have not been hit, maybe". For those who have paid attention to those other accidents(even though the local transit isn't as sexy to hate on as Uber, and they didn't involve AI), it can actually be quite shocking how little of a blip it causes in the transportation system.
I suggest adding a Google login option as well since it's an android app. I don't have FB and don't want to type email/password.
Uber's self driving tech has blind spots
> why does any one trust the companies who provide this service at all?

I don't think they do. I think either they provide a service that people want, or that they truly have no idea they're the product.
My first experience with programming was making a "dump file" editor for my Diablo character in 8th grade with Visual Basic.

Someone had built a utility to dump the memory for your character to a file, where if you knew or could figure out the addresses, you could edit it and load it back into the game. I spent a lot of time changing a value in game, dumping the memory, and running a little diff tool I built to figure out where everything was. Then I built a little editor that could edit your character and item stats with a ui that looked like the game.

Such huge nostalgia for that game. StarCraft Remastered really brought back memories too. Blizzard is so, so good at game design.
You're correct, I read "BOFH" as a negative. I apologize since you did not mean it in that way. I never thought that BOFH would ever be considered the good guy in the story :)
This is exactly what the burgeoning automobile industry did early last century. Its why we have j walking laws.
Cars were faster than horses and so people were getting hit. The automotive industry responded in the same way you describe essentially creating j walking laws. History repeats itself!
I can’t imagine the selling point from a consumers point of view either.

I can imagine extremely well the field day fb product managers must have had with the notion of a 24/7 real time data feed of people’s homes.
Compare these two different aspects of journalism

https://www.nytimes.com/2018/02/16/world/asia/china-africa-b...

https://www.youtube.com/watch?v=JN9wFtiJtBM

China Uncensored's video barely scratches the surface except for some things that China does in Africa. The other is an actual journalism piece which goes indepth on what people in Africa think of the situation while also going forlaying into China's involvement with Africa.

https://www.economist.com/news/china/21737283-it-has-problem...

This article too goes into actual journalism with an indepth review on China's relations with race and how they see race as well.

https://www.economist.com/news/briefing/21737558-clear-think...

From the economist and another "China-critical" piece. I'm going to be honest though, most articles regarding China from the economist or Financial Times are going to be "China-critical", just varying degrees on what you consider critical to be. Most aren't going to be overly pessimistic about any small thing China does (as China Uncensored does for everything) and most are going to err on the side of mild concern.

China Uncensored likes to over-exaggerate a lot of things. Problems come from their clickbaity headlines and lack of acting like an actual news provider.
Thanks. I was really disappointed about the replies to my message. Because just claiming that "yes, they do not care, it's a fact", doesn't make it a fact. No links provided. Nothing.

(In case someone wonders what's the evidence for claiming that the GIMP devs do actually care about the project: the evidence is the release itself. People don't volunteer to working on FOSS software and not care about the software or its users ;) )
So it's basically a recurrent neural-net version of model-predictive control, applied to reinforcement learning problems?

Nice.
>I hate it when library authors blame users (consuming developers in this case) for their blunders.

I’m sorry the post came across this way. We didn’t intend to blame the users. The component API was virtually unchanged for five years, and when it was originally designed, we didn’t anticipate how it would be used, so the hooks were pretty low level and matched how React worked internally. These days we have a better idea of where we want to take React (I hope that my talk[1] may inspire you even though you already formed a negative opinion). The work we're doing now is just to fix the mistakes we made in the past with a gradual migration path.

>no wonder we're ending up with gobbledygook like "getSnapshotBeforeUpdate(...)."

I totally see what you mean but this particular lifecycle is for a very rare use case. If you have better suggestions for naming it please let us know—we have an open RFC process and you are welcome to participate there.[2] We didn’t separate it on a whim—it is essential to have a pure lifecycle like this to implement some use cases (like autoscrolling to new data) with asynchronous rendering[1].

>I ended up populating data via componentWillMount on the back-end. Terrible solution, but hey, it's the only one React has

You're right—but this solution doesn't solve async data fetching. It only works when the data is synchronously available, and per the post, in that case you can already use the constructor.[3]

>This will not work on the server-side because technically components never mount when doing SSR.

I think you might have missed this part of the post:

>In the longer term, the canonical way to fetch data in React components will likely be based on the “suspense” API introduced at JSConf Iceland. Both simple data fetching solutions and libraries like Apollo and Relay will be able to use it under the hood. It is significantly less verbose than either of the above solutions, but will not be finalized in time for the 16.3 release.

The mentioned “suspense” API is both much less verbose and actually was designed with server rendering in mind. It would let us fetch data on the server and on the client and suspend rendering until the data is ready (and show a placeholder if it takes too long).

The lifecycle changes in these blog posts are exactly the kind of work we need to do to make APIs like Suspense possible. Again, I encourage you to watch my talk[1], the second half of which demonstrates this API.

I hope this clarifies our position a bit, and I’m sorry if it seemed like we don’t care about our users. It took us about a month to write this blog post, and we know it still doesn’t address all use cases. We’ll take your feedback in mind next time we amend it. Thanks!

[1]: https://reactjs.org/blog/2018/03/01/sneak-peek-beyond-react-...

[2]: https://github.com/reactjs/rfcs/pull/33

[3]: https://reactjs.org/blog/2018/03/27/update-on-async-renderin...
If the person knew they were there, yes. That's the case with the LIDAR.
Did they ever make meaningful contributions? I recall when they first revived the WRT branding, they promised open-source support for the Marvell chipsets they were now using, but it took an extremely long time for any code to show up, and it was far from being in a state to upstream. I haven't paid close attention since then, but I don't recall running across any mention that Linksys was directly helping improve the open-source Marvell drivers.
Buying a facebook speaker, or really any home-speaker for that matter seems like a really bad idea. You give it the ability to record everything in your home for a slight utility.