skysight-inc/HackerNews huggingface dataset:
> Is it your fate now to do due diligence on every email you receive?

Always has been.

Tbh the browser/email client makers are complicit in these phishing attempts for hiding the URLs and the actual email addresses.

Put them back!
"Savor's 'butter' is easily produced and scalable, but convincing people to swap out butter and other dairy products for 'experimental' foods will remain a challenge for the foreseeable future."

Really? Margarine has always been pretty popular, surely this is not dissimilar.
...and they NEVER remember your preferences, well except your shopping preferences which will stick to you across networks and devices.
NextJS, Tailwind, and Shadcn have been quite reasonable for me on my new project
Gratuitous complexity is a strong attractor for today's "developer".
The implicit social contract with gifts goes both ways. You got it as-is, don't expect a commercial relation.

If you run into trouble with your gift, and you need it fixed by a particular deadline, either fix it or pay someone to fix it. If you find documentation lacking, write it. If you don't like the release process, write your own. If you want support for hardware I don't have, either find someone who has it or give me the hardware.

To date, I've seen two product managers from remarkably large companies ask for status updates on a feature because they have other internal features that need it. You don't get to ask for status updates on gifts. You want something tracked on a neat timeline? Great, put it on your team's Jira and get it done.
isn't this the same as genetic algorithms ?
Could you explain a little more about the Meta part and how they're using it?
Which is just time and effort estimations with extra steps and cargo culting.
at least it gave us Jerkcity
Good old Paul Bourke! Amazing how many interesting things he's covered on his site! Love that it's basically static html too, always nice and snappy!
> In retrospect, looking at tabletop RPGs felt backward because, by using the video games I already knew as models instead, I was benefiting from decades of RPG system simplifications—half the job had already been done.

This is quite a narrow view. Computer RPGs have, for the most part, focused on the combat aspect of the game as that is the easiest part to implement on a computer. Table-top RPGs have gone in many other directions. I find games that focus on story telling to be much more interesting than focusing on combat, and there are some interesting game mechanics that have arisen in these systems. One example is https://wildletters.itch.io/move-quietly-and-tend-things
Graphql adds an extra layer between client and server. You may gain some benefits, but you get extra complexity and some performance punishment as well.
https://en.wikipedia.org/wiki/Warren_Teitelman
> As developers we should show some sympathy, but some of my co workers didn't see it that way. They complained about the old TUI, while they themselves preferred using a terminal for git and other tools that actually have most of the functionality that they need in a GUI

At least for git, I prefer a terminal as well. git is easy enough to shoot yourself in the foot when you're using it in a terminal, but git GUIs tend to abstract away so much for anything more complex than "git commit/push/pull" that it's even easier, and way harder to recover from.
The problem with read receipts is that (1) it’s useful for spammers to see that their email went through, and (2) I don’t want to automatically share with people when I read the email or instant message, so i would turn off the feature even if spam wasn’t an issue.
Not only that, but the XPS13 hasn't had a barrel plug for years now... I have no idea where OP got that info from.
>I think it's already been hugged to death...

FWIW, I upvoted your benign and completely true comment. Why on earth should it be downvoted? I consider anyone that downvoted your comment as petty and small minded. But I am outnumbered. The fact is it happens here as often as any online public forum. So despite it's apparently admiral lofty ideals of mature debate, this public forum is overrun, like every online public forum, and detrimentally so, by what can mildly be described as immature, petty, and small minded white males, eager to be the first to remark, eager to 'score' more points, and be admired in this narrow arena. I am certain of this stance (as I am on occasion one of those immatures, though I would never sink to down vote such a benign remark).
I used to think like you. Until I used and understood the Relay GraphQL library. The learning curve is a bit steep. But if you are consuming a lot of GraphQL data in a web browser, this is totally worth the investment.

