MurphyA/hacker-news huggingface dataset:
Show HN: What Games Play? Pacman and Battle City
by harperhuang | 2025-07-10 06:59:49+00:00
Hello everyone! I'm excited to share that my game collection has recently been updated with two new classic games - Pac-Man and Tank Battle. I'd love for you to try them out when you have some free time! Feel free to bookmark the website so you can enjoy these games while waiting for the bus, standing in line, or during your break time. Hope they help make those moments a bit more fun!
by geokon | 2025-07-10 06:59:50+00:00
I find 95% Clojure has the right tools to write very terse code. But in some cases the functional transducer/piped paradigm can't be contorted to the problem.

Usually these are problems where you need to run along a list and check neighboring elements. You can use amap or map-indexed but it's just not ergonomic or Clojure-y (vs for instance the imperative C++ iterator model)

The best short example I can think of is Fibbonacci

https://4clojure.oxal.org/#/problem/26/solutions

I find all the solutions hard to read. They're all ugly. Their performance characteristics are hard to know at a glance
by ryuker16 | 2025-07-10 06:59:57+00:00
Double blind testing has been done on this so none of what your essay is saying has not been tested or studied.

Putting adhd or depressed people in a paradise situation does not make them not adhd or depressed.

Ive lived in a few different countries. Societies that dont label or believe in psychology just outcast the mentally ill as weirdos and encourage them to drink away their troubles.
by reify | 2025-07-10 07:01:13+00:00
I think its a great idea

After all we have to tolerate the numbskulls who think people want to read regurgitated news links galore.

People can go those sites if they want to read them.

the guardian, theatlantic, thetimes, newyorker, foxnews, bloomberg, facebook, dailymail, nytimes, washingtonpost, nypost, amazon? twitter, bbc, wsj.

same old stories, different named sites

I like to read interestng stuff by interesting people not MSN biased news.
by ralfj | 2025-07-10 07:02:58+00:00
Pointer aliasing information is often crucial for vectorization. So in that sense TB is a big boost for vectorization.

Also, note that the paper discussed here is about the model / language specification that defines the envelope of what the compiler is allowed to optimize. Actually getting the compiler to optimize concrete real-world cases is an entirely separate line of work, and needs completely different expertise -- expertise me and my group do not have. We can only lay the framework for compiler wizards to have fun with. :)
by TFYS | 2025-07-10 07:03:35+00:00
Unless the country can be completely self-sufficient, even that is not enough. If a country decides to cut working hours and other's won't, it will eventually not be able to afford the resources it needs from other countries because the countries that squeeze their workers will have more money to pay for them. I believe these competition based systems will be our downfall. Nobody can do anything that doesn't improve their position compared to competing countries/companies/people, even if it would make things better overall. If you do, you lose and die out. We will use all our resources, kill each other, etc in pursuit of victory for as long as the systems of this planet can support it and then we die.
by karlperera | 2025-07-10 07:03:40+00:00
Hi HN, I came across this new research from University College London and Goettingen University that seems like a significant step in predictive medicine.

They've developed an AI model that analyzes a panel of eight key proteins in a person's blood. In their study, the model was able to identify patients who would go on to develop Parkinson's disease with 100% accuracy, up to seven years before any motor symptoms appeared.

The "100% accuracy" claim is obviously a very bold one and will need to be tested to verify this. The use of a simple blood test could be a game-changer for clinical trials and, eventually, early treatment. let me ask this: what do we do when we still cannot cure Parkinson's but can predict it?
by southernplaces7 | 2025-07-10 07:04:12+00:00
Color me shocked. I'd have never imagined that they'd detect such a thing from the honest, law-abiding, rules-beholden public servants of ICE and its federal law enforcement colleagues.

Seriously though and on a practical note, anyone who really does care about their identity being revealed, or getting nailed by some kind of law enforcement crackdown/harassment on traced and identified participants after a protest should simply not bring their phone to one of these events, at all.

If you really need communication during, get a burner right before the event, buy it with cash, preferably somewhere where a dozen cameras don't get your face plastered all over them (and while not having your normal phone with you when you go buy the burner), and dont download any apps with personally identifying accounts to it. After, toss that same burner phone right away or deactivate it completely. well before coming back into proximity of people you normally know, your home, or places you frequently habituate.
by bluecalm | 2025-07-10 07:04:18+00:00
>>Good job Europe, keep blazing a trail which I hope my country eventually decides to follow.

While GDPR had some good intentions the way it implemented in practice just makes things more difficult for consumers and changes little. For example in Poland one of the major banks still forces you to accept them sharing your information with advertising partners.

The main effect of the regulation is that you waste 30 seconds on every call to a business you make for listening about stuff about their privacy policy and the on every form you have to consent to something or be denied service.
by manzanillo | 2025-07-10 07:04:54+00:00
Today, at IQM we are launching a major upgrade to our cloud quantum computing platform, IQM Resonance. The goal is to accelerate quantum research and software development by providing more powerful tools and, crucially, greater access to advanced hardware.

To empower advanced users and researchers, we've added a host of new features, including a new freemium plan to democratize access:

Access to our 54-qubit Crystal system: We're making our powerful Crystal 54-qubit quantum computer available on the platform.For a limited time, also available for users on our new freemium Starter Tier.

Pulse-Level Access: For those who need to go beyond standard gate-based programming, you can now directly program pulse schedules to conduct fine-tuned experiments and explore novel quantum operations.

Advanced Error Handling: We're rolling out crucial error suppression and mitigation strategies, starting with dynamical decoupling to protect qubits from environmental noise. This allows for more precise and reliable experimental results.

QAOA Library: A new Quantum Approximate Optimization Algorithm (QAOA) library is now available, enabling researchers to quickly build, test, and optimize circuits for combinatorial optimization problems.

New SDK Default: We've integrated Qrisp as our default SDK. While we continue to support popular frameworks like Qiskit, Cirq, and Cuda Quantum, we've found Qrisp offers significant performance advantages in terms of gate-counts and compiler scaling.

Our aim with Resonance 2.0 is to simplify the development process and provide a consistent, powerful foundation for innovation. We believe that by combining accessibility with advanced control, we can help the community push the boundaries of quantum computing.

I'd love to hear your thoughts and answer any questions you might have.
by vidarh | 2025-07-10 07:05:15+00:00
> Indeed. The unspoken requirement behind (too) smart interpreters is 'I don't want to spend time segregating permissions and want a do-anything machine.'

> Since time immemorial, that turns out to be a very bad idea.

Sometimes you can't, or it costs more to do it than it costs to accept the risk or insure against the possible bad outcomes.

Mitigating every risk is bad risk management.

But we can presumably agree that you shouldn't blindly go into this. If you choose to accept those risks, it needs to be a conscious choice - a result of actually understanding that the risk is there, and the possible repercussions.

> This is and always will be the solution.

It's the solution when it doesn't prevent meeting the goal.

Sometimes accepting risks is the correct risk management strategy.

Risk management is never just mitigation - it is figuring out the correct tradeoff between accepting, mitigating, transferring, or insuring against the risk.
by eightnoteight | 2025-07-10 07:05:52+00:00
Zenact AI | Founding Engineers & Interns | Full-Time + 6-Month Internships | Onsite Bangalore | Location flexible for internships (India)

Tech: Golang • Python • AI Agents

At Zenact AI, we are building AI agents that test apps like real users. I personally faced this problem at Zomato for over 6 years while handling many bugs and incidents.

We launched recently and already got 35+ signups from leading unicorns & soonicorns in India.

Backed by the Zomato mafia.

Team comes with deep expertise from Zomato’s scale journey.

Roles:

Founding Engineers.

Interns (6 months). Must’ve built serious projects or freelanced early in college.

You’ll work on:

* Building the platform from the active feedback from the customers, with heavy focus on improving the end to end latency of testing.

* Fine-tuned vision & reasoning models (currently 92% accuracy vs SOTA ~60%)

