skysight-inc/HackerNews huggingface dataset:
My brother was studying Veterinary Science back in the day. As part of some lab work they had to do, they needed to look through a microscope and count some types of organisms they say in the microscope.

So he had this good idea of creating a simple application that would allow him to enter his data in the computer without having to move his eyes out of the microscope. He did this with a keyboard numpad and a quick VB6 prototype (which I finished the coding part for).

Those are the kind of great small programs that VB5/6 allowed people to do. And there were a lot of those small utilities all over the internet. No paywall, no ads, no subscriptions. I miss those days of creativity and sharing for the sake of it. Now the internet is all just SEO, ads and greed. What happened to kids/young Millenials and Zs?
It could be an actual mistake.

On the other hand I know Nvida and others are sensitive to how they're perceived by non crypto folks and would / could even accidentally try to downplay how much the price / sales are driven by crypto.

But you really shouldn't do that in an earnings report.
Part of the reason is for the past 100 years we've been teasing out all the details of these theories and verifying them. We've only recently discovered where the incompatibility of these theories present problems - and now we're tackling them. What I'm really saying is there hasn't been a whole lot of people trying to bring together QM and GR, not to the level that's going on at present. For those who had been trying to reconcile the two theories they were working with theories in progress, theories who's impacts were just being understood. As another commenter mentioned these things take time to bake!
This is scary when applied to consciousness to. How will we ever understand what makes consciousness from within consciousness?
We have had a wonderful experience with https://prisma.io
> dunking on my team

Translation: While I'm ostensibly apologizing please note that I'm actually the victim here, everyone please feel sorry for me and my team.
Sorry, I meant a similar car of the same make/model. I.e., another Honda Insight from another dealer.

FWIW, I've always loved the Insight and wish they made more of them :-)
>In other words, the Fed feels it can continue to juice financial assets and exacerbate wealth inequality so long as the average person doesn’t notice price increases...

And the Fed is not quantifying stealth consumer inflation, which people do notice in spend, namely "shrinkflation" where consumer goods manufacturers reduce the amount of corn flakes in the box and hold the price the same. This was a trend happening before the headline inflation number started to move.
I like how this is currently the top-voted comment.

It a great example of the fundamental process at the root of all humans progress/knowledge: a creative conjecture/idea which can (hopefully) be tested against reality and rejected or accepted based on how well it solves the problem and explains something about reality.
>That is "combative, thin-skinned and hostile to outsiders"?

Yes. They reference an apology, didn't actually make one, and it was roughly a year after they were combative, thin skinned, and hostile to outsiders. So their words now don't negate the fact that they were actually those things.

And the original now-edited response here was itself still combative, so I don't have much reason to believe they've actually changed rather than just trying to put a nice public face on about it.
You can use GET. https://graphql.org/learn/serving-over-http/#get-request

That being said, caching needs to be done at the resolution layer rather than the request layer. Under REST, APIs are generally modeled as returning individual objects or lists of one kind of object, which makes requests a reasonable thing to cache. Under GraphQL, each resolver returns a different type of content, and the mixed bag of content means that there should probably be different cache policies and invalidation for each kind of data provided by each resolver.

The status code being 200 even though your query is wrong or failed to correctly return data makes sense for the same reason. If you got a 500 because one field failed to correctly resolve, but the rest of the query was fine, the 500 is only telling you that something went wrong without letting you know exactly what it is. In GraphQL, we should save the status codes for request-level network issues rather than semantic issues with the request or the response.
This reminds me of some physicist I can't remember trying to refute William Lane Craig's formulation of the Kalam Cosmological Argument, a classical Islamic argument for the existence of God going something like:

1. Everything that begins to exist has a cause.

2. The universe began to exist.

3. Therefore, the universe must have a cause of its existence, and that cause is God.

The issue is with the first premise. If you only understand causality from within a temporal framework, then your understanding only works from within a temporal framework. "Everything that begins to exist has a cause" presupposes the cause exists before the effect and that presupposition becomes incoherent at the beginning of time itself. If the big bang is the start of time, then nothing exists "before" the big bang because the very notion of "before" is meaningless without time. Our understanding of every event on the universal timeline is that it is linked inextricably by necessity and sufficiency to some set of prior events, and we call that causation, but attempting to use the same logic and language regarding the existence of the timeline results in paradoxical, meaningless statements.
> With this sentiment why is Saudi Arabia not more accepting of homosexuality then?

Because Saudi Arabia is a religiously fundamentalist theocracy and literally punishes people engaging in any activities perceived to suggest homosexuality with physical violence or death.

