MurphyA/hacker-news huggingface dataset:
by andsoitis | 2025-11-08 13:56:25+00:00
> this is utterly routine. It even has the name used here: Cross-compiling.

Zig makes cross-compilation trivial and part of the language philosophy.

Other languages either rely on external toolchains (C/C++, Rust with C deps) or are limited in target flexibility (Go).

For projects targeting multiple OS/architectures, Zig is currently the most straightforward option.
by radanskoric | 2025-11-08 13:56:34+00:00
Have you used it over the last few years? It has it been rapidly improving, mainly because Shopify put a team full time on it. It doesn’t take a lot of people to optimize a VM/interpreter it just has to be the right people.

And the question is always “fast enough for what?” Different languages are more suitable for different types of projects. I wouldn’t code a rendering engine in Ruby but for web apps it’s amazing.
by dredmorbius | 2025-11-08 13:57:21+00:00
Efficiency- and longevity-wise, pretty good.

They're fragile as heck, though, and contain mercury (albeit a small quantity in a relatively less-harmful form). Breakage needs to be handled appropriately, and disposal is as hazardous waste.

LEDs are more efficient, offer better (and often more flexible) light quality, are damndably rugged, and have far less toxic material load. Given the balance, I'd be swapping out CFLs (and have been).
by bityard | 2025-11-08 13:57:52+00:00
I think one thing you are running into here in the HN comments is that ligatures as they relate to source code editing can be somewhat controversial among developers who are especially vocal about their preferences.

Some people believe that ligatures make source code more readable. Even, perhaps, beautiful or "comfy."

Others feel that past a certain point, programming font choice doesn't really matter much and that too much time spent sharpening the saw means you never get around to cutting the wood. Or that hiding two physical symbols behind a single logical one for the sake of aesthetics is somewhere between pointless and dishonest.

Still others are of the opinion that we wouldn't need ligatures at all if programming languages understood Unicode. The other problem of course being that most of us don't have Unicode keyboards.

Your project seems to have somehow managed to upset all three camps and for that, I salute you and have starred your project on GitHub.
by Thorrez | 2025-11-08 13:58:05+00:00
Here's what I'm suggesting: query all your current passwords against the password API. Then you'll know which of your current password are compromised. Change them.

You don't need to query old passwords, only current passwords. If you're talking about accounts that you've forgotten the password to: then do you care about those accounts? If yes, probably best to do a password reset and set a new password. If you don't care about the account, then why bother?

As for why HIBP doesn't provide an API linking passwords to emails: HIBP has no database that links passwords and emails. So they can't provide any way to query that. They don't want to be in the business of linking passwords to emails.
by amelius | 2025-11-08 13:58:10+00:00
Briefly, with an example: instead of going through menus looking for the option you need, you can just tell the AI (with a voice command) what you want to do. At that point it does not matter who has the nicest menus.

Advanced users are already seeing this. You don't need HandBrake anymore. You can just use ffmpeg directly and ChatGPT will tell you the command line arguments.
by TheAtomic | 2025-11-08 13:58:36+00:00
THIS! Ads, misusing notifications (thank LinkedIn for that idea), Tahoe's self-indulgent UI, changes for no reason than some new designer has an idea, getting things ready for spatial, the stupid dispute with Nvidia...

Apple has a ruthless competitive upper echelon that gets rewarded on metrics that prioritize market hits and revenue increases. Get ready for more of this.

Obligatory I've been using Macs since the SE comment but I know Apple gives 2 damns about that.
by PaulHoule | 2025-11-08 13:58:50+00:00
All I can think of is

https://video.disney.com/watch/sorcerer-s-apprentice-fantasi...

The core thing about AI coding is “sometimes it works and sometimes it doesn’t”. There are times when I ask an agent to do something and it does a great job, other times when it takes three attempts. There was that time I was struggling with a TypeScript code base where the errors didn’t make sense to either me or the AI but in three days of hacking on it with AI help I whipped the code into shape, understood what was going on, and the AI became able to do application-level tasks (“add a new field to this form”)