* AI agents for mobile testing, reasoning flows.

Apply: shoot a mail to sri@zenact.ai or fill form here: https://forms.gle/yWproMowhA4ZF4gv6
by globular-toast | 2025-07-10 07:06:32+00:00
This seems to mostly boil down to including links rather than just IDs and having the client "just know" how to use those IDs.

Django Rest Framework seems to do this by default. There seems very little reason not to include links over hardcoding URLs in clients. Imagine just being able to restructure your backend and clients just follow along. No complicated migrations etc. I suspect many people just live with crappy backends because it's too difficult to coordinate the rollout of a v2 API.

However, this doesn't cover everything. There's still a ton of "out of band" information shared between client and server. Maybe there's a way to embed Swagger-style docs directly into an API and truly decouple server and client, bit it would seem to take a lot more than just using links over IDs.

Still I think there's nothing to lose by using links over IDs. Just do it on your next API (or use something like DRF that does it for you).
Ask HN: Pricing strategy for macOS App
by fandorin | 2025-07-10 07:06:33+00:00
I have created a macOS (desktop) app that has been gaining some reasonable traction over the last year. My current (and the only) pricing strategy is a fixed $16 one-time fee for the full app (can be installed on 2 Macs) and a free-to-use tier for the limited app. No recurring payments, no subscriptions. People are using the app and buying the license - so that's good.

I know that for SaaS-type products, the most optimal pricing strategy is almost always subscriptions, but what about desktop apps? What are your experiences (as a creator and as a user of such apps)? Should I change it to something like: - free tier (limited app) - one-year license fee (lower than the current price) - lifetime license fee (as it is now)

Or should I keep it as it is and stop thinking about it for now?

Thanks for any suggestions.
by NitpickLawyer | 2025-07-10 07:06:37+00:00
4x o3 and 2x opus 4 on ARC-AGI2... Other independent benchmarks look strong as well. It's that revolving meme with each model claiming "best in the world" for like a month. Good for consumers, as long as the prices remain in this range. Also more diverse datasets for training open access models. Win-win.

Watching people doing mental gymnastics because spaceman bad is sad. Lots of people need media detox for a while. They used to call LLMs "stochastic parrots", but looking at this thread and reddit right now, the "people" are just parroting stupid hateful stuff. You're supposed to be better! Be.
by ralfj | 2025-07-10 07:07:06+00:00
OTOH we have https://web.ist.utl.pt/nuno.lopes/pubs/ub-pldi25.pdf which shows that on a range of benchmarks, disabling all provenance-based reasoning (no strict aliasing, no "derived from" reasoning, only straight-forward "I know the addresses must be actually different") has a much smaller perf impact than I would ever have expected.
by Ygg2 | 2025-07-10 07:07:42+00:00
Conclusion is scathing:

> The findings highlight significant variations in the theoretical detection capabilities of these techniques and reveal that, in practice, the implementations of most available sanitizers fall short of their conceptual potential. Furthermore, the evaluation demonstrates the complexities and diversity of memory bugs in C/C++, as well as the challenges associated with detecting them. For instance, our results show that SoftBound+CETS, a conceptually complete sanitizer, misses nearly a quarter of spatial memory bugs in its original implementation, while ASan, likely the most widely used memory sanitizer, cannot detect 50% of use-after-* bugs and any non-linear overflows and under- flows. Ultimately, our evaluation concludes that no sanitizer currently provides complete temporal or spatial memory safety
by giingyui | 2025-07-10 07:07:56+00:00
I profoundly dislike the politics of most “leaders” for lack of a better word in the world of tech, but here I am typing these words in an iPhone. Refusing to use something because of who created it or who benefits from it is a bit too much I think, to the point of being unworkable depending on the case.

In other words as much as I’d like to vote with my wallet that is not always practical. And that extends to everything, not only tech.
by hamcocar | 2025-07-10 07:09:03+00:00
I am very sorry, but you do not address that TBAA, like C has by default, generally is easier than just no aliasing, like what Rust has for mutable references. This is a major difference. C code can opt into a similar kind of aliasing, namely by using _restrict_, but that is opt-in, while it is always on for Rust.

