skysight-inc/HackerNews huggingface dataset:
These are just assertions with little to back them up. As TFA says, you can make all the same claims for REST. And GraphQL works the same as REST. But instead of a complex mishmash if positional and named parameters, it has a super simple query structure.

When you create a stack of REST APIs, you’re creating a DSL. But it’s a DSL with arbitrary and frequently undocumented relationships between objects, no type safety, and masses of hidden complexity.

GraphQL is simple. If you don’t think it’s simple, you don’t understand it.

> One big issue of GraphQL is also that API clients tend to suck. That's not a problem for OpenAPIs.

The clients are unnecessary. You can get ridiculously complex clients for REST, too. But you can also use GraphQL just using fetch().

The only material difference between the two from a client perspective is:

* REST gives you everything, even if you don’t want it

* GraphQL requires you to request what you want using a minimal query language.

GraphQL also lets you perform multiple queries in parallel, on the server, which REST can’t easily do.

REST is a PITA for any data model that’s more complex than CRUD.
It would let you paste a lot of existing markdown into google docs
Not types, functions. Where the macro is essentially a forward declaration but the implementation is deep inside the code and is not exposed via headers.
How is anybody supposed to know if it was worth it?
I've never met any maintainer feeling entitled to their users' money, most commonly I've seen users feeling entitled to support, premium support and 247 support, and bespoke features, from open source maintainers, wtf is this guy talking about, just few weeks ago there were people from microsoft expecting priority fixes from ffmpeg for free
I think on the first read I didn't get that your article was basically about 'floating times', which upon a second read I totally agree is a weird default and good to avoid!
Or, more likely

Increased productivity => increased profits => shareholders see number goes up => number must go more up year on year => everything (including safety) falls to the wayside in the pursuit of more profit
yeah matches my experience
Yes, project managers easily can have that level of comprehension, but it is rare to meet a project manager that understands that a time range is something like a confidence interval. That is, if it is estimated a task will take 3-9 weeks, with some probability (say like 10%) it will take an even shorter or longer amount of time. There is uncertainty encoded in the time range, but the time range itself is also uncertain.

Fundamentally, the problem is that project managers set deadlines based on statistical estimates from developers. Despite the fact that they set the deadline and do not understand the dispersion, they want developers to be responsible for misses. Sometimes, people mistankenly believe that there
is some magical practice that can eliminate the uncertainty from estimation. You can make predictions with things like story points and achieve a certain amount of accuracy with a certain amount of dispersion. Statistically, it is the longitudinal behavior that can be predicted (sprint success rate at a specific velocity on a stable team), but we focus on cross sectional details (we missed this sprint).

Project management is generally not considered a field requiring statistical expertise but modeling reality of the work requires it.
Personally I found the biggest problem for local models is the lack of integrationa, it can't search the web, it can't use wolfram alpha for math, etc

LLMs are great as routers, only rarely are they good doing something on their own.
GC doesn't have to stop the world. There are fully concurrent GC engines.
Are you just repeating a thread that went viral on reddit or have you had personal experience with this?

