MurphyA/hacker-news huggingface dataset:
by baobabKoodaa | 2025-11-25 18:27:31+00:00
Okay, fair enough. It just looked like a sockpuppet account, but okay, I believe you you're real. Sorry.

FWIW your claim here is false: "Everything you have commented on this post has been negative". I don't think this comment of mine was negative: "the landing page is one of the most beautifully designed things I have seen in a long time". Also note that when someone criticized the level of fees, I responded to that comment by saying that the fees were "standard" (as opposed to high). So just to set the record straight, not "everything" I commented here was negative.
by endymion-light | 2025-11-25 18:27:38+00:00
I mean, gambling for underage children is already illegal due to a myriad of reasons. I'd argue the psychological design of gacha games should be limited. Building patterns that get adults addicted, and advertising them specifically to children is the problem.

In the same way if a casino advertised child roulette wheels, I'd want legislation to step in.
by skwee357 | 2025-11-25 18:29:17+00:00
I'm sorry, but seeing the words "dev" and "struggling with webhooks" in the same sentence makes me cringe.

I mean, I have nothing against higher level abstractions, but I'd be worried to ship (as a dev) and use (as a customer) a product that was built by someone who does not have deep understanding of what they are doing.
by dperfect | 2025-11-25 18:29:20+00:00
It looks like this does make some things easier, but I'm not sure if it's actually better.

From what I can tell, any time you use this to check something like the customer's subscription state (or anything else payment-related) - either from the front end or the back end - it's going to perform an API request to Flowglad's servers. If you care about responsiveness, I'm not sure that's a good idea. Of course, you can cache that state if you need to access it frequently, but then it kind of defeats the purpose of this layer.

Stripe integration can be tricky, but if you don't want to store anything locally, you might as well just hit Stripe's APIs without the middleman. For the payment systems I've worked on, having cached state in the database is actually really nice, even if it's a bit more work. Want to do a complicated query on your customers based on payment/subscription state and a bunch of other criteria? It's just a DB query. With this, I think you'll be hoping they expose an API to query what you need and how you need it. Otherwise, you'll be stuck waiting for a thousand API requests to fetch the state of each of your customers.
by Spivak | 2025-11-25 18:29:29+00:00
This is exactly the kind of tortured logic I was talking about. By going this route you're actually agreeing with me and then doing whatever mental gymnastics necessary to twist everything that only harms the individual into some communal harm. Your argument applies equally to riding a motorcycle.

Obviously eating cheeseburgers should be illegal because you'll put a strain on the medical system when you get hypertension and heart disease.
by mbreese | 2025-11-25 18:29:29+00:00
I think we agree more than we don’t and the rest are personal preferences and policy differences. But we largely agree in principle.

I like the idea of having a person whose job is approving releases. Kind of like a QC tag — this release was approved by XX. I saw the issue as PostHog having a credential available to the CI/CD that had the authority to push releases automatically. When a new GitHub action was added, that credential was abused to push a bad update to npm. I might be wrong, I don’t deal with npm that much.

There are many ways to fix this.
by lenerdenator | 2025-11-25 18:29:56+00:00
They're people, but they're not politicians or regulators with the ability to do anything about it.

At a certain point, you need to have a statute that says "thou shalt not offer cybersex and online gambling to children", and you need someone with the statutory authority to charge Roblox with doing so and penalize them after due process. Either we don't have that statute, or the people with the statutory authority don't enforce things like they should.
by xscott | 2025-11-25 18:30:20+00:00
I see your point, and it's a nice example, but not completely parallel to the Rust/StandardML thing. Here, your RHS is an initializer, not a value.

// I don't think this flies in C or C++, // even with "designated initializers": f({ .flag = true, .value = 123, .stuff=0.456}); // Both of these "probably" do work: f((some_struct){ .flag = true, ... }); f(some_struct{ .flag = true, ... }); // So this should work too: auto a = (some_struct){ .flag = true, ... };

