Hacker Newsnew | past | comments | ask | show | jobs | submit | supernes's commentslogin

I tried it recently. Uploaded around 300 documents (1GB) and then went to delete them. Maybe my client was buggy, because the S3 service inside the container crashed and couldn't recover - I had to restart it. It's a really cool project, but I wouldn't really call it "reliable" from my experience.


> Several users have reported to me that a workaround is to sign up for Apple’s public beta program and opt in to the iOS 18 public beta track, at which point you’ll be offered 18.7.3.

Thanks for that, just enrolled at downloading the update now.


> By comparing the photo on an identification card with the holder's actual face on a real-time basis, we can fully prevent the activation of phones registered under a false name using stolen or fabricated IDs.

Don't employees at the POS already check the customer's ID by comparing their face to the ID photo "on a real-time basis" using their eyes? What am I missing?


> You can still use JSDoc in your typescript files, but why do you want to do that?

JSDoc is more than type annotations. I use it for method and parameter descriptions, deprecation notices, inline examples, etc even in TS files.


The only thing this will achieve is making accurate, reliable information harder to find once the garbage it generates gets ingested by the other models.


Tested it on a RX 7800XT on Chromium 142 (Windows) and it maintains 60fps up to ~6M nodes, very impressive.


Great! I pushed it to 120 million and my PC froze. There is diffing and culling but in this benchmark all nodes are drawn since they exist within screen bounds.


Every single time I try to use it for research or learning it ends up spitting subtly invalid code. Results range from imaginary APIs that don't exist to straight up invalid syntax, not to mention outdated info, contradictory reasoning and flat out wrong explanations.

Maybe spending $200/mo or whatever to access the top-of-the-line models will mitigate some of that, but I'd rather come up with the solution and gain the understanding myself, then spend the money on something worthwile.


They'll put it in the Mini when they push out a new Studio to upsell to.


Apple can save some memory by rewriting it as an Electron app.


This is amazingly bad at following instructions. It ignores most of the follow-up prompts, doesn't understand page structure semantics, and the generated results have really bad accessibility. It's almost like it spits out a couple of templates and then fails to customize them. Absolutely useless.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: