MurphyA/hacker-news huggingface dataset:
by arjie | 2025-11-10 08:00:33+00:00
Going off my memory here:

* The labs that did traditional PGT-M available to us wanted embryo biopsy, parent samples, grandparent sample. The PGT-WGS guys wanted embryo biopsy, parent sample. For reasons specific to us, grandparent samples were not easy - and I found the reason for not requiring it convincing.

* I preferred moving from the biology space to the data space because:

* * At the time, only some 25 years had passed between the association of the variant with hearing loss and our attempt. There was a reasonable possibility our last child would be 5 years out from there, depending on implantation success, needing to go to surrogates, etc. That's a fifth of the way again from original discovery. It's entirely possible that new associations are found in that period.

* * I am a bad biologist, but I have a degree in Mathematics and I would say I'm a competent programmer. I should be able to stitch together a minimal bioinformatics pipeline, if required, with the assistance of my cousins (two of whom have Ph.D.s in Molecular Biology).

* I trusted the WGS process more because of greater effective transparency. At the end of the process, I requested and obtained the FASTQs for our embryos. This is far superior to receiving a Detected / Not Detected result.
by augment_me | 2025-11-10 08:01:46+00:00
I agree but then the reality is that we are here now, so it's no longer ridiculous. So if you are that brilliant, you understand that there is no point of fighting the current, so to make your life easier and to get the job where you can feel fulfillment, you might have to adjust your CV to fit the reality. That is a part of the intelligence you need to adapt and has always been.
by littlecranky67 | 2025-11-10 08:01:53+00:00
Website is overly dramatic. Google doesn't hate XSLT, it is simply no one wants to maintain libxslt and it is full of security issues. Given how rarely it is used, it is just not worth the time + money. If the author wants to raise money to pay a developer willing to maintain libxslt, Google might revise the decision.
by neobrain | 2025-11-10 08:01:56+00:00
SUID by itself is not a security liability. Typically, programs using SUID quickly drop their additional privileges during startup to avoid the scenario you're describing. So the vulnerability in firejail would have to be early during startup before any of that.

Still, it can happen of course, particularly with memory-unsafe languages. Conversely without root privileges you have to sacrifice strength of your sandbox, widening the vulnerability window in the app you were trying to constrain to begin with.

Meanwhile bubblewrap relies on user namespaces, which come with their own set of security problems. They are disabled by default in many distributions for that reason.
by arz1010 | 2025-11-10 08:02:24+00:00
Looking for: UX / UI / Interaction / Product Designer Roles

Location: Hyderabad, India

Remote: Yes

Willing to relocate: Yes (National & International Tech hubs)

Technologies: Figma, Adobe(Photoshop, Illustrator, After effects, Premiere Pro), Rive, Framer, HTML5, CSS3, JavaScript, ReactJS, Maze, Google Forms, Excel

Portfolio & Resume: https://arunuxid.framer.website/

Email: arun.uxid@gmail.com
by rorytbyrne | 2025-11-10 08:02:53+00:00
I made a HN-like discussion forum for (meta)science.

https://talk.amacrin.com/

Most (meta)science discussion is either fragmented on Twitter/Bsky, or a bit too formal. I thought a centralised place for deeper, casual discussions might be helpful, so I'm testing that theory.

Launched a few days ago, so it might have some rough edges. I'm considering making it user-invite-only soon, but for now it's fully open for signup. I'll also move it to its own domain once I think of a better name.
by MarceColl | 2025-11-10 08:03:25+00:00
https://katarineko.com

I think by this point everyone that is learning a language knows that immersion is very important, however a problem I've had myself is that the content that interests me is beyond my reach, and the content that is within reach doesn't interest me.

This is my attempt at doing something to remediate that. You select the content you want, and I create a personalized study plan to learn the most important words to achieve a target % of understanding. Then I generate a short story each week for your particular level containing the new words in the context of your content.

The idea is to bring the content you want to learn to your level so you can watch what you want to watch.
by jjcob | 2025-11-10 08:04:08+00:00
> Is everything 3% cheaper in the eu?

No, because in Europe sales tax is higher and included in the displayed price, so stuff is generally more expensive. But obviously everything is 3% cheaper than it would be if businesses still had to pay 3% fees. (credit card fees used to be really high before EU regulation came in -- the minimum fee was so high that merchants sometimes paid more in fees than they made in profit when a customer swiped a credit card instead of a debit card).

But the much bigger advantage is that reward cards aren't a thing, and credit card usage is much less common. Most people just use their debit cards. Credit card debt is much less of a problem because credit cards aren't advertised like they are in the US. People spend less if they don't always have $3000 of credit available.
by spacedcowboy | 2025-11-10 08:05:44+00:00
Atari 8-bit basic used something pretty similar to this [1], except it did have normalization. It only had 10 BCD digits (5 bytes) and 2 digits (1 byte) for exponent, so more of a DEC48 but still… That was a loooong time ago…

