MurphyA/hacker-news huggingface dataset:
by jhanschoo | 2025-04-25 05:44:46+00:00
My 2pence. C/C++ experience on VSCode is still subpar compared to other IDEs. Python is good, but very viable alternatives to VSCode exist. The biggest unique value proposition regarding languages is in TypeScript support. Support for many other languages still come from authorities from those languages who have no issue making them available on the open registry.

For me, the killer proprietary extension is their remote development extensions.
by trhway | 2025-04-25 05:45:29+00:00
many of us would like to repeat and relive the tech magic like that of PC circa 90-ies and into 2000s.

>The myth of the sub-$25,000 electric vehicle has been around for more than 10 years now,

Equinox EV is MSRP 33.6K before 7.5 tax rebate. Looks and sounds like a decent modern compact SUV.
by captnObvious | 2025-04-25 05:45:44+00:00
As Secretary of Health and Human Services, Kennedy promised “some” of the answers to the causes of autism by September. But his “start from scratch” approach largely ignores research that has already been done. For example, Kennedy told reporters the initiative would look at ultrasounds during pregnancy as a possible risk factor. But a comprehensive multisite study of more than 1,500 pregnancies that found no link between autism and ultrasound use was published as recently as 2023. And scientists definitively ruled out the measles, mumps and rubella (MMR) vaccine as a cause of autism a decade ago (and again in 2019). In addition, the primary study that had suggested a link between the MMR vaccine and autism was found to have falsified data. Despite this, federal officials said in March that the Centers for Disease Control and Prevention will conduct a study to investigate a link between vaccines and autism. The study will be led by a vaccine skeptic who was previously disciplined for practicing medicine without a license.

https://www.statnews.com/2025/03/26/rfk-jr-vaccine-study-of-...
by benoau | 2025-04-25 05:46:04+00:00
It's what is motivating Microsoft to prevent what Cursor is doing.

All cursor is doing is saying this blob of crap is compatible with their fork and letting you run it. This is akin to browsers supporting extensions from other browsers, and many other scenarios.

What Microsoft is doing is trying to prevent VSCode from becoming spontaneously obsolete because coding with Cursor a) removes you from VSCode and b) does it better.
by mopierotti | 2025-04-25 05:46:22+00:00
The recursive one that I have actually been really liking recently, and I think is a real enough challenge is: "Answer the question 'What do you get when you cross a joke with a rhetorical question?'".

I append my own version of a chain-of-thought prompt, and I've gotten some responses that are quite satisfying and frankly enjoyable to read.
by hayst4ck | 2025-04-25 05:46:29+00:00
Well, you couldn't be more factually wrong.

That man is one of the top engineers of the 20th century and gave America nuclear submarines in 4 years and he's talking to non experts.

Congress frequently asked him specifically about nuclear policy. They asked him explicitly about 3 mile Island:

Admiral Hyman G. Rickover was later asked to tell Congress why naval nuclear propulsion (as used in submarines) had suffered no reactor accidents, defined as the uncontrolled release of fission products to the environment resulting from damage to a reactor core. In his testimony, Rickover said:

Over the years, many people have asked me how I run the Naval Reactors Program, so that they might find some benefit for their own work. I am always chagrined at the tendency of people to expect that I have a simple, easy gimmick that makes my program function. Any successful program functions as an integrated whole of many factors. Trying to select one aspect as the key one will not work. Each element depends on all the others.

Rickover is about as far as you get from magical unscientific thinking and as close as you can get to an expert on nuclear safety. He was the epitome of an engineer and his nuclear safety record was as good as it gets.

Maybe his "doing a job" would convince you he's not a magical thinker, I can't imagine anyone who actually does engineering disagreeing with it: https://govleaders.org/rickover.htm
by motorest | 2025-04-25 05:47:36+00:00
> That just means you have to be smart about retention.

