skysight-inc/HackerNews huggingface dataset:
> Explain to me how BLM controlled America in the 1920s.

Progressive movements in general, not BLM and MeToo in particular.

The Atlantic, The New Republic, the American Economics Association, Planned Parenthood and many other Progressive organizations have been around for over a century. BLM is a particular instance of the sort of "third wave" of Progressive activism, which is based on expanding the civil rights movement.

(The first wave Progressives wanted nothing to do with civil rights, and most were virulent and unrepentant racists like Woodrow Wilson or Margaret Sanger. The second wave was based around the welfare state and neutrality on racial issues, and included FDR, Harry Truman and the New Deal coalition. All three groups advocate for nearly identical policies, and yet have contradictory stated goals.)
Sure, but the design of GraphQL, and the majority of the GraphQL backend tooling, lends itself to performance issues much more strongly than a boring REST API. I don't know if there are alternative backend tools, but my experience has been quite painful.

The "graph" part - GraphQL seems to want you to build these big interconnected webs of types. But there isn't good tooling on the backend to deal with resolving relationships between types efficiently. Someone decides they need user.friends.pets.names, and now my backend code is doing 3 DB round trips because my GraphQL server lib doesn't understand it can turn the relationship between the types into a JOIN. I decide that's no good and the query needs to be faster, the alternative is I have to do the JOIN every time even if the client didn't actually request friends. And if I'm going to overfetch from the DB, might as well send that data to the client anyway?

My experience was that because of how backend GraphQL servers are written, it becomes very challenging to reason about performance. It's hard to think about how your nice type resolvers are going to interact, and fan out into some nightmare n+1 query problem performance pit.

I know there are some better tools than this, which I sadly haven't tried...
It all seems very interesting, I may try and experiment putting it in front of my current prod GraphQL schema and making a few queries, once I get the auth stuff figured out. One question though, is any of this going to be open source? The on-prem-first focus you have is certainly a selling point for me as I already run my entire backend in Amazon's ECS so adding another service for the wundergraph would be very simple - however, I'm always weary of using non-open source software that I can't fork and patch, as I've had to do that many a time due to not being able to wait for patches to be upstreamed.
Regardless, I think the points you make in your blog posts are spot on, and I'm looking forward to watching this project evolve.
Uber and Lyft Just Bought a Law in California
Not sure about that, there are plenty of island-states in Europe that would surely have more coast per km2. Cyprus, Malta, Faroe Islands and more comes to mind.
> Nor would they advise a diabetic to abstain from carbs, and so take away the trigger for their condition. (Ie - you don't have diabetes if you don't eat carbs.) 99.9% of doctors will only prescribe drugs

They don't right now, because the evidence around the long-term effects isn't sufficient. They're clearly coming round to it though. See the section "Dietary advice" in NICE guidance.

https://www.nice.org.uk/guidance/ng17/resources/2019-surveil...
This is the mass market application of PrimeSense's Time-of-flight sensor. They were first known by the Structured-light sensor used in the Xbox Kinect camera, but were later bought by Apple and used for Face ID. ToF is a more difficult technology than Structured-light, but the spatial and temporal resolutions are much higher. Rotating Lidar is also ToF, with lower spatial and temporal resolution.

https://en.wikipedia.org/wiki/PrimeSense
https://en.wikipedia.org/wiki/Time-of-flight_camera
https://en.wikipedia.org/wiki/Structured-light_3D_scanner
The premise that copyleft licenses force or encourage devs to "contribute back to the community" (the most common claim) is ridiculous. Contribute what? And to whose community?

Let's say you've written a library and published it under GPL and it gets used in a cellphone or an automobile. The "community" of users for that paid product is not the same as the users for your dev library. In fact, most commercial software innards don't have a "community" at all. I think that's a complete fiction. What they have is customers who pay.

When the automaker changes that code, do you really want it back? Are you really going to publish their automobile version or cellphone version of your library back into your "community?" If its a simple bug fix, you might, but again this big company isn't republishing your software just to fix your bugs. They've modified it for their application. Do you want or need their mods? Are their devs in the same "community" as yours? I don't think so.

GPL tries to reach into the surrounding and supporting code that the commercial entity writes and somehow force that company to "contribute" that code back to a non-existent community of people. What right does the first developer have over any code that the second dev wrote? That idea that the first author could reach into my code or my product and have anything to say about it is antithetical to the values of open source software right from the start.

Non-permissive licenses use the tools of the enemy to try to do something that sounds good on the surface but in practice is immoral and largely unenforceable. I would argue that, far from encouraging liberal software use and development, restrictive FOSS licenses like GPL and its cousins prevent a great deal of software from ever being commercialized and also prevent great products from reaching users because no one bothers to commercialize them.