It was slightly more logical to use BCD on the 6502 because it had a BCD maths mode [2], so primitive machine opcodes (ADC, SBC) could understand BCD and preserve carry, zero etc flags

[1]: https://www.atarimax.com/freenet/freenet_material/5.8-BitCom...

[2]: http://www.6502.org/tutorials/decimal_mode.html
by zkmon | 2025-11-10 08:06:42+00:00
Cool project and very nicely done!! claps.

You know what, I used to plan my leaving from home based on the timings at the station, but soon I realized that it is not worth it. It is not because trains are not sticking to the time table. Just randomly starting at your own comfort eliminates the anxiety that comes with planning. Your average wait time might increase to half of the interval between the trains, but that would be an increase of only a few minutes for mornings, in return for never bothering to check time again.
by 0manrho | 2025-11-10 08:06:43+00:00
Agreed. Are TP-Link the bastion of advanced security/tech/features and futureproofing? No. But they do what they say they do on the box, and do it reliably which unfortunately is more than you can say for a lot of things these days, no matter the price/payment model.

If you just need a basic ass device for simple non-critical shit without a bunch of proprietary bullshit and dark patterns, it's hard to beat TPLink for the money.

The fact that they still get support/updates long passed the typical lifespan of competing devices several times their price point is just icing on the cake.
by pseudosavant | 2025-11-10 08:06:44+00:00
This site is a bit of a Rorschach test as it plays both sides of this argument: bad Google for killing XSLT, and the silliness of pushing for XSLT adoption in 2025.

"Tell your friends and family about XSLT. Keep XSLT alive! Add XSLT to your website and weblog today before it is too late!"
by impossiblefork | 2025-11-10 08:07:57+00:00
Yes, but in the end you still live in physical reality, and this determines our actual productivity.

Whether we can make a boat, or a tennis racket, or a toothbrush cheaply is in the end what determines how many people can have boats, tennis rackets and toothbrushes, not whether the service economy, or our scientific research is excellent. We can hope to be able to do neat stuff and trade that for products, but in the end, once trade is no longer mandatory when people do not need to obtain foreign currency to obtain oil, everything having become battery-electric, I suspect that everybody will be better off simply building what they want.
by rzk | 2025-11-10 08:10:30+00:00
There's a quote in that blog that I quite liked:

We’ve engineered movement out of our lives. We sit in chairs, stare at screens, and outsource physical effort to machines. Then we try to cram all our movement into 45-minute bursts a few times a week.

This is like eating only once a week and calling it a balanced diet. Most people are malnourished, not from lack of food, but from a lack of diverse, nutrient-dense movement.
by somenameforme | 2025-11-10 08:10:37+00:00
People of a profound initial bias will, in general, believe anything that supports that bias, and reject anything that challenges it, in both cases without any real consideration or thought whatsoever. So I don't think examples of individuals being "misled" by e.g. AI generated images or video, to extremes, is entirely realistic. Rather they were already at those extremes and will just eat up anything that appeals to those extremes.

To take a less politically charged example, imagine there is fake content 'proving' that the Moon landing is faked. Is that going to meaningfully sway people who don't have a major opinion one way or the other? Probably not, certainly not in meaningful numbers. And in general I think the truth does come out on most things. And when people find they have been misled, particularly if it was somebody they thought they could trust, it tends to result in a major rubber-banding in the opposite direction.
by khafra | 2025-11-10 08:10:38+00:00
Your free advice is well-taken and apropos in 2015 and before. The major point of the essay is that junior builders--e.g., people doing tasks that are standardized and understood well enough to automate--no longer get hired. Either we get a new way to identify the ability to complete open-ended work, or the tech sector suffers a succession failure (or everybody gets replaced by robots before the current generation of senior experts retires).
by oulipo2 | 2025-11-10 08:10:44+00:00
Thanks for your message!

So the value prop are multiple things:

- you can indeed change the cells! When the industry matures, we might have a "second-life cell cycling" path where old cells are re-tested and matched so you could switch individual cells, but for now, as those "matched cells" aren't widely available we recommend you switch everything to new cells (this would cost an end-user about $50 rather than buying a new battery for $200/$300)

- our battery is also very high quality (passes all certifications, waterproof, fireproof, connected, with safety alerts)

- even if you need to change all the cells sometimes, getting back "pristine cells" rather than "damaged, welded and unwelded cells" will allow for multiple things: putting them in a second-life cycle for eg. energy storage batteries, and even better recycling (since you can get cells out of the casing, the recycling process is even more efficient)

- now the cells are perhaps 1/3rd the cost of a battery, so all things being equal, you'd rather be able to change all cells than throw in the trash the old battery