And there is newer UB as well in Rust stdlib

https://github.com/rust-lang/rust/pull/139553
by reify | 2025-07-10 07:09:19+00:00
no we shouldn't!

because ai could never experience suffering

Suffering is the price we pay for a consciousness capable of love and the loss of love, of hope and the devastation of hope. Because suffering, like consciousness itself, is a full-body phenomenon — glands secreting fear, nerves conducting loneliness, neurotransmitters recoiling with regret — a disembodied pseudo-consciousness is fundamentally incapable of suffering and that transmutation of suffering into meaning we call art:

An algorithm will never know anything beyond the execution of its programmed plan; it is fundamentally spared the failure of its aims because failure can never be the successful execution of the command to fail.

We create — poems and paintings, stories and songs — to find a language for the bewilderment of being alive, the failure of it, the fulness of it, and to have lived fully is not to have spared yourself.

https://www.themarginalian.org/2025/07/07/suffering-creativi...
by azangru | 2025-07-10 07:09:22+00:00
> While I'd generally agree that most companies can change their name, encroaching on a basic letter should be off limits

To me it's the other way around. If the platform had been named X from the start, then a language would have developed around it, including what its messages are called, or what verb is used to refer to posting a message. We, the public, wouldn't have known any better. With Twitter, we do know better — better name, better nouns, better verbs (even a better logo; but that's by the by). Bosses can rename their products as much as they like; it's just surprising to me that we as a public so obligingly give up this tiny bit of our language.

> like naming your company "The" or "God".

Consider truth social :-) I am amazed people agree to call the messages there 'truths', and reposts, 'retruths'. So embarrassing.
by sym5731 | 2025-07-10 07:09:24+00:00
Hello, I'm the author of the post. Before answering your comment I want to thank you for reading my article and for talking about it.

> Based on the other blog posts it appears the author is too young to remember a time before smartphones.

You are probably right, I'm in my mid twenties and I was in middle school when the first smartphones came out.

What I mean in my article It's not the demonization of smartphones as a form of technology, but rather the compulsive attitude of use I see more and more often.

I agree that watching what's happening in the world is more interesting than staring to the void on the subway, and I'm absolutely not saying that engaging conversations with strangers is a plausible alternative in most situations.

So I reiterate that my article was aimed at that attitude of obsessive attachment that makes you scroll twenty Reels before you even have time to get on the subway or sit on a park bench.

Sometimes taking ten minutes of mental presence, where you make yourself aware of what's happening around you can be healthy.
by t0bia_s | 2025-07-10 07:09:40+00:00
You can ignore features that aren't made for you

Another terrible design in darktable is default settings. I have no problem with options, but then you need carefully choose defaults that are selected questionable here - pure exhibitionism right after opening software.

I don't agree with your statement about developing by photographers. If so, there is higher probability that they would focus on UI with more aesthetic care than coders would do.

Lack of AI masking is too expensive to use by professionals. You simply cannot afford to mask manually bunch of images. Wider adoption among photographers is simply impossible.
by jackdoe | 2025-07-10 07:09:58+00:00
an interesting article gibbitz linked in a dup post

https://www.edn.com/toyotas-killer-firmware-bad-design-and-i...

> Embedded software used to be low-level code we’d bang together using C or assembler. These days, even a relatively straightforward, albeit critical, task like throttle control is likely to use a sophisticated RTOS and tens of thousands of lines of code.
by bigyabai | 2025-07-10 07:10:48+00:00
My big gripe with Music is that big butt-ugly modal ad they prompt you with if you're one of the billions of humans that don't pay for Apple Music: https://discussions.apple.com/thread/253368403

It's something I'd have expected out of Microsoft, but from Apple it's a particularly shitty gesture. A big warning sign to the user that "your" device hasn't been fully paid-off yet.

