skysight-inc/HackerNews huggingface dataset:
I'm a native Chinese. I think it's 猪扒 饭 or 鸡扒 饭, 猪扒=猪排=pork chops*.

Note: 排 literally means ribs. But this dish has been evolved quite a bit and now 猪排 could be any part of pork, and I'd say pork chop is actually more common than actual ribs nowadays. Same goes to chicken - 鸡排/鸡扒 is typically just chicken breast (not like chicken has ribs to begin with, hehe).
> anyone with a brain knew the cards weren’t going to gamers

Gamers, and industry insiders, knew this. The general public (i.e. most investors) didn't. Most non-desktop gamers couldn't give two figs about the intricacies of the videocard market, they just invest in growing companies/stocks.

Or, to put it another way, NVidia Stocks go brrr, buy. Nvidia stock no longer go brrr, complain.
>You find everyone is usually trying their best if you ever have face to face (except server admins, they are stone-cold psychopaths, stay away).

The server admin is a reflection of the union of the community of devs, maintainers, designers of their hardware, and users/benefactors of their boxen.

If your server admin is a psychopath. You may want to take a hard look what goes into keeping their boxen ticking along smoothly, and the demands of those using it.

Sometimes you get to be a peaceful, serene shepherd.

Sometimes, you're trying to keep that last critical link to reinforcements alive under siege from all threats, foreign and domestic, all at the same time.

Occupational hazard I guess.
Man this whole interaction really makes you guys look incompetent DHowett
What Is the Stock Market For?
Nope. FB would have gone the way of MySpace already if that were the case. Rather than a saturation point, they've hit a plateau in many cases- where will they go next? Zuckerberg is looking to reinvent FB for the next stage of growth. Instead of "moar better FB" he realizes that there needs to be something that's not just more, but different. And if he does it right, everyone will flock to it like so many did in the early FB days. Also, FB Marketplace is the new Craigslist in so many ways. Saturation point? No. Just maturing and ready for the next stage of evolution- whatever that will be.
That there are other considerations for a seller aren't really relevant when the post is about bidding just higher than a round number to win it. Just as explaining how you won the bid at 2k lower by having a cash offer and writing a nice letter and being accommodating with their move out times is irrelevant to the round number argument. The story of bidding 701k is clearly in the realm of "all else being equal", nudging the price up a relatively insignificant amount can have a significant effect.
I wonder if they’re using the GPUs in radars.
Adressing issues directly in the wrong way is a much better motivation for PR teams to jump in.
You can combine multiple queries into one request in such a way that transport layer caching just isn’t effective.

If you’re making a content and read heavy website, you can run GraphQL over GET, and cache traditionally.

The spec says nothing about the transport layer itself.

Why return 200 for a request, when part of it failed?

Separation of concerns. Network layer errors are one thing, application layer errors are another.

They require different resolutions.

With a network layer issue, you could retry, or perhaps you need to fetch a new access token then retry.

For application layer issues, say you request data on 4 different entities, but the service for one of those types is down. Should you chuck out the whole request, or return everything and something like a Problem or Error type for the failed one?

Perhaps you tried to access a field you don’t have permissions for, or require elevated permissions. Should you fail the whole request, or return an error on the field itself, allowing you to inform the user what you need them to do to continue?