- we also have seen some batteries fail because of broken electronics, etc, which are just $30 to replace, and our battery makes it extremely simple to do so
by djmips | 2025-11-10 08:11:52+00:00
Well noted, the article is a treasure! They do mention dragging a Donkey Kong with them to Ricoh and that they wanted to surpass everything before and make something that was as capable as their arcade hardware. The scrolling of the 2A03 design was a major advantage. It's very enlightening to see how they were inspired by the Colecovision but wanted to surpass it which they did in many ways.
by barrenko | 2025-11-10 08:12:38+00:00
With this in mind, I'd like to propose an alternative to OP. E.g. he may be extremely unlucky in the following 7 months in his job hunt, and tech is not what it used to be.

If the uses these 7 months to focus on his writing on the other hand... We'll need people with a soul and technical chops to cover this apocalypse (using it in the original sense of the word).
by inglor_cz | 2025-11-10 08:12:45+00:00
"without reliance on allies"

This is unrealistic for smaller countries, like Ancient Greek poleis or contemporary Estonia. Under your logic, they would have to give up their existence and join some empire.

In practice, already the Greco-Persian wars are an indication that alliances of smaller nations are viable, and that they are more efficient due to specialization. This is not a new problem, nor is it specific for post-industrial history; the Athens were better at fighting at sea, other poleis could provide hoplites.
by stevefan1999 | 2025-11-10 08:13:15+00:00
I'm working on a K8S hosting solution that just gives the user a simple Kubernetes cluster. I (or we) handle the compute, (networked) storage and ingress hosting for you, and the cluster provision time should be within minutes.

You just need to pay for a fixed monthly upfront cost rather than PAYG, giving small developers a good save of their money.

In other words, this is similar to self hosting with K0S/K3S/OpenShift, except you don't have to own servers to begin with, in other words, it is a little similar to serverless K8S.

Well, all you those you can actually do with a VPS today, heck why do I have to do it if EKS/GKE/LKE/OKE/DOKS exists? That's because it takes a lot of time to properly setup VPC/EBS/S3/EC2, you need to pay an insane amount of premium and overheads to those while an ordinary user just don't want to hassle too much.

I want to undercut the big clouds by saving people's money and time. I have had enough of seeing a ludicrous EKS billing. I just want K8S to be the control panel of everything.

Deploy, run and scale later, simple as that
by charcircuit | 2025-11-10 08:14:10+00:00
> XSLT will soon enter the Google graveyard.

The google graveyard is for products Google has made. It's not for features that were unshipped. XSLT will not enter the Google graveyard for that reason.

>We must conclude Google hates XML & RSS!

Google reader was shutdown due to usage declining and lack of willingness for Google to continue investing resources into the product. It's not that Google hate XML and RSS. It's that end users and developers don't use XSLT and RSS enough to warrant investing into it.

>by killing [RSS] Google can control the media

The vast majority of people in the world do not get their news by RSS. It's never would have taken over the media complex. There are other surfaces for news like X which Google is not able to control. Google is not the only surface where news can surface.

> Google are now trying to control LEGISLATION. With these technologies removed what is stopping Google?

It is quite a reach to say that Google removing XSLT will give them control over government legislation. They are completely unrelated.

>How much did Google pay for this support?

Google is not paying for support. These browsers have essentially a revenue sharing agreements with the traffic they provide Google with. The payments are for the traffic to Google.
by Semaphor | 2025-11-10 08:14:21+00:00
I recently looked into beets, but it seems it’s focused on automation, is that correct? I often buy stuff that has just been released, and that’s not yet in any database, so no automation works.

My current workflow is download, unzip and manually tag (mainly genres, sometimes badly named artists/albums) with MusicBee (which gives me autocomplete for genres so I can reuse existing ones), and then copy the files to the server for Navidrome to pick them up.

Throwing this out here to see if beets would actually work well with what I want after all.
by gitgud | 2025-11-10 08:15:40+00:00
> People only read your code when something is wrong, which means they’re already annoyed before they get to your bit and if your bit is also annoying you’re going to either hear about it or get frozen out because if it.

If you’re talking about angry issues in FOSS, then there’s another positive way to look at this.

Not only did at least 1 person run your code somehow, they also cared enough to find the source and report it to you. Which means your code has value!!

But generally people are pretty nice when reporting issues to small projects
by gucci-on-fleek | 2025-11-10 08:15:53+00:00
I'm strongly against the removal of XSLT support from browsers—I use both the JavaScript "XSLTProcessor" functions [0] and "<?xml-stylesheet …?>" [1] on my personal website, I commented on the original GitHub thread [2], and I use XSLT for non-web purposes [3].

But I think that this website is being hyperbolic: I believe that Google's stated security/maintenance justifications are genuine (but wildly misguided), and I certainly don't believe that Google is paying Mozilla/Apple to drop XSLT support. I'm all in favour of trying to preserve XSLT support, but a page like this is more likely to annoy the decision-makers than to convince them to not remove XSLT support.