> Or, did their media push it down their citizens throats until accepted as is being done today.

You're using a metaphor that implies violent coersion. Can you elaborate on what you mean by "pushing it down their throats"? If you're referring to "overrepresentation"[0], can you elaborate who is doing it, why you think they're doing it (i.e. to what ultimate cause beyond "normalizing minorities") and why that is bad or objectionable?

It reads like you're trying to say a lot of things you don't want to spell out but I'm not sure what they are. Just to be sure: I'm a white European heterosexual man, you don't have to worry about offending me.

[0]: If you strictly mean demographic proportions, I guess is fair when applied to shows and films individually, though I'd like to see some numbers if you want to claim that this applies to Netflix's entire offering as a whole.
> this isn't a Jame Bond movie.

It doesn't take James Bond to lift some fingerprints off a surface. Anyone with physical proximity and a little practice can manage that much. People have managed to fool fingerprint readers with Gummi Bears before, much less specially-designed equipment. It's a practical attack, unlike attempting to brute-force a truly random 10-character password from a 78-character alphabet (uppercase, lowercase, digits, and half of the 32 symbols on a PC-104 keyboard).

> Secondly, humans can't remember\generate truly secure passwords, unique for every account they own. they usually rely on a tool like a password manager.

Which is perfectly fine. You aren't going to break their password manager either. The weak point is the users who aren't using password managers, because they try to get by with less-than-random passwords which are susceptible to cracking. Or biometrics, which aren't secret at all.
Yikes. Ego and open source do not mix well.
"Effective Altruism" ultimately fails because money is mischievous and has a mind of its own. That is, if you devote your life to making as much money as possible you've already given up your agency and it's almost inevitable that you'll do more harm making the money than you can possibly do good spending it.

https://en.wikipedia.org/wiki/Marx%27s_theory_of_alienation
I don't know what devil you are representing? The assertion is that you can buy a new 4G phone today and get booted off their network for using it because it is not on a list of phone models they sold.
Did mine at 50.
Two things:

#1. The fundamentals are the same, but a lot of things have changed in the past 30 years. The coursework, somewhat, brings you closer to up-to-date.

#2. Non-FAANG. Looking to be a director or a tech fellow? No formal education during your career is a bad signal. Of course there are exceptions, but it is expected that you have invested in yourself (MBA also meets this requirement).

My personal achievements:

#1. Greatly improved my writing skills.

#2. Understand deeply and can communicate technical concepts that previously I dealt with on the "gut feel" level.

#3. Able to identify ignorance and stupidity in my leadership directly, where previously I lacked enough context to be sure of them being wrong.
In the future, when you think someone is being a fucking moron, never actually call them a fucking moron. Because if it turns out they weren't a fucking moron and you were wrong all along, you're going to look, well, like this.

The way to navigate the conversation would have been something closer to this: "I thought it was already doing this, but I'll check again, maybe we misread the doc. Also there's X, Y, and Z to consider that may make what you suggest harder than it seems on the surface".

That all being said, I kind of don't like anybody in this kerfluffle. I think your assessment of his character isn't terribly off the mark and now you're caught in a version of "the worst person you know actually has a point".

Now, we can sit here and discuss whether his approach engendered a response in kind or not, but at some point, someone has to be the duck and let the personal slide off their backs.
Would this solve the problem described? Sounds like the annoying part is solely on the front-end, the unpacking/flattening of what the Postgraphile service returns. From their description, I wouldn't be surprised if they were already using Postgraphile or Hasura as "the graph layer".
Section 17(a)(2) and (3) of the Securities Act

"(2)to obtain money or property by means of any untrue statement of a material fact or any omission to state a material fact necessary in order to make the statements made, in light of the circumstances under which they were made, not misleading; or

(3)to engage in any transaction, practice, or course of business which operates or would operate as a fraud or deceit upon the purchaser."
Google minimizing its own screen time is smart, but I think it's harder to encourage this at the ecosystem level. For example, a useful but flawed metric for deciding whether a search link is good is that the user clicks on the link and doesn't come back for a while.

A user bouncing off a website immediately shows that it's probably a bad choice for them, but unfortunately not bouncing off it sometimes means that the website is gaming the metrics by wasting people's time through whatever means.

In particular there are websites that are automatically generated in a way so you don't figure that out immediately. They look like they might answer your question, but under closer inspection it's nonsense.

Videos that look like they might answer your question are another example of a time-waster.