Because after that reddit post I asked all of my Swedish friends who are parents, none of them said it'd be normal to not serve dinner to their kids playdates. And I don't think anyone said it's happened to them when they were kids either.
Since my neighbouring comment (https://news.ycombinator.com/item?id=40983181) brings up a good point which I also would have brought up, I want to give another point:

At school, there existed some classmates who hated math as a school subject, but nevertheless loved my ramblings about mathematical topics (well, they were at least more interesting than some other school subjects). Nevertheless, I guess my style of motivating people to like and do math would not be loved by parents: it it rather of the style "I'll explain you stuff about plant and process engineering so that you can build a weed farm that will be harder to detect by the police" for math, i.e. explain what subversive stuff you can do if you know math. I don't want to go into the details here.

This is deeply motivating for particular kinds of kids (with punk traits) to become quite interested in mathematical topics, but of course many parents would hate it because my teaching methods for math turn the child into a bad citizen. ;-)
It’s a pretty powerful one-liner right? ;)
Wiktionary says of Erdapfel (which OP admittedly with '?' wasn't sure how to translate):

> From Middle High German ertapfel, erdapfel, ertöpfel, erdöpfel, ertaphel (“mandrake, cucumber, pumpkin, melon”), from Old High German erdapful, erdaphul (“pumpkin, squash, melon”)
yeah exactly only $100M/yr? barely covers expenses
Neat. That's the 2024 European Championship Football tournament.

The basic open data is free, but doesn't include the "360 metrics" table (requires data subscription) for the following real-time data for each player, so saying "free data" is a teaser:

50_50 bad_behaviour_card ball_receipt_exceeds_distance ball_receipt_in_space ball_receipt_outcome ball_recovery_offensive ball_recovery_recovery_failure block_deflection block_offensive block_save_block carry_end_location clearance_aerial_won clearance_body_part clearance_head clearance_left_foot clearance_other clearance_right_foot counterpress distance_to_nearest_defender dribble_no_touch dribble_nutmeg dribble_outcome dribble_overrun duel_outcome duel_type duration foul_committed_advantage foul_committed_card foul_committed_offensive foul_committed_penalty foul_committed_type foul_won_advantage foul_won_defensive foul_won_penalty goalkeeper_body_part goalkeeper_end_location goalkeeper_lost_in_play goalkeeper_lost_out goalkeeper_outcome goalkeeper_position goalkeeper_punched_out goalkeeper_shot_saved_off_target goalkeeper_shot_saved_to_post goalkeeper_success_in_play goalkeeper_technique goalkeeper_type half_start_late_video_start id index injury_stoppage_in_chain interception_outcome line_breaking_pass location minute miscontrol_aerial_won num_defenders_on_goal_side_of_actor obv_against_after obv_against_before obv_against_net obv_for_after obv_for_before obv_for_net obv_total_net off_camera out pass_aerial_won pass_angle pass_assisted_shot_id pass_body_part pass_cross pass_cut_back pass_deflected pass_end_location pass_goal_assist pass_height pass_inswinging pass_length pass_miscommunication pass_no_touch pass_outcome pass_outswinging pass_recipient pass_shot_assist pass_straight pass_switch pass_technique pass_through_ball pass_type pass_xclaim period play_pattern player player_id player_off_permanent position possession possession_team possession_team_id related_events second shot_aerial_won shot_body_part shot_deflected shot_end_location shot_first_time shot_freeze_frame shot_key_pass_id shot_one_on_one shot_open_goal shot_outcome shot_redirect shot_saved_off_target shot_saved_to_post shot_statsbomb_xg shot_statsbomb_xg2 shot_technique shot_type substitution_outcome substitution_replacement team timestamp type under_pressure visible_opponents visible_teammates
Ahh yes, LLMs ( preneutered!) may cause a resurgence of diagramming (used in vengeance)

https://terrytao.wordpress.com/2023/11/18/formalizing-the-pr...
What difference does it make? It's not like most GenAI provides more value than random tokens.
This article is filled with odd takes.

> But, like most people, I’m not persuaded by those who release something into the world for free, and basically guilt trip people for it.

Who guilt trips their users into donating to them?

> To bring food to the table; that’s all you have to do. The key mistake is to confuse the sustainability of your hobby with your own. Free labor is inhumane, yes. But in the case of open source software, it is self-inflicted.
> Do it at least to make your job easier. Let the FAANGs pretend they do it selflessly.

Do you perhaps not love writing software as much as the title suggests?

Is it inhumane for a cook to prepare a meal in his free time?
Is it inhumane for a mechanic to change a friends oil?
What's free labor about open source hobby projects?
> (except the middle east)!

Indeed. Such displays aren't meant to change what people believe, only to make people feel good by affirming what they already believe. In places where the majority don't feel that way, the display is omitted. It's cynical pandering, not earnest activism.
Doesn't sound too serious.
GraphQL is painful. I am thinking some SQL but with more access control would be better.
They meant here on HackerNews. The only thing I really miss sometimes is a way to quote without resorting to indented code blocks.

> Just a tiny hint that any paragraph like this starting with a greater-than sign is a quote.
This line is so disconnected from reality I wonder if he's using a LLM to write blog posts.
It's a different model. Microsoft did work on green threads a while ago and decided against continuing.

Links:

https://github.com/dotnet/runtimelab/issues/2398

https://github.com/dotnet/runtimelab/blob/feature/green-thre...
> First of all, Nadella has created a trillion dollars of value over his leadership. His pay packet of $40m is nothing

Unless he was going to pay out of his pocket if he bankrupted Microsoft, that argument doesn't pass the sniff test.

Also, he has created a trillion dollars of valuation. That's not the same thing as value, just ask the Japanese property market in the 1990s. Current stock price can also entirely disconnected from reality and mid to long term future, just ask GE and Boeing.

If the AI/LLM hype dies down, a big chunk of that valuation will disappear, without anything meaningfully changing.
I agree with you that gender or color of the skin has nothing to do with how well can someone write code. Both gender nor skin color should not be any factor in hiring.
There is a whole industry centered around this practice of grabbing expired domains, putting back the content based on internet archive snapshots, and using the SEO juice to help rank money sites. Nobody will read these blogs, it's just for google crawler's eyes.
Hmm, this is a really good questions and would definitely require a bit more information about the customer relation to fully answer.

In a setup where you can deprecate fields and remove them after X weeks I think it could wor well - My impression is just not that enterprise works like that?

I would probably go the route of having fully versioned APIs in the specific setup (GraphQl or not) - which is something that would be a hassle with a tight coupling between the Prisma schema and the GraphQl schema as proposed.

Thinking about it, all the situations where I have successfully used GraphQL, there has been a relatively tight coupling between the database schema and the graphQl schema. Previously it has been Ecto + Absinthe + Zeus (Elixir on the backend).
> I've never met any maintainer feeling entitled to their users' money

Exactly. What I'd like to see more is: "There is a bug that $COMPANY wants fixed ASAP - how about you pay me or one of your employees for _that_?"
It depends on whether your chosen platform can do it.

If you're coding resolvers by hand, that is not fun. But for example the Lighthouse GraphQL layer for Laravel (it's a schema-first thing based on the Webonyx PHP GraphQL reference implementation) can do a lot of this for you using schema decorations.