If you love our industry, please help your fellow devs by giving them the maximum ability to use your work in their own work so that they can create businesses, pay the bills, hire other devs, and so on and so forth.
I don't dispute that, I'm more mean that the actor model abstracts that away rather than doing manual green threads
Gaming companies generally have a surplus of potential employees. These employees will do a lot to work in the gaming industry (see crunch time, lower pay, etc, etc.). So employees will move to where the companies are.

If you look at older companies they're often headquartered in second or third tier areas. Not middle of nowhere but also not the hip city. Seattle wasn't a hot place when Microsoft started there. South Bay (Google, Yahoo, etc, etc.) is pretty desolate compared to San Francisco and an 45 minute drive away. However commercial rent is cheaper and there's room to expand over time.

It's only companies that don't have good ways of pulling in employees that tend to locate in the hip areas as they need every advantage they can get.

edit: Also if your employees are older and with kids then they value more than living in the "hip" places. They want a nice calm suburban location with good schools.
Wait, I've listened to that piece and it doesn't mention broken glass there. Did I miss it? Do you have a timestamp? And I agree on all points that he makes. The only thing related to BLM protests is that he mentions some folks asking to kiss their shoes or asking others to knee, but even in those cases he is careful enough to clarify, that he doesn't thinke they are actually BLM protesters. And they are jerks for sure no matter what their skin color is.

Regarding evidence I have a couple of thoughts - I don't think the situation was such that required publishing the evidence. If Carol or someone else would question the claims, showing the evidence would be necessary. (I don't count uberfemenist allegations since they are utterly disrespectful). Moreover, even if Bret doesn't have the evidence (like for the conversation with Carol over the phone), it doesn't mean that he should never tell about the story. Obviously we don't have to believe it either. Moreover, my impression is that Bret himself isn't very willng to dig into this story, it is mostly Eric pushing him.

I don't quite get what other claims he isn't able to back up. What did he claim about covid or 9/11 that he wasnt' able to back up? I only saw him questioning the explanation give about one of the buildings collapse. By unity theory - do you mean his physics theory? Whell, I haven't paid attention to that, but I'm not sure how are you supposed to back it up? If it contradicts the observation/experiment, or is self-contradictory, it is bust, but what does it mean to "back it up"?

Where did he made the claim about 3 Nobel prizes? He said that Bret might have had one in the video that is linked multiple times from the uberfeminist blog, but I haven't actually heard about the other two.