In a way, websites where you can see immediately that it's not what you're looking for are better than the ones where it's unclear. Best would be actually finding an answer. That can't be judged by screen time, though.
Ok, use https://github.com/join-monster/join-monster. If you need autogeneration from the DB instead of hand-curated joins defined on the schema, consider https://www.graphile.org/postgraphile/ or https://hasura.io/.
Sounds like a pretext to begin regulating tech like finance.
Maybe yes. It was very weird: even without sending any error messages to Sentry, it was still slow just by having the composer package installed. Some Sentry DNS thing? (https://docs.sentry.io/platforms/php/guides/laravel/#configu...)
> GraphQL is a great experience when you consume it and the service fulfills your query needs. Because you just ask stuff and you get them. It's really cool.

How about caching? It feels like GraphQL tries to win some (arguable) flexibility in putting together clients and in the process throws out most of the operational advantages of resource-based APIs with significant disadvantages in both how to put together a backend.
If you had a rigorously defined system you could put rigorous limits on it.

If it's not rigorously defined there are no limits, just what people can get away with.

With GraphQL you get the worst of both worlds that people can't write arbitrary queries but they can still trash the system. At least with undefined semantics people don't need to argue about whether or not they got the right answers.
It is a good way to communicate though.
Yeah zsh is even the default shell in modern macOS. So either target zsh, or POSIX sh.
> NVIDIA agreed to a cease-and-desist order and to pay a $5.5 million penalty.

So roughly 0.02% of last year's revenue. Basically a warning, I guess.
I am with you. Every time I looked at GraphQL or asked to implement one, I had to say no.

How is this a good thing for the backend or infra engineers? It's a mega facade without a lot of toolings to help the backend.

GraphQL reminded me of common ORM criticisms. Wide API surface area with a lot of rooms for accidents. And GraphQL made it worse by being exposed as a service.
This really only gets people with a certain accent though.
If even their own operational telemetry were misrepresented, one might have started wondering about the accuracy of what they're reporting to their customers.

So, I agree, but it's not like they really had a choice :)
> Sometimes though, the path it takes for the code to reach the part I'm interested in can be pretty obscure. It's in these cases that the debugger truly shines.

I feel that it is the opposite. It is where the path is obscure that logging works really well. It can be iteratively refined and repeated.
> GraphQL is a great experience when you consume it and the service fulfills your query needs.

Unless you already know SQL, and you realise how small and simple the queries could be, then it's really not a great experience to be forced to use graphql.
I've pointed out flaws to the dev team at MS they were pretty quick about acknowledging it and fixing the problem. There were some showstoppers in the media encoders early on when they were developing win10. The only thing they asked is that I prove the issue was real and as soon as I did they were on top of it.

They were also pretty quick and helpful with answering any question I had. I guess it depends on what team you get ahold of. Or, maybe how you ask the questions. I always try to be polite and patient, which is hard to do when you're in a time crunch.

They really were trying to push azure hard in a situation that didn't require it. It was odd at the time. I chalked it up to the team evangelizing a new feature that they knew was going to rake in money, so they were required to bring it up. I remember it was funny and a little annoying to have to keep saying no... now let's get back on topic.

But, they never insulted me. It was a very professional experience. Sad to hear this kind of thing is happening now.
A fake smile at least tells me they know that a different response would be unprofessional, rather than making the an unprofessional comment and not being self aware enough to realize it until it's pointed out.
Potassium atoms are bigger, so I think it's only 10^12 if you want to compare per-atom, but yes.
yup, A&A “filtering” anything is a sure sign…

That said, their solution to complying with the law seems well thought out and I appreciate their detailed explanation.
> It was an awful attempt at an apology

> Counting check marked boxes on a wikihow list isn't a good way to measure the quality of an apology.

If anything, it's a way. Suggest something better for your definition of "good", as it looks like you're making a speculative criticism for your own edification.
Regardless, both murder and capital punishment are state level issues.
mobile ad cancer
Seems like projection, and everyone upvoting this is sharing in it because it's the case for the vast majority of us.
Spending money on charities effectively does not necessitate maximizing income at any cost. But in the first place, generating high income does not necessitate imposing harm. A marxist would construe that it would by virtue that they believe all enterprise is exploitation, not by measuring harm.

What I infer (but is left unsaid) of the denigration of EA on the part of far-left ideologues is that they think charity is a joke. They will not promote it, on the conceit that it would undermine the Socialist mission. The outcomes for beneficiaries are irrelevant.
"Beauty" it not a word I've ever heard associated with Java GUIs before. From browsing screenshots Swing looks to me like non-native 1990s clunkiness. Am I missing something?
Playing devils advocate here:

Is the status code query specific or request specific? If I have a resolver that can handle multiple queries, does it matter if one or more queries internally fails? Doesn’t that mean the request was either degraded or failed entirely? Seems like extra overhead for the frontend when the queries are just a means to data which is generally parsed and validated anyways, so aren’t query-level status within a single request sort of redundant to a frontend?

IMO status code should be request level, but I can see the reasoning you’re presenting about query-level. Interesting thought.
> It's not that the tech they're critique is really bad

I think marketing is somewhat to blame here. I work in the GraphQL space and there's not a lot of incentive to do neutral education.

The goal is to get users to associate "GraphQL" with particular products/implementations.

Half of my dayjob consists of explaining to others why $OTHERCOMPANY is not a competitor, because despite us both being GraphQL tools we do orthogonal things. Marketing doesn't help this.

On top of this, GraphQL is (in my opinion) pretty complicated. It's not explainable in a sentence the way you can RESTful URLs, it takes a bit longer to grasp.

Despite all of this, GraphQL is the best thing since sliced bread as far as I am concerned and I will continue building services in it until something better comes along.
Oh nice! No more futzing around with GPG. You just made my day.
Took this journey myself 8ish years ago to learn Clojure. I think by default most experienced devs in other languages will find it frustrating.

It seems to be a language where it is frustrating up to a certain point and then once you cross over that line, somehow it just all makes sense and seems so elegant you almost can't go back to other languages. So just know that if you keep going you will be in for more frustration, but the tip of the peak will be there eventually and then it all falls into place.
NVIDIA is required to monitor material risks to its business and disclose them to shareholders. I think in theory the reason for that requirement is so that unsophisticated retail investors don't buy the stock and then lose a bunch of money due to risks they didn't anticipate, though it feels pretty quaint to expect retail investors to read Forms 10-Q.

Importantly, they did (according to the press release) know that a big part of their sales growth was from cryptomining. I have no idea how they measured the magnitude, but miners weren't exactly quiet about scooping up graphics cards.
They are engaging externally because the issue has gained traction in the community. I also don't think people need to be grateful because they were blessed with a response.
Yes, it's a rate.

This isn't household energy consumption, it's per capita energy consumption.

Take the 100 Quad (quadrillion BTU) total annual energy usage of the US and divide by the 330 million population, and convert the result to kW:

You have: (100 quad/year) / 330 million
You want: kW
* 10.131338
/ 0.098703643

The net power consumption for each American is 10 kW constant. That's about 10 electric hair dryers running 24/7/365.

It accounts for all energy usage --- domestic/residential, transportation, commercial, and industrial. As well as lost (waste) energy.

And yes, it's a lot.

The 2021 actual total US energy consumption was 97.3 quad. So I'm about 2.7% high. That's still 9.9 kW constant though.

https://flowcharts.llnl.gov/
I don't know about others, but that does sound like a real apology to me. At least they plainly write that they were wrong and not only "sorry for how this was handled" or something similar. I'm really curious what more you could expect...
This is great advice (except the server admin part :-) !!)