The point is precisely that the client processes the error closest to where it’s relevant. This works especially well with component based rendering.
I actually consider myself a bit left of center; definitely very moderate. Certainly by any US standards (hint, I don't live anywhere close to there). So, I kind of resent the gratuitous labeling a bit.

This is a simple case of objectively government projects around the world failing over and over again for more or less the same reasons. There are quite many studies on that topic. Lots of nice articles that get written whenever another one fails. So, that's not a right wing mantra against big government but a nice argument that maybe they should try doing things differently. Especially considering that there are some well run countries with more success on this front. Quite a few of those countries are what you might label classic big government states. I lived in a few of them (Sweden, Finland, Netherlands). These three have had some duds but also some successes when it comes to government IT projects. Overall well run places.
I just saw a Rivian Truck in the wild while I was on vacation this last week. I was really surprised as I hadn't realized they were shipping yet. It was exciting to see it, as I've been interested in the 2nd generation of new EV companies (Basically companies founded to make EVs following Tesla's success, not historic Auto makers) and whether or not they have a product to ship. A former coworker of mine left our old-world automaker employer to work at Rivian. I was interested in pursuing something similar, but at the time it would've meant moving.
Why does it matter though
I like that better than charity.

The profit motive motivates Boeing to make the 777, motivates Microsoft to make Windows, etc.

In non-profits, frequently, money works its mischief unopposed, but the motive of "you can make a huge amount of money for yourself and your investors by satisfying a need" is a force for good.
Having had lived in urban areas all my life, American urban cities are criminally under built. There is sooo much room for growth (note room doesn’t mean land, it means airspace).

If you have a pastoralist dream, feel free to build rural housing units. But for the government to spread out the country and then try to connect it using extractive transportation technologies (gas, batteries etc) just seems like roundabout / inefficient way to achieve the same goal.
I am not a Pascal developer, but Lazarus + Free Pascal >>>>>>>>> Netbeans and Java. Seriously. Java looks like a turd everywhere and it's laggy and slow even on a mid range machine.
On older ones like my Celeron the lag on menues it's noticeable.

Also, modern Free Pascal has OOP classes and methods if you like these.
If you run software made in Free Pascal like Cartes Du Ciel and them some Java one like Sweet Home 3D, the first one will run circles on snappiness and speed over the second one.

IDK how Java can be appreciated, most of its desktop software runs far worse than AMSN over TCL/TK in early/mid 00's under an Athlon.
Yes, I’m mostly teasing. That said, you can’t guarantee that “yeet” won’t grow on the community though :-)
This reminds me of a story of Mount Everest - apparently the people who did the first measurement had it come in at exactly 29,000 feet - so they said 29,002 to make it sound like they weren't making it up. Official measurement now is 29,032 feet.
Read-only permissions still leave you open to resource exhaustion attacks.

On the write side, it's nice to have your query return structured data that can automatically update your client-side cache.
Hell yes. Good knowledge of SQL is a superpower and is becoming a rare art form.

The new generation of devs thinks that frameworks and ORMs will do the magic for them at no cost, but they don't. There is no substitute for leveraging your storage engine to the max.

The sad part is that databases have evolved and became much better in the last 20 years (I started with MySQL 3.x), but we just don't use them. Everyone acts like "microservices" solved all of our technical challenges. Right.
Better than working at Wendys!
I think this is solved by creating "full stack" teams where the front end developers who want the GraphQL API are also the same team who define the schema and build the service that serves that API. In large companies where GraphQL makes sense, that GraphQL API service would just call into pre-existing services that serve JSON, Protobuf etc maintained by 100% back end teams.
> There's so many blog posts saying look, we're so smart

Have you read Casey's twitter feed? The man routinely goes into long twitter thread rants about how stupid everyone else is.

His favorite target seems to be...drumroll please...large corporation software teams.
Not necessarily. There actually was significant growth in gaming with covid and there were lots of improvements with Nvidia's cards so it would be reasonable to assume most the growth is coming from that.

Public companies need to be ahead of risks for investors. If they weren't mentioning crypto mining in earnings reports then that doesn't look good at all.
Right, note that I said safe Rust, which is the vast vast majority of Rust out there. This is a major improvement over, say, C, where any line of code could be potentially unsafe.
Sure. A grown adult can take on a turkey, but that adult will definitely take some blows from the turkey's spurs. Like someone else mentioned, it's not worth it over a public space in the city.
The way M&A usually works is that all sides have bankers/advisers who run Excel spreadsheet calculations that come out with different precise numbers depending on a couple of scenario parameters. Those are put on PowerPoint slides and presented to management. The decision whether to go with one of the precise numbers (or some aggregate thereof), or some close by round number has more to do with bidding tactics, game theory and psychology, so I think this research actually quite interesting.

If you're a manager involved in some bidding process, what this article is telling you could be somewhat loosely rephrased as "use the Excel numbers rather than the ones that stuck in your head after the presentation", which is interesting advice.
Ask HN: Have you had your Miracle Year yet?
I was reading this Wikipedia entry for Einstein's so called 'Miracle Year'. From the entry:

> The annus mirabilis papers (from Latin annus mīrābilis, "miracle year") are the four papers that Albert Einstein published in Annalen der Physik (Annals of Physics), a scientific journal, in 1905

I don't think I've had my miracle year yet though, but there were certainly years in my twenties where I was supremely productive, and lately I'm just trying to recapture the wild creativity of those days and be more elastic & serendipitous especially when it comes to creativity.

Have you had your miracle year yet? Are you aiming to have one?
> the same backwards superiority from backend devs as I saw a decade ago

Again, even from observing you in this thread you've decided one comment represents all backend developers. You probably made the same mistake a decade ago. It's not us vs them. It's just some individuals talking.
Nice work! I recently built a similar page, https://letscooktime.com , might be good to compare notes.

On integrating with recipe APIs, you can scrape recipe structured metadata. Most web sites use the google structured data, you can query for a script tag with type ld+json and find the structured data. See more information here: https://developers.google.com/search/docs/advanced/structure...
The "Holy Roman Empire" was neither Holy, Roman or an Empire.
Photos: Deconstruction of the S610 Foudroyant in Cherbourg
Don't ever trust US publications with 0-60 times. They do those trials at quarter mile tracks.

There is barely any asphalt left there it's all tire rubble which increase the grip especially on launch.

The real data is from UK/DE magazines, they try on highways abandoned airstrips.

Going below 3.5s in 0-60 acceleration is like going past 225mph on pure speed. It can happen but all conditions have to align perfectly , hence it's not real world conditions.
https://en.wikipedia.org/wiki/Deportation#Military_occupatio...
I kind of agree. Their source map thing to get better traces is a nicety, but few would find it release blocking to forgo it

Edit due to other comment: this assumes CI/CD. If you were deploying only weekly then this might be good reason to delay
People don't make anything "truly new," they extrapolate from similar information they already have and build on what they know through association or translation, which is what machines can also do. No one who has never even seen an internal combustion engine is going to spontaneously invent a better one, regardless of how brilliant they are.
I hate engaging in surrogate activities which are only abstractly related to the things I need to survive. Even though I understand it's necessary due to the sophistication of manufacturing and the economies of scale of it all, it's mentally destructive.

The worst part of software development for me is knowing that all of my work will eventually be thrown away or useless soon.

I stopped caring about my work completely. I force myself to continue because only because it pays well for the amount of time I spend on it. I make much less than SV types on here. But it's much more efficient than any alternatives I have identified so far, even though I accomplish nearly nothing essential. My current job only exists because a bureaucrat decided their government needs to invasively monitor my company's financial activity. How useful!

I only care about my family, especially my children, and the time I spend together with them chilling, cooking, playing, and learning.
>This whole process is sucky for seemingly no reason. We found our own home we want and put a single offer and it got accepted and yet our realtor is taking a 2.5% cut.

Industry collusion in a free market can be countered by entering the market to compete. Offer 0.5% and people should flock to you right?

>Our mortgage officer only seems knowledgeable because they uses terms I can't understand but it seems like most of their work is just plugging my numbers into a calculator to tell me my options (and not really giving me much advice). Seems like I could do this myself but I'm scared my info will get sold to a million more people.

Precisely what it is. To give investing advice they require a fair amount of paperwork which they havent done. So they cant give you advice or risk being liable.

>These things are just the beginning and I'd imagine there are some tools or approaches that could reduce the pain, even just a little bit.

Here's the thing. Many of the western countries have switched to a service economy. 90% of Canadian GDP is derived from services. https://en.wikipedia.org/wiki/Service_(economics)#Service_ty...

A very high percentage of these jobs are bullshit jobs. You could basically just stop doing anything of any usefulness and nobody will ever fire you. When you break down where does the actual GDP really come from? It's Finance, Insurance, and Real estate.

So basically Canada's GDP exists in that for you to buy a house you need to artificially connect to these and give a slice of the pie. The incentive to a government or politician is literally the opposite. Any attempt to fix this broken system will mean an economic depression.

If anything happens, they will find a way to make more people involved. You can see that in Canada. You'll soon have the right to a home inspection. So now home inspectors are going to be a booming industry and yet another hand in the pie. In about 5 years they'll be proposing another hand.

Imagine as well, could the government come along and tax these entities? Canadian banks are world renown for their power. Do you think we could tax the banks or the others? No way. All taxes are going to target entities which actually do something. Oil industry, lumber, farming. The taxes can't target FIRE at all. Any amount of downward pressure on this unholy arrangement will be a disaster.

So the process isn't going to suck less. It's only going to suck more.
> prioritizing sales to an target audience that is known to be _extremely_ volatile.

Every crypto growth cycle is assumed (by enthusiasts) to be more resilient than the prior growth cycle, on the path to steady growth, and this has turned out to be true, with longer and longer steadier growth cycles, with less and less amplitude in the growth and troughs.

in 2018 there was the same optimism, that culminated in a long steep crypto bear market, the longest one so far. Although I think it is obvious that bubbles pop, especially crypto bubbles, I don't think it was obvious or relevant that sales to miners would disrupt so immediately that Nvidia investors needed to know this level of nuance. miners have such high profit margins (if integrated properly) that steep declines in crypto prices shouldn't affect them, but in this case it did.

Especially when looking at the resilience and structure of the mining sector now.

I think this is an odd demand by the SEC, but Nvidia settled it for pennies so moving on.
He had a column in the New York Times (https://www.nytimes.com/column/good-question-randall-munroe-...) that worked as a continuation of it in that 4 year gap.
Until very recently (a year or two ago?), the US didn't allow film studios to own movie theaters. Hadn't for something like 70 years. That was due to antitrust action over a situation pretty similar to what's happening with streaming services.
They can and are raising rates, but do you think it’s feasible for them to go full Volcker if that’s what it takes to beat back inflation? When I worry about the debt to GDP ratio, it’s not about whether we can withstand bumping from 0% to 1-2%, it’s whether we can withstand historically normal ranges, let alone what it took in the 80s.
Hah! Ironic that I see them mostly crossing Franklin Ave on my way to the dog park.
We actually took the same approach Casey suggested, at least when it comes to the drawing part which is what this is about. A lot of terminals implement it that way. We have a long way ahead of us to improve the performance of our text ingestion now though.

I'm not sure what role Casey's feedback had in this being considered for implementation. His original termbench tool was _incredibly_ valuable for sure, but I'm not sure later discussions changed the outcome of that. If we had figured out a way to solve the issue while we continue using Direct2D, we would've definitely sticked with Direct2D. Since there was no solution, there was only one other way to solve it and it's a way that has many other terminals already do it.
I’m intrigued by the fact that the press release focuses on cryptomining, specifically, but also suggests that the issue has to do with fiduciary duty. Would Nvidia have been charged if they had failed to disclose a similar volume of sales to, say, scientific research labs?

In other words, is this about the US’s policy towards (foreign?) crypto operations, or is it “just” about nvidia’s investors?
I'm not entirely sure what you mean with "unpacking/flattening", you have to do that for every API returning JSON?
Note that this is the announcement of a settlement. Nvidia agrees to pay 5.5 million, agrees to state the risk, and doesn’t admit to fault. No one is in serious trouble... nvidia should have indicated the risk, and didn’t... (probably because someone in legal fucked up). It’s not like investors didn’t know this was a risk!
It's pretty clear the disconnect here, there's one side that says "Do this optimization it's trivial" and the other side going "We have to write an entire text renderer that's far from trivial" and the result was this blogpost saying "Hey we didn't this thing and it was trivial! All we had to do was write an entire text renderer first". So in a straight forward sense yes, the concept is trivial, but in a more real sense it's not, since your straight forward idea is straight forward only once you've done something difficult.
I'm not speaking for 7952 but I'd say it's rather commonplace in most if not all anglophone countries. I'm in Australia and there's a sense of insecurity here but it's not as pronounced as in the US. Having worked in the US as well as Europe including Germany and Austria (living in Vienna) my observation backs up your comment (albeit that info is a bit dated now).

I could offer reasons as to why but they'd only be educated guesses. It's a big problem so some definitive data would be very helpful/useful.
I worked in the data federation space for a number of years (it's actually quite an old term, I worked in it back in 2013, around the time there was an early wave of activity around this and the concept of a "data fabric").

When I saw GraphQL come out, I knew that what you are saying would happen.

In the data federation tool I worked in, SQL was the interface abstraction to join across heterogenous platforms (think of things like Presto/Trino or Dremio). GraphQL as an interface requires the same underlying infrastructure as that data federation tool I worked on in terms of query analysis, parsing, planning, optimization, execution, etc.

Those are "hard problems" due to lack of standardized interfaces, access patterns, direct data access, I/O, network bandwidth and infra related latency, costs, compatibility, data types, etc. These problems are distributed system problems coupled with often incompatible interface layers (e.g., even if you are using multiple SQL databases with GraphQL, you run into the same).

If your scale is such that you can build GraphQL on a handful of systems and for a handful of use cases, great! If you have to go to a certain larger scale, you're back into federation territory (which in the app layer might also be called API composition).

One potential option - when you reach the point where you need complex GraphQL query coordination, more than seems to make sense to implement, pair it with a data federation tool such as Presto/Trino, Dremio, Denodo, or research approaches such as caching/materialized views (engines like that are becoming decoupled from databases, such as Materialize.io) - and let those engines do the hard work.

In that case your work becomes more like GraphQL -> SQL or API -> a data federation, caching or materialization platform. CQRS and event sourcing plays a role here too.

Consider also, the possibility that if you are willing to accept a bit of delay in aggregated results from multiple systems, doing those compositions or aggregations in the data platform layer, and simple feeding those to the GraphQL interface. That could even be done in a single database/data platform if you really wanted without too much fancy federation tech.

Federation is powerful but complex. It seems like a fun hard problem, but for many tech teams, it can be a complexity and time suck. My recommendation would be try to avoid building that if you can.
That’s a different argument than how much the minimum wage is. You would have the same problem with a $9 minimum wage or a $25 one.
But every possible chess move can be defined in advance, and therefore no "new" chess moves can be created. This is true of any endeavor which has fixed constraints -- which means all software code!

The miracle of humans, to put it colorfully, is that we can truly devise new information which never existed before -- not in any program or algorithm. We can make things possible which were not possible in a previous paradigm. This cannot be done in software, no matter how cleverly coded, for the software is always written with the information already in mind and already planned for.
Interesting... I would think symbolically deriving the Euler-Lagrange equations from the Lagrangian would be quite hard in practice.
Isn't a saturation point a synonym for a plateau?

Once something is saturated with X, you cannot add any more X to it.