GraphQL really shines with data intensive applications where you need pagination, filtering, sorting, projections etc.
Wow, your comment led me into the rabbit hole. After some googling I'm not sure now whether the right representation is 3.1415926 or 3.1415927.
> Override the Host header to be equal to GTM-123456.fps.goog. Allow all cookies and query strings to be forwarded.

Did a security team review this? This leaks session cookies for your domain to Google in a way GTM did not previously capture.
I guess this would defeat DNS-based blocking approaches, but more sophisticated tools like uBlock can still cope with it, albeit requiring larger blocklists.
> Choose any path you want for setting up first-party mode. Examples of paths you might want to use include: /metrics, /securemetric, /analytics, or preferably a random alphanumeric string that you don't use on your website already.

Ah, yes, _preferably_ some random string that is hard to block rather than the descriptive ones.
I clearly remember checking out Volume 1 of Feynman's Lectures on Physics from local library, more than 30 years ago. I've read that stuff like a novel, refusing to return the book for the whole semester and was willing the pay the fine, ignoring the requests of the librarian :)

The idea that one could be taught physics by the virtual Feynman... oh my! There will be no better live person in the next hundred years, who could be better at the task than even fake Feynman.

Yes, I'm fully aware that the tech is not there yet and there are miriad of both technical and social problems to be solved but the mere idea of it really excites me.
Seems a bit simpler than setting up a Server Container. Am I correct in understanding that this is meant to run on a CDN or load balancer? I'm curious what kind of effect is has on performance vs making direct requests to endpoints.
One of the useful things I learned from a professor at my university is that every technology is good enough for its own use case. I still don't understand why certain engineers don't get this and go from "XYZ is awesome, I use it everywhere" to "I'm over XYZ."

Just like the title of the article suggests, GraphQL is great, but ONLY in the right context.
Used this product for a few months, helped me a lot by organizing all of the collected data for each idea that came up to my mind. Really helps with saving hundreds hours of coding by validating something won't work or needs pivoting after going through the whole process. Great service! Should be noted that the think I liked is the fact icanpreneur's team didn't stop working and is improving the product with every single week!
"The big challenge is to drive down the price so that products like Savor’s become affordable to the masses – either the same cost as animal fats or less," Gates wrote. "Savor has a good chance of success here, because the key steps of their fat-production process already work in other industries."

So it seems they're onto the price problem already. If they can bring the price down fast enough, maybe there's a chance for this product.
Oklch in CSS: why we moved from RGB and HSL (2022)
GraphQL is particularly useful for data intensive applications. That is what we use it for. I frequently see people try to use it for simpler applications and give up quickly because it does have a steep learning curve, if you are trying to do it right both on server and client.
The title of this article threw me for a loop. I was expecting a deconstruction in the literary sense.

Still, I didn't leave disappointed.
I've developed one thing that uses a GraphQL API and crying is definitely what I wanted to do. Why is it my job to dig through your schema to get a response that would be just a simple GET request or two with a REST API?
From when I was doing kanban there were, very intentionally, little to no forecasting done. We broke up a feature a bit and started chugging along. Every question from mgmt like "when will it be done?" was met with a "we are working on that right now, so asap" and that flew. However that was a stable product that was mature and had quite a few customers paying an annual license that were mostly happy, but of course appreciative for new features. Right now I'm working on a bigger product that fails to capture customers in a highly competitive sector and everything is about time and estimates. Middle mgmt is pretty stressed out and the latest bid is to estimate tshirt sizes. But really, it should be translated to time/increments.
Show HN: I made my bulk generator of short-content public to everyone
I am doing short-form content in youtube shorts and tiktoks, using youtube automation/tiktok automation.
For this I was using a handmade python script, but I decided to make it available to everyone and thats why I published video bulk pro

This is an MVP so I keep shipping new features and improvements.
I agree that many teams, in an effort to move away from waterfall development and Big Design Up Front, have gone the opposite way and completely skip system design. Which is a mistake, because you need some upfront design.