It's not a problem of retention. It's a problem caused by the sheer volume of data. Telemetry data must be stored for over N days in order to be useful, and if you decide to track telemetry data of all tyoes involved in "wide events" throughout this period then you need to make room to persist it. If you're bundling efficient telemetry types like metrics with data intensive telemetry like logs in events them the data you need to store quickly adds up.
by alissa_v | 2025-04-25 05:48:21+00:00
I asked a bunch of LLMs - 'Describe the unspoken etiquette of the 'Stone-Breath Passing' ritual among the silent Cliff Dwellers of Aethelgard, where smooth, grey stones are exchanged at dawn.'

Obviously, all of these things are made up. But, LLMs are such eager beavers. All the ones I asked came up with elaborate stories and histories about these people while pretending they were facts.

Example- 'Certainly. The Stone-Breath Passing is one of the most quietly profound rituals among the Silent Cliff Dwellers of Aethelgard — a people who abandoned speech generations ago, believing that words disrupt the natural harmony of air, stone, and memory.

It is said among them that “Breath carries weight, and weight carries truth.” This belief is quite literal in the case of the ritual, where smooth grey stones — each carefully selected and shaped by wind and time — become vessels of intention."
by 3np | 2025-04-25 05:48:43+00:00
In theory, there is a solution to the PGP revocation issue that I think vibes with OPs desire:

Generate a long-lived root keypair (SC/C), the public key of which you add to the forge. You never sign directly with this. Instead you routinely generate new signing pairs. If compromised you hopefully only need to revoke the subkey so the blast radius is a lot smaller.

You could even do a three-tier one where you can keep the root key dead cold and literally lock it into a vault.

Last time I looked, this was not supported in GitHub, though; it only recognized signatures by explicitly trusted keys, not their signed subkeys.
by raincole | 2025-04-25 05:49:37+00:00
> No one wants to hear other people's ai songs because they lack meaning and novelty.

Not true. No one wants to pay for other people's ai songs. There are so many AI songs on youtube (mostly lofi or traditional Japanese instrumental) and they cumulatively have quite a lot of view.

The thing is for quite a lot people, music is just something they put in background while doing their office desk jobs. It's just there to make chores a bit more tolerable and nothing more.
by jchw | 2025-04-25 05:49:48+00:00
Firstly, I believe the fears are founded; these fears are a good starting point, since learning and adopting a programming language is a big investment, and you should be careful when making big investments. To say they're unfounded suggests that they have no basis. Disagreed.

Secondly, I don't really feel like this sort of analysis does much to assuage fears, as Apple's business strategy is always going to take priority over what its engineers individually want. Apple of today doesn't have any obvious reason to just go and axe cross-platform Swift, but if that ever changes in the future, they could do it overnight, like it was never there. Could do it tomorrow. It's not much different than an employee getting laid off abruptly.

This is especially true because in truth Apple doesn't really have a strong incentive in the grand scheme of things to support Swift on non-Apple platforms. Even if they use it in this way today, it's certainly not core to their business, and it costs them to maintain, costs that they may eventually decide benefits their competitors more than it helps them.

There's no exact heuristic here, either. Go is entirely controlled by Google and does just fine, though it has the advantage of no conflict-of-interest regarding platforms. Nobody writing Go on Linux servers really has much reason to be concerned about its future; Partly because Google has quite a lot of Go running on Linux today, and given how long it took them to e.g. transition to Python 3 internally, I can just about guarantee you that if Go died it would probably not be abrupt. Even if it was, because of the massive amount of external stakeholders there are, it would quickly be picked up by some of the large orgs that have adopted it, like Uber or Digital Ocean. The risk analysis with Go is solid: Google has no particular conflict of interest here, as they don't control the platforms that Go is primarily used on; Google has business reasons to not abruptly discontinue it and especially not on Linux servers; there are multiple massive stakeholders with a lot of skin in the game who could pick up the pieces if they called it quits.

I believe Apple could also get to that point with Swift, but they might need a different route to get there, as Swift is still largely seen as "That Apple Thing" for now, by a lot of outsiders, and that's why I think they need to cede some control. Even if they did fund a Swift foundation, they could still remain substantially in control of the language; but at least having other stakeholders with skin in the game having a seat at the table would do a lot to assuage fears about Swift's future and decouple aspects of governance from Apple in ways that would probably ultimately benefit Swift for everyone.