I just can’t see an AI coder going 8 hours and making anything that doesn’t take 16 hours to whip into shape.
by tacker2000 | 2025-11-08 13:58:56+00:00
You are talking about changing arrows to unicode arrows.

These arrow symbols are NOT identifiers but a specific syntax used in these C type languages, and then you give examples of identifiers being able to be specified in unicode.

This is not the same thing, so i have to assume that you are confused here.

Also, my point is that keyboard layouts are so ingrained that they will never change, and even if they change, it wouldnt be for some niche use like using unicode arrows.
by etempleton | 2025-11-08 14:00:06+00:00
These moves are the dumbest thing Apple can do for the long- term. It is one of the few differentiators they have between Android and Windows.

The App Store ads are one thing, it is a store after all, but adding ads to a core OS functionality like Maps is clear degradation of service. When people spend 1 to 2 grand on a premium phone they don’t expect to see ads, ever.
by lapcat | 2025-11-08 14:02:27+00:00
The submitted article is about iOS, not macOS. Apple unfortunately used the same word "notarization" on both platforms, but the processes are not even remotely similar. Perhaps the confusion was deliberate, but in any case, many commenters here are confused and mistakenly believe that iOS notarization is like macOS notarization.

iOS notarization is still manual review by Apple, but with fewer rules and restrictions.

https://developer.apple.com/help/app-store-connect/managing-...

> If you’ve opted into alternative distribution for customers in the European Union, you can choose to make your app version eligible for distribution on alternative app marketplaces or websites only by selecting to have it evaluated based on the Notarization Review Guidelines (a subset of the App Review Guidelines). Otherwise, App Review uses App Review Guidelines to evaluate your app version to make it eligible for distribution on the App Store, alternative app marketplaces, and websites if approved.
by kibwen | 2025-11-08 14:02:46+00:00
> I don’t think Java and Rust were so ok with completely removing features.

This just shows that you weren't around for pre-1.0 Rust. Back then Rust was infamous for the language making breaking changes every week. Check out this issue from 2013 tracking support for features which were deprecated but had yet to be removed from the compiler: https://github.com/rust-lang/rust/issues/4707 , and that's just a single snapshot from one moment in Rust's prehistory.
by rkomorn | 2025-11-08 14:02:54+00:00
Distros like Mint, Ubuntu, Bluefin, etc all annoy me to the same extent as Windows.

Distros like Arch, NixOS (my current laptop driver) or even Debian require a bunch of tinkering to get some things to behave properly.

Also, I get tired of all the tech "reboots", eg the 3 or 4 different ways of setting up network or DNS, pipewire vs pulseaudio vs whatever, Wayland vs X11, etc.
by wronex | 2025-11-08 14:03:38+00:00
The nice thing with KiCAD is that a part is simply a symbol (schematic element) with enough parameters attached. You can specify footprints, MPN, ratings, value, etc. then store it in your approved and verified symbol library for use in all your projects. Use your R_4.7k_0603 symbol an it comes preconfigured with footprint, MPN, rating etc. Making these symbols is a lot of work but very simple.

Unfortunately there is no standard name for these parameters beyond footprint, value and some others. MPN, brand, rating etc. are not default. This hinders bigger adoption I think, and makes every project unique. This should be improved.
by tomhow | 2025-11-08 14:03:49+00:00
You can't comment like this on Hacker News, no matter what you're replying to. It's not what this site is for, and destroys what it is for. If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.
by mrweasel | 2025-11-08 14:04:16+00:00
I would recommend trying Ecosia, their search have become really good. Better than DuckDuckGo, Bing and Google to be honest. They use a mix of Bing, Google and a few other things, most recently their own index which they collaborate on with Qwants (only for German and French at this point).

Originally I switched due to their environmental focus and the way they run the company, but the quality of the results keeps me there. They have their own ! query, like DuckDuckGo. So !maps for Google Maps and !w for Wikipedia.
by rainsford | 2025-11-08 14:04:32+00:00
The VFR stuff is always optional for ATC. VFR aircraft can request those things and ATC will usually accommodate, but it's workload dependent and ATC can and does decline, that's the whole tradeoff of flying under VFR rules. I'm less sure on the others, but I'm pretty sure they're all optional as well for ATC.