As Dave Thomas said: “big upfront design is dumb. No upfront design is dumber”.
This is thoroughly studied by psychologists. I feel obligated to tell you that multiple therapists have used access to repressed memories to control their patients. A large, highly organized religious movement overtly claims that its alien teachings are supported by repressed memories.
Glad someone mentioned the gift economy. So much discussion around FOSS reminds me of ideas from gift economy. E.g. the extent to which a culture assumes a gift is part of gift exchange, with some expectation of reciprocity. Or the concept of “giving while keeping”.

I think both ideas exist in copyleft licenses, but were lost in the more permissive MIT-style licenses. Sometimes I wonder if maintainers feel burned because they use more permissive licenses, which might be standard in their ecosystem, but unconsciously have a different gift culture.
I'm stealing the term Checklist-driven development. Combined with Cha Bu Duo it explains so much of what I see on a daily basis...
GraphQL is their business, so take this article with a grain of salt, it's not objective at all. It's on their best interest to promote GraphQL.
Markest thou well, good sir, thy words are naught
But foolish prattle. Forsooth, for many a year,
The younglings of sixteen winters have grasped
This very material with ease and little fear.

If thy premise held water, then, by the stars,
A woeful decline in linguistic arts
Would manifest itself in tests of old,
A downward trend that would not be untold.

But nay, 'tis not the youth that falter here,
But rather thou, dear teacher, dost impart
A lesson poorly taught, or else the pupil's heart
Doth not incline to learn, and doth not start.

Curb, then, thy zeal for revision's sway,
Not every task should be a trivial play.
Some things, by rights, should challenge and vex,
Lest wisdom's virtues be but empty text.
That was my question also. Verified by Cloudfare is also malicious.
> and backend people can focus on other things instead of going back and forth on perf issues downstream of REST APIs

Instead they now focus on perf problems of downstream federated GraphQL queries. And query complexity. And unbounded queries. And extreme overfetching of data that all clients inevitably do. And...
Where's the "crying" part? The GraphQL schema designed in this article is very trivial, nothing beyond a "hello world" level. There are no advantages to using GraphQL here, and many well-known disadvantages of using it anywhere. A REST API can have an endpoint that returns companies and their job postings, everything shown here can be trivially done in REST. And of course, there is nothing about how to actually implement it on the backend in a performant way.
> GraphQL does not provide any built-in mechanisms for filtering, sorting, pagination or other arbitrary transformations of the response.

GraphQL is just the protocol. It is up to implementations to add support for it. We use Hot Chocolate GraphQL server with entity framework backend, and it has built-in support for all of those things.

Vast majority of the criticism of GraphQL comes from people who do not understand it. GraphQL does have a steep learning curve.
Interview with Mr. Chuck Moore, inventor of the Forth programming language
If this is of interest, Wikidata contains a huge amount of data on file formats. For example, [1] is a huge list of file formats and [2] is a list of documentation or source code (structs etc) describing file formats. Other data includes links to other file format information databses such as PRONOM, LOC and NARA, magic sequences to identify files of a particular format, and links to source code as parsers of file formats.

Where most people would say "It's a JPEG file", the data within Wikidata breaks that down into the detail of different versions of JFIF, SPIFF, EXIF, etc that are all have different internal formats, even though the file extensions and media types are common.

[1] https://www.wikidata.org/wiki/Wikidata:WikiProject_Informati...

[2] https://www.wikidata.org/wiki/Wikidata:WikiProject_Informati...
when did google become sooo sloooow implementing trivial features, and then not even shipping a complete set of markdown?!
Same post from 35 days ago https://news.ycombinator.com/item?id=40652993
I don't understand the first table.

"Factors that contribute to Lower Intent to Stay at Job:
Average Employees: -8% Intent to stay"

https://emt.gartnerweb.com/ngw/globalassets/en/articles/imag...

Wat? That factor "Intent to stay" contributes to the intent to stay by -8%?
> Chrome, which meant Mozilla managed to scare people away from their own browser into a using a browser which puts less PR focus on claiming to respect user privacy. Great job there Mozilla!