It's sometimes tough to dissociate the problem with the people involved. Hope this will have a positive resolution as most of the people seem to be experts at what they do.
Just wait till the feds find out that my "gaming" card has been used extensively to train pytorch models. Book um danno!

Are you telling your investors that you're using your gaming card for games, and then using it for pytorch models?

Remembering that this is the SEC, not the FBI, gives you a lot of context.
Thank you for your suggestion! I believe I can't just edit the article now, since that would be disingenuous, but I'll try to avoid sarcasm in the future and use something like you suggested instead.
I just keep imagining a neon green crocodile wearing a backwards baseball cap while surfing on a keyboard, with a big RB! on their shirt in a paint-splattery font.

Maybe a little hard to fit all that on a toolbar-scaled icon. Just RB! in paint-splat neon green would go a long way to increasing the RAD FACTOR though. :)
But not to Casey. You dotted out who they apologized to and it was not the person they insulted, but to the "community".

> We were wrong. As such, we dedicate this experimental renderer to the community as an olive branch. We know we have so much more to learn, but we hope that you will accept our apology and understand we’re humans behind this product with a capability and willingness to learn from our past mistakes.

Seems rather childish.
> Any idea why so many would be bisexual vs fully homosexual?

Note that the 20% gen-z study also said "Gen Z women are roughly 3 times more likely than men to identify as LGBTQ", so a 5% : 15% split. And, you know, bisexual woman age 20-25 being LGBT is technically correct, the best kind of correct.