p.s. it is quite tedious to type that much, if you want we can chat by voice/video, just drop me an email by appending gmail to my nickname.
Oh no! 65 people died :(

Keep yer dirty hands off my speed controller.
Voters rejecting the war on drugs is a win for public health
This is awfully expensive for a service that Gmail includes for free.
Sorry, none of what you wrote make any sense to me. Which company is being subsidised here?

Rockstar was from UK? I thought the first GTA was developed by Rockstar Canada? And its former self BMG Interactive Entertainment was part of the German arm of Bertelsmann AG.

I dont see how UK Government and public money has anything to do with all this, care to explain in more details?
Yes, this is different from dark matter. This is baryonic "matter" that is predicted by our theories but that had not been previously detected.

However the title is misleading, this is not the discovery of this matter even if the press release makes it look so. Previous detections of this matter had been discussed on HN before https://news.ycombinator.com/item?id=17953600

What this is is an advance on our understanding of this previously undetected matter. You can read more about it here https://www.aanda.org/articles/aa/full_html/2020/11/aa38521-..., this work has advanced our knowledge of the temperature and density of the cosmic filaments where this previously undetected matter is.

I'm not an astrophysicist but I did my PhD about the stacking technique used in this paper (but applied to other problem). It was a long time ago though, I could be forgetting something important.
That and 8GB RAM, plus NVMe or PCI Express with some internal space for a hard drive.

Also, make the case easy to open with screws...
As a consumer, I think it's regrettable that they don't show EV in a different way. It served for me as a signal that the website were less likely to be scammers.

But maybe Mozilla & Google, were aware of it being used like that and thought that EV certs were not reliable enough to be used as a signal of trustworthiness?
I don't get the joke here, but just want to point out that Finnish is subject to the same taboo. "Karhu" is related to "karhea" ie. refers to the rough fur/pelt of the bear. The original Fenno-Ugric word os probably something like otso or ohto.
India's UPI continues to grow. October vs. September data in detail
"better alternative to Green threads"

Do you have opinions about Java's Project Loom?

I'm a simple bear. I have always struggled with the architecture and organization of my async code. Stuff like exception handling, percolating errors up, rational back pressure and retry.

My goal is to rewrite some of my server code using Project Loom, to see how it helps.

"why we don't make fuller use of ... the fortunes of RAM we have now"

I know you mention this as an aside, but I'd appreciate examples.

I've been personally frustrated by teammates using external key/value stores for hot data sets which would trivially fit within RAM. But haven't had ready-made solutions.

One recurring objection, for which I've had no good response, is how to quickly hoist (prime, seed, better term needed here) the RAM of new instances.

Last time this came up, I helped come up with a compromise kludge using Redis. We added a local Redis instance to each web server, had the "master" create regular snapshots, copied that snapshot onto new EC2 instances during boot, used the snapshot to prime its local cache.

It worked pretty good. Though I would have preferred in process, using Redis allowed better inspection and debugging, which was pretty cool. But devops wise, this Rube Goldberg kludge broke most teammate's brains.

Thanks for listening. I keep looking to see if anyone's got a more turnkey solution.
I think a lot of people use "modern" to mean "doesn't look dated or unfamiliar to me." In programming language commentary, it generally means "looks like C or ALGOL."
Example of Live Streaming System – open-source
Example of Live Streaming System - Open Source
https://github.com/nelsonwenner/stream-live-system
I've never used clojures syntax, but my suspicion is that until first class parallelism can be used with what feels like just an annotation or another type in imperative code paths, without having to actually change one's way of thinking much from the c abstract machine concept, we won't get to the goal of parallel by default very quickly.
Thank you, but I wasn't very clear. What I'd like is a download including the .git directory, not just a snapshot of the latest code.
Must check these before accepting guest article on your blog
I think for most of here our first C64 program looked something like:

10 PRINT "TODD RULES"

20 GOTO 10
Nitpick: Actors or goroutines or async are mostly used to deal with concurrency. CUDA & friends are used for parallelism.

The paper: The motivation is a problem suitable to be solved via rule systems. It's a bit unclear why the rule system needs to be grafted on top of an actor model.

Actors: Programming with async messages is hard. Message ordering matters, no clear error reporting, no stack traces, distributed state. This is hardware hard, as in bring in formal verification methods hard. To be avoided in favor of a centralized coordinator solution if at all possible.

I wonder if, alternatively, one could use Rx processing over the stream of events.

Motivating example from the paper:

1. Turn on the lights in a room if someone enters, and the ambient light is less than 40lux.

2. Turn off the lights in a room after two minutes without detecting any movement.

3. Send a notification when a window has been open for over an hour.

4. Send a notification if someone presses the doorbell, but only if no notification was already sent in the past 30 seconds.

5. Detect home arrival or leaving based on a particular sequence of messages, and activate the corresponding scene.

6. Send a notification if the combined electricity consumption of the past three weeks is greater than 200 kWh.

7. Send a notification if the boiler fires three Floor Heating Failures and one InternalFailure within the past hour, but only if no notification was sent in the past hour.
But this is operated by humans. Gmail uses a glorified Perl script.
eBPF: Put the Kubernetes Data Plane in the Kernel
It's easy to spin up a server. Spinning up a server that can actually access your data in a way that has reasonable performance is another matter entirely.
Seeing trying to save some data on PGP keys in pacman db while removing differential packages makes me somewhat angry. Really? That is the a plan of priorities for pacman?

Well, wasn't huge fan of previous diff implementation either - making diffs of already compressed data was a big stopper for significant reduction of bandwidth. But still 20-30% on average for rolling distro is significant improvement. And I bet that with proper unrolling compressed files then making diff and then getting it back together it would bring another "extra" 20-40% savings.
Show HN: Free Illustrations for Geeks – Kung Fu Geek
Is there an electric generator evolution scenario here Intel should be watching for?

Back in the day before the electric grid really caught on, hydro- and coal-powered electric generators could be found in businesses large and small that had needs that went well beyond the limited voltage and amperage requirements of the meager electrified buildings at the time. It made sense for a business to have its own power plant engineering department to just feed and maintain the beasties if the productivity from thirsty electrically-powered machines far outweighed the enormous cost of an in-house power plant, consumables and staffing. As the grid evolved though, this need went away, and only really heavy industry these days exceed the delivery capabilities of the grid will run their own on-site power plant (more often they just try to "peer" co-locate next to a "real" power plant, kind of like HFT's with exchanges). Power plant manufacturing is now a heavily-specialized industry with margins much lower than Intel has become accustomed to.

Could the "grid" of the Net, cloud and mobile devices evolve to the point where the existing PC and server markets retreats in relative scale into "heavy industrial" applications like cloud infrastructure, and shift out Intel's cash flow from under them? Under such a scenario, the PC and server markets don't shrink as much as grow dramatically slower on a relative basis to B2C-grade gear and infrastructure that explodes in growth comparatively. Intel will still be plenty profitable if well-run, and still be mighty, but won't grab all the headlines, and evolve into a GE-like "mainstream" business.
It can do, however you can also use views, custom query functions for whole queries or for specific columns, custom mutation functions, or simply extend the schema at the Node application level to do a lot more than just the structure of the DB tables. For me it just means I don't have to write any code other than the schema to simply expose CRUD actions with filter and sort and such things - the escape hatches have been perfectly adequate for more complex behaviour.
Bearing arms is regulated in much of the US, so I'm not sure you'd actually gain anything if you got encryption to count as arms.
Not really in Erlang, since you manually build the actors with a recursive tail call. There's nothing called an "actor" in Erlang, but it's definitely an actor-based language.
Currently you can get it from the author's gitlab: https://gitlab.com/dstftw/youtube-dl , i.e. git clone 'https://gitlab.com/dstftw/youtube-dl.git'
I'm still in disbelief canned Stargate Universe after two seasons. Last 2 seasons of SG-1 was just garbage, Stargate Atlantis was about as cheesy as the 80s Buck Rogers series. But to me Universe stood out as kind of the anti-Star Trek -- instead of the magical space ship that can go anywhere and do anything the plot requires, you've got the dodgy rust bucket that just goes one direction and you can't really do much other then be along for the ride. Kind of like the way James Bond was more or less limited to the gadgets that Q gave him at the start of the movie vs cartoon character that can produce any object from its pocket at will.
Ye well the turbines doesn't build them self ofcourse.

I just mean that Denmark probably has the best locations to put them in the whole of Europe. Flat land and alot of see dunes.

The article didn't touch that. Obvoiusly bad policies could have had them stuck at burning oil ...
Best Places to Sell Your Videos Online and Make Money
There's something I never quite understood about GraphQL, and this seems like a good thread to ask!

With REST, all my APIs are defined and I can easily test all the database queries my server will run, check that they're indexed, etc. But with GraphQL, my understanding is a client might be able to request something like "Give me all users whose phone number starts with 555". It's possible that query isn't indexed, and after deploying the app we end up tanking our database performance, right? That seems like a huge potential issue to me, but I might be misunderstanding how it works in practice.
In my experience, accountants want to capitalize software development costs (makes the bottom line look better) but must expense maintenance (i.e., bug-fixing). So that translates to a (slight?) preference for quality software that has fewer bugs.
Ye sure that is correct. "A lot of coast per km2 compared to other countries", then.
GraphQL also allows the frontend team to iterate faster, because they don't need to ask the API team to change an endpoint, or add one. The API team also moves faster, they define the relationships and they are done, no going back and updating endpoints.

GraphQL creates a data graph that powers the UI, REST creates a database that you can query on the UI and you have to compose it all together and manage.
I know little about conditions in African villages. Do they ever make city trips where they have access to free wifi with unlimited data?
Many (most?) HDMI monitors have an audio-out jack.
> With rest, you can only paginate that particular call. You cannot really paginate different results in that one call.

Where did you get this idea that REST in any way dictates how you do pagination?
I think so, and we 100% should do, but I just did a test and the secret I committed was still working a full minute after I converted the repo. Could be that the scan was in a queue, could be that it didn't trigger.

I'll dig into it and make sure this is working and is fast - it's a critical time to do a full scan of the repo's git history.
Even if users don’t have 5G, why is your rest api so slow that it’s an issue? Why is graphql the solution? The featured article points out that optimising rest can be a better solution, in terms of time and effort, than implementing graphql. The problem that graphql solves isn’t this one.
Here's a human-interest story on this same medication: https://www.youtube.com/watch?v=i9XeeVSRlYs
Exactly. I don't know where the phrase "contribute to the community" came from but it's not in the GPL license text.

All you have to do to comply is make your own source code available on request to users who accept your license, along with installation instructions to build the running product. That's not contributing anything to the other dev's community.
Many doctors are good people and entered medicine to help others. But after about 5 min in practice realize you have no idea how to actually help most people, let alone cure them. New drugs get advertised to you even more heavily than to your patients, and so you prescribe.

Systemic approaches to helping your patients are hard and those doctors that try it often don’t take insurance because most insurance companies won’t pay for their trouble. They want to fall back on the hard numbers of a limited set of narrow interventions.

Perhaps if there was more upstream incentive to keep patients healthy things would be different. But at the end of the day, many patients are not compliant and are very resistant to lifestyle changes, and as a doctor, despite knowing more today about the human body than ever in history, deep down you know you’re little better than a charlatan.
Orb launched Deploy full stack ML apps easier