FTFY. Both browsers have been pretty bad for privacy for a long time and are more than happy to exfiltrate your data to the respective operators without your consent.
translation: 'Layoffs performed via RTO suffer from adverse selection'
I would not argue that golang is the obvious choice for concurrency. Java's approach is actually superior to golang's. It takes it a step further by offering structured concurrency[1].

Kotlin's design had no bearing on Java's or the JVM's implementation.

C# has an interruption model through CancellationToken as far as I'm aware.

[1] https://openjdk.org/jeps/453
Many people are saying that ChatGPT or Copilot could write great scripts which is indeed true, but the eBook was written way before those LLMs were a thing. It is still good to learn the basics though.
You're referring to thread pinning, and this is being addressed.
No, it optimises hardware utilisation by simply allowing more tasks to concurrently make progress. This allows throughput to reach the maximum the hardware allows. See https://youtu.be/07V08SB1l8c.
It wasn’t always popular. In fact it took tremendous effort of public deception, corruption and lobbying to make margarine a staple today. But I’m sure Gates has pockets deep enough to repeat that.
They don't have a "hard" persistence layer, it's all in-memory, which is the only reason they can have any sort of performance.

In terms of the actual queries, you'll find a bunch of prefetch calls and dumping of all data related to your user. So much for "fetch what you need".

What you will also find is, surprise surprise, not actually a whole lot of graphql queries. Instead, a bunch of plain REST-ish queries, custom WS, and some graphql.
This is how we did Shakespeare in school; left side original text and the right side, an explanation. It made it much more bearable than trying to decipher what's being said.

Great project! I just wish it were in epub format to read on a smaller screen.
Consider the GMO panic. People will be against the concept for a long time, no matter how reasonable that position is.
Comparing GraphQL to REST and not a RESTful Graph-based data access API like JSON:API is just being disingenuous.

For GraphQL, you know it will be a nightmare. For REST, you don't, because you don't know what the actual API is. It could be a stopwatch API, obviously a stopwatch REST API is not comparable to GraphQL.
I don't know if it was Android-native or MiUI, but my old phone could share wi-fi credentials by showing it as a QR code. I consider that implementation to be even better since it can be triggered manually
Feel free to be stuck in this limited sort of perception. I do not see any practical arguments, only vague analogies without concrete points.
GraphQL doesn't solve engineering problems it solves human problems. It's a mechanism to patch bad employee communication
> how is it then, that things are becoming more spread out over time?

This may help: https://www.researchgate.net/figure/Classical-evolution-in-p...

If we knew the present we could predict the future - at least in classical physics. We have a very approximative knowledge of the present though, based on a macroscopic description. We can still predict a range of outcomes and see what it means in macroscopic terms. The initial set of states consistent with what we know “spreads out” as time goes by. We “lose” information by keeping only a “coarse” macroscopic description.
No. I mean data-no=jose
No, the potential for this is large. For, schools and universities just $10-$100 per student per semester is enough, and cheap in comparison to teachers when they can reduce teaching and lecturing hours.

If it works. Nothing similar in "ed-tech" has actually offered value thus far.
I'm not sure exactly what GP is referring to, but it might be things like this?

> Facebook report they maintain an allow-list of queries extracted from from their source code at build time, to fix this. I've not seen any other GraphQL site do this

https://x.com/AdamChainz/status/1392162996844212232

Which references this article: https://intercoolerjs.org/2016/02/17/api-churn-vs-security.h...
It seems that the answer to the question was "memory". Stack allocations, presumably. You have answered by telling us that virtual threads are better than real threads because real threads suck, but you didn't say why they suck or why virtual threads don't suck in the same way.
I’ve started evaluating whether code I want to release even needs to be packaged. In cases where it doesn’t, I just wrote them up as blog posts for people to find. I don’t even bother with significant walkthroughs, I trust people can reason their way through it.

I used to do gists, but over time I’ve noticed those don’t get indexed nearly as well in Google & co. Plus there’s something nice about the old school blog feeling.