Now the difference might be that ATC will be more likely to deny these requests, which could be somewhat disruptive to flights that were expecting to be approved. But it should never be assumed so hopefully they have backup plans.
by swiftcoder | 2025-11-08 14:04:35+00:00
The view part would be fine, the problem is updating the state. In a language which discourages shared mutability, most of the solutions are not terribly ergonomic.

You either end up needing to:

- handle all your state via interior mutability (i.e. Arc<RefCell<_>>)

- use a reducer (i.e. the state blob is immutable during rendering, updates are deferred via events that are delivered between frames)

- or invert the relationship between state and view (i.e. immediate-mode) which comes with it's own implementation challenges (caching immediate mode views is hard)
by techscruggs | 2025-11-08 14:05:21+00:00
Remember that Steve Jobs appointed his COO Tim Cook to take over Apple. Not Ives or Cue or Federighi. I've always seen this as an acknowledgment that without Jobs the company would not be able to innovate in the same way.

Having acknowledged that, Apple shifted to the value extraction phase of its business lifecycle.

It sucks.

It like when your favorite band starts selling out, but as publicly traded company, I am not sure it is avoidable.
by Rochus | 2025-11-08 14:05:36+00:00
Works great, just generated my first songs. Great composition and arrangement (not yet as great as Suno, see below). But the sound quality is better than Suno (less compression/alias artefacts, more transparent)! Is it possible to upload my songs (audio) and create a cover version of them?

EDIT: here my first attempts:

- http://rochus-keller.ch/Diverses/musci.io_My_first_attempt_0...

- http://rochus-keller.ch/Diverses/musci.io_My_first_attempt_0...

And for comparison a couple of songs created with Suno with the same kind of prompt (but with audio upload): https://rochus-keller.ch/?p=1428
by mort96 | 2025-11-08 14:06:42+00:00
The point is that notarization plays the same role for both platforms: checks whose purpose is to make sure that the software won't harm the user's device, unrelated to the App Store review process. Both platforms have an additional App Store review process which is significantly more strict, and the notarization process isn't supposed to involve App Store review for either platform.

When Apple denies notarization for bullshit reasons on one platform, it makes me highly suspicious of their motivation for notarization on all platforms.
by ants_everywhere | 2025-11-08 14:06:57+00:00
There was a large literature on language acquisition prior to the invention of LLMs that showed that Chomsky's argument likely wasn't correct. This is in addition to the fact that he significantly underestimated the amount of linguistic input children receive.

There's too much to hash it out here in HN. You can try to save the LAD argument by a strategic retreat, but it's been in retreat for decades now and keeps losing ground. It's clear that neural networks can learn the rules of grammar without specifically baking grammatical hierarchies into the network. You can retreat to saying it's about setting hyper parameters or priors but even the evidence for that is marginal.

There are certainly features of the brain that make language learning easier (such as size) but POS doesn't really provide anything to guide research and is mostly of historical interest now. It's a claim that something is impossible, which is a strong claim. And the evidence for it is poor. It's not clear it would have any adherents if it were proposed anew today. And this is all before LLMs enter the picture.

The research from neuroscience and learning theory and machine learning etc have all pointed toward a view of the brain as significantly different from the psychological nativism view. When many prominent results in the nativist camp failed to replicate during the replicability crisis, most big name researchers pivoted to other fields. Marcus is one of the remaining vocal holdouts for nativism. And his beliefs about AI align very closely with all the old debates about statistical learning models vs symbolic manipulation etc.

> Why are other intelligent animals not able to learn human languages?

Animals and plants do communicate with each other in structured ways. Animals can learn to communicate with humans. This is one of those areas where you can choose to try to see the continuities with communication or you can try to define a vision of language that isolates human language as completely set apart. I think human language is more like an outlier in complexity to the communication animals do rather than a fundamentally different thing. In that sense there's not much of a mystery given brain size, number of neurons, sociality etc.

> The argument is that there is not enough information available to a child to do this