https://lighthouse-php.com

It has where/filter/sort/pagination, automatic scope narrowing etc., and you have very little code (if any) beyond the graphql schema to set it up. It integrates brilliantly with the Eloquent query builder.

One of the best applications for PHP IMO; it is really enormously productive.
That makes sense, you are just the right amount of racist when hiring
> PHD, MD, DDS, DO, OBGYN

PhD is an "almost initialism" :P and would be very hard to read without spelling out the letters.

MD, DDS and DO are initialisms and there's no other way to read it.

ObGyn is more of an acronym and it would make sense to read it as a word.
Goths aren't extinct, they were from southern Scandinavia and their descendants are Scandinavian people.

Aztecs became the Nahua people in Mexico, there are millions of them so not extinct.

I'm not well versed in Celtic people but I guess it's the same as the Goths and Aztecs, their descendants live today in Scotland/UK/Ireland/wherever they moved.
I did some similar testing a few days ago[1]. Comparing platform threads to virtual threads doing API calls. They mention the right conditions like having high task delays, but it also depends on what the task is. Threads.sleep(1) performs better on virtual threads than platform threads but a rest call taking a few ms performs worse.

[1] https://davidvlijmincx.com/posts/virtual-thread-performance-...
DEI: diversity, equity and inclusion. Is it just me not knowing (article didn't define it)?
I personally think GraphQL delivered on quite a lot of its hype, and I have become a bit more forgiving of web dev hype cycles in the light of crypto, NFT and generative-BS hype cycles...
It is much harder to build something vast than it is to haul a lump of rock up a hill.

Nadella may not be carrying rocks but he's the one figuring out which rocks and where they should go.
But it's not so scalable as online connected DB.
Betting.
Dispersion-assisted high-dimensional photodetector
> Well, they’ve been trying to fight the advertisers for, oh, 2 decades now; and the advertisers have basically won every fight repeatedly.

Who has been fighting the advertisers? Mozilla? No, they haven't even included a basic ad blocker with FF, only some lackluster "tracking protection" that barely anyone is going to enable (while implementing whatever new privacy leaks Google proposes). If the advertisers have won any fights it is only because Mozilla hasn't even bothered to show up.
Maybe C# is going to have a new asynv await model but the fragmentation of libs and codes cannot be undone probably.

Java has the power that they make relatively more decisions about the language and the libs that they don’t have to fix later. That’s a great value if you’re not building throw-away software but SaaS or something that has to live long.
> I've not yet seen a study that shows that virtual threads offer a huge benefit.

Not exactly Java virtual threads, but a study on how userland threads beat kernel threads.

https://cs.uwaterloo.ca/~mkarsten/papers/sigmetrics2020.html

For quick results, check figures 11 and 15 from the (preprint) paper. Userland threads ("fred") have ~50% higher throughput while having orders of magnitude better latency at high load levels, in a real-world application (memcached).
FBI cracked Trump shooter's phone with tech from Israel's Cellebrite
Disney – Design and Control of a Bipedal Robotic Character
Why would websites bother with an arms race to block a browser barely anyone uses?
I’m considering finding another line of work so that I can persue my lifelong passion around software without a bunch of godawful sociopaths turning the levers.

I imagine I’d be only middling as a car salesman, but it would hopefully be enough to hack for the joy of it again on nights and weekends.
> - Even in language learning. We have the useful fiction that there is a 1-1 relationship between words in two languages, but there almost never is.

It's not really a problem: space repetition is a way to build familiarity with vocabulary. Once it is done, more finer uses can be inferred from context. The value lies in breadth not depth.
Since they cancelled the work on zluda and absolutely fail to do anything about other options, I really believe there's some "don't do it or you'll get sued to hell and back" agreement. They can't be so dumb they just miss it by accident.
I find it really useful when your API accesses many different data sources, especially if they aren’t ones you control. You can make requests out only if you need to based on the query fields. It’s a great layer of glue for other APIs. If those other APIs are also GQL the process is very easy on your end.

GQL can abstract auth layers for external services, the user only has to auth with your service. The user only has to keep track of your single GQL url path instead of remembering “GET /users, PUT /posts, etc”. You’d probably have a premade GQL playground setup at the single URL too. If you forget the query options, do an introspection query, which most interactive GQL clients do in the background for you. It also makes caching/memos really easy, as you can memoize the GQL layer based on user query instead of implementing it for each upstream resource. Same deal with rate limiting. Also being able to ask for arbitrary number of resources by just making more named queries in a single request can be useful.

Having the .gql file be THE source of truth and typing for your schema is really nice. Most other setups I've seen like OpenAPI are usually disconnected from your actual API code, where it’s technically possible to diverge from your stated schema.
When I started to work at a big company on car safety, my manager told me as a joke: "the safest car is the car that doesn't move".
No what it means is that instead of hiring bob's friend another white dude and then james that guys best bud you pull some resumes and do some interviews in hopes of not missing out on qualified people.
First, that was not me who you just responded to.

Second, I don't think it's very comparable. The big drawback of "RESTful APIs" is that you cannot combine things. You call an endpoint and you add some query parameters, that's pretty much it.

In Graphql, you can combine and even nest queries. You simply cannot (or don't want to) generate all combinations in advance, so you'll decide adhoc in your code. Therefore you need a library that can do these combinations adhoc for you in a typesafe way.
My employer uses Microsoft as a single sign-on and the poor UX is a huge risk. People just get sick of endless shoddy login prompts and authenticator app warnings. It trains users to enter credentials without enough thought. Something like passkeys could be so much better. Security needs to consider unintended consequences of user behaviour much more thoroughly.
Better link: <https://dilbert-viewer.herokuapp.com/2004-03-28>
I don't have the numbers to back this opinion, but I believe that consistently ranking in the top 5% in all the games will greatly increase your chances of winning the league. It's not necessary to win every stage, but just having high scores consistently will likely make you win the league.
I’m not sure if they still use it, but there was an Inertial Reference System on board - you set your location at the start of the flight, and then it can (roughly) give you a position using dead reckoning. A large disagreement between this position and the GPS position would result in an alert.
So if most of the issues with GraphQL are the same as with the other approach, what is the point of GraphQL that justifies all the complexity?
Boosting PHP performance: mastering OPcache optimization with Blackfire
Safety is not a “luxury enabled by profit”. It’s one of many necessary dimensions for efficiently creating value over time.

If you are a sole trader and you fall off a ladder and hurt yourself because you took some stupid shortcut, the cost is extremely high.

If you work for someone and they make you do something stupid that hurts you, the cost to them has traditionally been relatively low, so they are motivated to push you because that’s better for them. Fortunately, in most modern countries this is no longer the case.

Safety only becomes a “luxury” when capital becomes concentrated into the hands of people for whom other people are disposable.
If you are already in a reactive framework, why would you change to virtual threads? Those frameworks pool threads and have their own event loop so I would say they are not suitable for virtual thread migration.
> It's like the author views their entire world through a lens of financial transactions

Title of the blog: Money in Transit

> and can't understand why anyone else sees it differently.

I didn't get that impression at all. My take is that he's simply providing a view of OSS through the lens of financial transactions.
No More Tears, No More Knots: Arena-Allocated Trees in Rust
It's important to sometimes remind entitled people to the four Effs of FOSS. Fix it, Fund it, Fork it, Fuck off/Flee (in that order).
Years ago MS decided to exploit IRC a very similar way by producing https://en.wikipedia.org/wiki/Microsoft_Comic_Chat - IRC networks and Channel operators hated this shit. It would add a tonne of extra encoding characters that weren't hidden in normal IRC clients.

All of this was because they wanted the critical mass of users and didn't want to work at establishing it themselves at the time.

(The funny part of it being that on the larger channels and networks, Comic chat was completely incapable of handling reasonably the large amount of chat volume in a channel)

Feels very similar where MS' entire philosophy is, if it works for us, we don't care if we spam non-MS people relentlessly.

Course it doesn't work that way, Sys-admins just end up banning/filtering or doing other work arounds to prune it.
Not especially efficient? Hmm, I'd noticed that range per kWh varies a lot but not checked in detail. That's disappointing.

The Ioniq series look amazing and are very popular, but are significantly larger cars (disadvantage for me, maybe advantage for others).

Edit: on.to? oh.no more like:

> "On 11 September 2023 Jonathan Lees and Gavin Maher of Teneo Financial Advisory Limited were appointed as Joint Administrators of Onto Holdings Limited. On the same date, Gavin Maher and Ian Wormleighton were also appointed as Joint Administrators over Onto Tech 1 Limited, Onto Tech 2 Limited, Onto Tech 3 Limited and Onto Tech 4 Limited, each a subsidiary of Onto Holdings Limited (together "the Companies"). "

:(
Or just publish the code on Github (or whatever platform you like) and then not interact with it. Whoever wants to make improvements can just fork your code, it's literally a button away.
In a farm, with a house building being shared by a large family or a few smaller ones, sharing beds in the same room to keep it warm during winter. Just like anywhere else in Europe at the time.
> but you dont seem to care if house and contents insurance doesn't insure people whose house is currently burning.

That is the case. If your house is currently on fire, no one will insure you. What are you doing about this awful situation?

> Therefore, medical "insurance" should not be insurance, but should be a fund. It should be paid into by all taxpayers at some rate proportional to their income (like VAT), and then the fund goes to fund _all_ non-elective medical procedures.

You seem to be extremely US-centric. You can't differentiate between "how the US does insurance" and "fundamental truths about insurance". This discussion is not just a proxy for an incredibly well-worn, and separate, conversation on US healthcare.