Take all that with a grain of salt. I didn't try to compile any of it for this reply.

Anyways, I only touched SML briefly 30 some years ago, and my reaction to this level of type inference sophistication in Rust went through phases of initial astonishment, quickly embracing it, and eventually being annoyed at it. Just like data flows from expressions calculating values, I like it when the type inference flows in similarly obvious ways.
by endymion-light | 2025-11-25 18:30:20+00:00
I mean, if someone was on a street corner selling child friendly cigarettes, I wouldn't call that a parenting issue.

I think parenting is one aspect, but surely you see how given it's a platform that advertises itself specifically for children, in the same way as if there was a children channel on the TV telling your kids to smoke crack, maybe someone should step in
by ASalazarMX | 2025-11-25 18:30:55+00:00
"Not great" doesn't necessarily mean "bad", it can be interpreted as "good", or even "very good". An honest title would have explicitly qualified how suitable the author found it was.

That the author avoided saying Python was a bad language outright speaks a great deal of its suitability. Well, that, and the majority data science in practice.
by ericmcer | 2025-11-25 18:31:09+00:00
I mean if we view it as a prediction algorithm and prompt it with "come up with a cool line to justify suicide" then that is a home run.

This does kinda suck because the same guardrails that prevent any kind of disturbing content can be used to control information. "If we feed your prompt directly to a generalized model kids will kill themselves! Let us carefully fine tune the model with our custom parameters and filter the input and output for you."
by whizzter | 2025-11-25 18:31:12+00:00
You intend to restrict this to a single market? There's some sibling comments that do point out that.

Much "annoyances" when it comes to money is all those weird laws and rules from lower level companies in place, improving things for developers is a laudable goal but I do hope that you guys have some real world experience with these systems apart from frustrations as system users because doing a good DX right now feels like it could make you end up in a dead end.
by RobinL | 2025-11-25 18:31:32+00:00
I think a lot of this comes down to the question: Why aren't tables first class citizens in programming languages?

If you step back, it's kind of weird that there's no mainstream programming language that has tables as first class citizens. Instead, we're stuck learning multiple APIs (polars, pandas) which are effectively programming languages for tables.

R is perhaps the closest, because it has data.frame as a 'first class citizen', but most people don't seem to use it, and use e.g. tibbles from dplyr instead.

The root cause seems to be that we still haven't figured out the best language to use to manipulate tabular data yet (i.e. the way of expressing this). It feels like there's been some convergence on some common ideas. Polars is kindof similar to dplyr. But no standard, except perhaps SQL.

FWIW, I agree that Python is not great, but I think it's also true R is not great. I don't agree with the specific comparisons in the piece.
by agreeahmed | 2025-11-25 18:31:40+00:00
I'd bet the typical payments integration has more complex requirements now than those from 10 years ago. That's what usually happens as a space becomes more important and, therefore, more regulated. Usually new entrants will come in and try to provide a tidier interface for solving an increasingly complex problem. In payments, as others in the comments have pointed out, that process is hampered by the gatekeepers involved.

You'd have to commit to building an amazing developer experience and navigating bank partnerships and compliance (per country), risk, antifraud, etc.

That's why the payments devex feels so behind the DB, hosting, or auth devex today.
by MengerSponge | 2025-11-25 18:31:51+00:00
Oh hush, you're not going to nerd snipe me into doing the thermal flux calculations today.

Optical photons don't carry an impossible amount of energy: I've seen liquid helium through a small coated window. The window was there for ion beam purposes, not "entertaining the grad student", and it was a big element in the heat budget!
by Bender | 2025-11-25 18:31:57+00:00
I've thought about making a forum where people can comment on threads from Reddit, HN, 4chan, etc... but I would have to reverse the moderation meaning a post is not visible until it has been reviewed and editing it would put it back into review state and nobody would like that.