Yes, but children are the humans who earn language in the typical case. So you can replace "child" with "human" especially with all the hedging I did in my first post (e.g. "essentially"). As I said above Chomsky is known to have underestimated the amount of input babies receive. Babies hear language from the moment they're born until they learn to speak. Also, as a parent, I often correct grammatical and other mistakes as toddlers learn to talk. Other parents do the same. Part of the POS is based on the premise that children don't get their grammar corrected often.
by brunosutic | 2025-11-08 14:08:07+00:00
> I would consider monthly Enterprise & yearly Enterprise the same plan, with modified cost & billing frequency.

How would you then call the objects that store costs and billing frequency? :)

Here's what Stripe uses:

- Product: "describes the goods or services". This is where you define a (plan) name and features.

- Price: defines the amount, currency, and (optional) billing interval. Since interval is optional, Prices can be used to define both recurring, and one-off purchases.

Technically, using Prices for recurring, and one-off payments is a brilliant idea. The problem is, no one refers to recurring payments as "prices". Everyone calls a "$50 per year" option a "plan".
by kcplate | 2025-11-08 14:09:07+00:00
> I am not saying it has a value, but 30% seems a lot.

I’d suggest that it’s cheap, at least historically compared to just about any other product that’s been sold. If I had a popular marketplace platform that basically sold my product without much need for human intervention on the transaction, that has real value. Honestly 30% seems like a bargain to me.

In marketing and sales of the product, any human that touches the process ultimately is getting a piece of that transaction. We may not have physical media, but that was actually probably the least of the expense associated with software products back in the day. Consider the army of people needed just to wholesale to retail, coordinate distribution, distribute…

My recollection from those days is that if the dev got 10% royalties of a purchase price they would have been ecstatic. If you offered them 70%? They probably would have thought “what’s the catch?”
by rainsford | 2025-11-08 14:09:25+00:00
Trusting the safety of a flight to the reliability of an ipad is a ludicrously bad idea. Lots of pilots fly with ipads as a tool and they're generally pretty good, but they're nowhere near up to aviation standards of reliability and banking the whole safety of the flight on the reliability of a consumer good seems unwise. Ask any private pilot who's flown on a hot sunny day with an overheating ipad how good the idea sounds.

Edit: More automation is certainly an idea that ATC should continue to pursue, and there has been progress already. But the idea that total automation is possible much less easy ignores a lot of the complexity and reality of how air traffic actually works.
by Pooge | 2025-11-08 14:09:26+00:00
> require a bunch of tinkering to get some things to behave properly

> the 3 or 4 different ways of setting up network or DNS, pipewire vs pulseaudio vs whatever, Wayland vs X11, etc

Sounds like a problem with your distribution. I've been on openSUSE Tumbleweed for years and I've never had to tinker with any of those.
by WoodenChair | 2025-11-08 14:09:59+00:00
> Not Ives or Cue or Federighi.

It’s “Ive” and Federighi wasn’t a candidate in 2011.

Also, how you think someone is going to work out and how they actually work out is still worth commenting on. Not every CEO would have extracted value in the same way. You can prioritize extracting value by making customers super happy so they buy more. That’s what the article is about.
by stego-tech | 2025-11-08 14:10:09+00:00
That’s an incredibly nihilistic and naive way of viewing regulation. Pre-Reagan but post-Depression, much of the regulations passed were beneficial to society and harmful to Capital interests: forcibly dividing investment banking from retail, for instance, to protect consumer deposits; the FDA, for gradually weeding out snake oil “cure-alls” and ensuring the safety of foodstuffs; eliminating child labor, setting livable minimum wages, creating overtime rules, protecting Unions and workers; safety standards for buildings like fire sprinklers, protected evacuation stairwells, engineering rules and sign-off requirements; and on, and on, and on.

Regulation is overwhelmingly positive, but the past fifty years have been a deliberate demonstration of the frailty and abusability of regulations by entrenched capital via regulatory capture, mainly to create people who (often unknowingly) champion a return to flammable mattresses, tainted foodstuffs, and corporate monopolies in the name of deregulation.