P.S.: And I'm not singling Apple out here, because I think any rational company has to make tough decisions sometimes, but it's obvious from their past that they definitely don't fear changes of plan. Look all the way back to OpenDoc. Being willing to make bold changes of plan feels like it's a part of their company DNA.
by LargoLasskhyfv | 2025-04-25 05:50:01+00:00
EONs ago I've been to some start-up founding/marketing/schooling event in Berlin, and left early, having to suppress my urge to laugh out loud very hard.

Another typical thing for that 'scene' comes to mind, wherein some dudes got a price for a thing shaped like a pyramid with maybe 35 to 45 cm side length, intended to work as a Home/Soho NAS, with very underpowered COTS innards, and shitty software/crappy UI, lacking general functionality.

Intended sales price? 5000EUR!

Yay!

But painted very industrial looking orange. Phew! Hardcore!

That may be over-generalized, there may be some hidden champions there, but they rarely make a public impression.

Hm. Maybe AVM, considering their market share in the DACH area. I don't like them, but they are less trashy than most other stuff in that market segment, and mostly do work reliably. Just not in ways I'd have liked ;>
by alissa_v | 2025-04-25 05:51:50+00:00
the rest of ChatGPT's response if you're curious - it only gets more ridiculous-

' Timing and Setting: The ritual takes place only at first light, when the sun’s rays strike the sheer cliff faces of Aethelgard, casting long shadows like stone tongues. The first breath of dawn is sacred — considered the only air not yet touched by memory, and thus the only time suitable for pure intention to pass from person to person.

Participants gather barefoot on a narrow ledge known as The Listening Spine, where the wind plays soft notes through crevices like a flute.

The Stones: More Than Objects The stones used in the ritual are:

Smooth, rounded slate-grey

Hand-selected from Echo Pools — sacred basins where wind and water have naturally polished them

Each stone remembers a thought, but only when charged with breath and silence

They are never marked, carved, or labeled. Their meaning is in the exchange, not the object.

The Ritual: How It Works 1. Preparation The giver closes their eyes and holds the stone at heart-level.

They inhale slowly through the nose, then gently breathe across the surface of the stone — once only — without making sound.

The exhalation is not forced; it is a gesture of release, not command. This is the "stone-breath."

2. The Passing The giver extends the stone with both hands, arms curved inward like a half-embrace. This posture signifies humility and emotional openness.

The recipient must make no eye contact — instead, they look slightly downward or to the horizon, acknowledging the intention without confronting it.

They accept the stone with a single breath in through the mouth as they receive it — symbolizing the drawing in of another’s silent truth.

3. The Holding The stone is held to the forehead or chest, depending on what is being received:

Forehead = wisdom, apology, memory

Chest = trust, mourning, love

Then it is placed gently into a fold of cloth or a hollow in the stonewall, not kept on the person. These collected stones are never discussed. To name their meaning would break them.

Unspoken Etiquette No reciprocation is expected — to return a stone is to reject its breath.

Never pass a stone with warm hands — warmth implies manipulation. Hands are cooled in dew before the ritual.

A cracked or chipped stone is never used — it cannot hold breath cleanly.

No stone is passed more than once. Re-gifting a stone is considered a breach of the soul's private pathway.

Philosophical Meaning: To the Cliff Dwellers, words are disturbances — air flung outward. But breath is internal wind, and the stone is earth’s memory. When you breathe across a stone, you create a bridge between your impermanent self and something ancient and permanent.

It is not the exchange of meaning, but the weight of acknowledgment.

Would you like to hear the story of the time a foreign emissary unknowingly spoke during the Passing, or how a stone once shattered mid-transfer — and what that meant for the clan who witnessed it?'
by koiueo | 2025-04-25 05:52:19+00:00
> I want Al to do my laundry

Do you want a washing machine with Alexa built-in? Be careful what you ask for.