The reason would be to have long running discussions which is the opposite of HN. Events evolve and so do discussions and details around them. Short lived threads also make it easier to memory-hole a topic.
by kiitos | 2025-11-25 18:32:00+00:00
> I have been writing production applications in Go for a few years now.

sorry, what?

https://gaultier.github.io/blog/a_million_ways_to_data_race_...

this code is obviously wrong, fractally wrong

why would you create a new PricingService for every request? what makes you think a mutex in each of those (obviously unique) PricingService values would somehow protect the (inexplicably shared) PricingInfo value??

> the fix

https://gaultier.github.io/blog/a_million_ways_to_data_race_...

what? this is in no way a fix to the problem.

it's impossible to believe the author's claims about their experience in the language, this is just absolute beginner stuff..
by nickpsecurity | 2025-11-25 18:32:07+00:00
"Human DNA contains 1.5 GB information."

Human DNA is tightly integrated with its environment. Instead of stand-alone, think compressed, source code of a high-level language running in an interpreter and with a standard library with 10-100x more functionality.

There's also how networks have combinational effects, some things in the body use temporal encodings, and who knows what else. We can't really estimate the information content of all of this put together since we don't even understand it. It is amazing, though.
by somenameforme | 2025-11-25 18:32:11+00:00
His comment said that "in Europe we already live in a completely safe society in historical and geographic terms." And in the past Europe dealt with never-ending wars which culminated in a war that left tens of millions dead. And even after that war, there was the never-ending threat of nuclear annihilation that was 100% justified as both sides lined up their nukes at one another and very nearly fired them. Nothing in your list is anywhere near the same scale. The only thing that would suffice is a fear that Russia invades a NATO country and effectively triggers WW3.
by serjester | 2025-11-25 18:32:17+00:00
Seems like their critique boils down to two areas - pandas limitations and fewer built ins to lean on.

Personally I've found polars has solved most of the "ugly" problems that I had with pandas. It's way faster, has an ergonomic API, seamless pandas interop and amazing support for custom extensions. We have to keep in mind Pandas is almost 20 years old now.

I will agree that Shiny is an amazing package, but I would argue it's less important now that LLMs will write most of your code.
by marcosdumay | 2025-11-25 18:33:21+00:00
You seem to not be operating in good faith, but that one is interesting:

> Then perhaps a larger amount of TNT

You can replicate something on the size of the WWII bombs with TNT, but you can't get anything much larger. A TNT explosion is relatively slow, and if you blow too much of it, it will disperse before blowing.
by devmor | 2025-11-25 18:33:32+00:00
This new study that did not find a causal link was part of the attempt to find out how. The original study was more of an observation than a deep dive.

You could think of it similar to a study that shows something like "People who don't watch network TV have fewer strokes", which could be an interesting correlation, but the causal effect might be something more like "people who are more health conscious tend to avoid sitting down for extended waking periods" which ultimately has nothing to do with TV.
by oldandboring | 2025-11-25 18:33:34+00:00
Almost nobody who works in software development is a licensed professional engineer. Many are even self-taught, and that includes both ICs and managers. I'm not saying this is direct causation but I do think it odd that we are so utterly dependent on software for so many critical things and yet we basically YOLO its development compared to what we expect of the people who design our bridges, our chemicals, our airplanes, etc.
by mbreese | 2025-11-25 18:33:35+00:00
This is a fair point. I think that the instability of early releases of BTRFS and the (lack of) commitment of especially RedHat made me not spend too much time working with it. The lack of a RAID solution made it not feasible for my purposes for a long time, and I was already quite familiar with ZFS through working with Solaris and FreeBSD. Trust in filesystems is hard won and easily lost[0].

I also think the popularity of FreeNAS especially contributed to the popularity of ZFS.