Regulations are a tool, a tool that can be wielded for the benefit of society or the benefit of Capital. It’s up to the electorate to be educated enough to advocate for proper use of said tool, rather than ignorantly swallow propaganda to let Capital run roughshod with them.
by embedding-shape | 2025-11-08 14:10:35+00:00
> Then why don't manufacturers recommend this?

They literally do! https://i.imgur.com/gCDuZZM.png

Rather than jumping into this whole thing in the middle, I'll ask you to begin from the beginning, catch up on what you missed on (the two earlier Technology Connections that were made before the submission article), so we can at least have the same base-level understanding of the situation first, then you can come back and we can argue the entire day.
by ethbr1 | 2025-11-08 14:10:51+00:00
I meant that the Fed, Treasury, etc. have powerful levels they can pull to head off initial effects.

What can overwhelm them is if those effects cascade and compound into second-order effects, typically multiplied in magnitude.

That's essentially what the fuck-up in 2008 was. The government let Bear Stearns fail because it could handle the effects. What it couldn't handle (or at least, was barely able to) were the second order effects of credit tightening, mortgage derivative repricing, counterparty trust loss, etc. etc.

The government could absolutely prop up the AI bubble, possibly indefinitely. What it can't do is cover second order fallout, if it turns out a lot of risky money was somehow tied into the bubble.
by lvl155 | 2025-11-08 14:12:31+00:00
I’ve been an Apple fan for as long as I can remember. I didn’t worship Jobs but he had complete control of Apple when he returned and molded the company in his vision. The company lacks that vision. Vision Pro is an example of that failure. Luckily for them iPhone and Mac will continue to dominate. They are here for another decade plus and once the AI bubble passes and we settle on clear winners, Apple will pounce on that opportunity. Am I heartbroken that they’re not the trailblazers? Outsiders? Hipsters? Yes. The brand has gone from Ferrari to Toyota. That’s quite literally the most perfect analogy.
by _benedict | 2025-11-08 14:12:55+00:00
I can’t speak for the authors, but I have been lucky enough to be collaborating with them on behalf of the Apache Cassandra project, to refine and prove the correctness of the Accord protocol - a derivative of EPaxos we have integrated into the database.

It would be fantastic if such a project could be pursued for this variant, which has the distinction of being the only “real world” implementation.

Either way, thank you for the original EPaxos paper - it has been a privilege to convert its intuitions into a practical system.
by drougge | 2025-11-08 14:14:20+00:00
This seems interesting, but I got stuck fairly early on when I read "all 32,385 possible input combinations". There are two 8 bit numbers, 16 totally independent bits. That's 65_536 combinations. 32_285 is close to half that, but not quite. Looking at it in binary it's 01111110_10000001, i.e. two 8 bit words that are the inverse of each other. How was this number arrived at, and why?

Looking later there's also a strange DAC that gives the lowest resistance to the least significant bit, thus making it the biggest contributor to the output. Very confusing.
by mapontosevenths | 2025-11-08 14:14:51+00:00
Outside of manufacturing defects you can expect HTL blu-rays to last for more than a hundred years when stored properly. Some estimates are as high as 300 years. Don't buy the cheap ones or store them outdoors and you'll be fine.

Some archival grade disc's are estimated to last 700 years or more and dont cost THAT much more.

DVD's and CDR'S used organic dies that broke down quickly. Blu-rays mostly use inorganic dies that last forever. Cheap LTH disc's being the exception.

MOST manufacturers like Verbatimm do not even produce the organic die LTH disc's anymore as people stopped buying them. There are still some floating around for sale, so avoid them.
by eviks | 2025-11-08 14:17:31+00:00
> This is not the same thing

So what? How is that relevant to your argument about fatal confusion? Why is confusion in supporting var𓀄 ok, but confusion supporting → in addition to -> suddenly fatal???

> they will never change

What's the point of this point, what does it address in this conversation? Who is talking about mandatory or even necessary global layout changes? Did you miss one of the alternatives I mentioned that allows changing nothing on your input side by letting your editor auto-substitute?