[0]: https://www.maxchernoff.ca/tools/Stardew-Valley-Item-Finder/

[1]: https://www.maxchernoff.ca/atom.xml

[2]: https://github.com/whatwg/html/pull/11563#issuecomment-31909...

[3]: https://github.com/gucci-on-fleek/lua-widow-control/blob/852...
by madaxe_again | 2025-11-10 08:16:00+00:00
I just don’t know that it’s feasible.

As the article mentions, the U.K. shipbuilding industry was dependent on cheap, skilled labour.

It doesn’t touch upon just how cheap.

My ancestors were riveters and boiler fitters in Glasgow from about the 1860s to the 1920s - they lived 30 to a room in tenements, three generations atop on another, and had to start work aged 5 or 6 to prevent the family from falling into destitution. The economics essentially demanded that you crank out descendants, as only by pooling a number of incomes could you survive. Everybody had horrific injuries of one variety or another. Most died before reaching 50.

The other thing that the article elides is just how much that workforce was shattered by the wars - an awful lot of Glaswegian and other shipbuilders signed up for the navy, as it was a much better opportunity than just making the boats - and proceeded to die at sea in droves. Their families did not receive compensation or their pay more often than not, as it was considered to be bad for morale to say a ship had been lost, and instead all aboard would be classed as missing or as deserters, and when they did finally say “yes, this ship was lost” 15 years after each war, it was usually far too late to be of any use.

Anyway. I just can’t see the working classes or international human rights organisations being willing to do the same again.
by imiric | 2025-11-10 08:16:29+00:00
> The point is that humans produce noise, too, sometimes even more than LLMs do.

Humans can produce noise, but humans using LLMs can produce orders of magnitude more of it.

But your stance is reasonable. If it improves the product, who cares who/what produced it. I personally find reviewing machine-generated code and the process of code review with a machine much more exhausting than interactions with humans, but you may feel otherwise.
by kortilla | 2025-11-10 08:16:31+00:00
> The US government directly buying stakes in Intel is A-OK, but any involvement from the CCP in any form in any company is Not Good ?

Yes, it’s the US government. Of course it thinks advancing US gov controlled technology is good and CCP influence in the US is bad. That’s a completely rational stance and it’s not even hypocritical until the CCP bans some US product and the US gov complains.
by noduerme | 2025-11-10 08:17:20+00:00
I suspect that very few of those 800 million chess players get paid to play chess all day every day as a job. More likely, it's an occasional hobby in their free time, which is great. Even at that, they only represent 10% of the 8 billion people on earth, which suggests that it's a small minority of people who actually care about solving puzzles. And of those, an even smaller number actually apply those skills to do it for a living.

What I'm trying to say is that if I were no longer paid to write code I might just end up with hobbies that occasionally stimulated my mind as opposed to having to constantly engage that muscle. Motivation makes a big difference, because even for those of us who compulsively solve puzzles there is plenty of time for ennui.
by alephnerd | 2025-11-10 08:17:37+00:00
My reply was primarily about American new grads - who overwhelmingly don't do grad school.

And your anecdote is exactly what I am trying to explain on HN.

We as employers are fine paying high salaries to mid-career talent, but it's hard to justify hiring a middle of the pack new grad from CSU East Bay for a $130k base salary new grad role when I can hire a mid-career US returned FAANG dev in BLR or HYD for $70k-90k TC.

We will still hire new grads in the US for a $130k-$180k base, but they will have to actually be worth it. The brutal reality is, if you didn't attend a target CS program for your Bachelors (Stanford, Cal, MIT, UIUC, CMU, UT Austin, GT, UMich, UW, Cornell, Harvard, Columbia), at this point you probably aren't landing a high paying CS job - just like how in India if you didn't get a good JEE score, you're essentially relegated to being stuck at WITCH because you didn't get into a good BTech program, and it's an employer's market

A lot of people on HN assume Indians (and other foreign nationals) only do b*tch work like legacy springboot crap (and ofc plenty of people do), but an equally large cohort is doing legitimately competitive and innovative work.
by cyphar | 2025-11-10 08:18:25+00:00
> I have an issue with low quality slop whether it comes from a machine or from a human.

It's very hard for a human to mask a low-quality PR as thought it were reasonable quality. It is incredibly easy for an LLM to do it (in fact that is precisely what they are trained to do).

In addition, when I see a low-quality PR, I try to mentor the submitter. That doesn't make sense to do for LLMs (the submitter might not even bother reading my comments).

> and have guidance like AGENTS.md files that tell coding robots how to be successful in the repo.

If none of the maintainers use such tools, why is it our responsibility to maintain documentation to appease them (in the hopes of reducing spam)? A policy limiting their use is much simpler to write and requires less maintenance.