[0] I still look at XFS skeptically after a crash I suffered nearly 20 years ago. It’s not a rational fear, but it’s still there.
by fragmede | 2025-11-25 18:34:05+00:00
The untold story is of landing software projects at Google. Google has landed countless software projects internally in order for Google.com to continue working, and the story of those will never reach the light of day, except in back room conversations never to be shared publicly. How did they go from internal platform product version one to version two? it's an amazing feat of engineering that can't be shown to the public, which is a loss for humanity, honestly, but capitalism isn't going to have it any other way.
by steveklabnik | 2025-11-25 18:34:20+00:00
It's similar but different: both are type variables, but it's true that it's used for the "other" type variables in Rust.

For what it's worth, I am not even sure that Graydon was the one who introduced lifetime syntax. He was a fan of terseness, though: Rust's keywords used to be all five characters or shorter.

Niko and pcwalton were the ones working on regions, Niko talks a little bit about the motivation for syntax here: https://smallcultfollowing.com/babysteps/blog/2012/03/28/avo...

Later posts include /& as syntax: https://smallcultfollowing.com/babysteps/blog/2012/04/25/ref...

Eventually, another syntax: https://smallcultfollowing.com/babysteps/blog/2012/07/10/bor... which turns into a &x/ syntax: https://smallcultfollowing.com/babysteps/blog/2012/07/17/bor...

Which turns into this one, talking about variants of possible syntax: https://smallcultfollowing.com/babysteps/blog/2012/12/30/lif...

At some point, we get the current syntax: https://smallcultfollowing.com/babysteps/blog/2013/04/04/nes...

So, it happened somewhere in here...
by ayaros | 2025-11-25 18:34:22+00:00
I can't argue with this.

Then again, writing stylesheets is still one of those things where, if you're not careful, everything spirals out of control. Often I'll make changes and wonder why nothing's happening and realize something was overridden by another rule somewhere, or I was mixing up two properties, or some other silly thing...

I also find it's a bit awkward to write var(--foo) every time... I wish I could just write --foo... I suppose there's a grammar issue somewhere, or maybe it would have increased the complexity of implementations of CSS.
by agreeahmed | 2025-11-25 18:34:40+00:00
Stripe Billing handles subscriptions and usage based billing now. Most software products fall in one of those two categories, or sometimes both. As a result, most software companies are paying more than 2.9% + $0.30 for Stripe, closer to 3.6% + $.30.

To only pay Stripe 2.9% + $.30 they'd need to only use Stripe just for charges, and either build their own billing engine (usually poor use of time) or use a 3rd party SaaS.
by transpute | 2025-11-25 18:34:47+00:00
Nvidia evaluated Rust and then chose SPARK/Ada for root of trust for GPU market segmentation licensing, which protects 50% profit margin and $4T market cap.

"Nvidia Security Team: “What if we just stopped using C?”, 170 comments (2022), https://news.ycombinator.com/item?id=42998383
by fhd2 | 2025-11-25 18:34:49+00:00
Fascinating, from skimming that, it does indeed appear that it would be within the GNU philosophy to distribute source code solely in exchange for payment. Doesn't cover a case where the source code is _already_ distributed though, then it's free to run.

And even if the source code was only distributed to paying customers, that'd likely be a temporary situation. A relevant quote:

"With free software, users don't have to pay the distribution fee in order to use the software. They can copy the program from a friend who has a copy, or with the help of a friend who has network access."

I do read the GPLv3 such that if someone _does_ buy the code in any fashion, you must provide the source code to them for free. Relevant excerpt from section 6:

"[...] give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge."

But yeah, no obligation to provide the source code for free to non-customers, fair point. Just no ability to stop customers from sharing it with non-customers. Does make sense.
by josefx | 2025-11-25 18:34:55+00:00
I think it is more a matter of convenience. There are countless string implementations for C, some tiny projects, others part of larger frameworks like Glib. At the end of the day a C developer has to decide if they are going to pull in half of gnome to handle a few lines of IO or if they are just going to use the functions the C standard conveniently ships with. Most people are going to do the later.
by garciasn | 2025-11-25 18:35:03+00:00
SAS > R > Python.