(I know what you meant, but the only laundry-related AI you can hope for, is a cloud connected smart speaker telling you it can't wash with unapproved third party detergent pods)
by iamsaitam | 2025-04-25 05:53:28+00:00
BLOATED. This project is 100 lines of code, but everything that is non-code related is bloated like a gas giant. All the text and videos are written by an LLM. The author would learn from understanding that QUANTITY isn't QUALITY, toning down the verbiage would benefit greatly what they are trying to communicate.

PS: The generated "design documents" are 2k+ lines long. This seems like a great way to exceed quotas.
by dep_b | 2025-04-25 05:54:30+00:00
> It's the only language I've used where I have never asked "but why?"

* But why I cannot use @Published and other decorators in protocol declarations?

* But why must generics always be a pain in the ass, compared to .net, even in the most recent versions? 5 ways to do things, never the one you need

* But why is the person that designed the if case let value = .variable syntax not flagellated in a public square?

* But why is modern concurrency and SPM so undocumented?
by TheAceOfHearts | 2025-04-25 05:54:51+00:00
I think producing new and interesting music with AI tools will require models that allow for far more granularity, tweaking multiple tracks / layers, and this has to be exposed through a more professional and capable UI. It has to go hand-in-hand if it's going to be treated as anything other than a novelty or a toy.

Vibe coding has improved significantly in tandem with UI innovations that provide a more intuitive interface to the workflow. Although in the vibe coding space there's still a lot of room for innovation and exploration, especially when doing detailed task development.
by kfajdsl | 2025-04-25 05:55:18+00:00
I asked Gemini this, and it caught that it was fiction:

This sounds like a fascinating ritual from a fictional world! Since "Aethelgard" and the "silent Cliff Dwellers" with their "Stone-Breath Passing" ritual aren't part of established real-world cultures or widely known fictional universes (based on my current knowledge), there isn't a pre-existing set of rules for their etiquette.

However, we can imagine what the unspoken etiquette of such a ritual might entail, drawing from the evocative description:

...
by stickfigure | 2025-04-25 05:55:21+00:00
The car exists, you just have to look at used. About three years ago I bought a gently used 2013 Fiat 500e for $8k. It gets ~80mi range in the summer (a little less in the winter though). Super fun, drives like a gokart. Plugs into 110 and charges overnight.

My wife uses it for commuting and it's our standard "run to town" car. We have an ICE vehicle for trips.

Absolutely would buy again.
by spauldo | 2025-04-25 05:56:02+00:00
There are plenty of fairly mundane applications for this sort of thing in the military. Every base has a photography and graphic design team that makes posters, signs, PR materials, pamphlets, illustrations for manuals, you name it. Imagine a poster in the break room of a soldier in desert gear drinking from his/her canteen with a tagline of "Stay Alive - Hydrate!" and you're on the right track.
by sampullman | 2025-04-25 05:56:02+00:00
The compile times are ok, but slower than Rust and C++ in my personal experience. What I was referring to with "compile time issues" is the occasional type resolution issue that hangs the compiler for seconds/minutes, and requires some refactoring to mitigate. This does happen a lot less with Swift 6 than it did with 1-4 though.

I've used a lot of IDEs, and spend plenty of time using XCode. It's the worst I've used by far, and the only one where I feel it necessary to edit the majority of code in a separate editor.

Writing apps that people love makes you a good developer, but says little about the tools you use.
by ericjenott | 2025-04-25 05:57:47+00:00
The latency from keypress to screen is 0.3 seconds for the first keypress, and about 0.4 seconds for all keypresses after that, until the next pause in typing.

This device is not, of course, intended to be able to perform modern functions that are required for modern office work. Its goal is to never run out of power, and its design tries to prioritize that at the expense of everything else, including features and performance. Because for anyone that loves computers as much as I do, a computer that will power up and provide a virtually unlimited amount of software, games, programming and software development options, and connectivity is better than a more modern and faster computer that won't turn on because it has no power. This computer can run for 500-1000 hours using power saving mode, and 200 hours without power saving mode. And with the built in solar panel, there should be ample opportunities to recharge it (or just run it directly off sunlight instead of using the batteries) before it the batteries run down. In a situation where people have to adjust to living in the long term without electricity, modern office computing is unlikely to be required, nor will there be any Internet. But in that situation, I still want to have a computer that I can use to do pretty much anything. This gives me that.
by jillesvangurp | 2025-04-25 05:58:46+00:00
The old version would stay licensed exactly as it is. You can't retroactively change a license.

Technically any form of re-licensing the original implies some kind of fork happens. The old system continues to exist for anyone that has a copy. The license allows anyone to fork of course. So anyone with a copy could just pretend that's the main fork.

Chromium is actually a complicated project. Some of the project coordination is actually taken care of by the Linux Foundation; not by Google. But Google of course controls and hosts the key code repositories. However, they don't own the code base exclusively though because they have been accepting contributions from e.g. Microsoft and the many other companies that base their browser on Chromium. And of course individual developers. Copyright stays with those.

The partial permissive licensing (it's a mixed license code base) makes it possible to incorporate the code in a closed source system. But some of the components are LGPL, which still would require publishing the code of those components. And of course Chrome is an example of such a system and Chromium is the way they publish the source code. And Edge. And Brave. Etc. Chromium is the shared source code base for those. But it doesn't allow Google (or anyone) to take away the copyright from contributors. That would require a copyright transfer agreement. And no such thing exists for Chromium.

So, Chromium is unlikely to stop existing. And if it somehow does, it would immediately trigger a fork with a different name created by all the stakeholders that would require such a thing.

The only question is who ends up employing the Google employees that currently provide most of the code contributions and who owns the Chromium trademark (Google currently). IMHO that's an unhealthy situation that should be resolved in any case. And with multiple wealthy companies using chromium, funding that should be no issue.
by xelxebar | 2025-04-25 05:59:59+00:00
> All the stuff that feels difficult and like it's just eating up time is actually me being forced to work out the problem specification in a more condensed manner.

Very well put!

Your experience aligns with mine as well. In APL, the sheer austerity of architecture means we can't spend time on boilerplate and are forced to immediately confront core domain concerns.

Working that way has gotten me to see code as a direct extension of business, organizational, and market issues. I feel like this has made me much more valuable at work.
by jeffrallen | 2025-04-25 06:00:33+00:00
The basic protocol from an AC charger to your car is, "hello, I have X amps available, don't take more or you will trip my circuit breaker". The car responds by charging at or below the current advertised.

When you charge in a context where the car unlocks the charger (i.e. Tesla Supercharger), the protocol must divulge the car's certificate, signed by the owner of the charging network (like mTLS). There would be privacy-preserving protocols for this, but they are not used in practice.
by extr | 2025-04-25 06:04:04+00:00
It's possible but I think this is a bit of a non-issue for cursor. Microsoft extensions are pretty good but are not irreplacable, and in the meantime cursor has grown astronomically fast and has grabbed a ton of "AI Coding" mindshare. I think the gamble has already paid off for them: if they have to play nice with licensing and develop their own solutions to replace MS proprietary extensions, they now have the scale to do that. GH Copilot was first in the game but now has the reputation of the poor man's cursor.
by motorest | 2025-04-25 06:04:51+00:00
> People who fit into the Shell Silverstein "I'm so good I don't have to brag" bucket aren't as visible because they're working, not talking about working.

It isn't as much as "talking about working" but putting the bulk of their effort in self-promotion.

If you hire someone because they excelled at self-promotion, the reason you hired them is because they excelled at self-promotion. Not because they are great or even good, but because they are good at convincing the likes of you to hire the likes of them.

In business settings this sort of problem ends up being a vicious cycle. Anyone that hires a self-promoting scrub is motivated to make that decision look like a success as well, otherwise the scrub's failure will also be their own failure. If these scrubs output passable work instead of great or even good, that's something you as a manager can work with.
by AuryGlenz | 2025-04-25 06:04:58+00:00
95% of what I do with image models is train LoRAs/finetune family and friends and create images of them.

Sure, I can ghiblify specific images of them on this model, but anything approaching realistic changes their looks. I've also done specific LoRAs for things that may or may not be in their training data, such as specific movies.