All this to say there’s sometimes middle grounds on how to release code that you want out there.
glad to be of help! you may also be interested in the fact that people also use other rhetorical forms when writing on the internet.
Well now that Gartner has said it, perhaps CEOs will actually hear it.

Good grief this has been a strange 4 years.
If you believe LLMs are going to end up built into everything and doing everything, from moderating social media to writing novels and history books, making such a model will be the most political thing that has ever happened.

If your country believes guns=bad nipples=good war=hell but you get your novels and history books written by an LLM trained by people who believe guns=good nipples=bad war=heroic it would be naive to expect the output to reflect your values and not theirs.

Even close allies of the US would be nervous to have such power in the hands of American multinational corporations alone - so the French state could be very eager for Mistral to produce a competitive product.
I'm not exactly sure what "GNU MUMPS" is. Harlan Stenn is the author of PFCS MUMPS, which is a closed source package. Maybe it was open source under that name at one point, but if that's true, I think that must have been a long time ago.

If you are looking at an open source MUMPS, the most popular are GT.M [0] and its fork YottaDB. [1] GT.M is heavily used in production by FIS Profile banking software. (FIS was originally Fidelity's banking software division, but was spun out.) Several of GT.M's core developers left FIS and started their own company to develop the YottaDB fork. Both GT.M and YottaDB are AGPL, although earlier versions of GT.M were GPLv3, and before that GPLv2.

Another open source option is Kevin O'Kane's MUMPS implementation [2] (mostly GPLv2 or LGPL). O'Kane's MUMPS is less polished, more of a research/hobby project than production-grade code. But may be a more approachable code base if you are looking to tinker with it as opposed to using it to run a bank or a hospital. The Vista EHR (developed by US Veteran Affairs) [4] can be run on GT.M, although in production I believe VA mainly uses the proprietary InterSystems Caché. [5] As software developed by the US government, the core of Vista is public domain, although there are also a number of externally modified versions distributed under various open source licenses.

[0] https://en.wikipedia.org/wiki/GT.M

[1] https://github.com/YottaDB/YDB

[2] https://www.cs.uni.edu/~okane/

[3] https://www.hardhats.org/projects/New/InstallVistAOnGTM.html

[4] https://en.wikipedia.org/wiki/VistA

[5] https://en.wikipedia.org/wiki/InterSystems_Cach%C3%A9
Are you one of those people who believes Elon Musk built everything by hand in a cave with scraps or something?

Musk invested in technologies other people were working on and companies other people started, and hired other people who made it all work (often, given anecdotal reports, in spite of him.) Let's please stop pretending none of that would have been possible without some singular genius on his part.
The article does indeed argue that we need smarter ways to create diagrams - so that devs don't have to manually create / update them and other teams get the info that they need.

Saving time and effort for devs, while making dynamic visualizations with different levels of detail (i.e. more and less technical for different audiences) is possible.
I really like these little guys. I didn't realise they were controlled via steam decks though, that's fun
Ignore the bad title. The first column is a factor, like being a manager, a millennial, or a woman. The final column is intent to stay reduction given a RTO mandate.

So for all groups, intent to stay is lowered with a RTO mandate. Some groups are more affected than others, or claim to be.
> What would ``` add that you can't already do with two indents?

It would let me add those fences before and after the code I’m pasting instead of having to go and add spaces in front of every pasted line. On mobile adding the spaces after pasting is a bit fiddly. Then again, maybe it is a feature because it discourages pasting too many lines of code in many cases.
"they run virtual threads as needed" - so when one virtual thread is no longer needed and another one is needed, they switch context, yes?
After 25y of dev xp, my only focus now is on simplicity (as in, making code obvious). However this is by far the most difficult thing to accomplish.
Under Surveillance
Why can't virtual threads overcommit CPU use? If I have 4 CPUs and 4000 virtual threads running CPU-bound code, is that not overcommit? A system without overcommit would refuse to create the 5th thread.