The focus of SAS and R were primarily limited to data science-related fields; however, Python is a far more generic programming language, thus the number of folks exposed to it is wider and thus the hiring pool of those who come in exposed to Python is FAR LARGER than SAS/R ever were, even when SAS was actively taught/utilized in undergraduate/graduate programs.

As a hiring leader in the Data Science and Engineering space, I have extensive experience with all of these + SQL, among others. Hiring has become much easier to go cross-field/post-secondary experience and find capable folks who can hit the ground running.
by watwut | 2025-11-25 18:35:13+00:00
These arguments are nuts. The kids I know play roblox games ... honestly because they like the games. That is really really it. I am very confident they are not earning rare robux on it, because I know what they play.

> So the games are completely pointless and are nothing like playing Counterstrike or Doom or starcraft at a LAN party.

Frankly, Doom was pointless for christ sake, as pointless as it gets. And yes, obviously a game appealing to 8-12 years old is pointless to a teenager or adult. No, kids wont play the grandpa games. And yes, they do not want to play only games adults deemed educational or training whatever you think counter strike trains enough. They play them literally because they find those games fun.
by fpoling | 2025-11-25 18:35:44+00:00
Surely one can abstract priority queue with mutexes into own data structure. However it will contain enough application-specific logic so a chance of reuse will be slim. So by directly working with mutexes one will have simpler code overall that can still be more easy to adapt to changing requirements.

In general the problem with channels is that they are not flexible enough while being rather abstract. A better abstraction is message passing with one message queue per thread like in Erlang. IMO it can cover more cases before one needs mutexes. But even with that proper back pressure and rate limiting is hard.
by kevstev | 2025-11-25 18:36:19+00:00
No floppy or CD? You were just asking for trouble then IMHO. It was common to have to reinstall windows every 6-9 months in the win9x days. That didn't even really work for ME, but by then win2000 came in to save the day. Software was primarily distributed on CD those days, being without a CD drive must have been a huge hardship.
by shadowgovt | 2025-11-25 18:36:27+00:00
The original video existed because Xtranormal.com lets you transform a written script into an auto-generated scene with procedurally-puppeted wireframed stock models and text-to-speech voice acting.

Any assertion that the world in which Broccoli Man was created was fundamentally different (in terms of "relying on someone else's framework to do a low-effort meme") from today is nostaglia. In fact, I suspect mbleigh spent more time on making the recreation work than was spent on the original Broccoli Man video.
by foobarian | 2025-11-25 18:36:49+00:00
> I prevent her from talking to others,

Honestly the voice comms have been a nice upgrade and I find I mind it a lot less than text. It's a lot easier to confirm the person on the other side is not some middle aged creep. It's also a lot more ergonomic for talking with friends (though they already tend to use facetime calls in the background)
by Weves | 2025-11-25 18:36:53+00:00
Hmm, will have to disagree here. I think "one chat to rule them all" is the way it will end.

It does requires having UI components for many different types of interactions (e.g. many ways to collect user input mid-session + display different tools responses like graphs and interactives). With this, people should be able to easily build complex tools/flows on top of that UI, and get a nice, single interface (no siloed tools/swapping) for free. And having this UI be open-source make this easier.
by razighter777 | 2025-11-25 18:37:07+00:00
> I'd rather see over-the-top evangelism than the lack of it, because the latter implies that things aren't going to change very fast.

No new technology should be an excuse to engage in unprofessional conduct.

When you propose changes to software, you listen to feedback, provide analysis of the benefits and detriments, and make an informed decision.

Rust isn't special, and isn't a pass to cause endless heartache for end users and developers because your code is in a "safer" language.

New rust code should be held to the same standards as new C and C++ code that causes breakage.

Evangelism isn't useful here, let the tool speak for itself.