> The longevity is the biggest concern to me when considering the third party apps.

And that's why I had to stop using MacOS entirely. It's absurd for a culture of paid software to have such horrible runtime compatibility. Meanwhile on Windows, you don't ever buy software that stops working. Even Linux has largely circumvented it's own ABI woes with sandboxed packaging. MacOS's statically linked app framework has every advantage in pushing out support timelines as far as Apple wants - they just don't want to push it very far, sadly.
by tsimionescu | 2025-07-10 07:10:49+00:00
I find it quite absurd to suggest that a ruling that forces corporations to simplify their business practices would cost $100 million to implement. I would be willing to bet the companies would significantly reduce their spending by following these rules, not increase them. But it's not in any way surprising that they'd find a judge who buys their massively overinflated estimates over the FTC's calculations.
by surrealistic | 2025-07-10 07:11:54+00:00
This whole cycle is full of caveats like this. Some people claim LLMs solved NPL and are on a pathway to true intelligence. Yet they keep turning out nonsense and we're now speedrunning 80s style expert systems on top of them.

Protein folding, like you said. Material sciences, "AI can produce bespoke recipes to spec" yeah lots of ideas that might or might not work in practice with zero pathway to production.

Statistical analysis of past data might look impressive with 2020s levels of power and compute density. But so far they've added more noise than signal to our systems.

And yet people will insist every day that the noise is music.
by o11c | 2025-07-10 07:12:50+00:00
> we are not able to opt out of diffusion of progress. People move between companies and between countries and take their ideas and talents with them.

Never forget that Industry itself came to America by way of direct theft. https://en.wikipedia.org/wiki/Samuel_Slater

=====

If you care about your users, you should always prefer some copyleft license.

Prefer permissive licenses only if you want to subsidize big business. Hopefully you have a plan for when they decide to take it closed-source and outcompete you. You probably don't, though, since that's not mentioned in the aggressive "use permissive licenses" marketing campaign they've been running for the last decade or two.

Permissive licenses can fit in a niche for software that has already been implemented many times. But the downsides remain, and why aren't you just using the existing code directly? The main occasion on which I will consider it is when everybody else is doing it wrong (and content to do so), and I as a user keep getting annoyed at hitting those limitations.

The second-worst reason to use permissive licensing is arguably "I don't understand how to dynamic linking".
by ralfj | 2025-07-10 07:12:57+00:00
> The aliasing rules of Rust for mutable references are different and more difficult than strict aliasing in C and C++.

"more difficult" is a subjective statement. Can you substantiate that claim?

I think there are indications that it is less difficult to write aliasing-correct Rust code than C code. Many major C codebeases entirely give up on even trying, and just set "-fno-strict-aliasing" instead. It is correct that some types are compatible, but in practice that doesn't actually help very much since very few types are compatible -- a lot of patterns people would like to write now need extra copies via memcpy to avoid strict aliasing violations, costing performance.

In contrast, Rust provides raw pointers that always let you opt-out of aliasing requirements (if you use them consistently); you will never have to add extra copies. Miri also provides evidence that getting aliasing right is not harder than dealing with other forms of UB such as data races and uninitialized memory (with Tree Borrows, those all occur about the same amount).

I would love to see someone write a strict aliasing sanitizers and run it on popular C codebases. I would expect a large fraction to be found to have UB.
by herbst | 2025-07-10 07:13:00+00:00
The next social network will not be another social network.

Most parts of Europe long moved away from any social media dependency all that's left is IM/chatting.

Where only WhatsApp is a somewhat popular American software, the rest isn't.

Edit:// to clarify I am not saying people aren't using Instagram or even Facebook. My point is they don't use it to socialize anymore
by whitehexagon | 2025-07-10 07:13:00+00:00
Nice, the posh stuff! I seem to recall that system included remote access and nice control panels.

I managed to get remote access working via an iobridge IO-204 X10 module and a custom iOS App. Great fun. I still have the X10 stuff lying around because I was then trying for local only using the X10 serial controller that I never managed to hack.