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

This isn't directly related to a school ban, but I can share another anecdote that reinforces your kids' thoughts. I'm a parent of 17 & 15 year olds and regularly (3-4x/yr) chaperone my 15yo daughter's soccer team to regional and national events. It's typically two vanloads of girls -- 18-24 kids -- and up until about three events back we let them have phones until lights out. As expected, if they weren't competing, they were on their phones. We instituted a revised policy last year where we take phones at 9pm (lights out at 10pm) and give them back after breakfast. It's made a world of difference in the camaraderie that's developed, since the girls now have to actually talk with each other. It's also led to improved travel maturity overall, and much more pleasant van rides [with only silent phone use allowed -- typically locked in with their personal pre-match music]. 10/10 do recommend.

I truly do not understand such a strong reaction. Maybe it's because I'm old, or maybe just generally well-rounded, but I had no trouble reading this at all. Moreover, it was engaging and the mystery is intriguing, and now I'm curious about it, too. Heck, the author even included a small glossary at the end.

I pay for Ultra and have been using Argon for a couple weeks. I just checked in both Agy and Gemini and Carbon is there for me now, too. I'll try it, but Argon is itself already so slow that I'm not sure Carbon will make sense for most activities.

On pro here and I can do about 2 design tasks a week before I hit usage limits with Argon. The usage limit with carbon is probably gone just loading the context.

I've been using Argon (Medium) pretty heavily the past couple of weeks to create a website and an app and am not coming close to my Ultra limits. I've used High for a couple of code reviews and security audits.

I'm not sure if I'm a sucker for paying $100/mo for this, and Google's harnesses are so underwhelming compared to Claude Code, but I'm not having a bad experience. Compared to the beginning of the year when Antigravity was almost unusable and Gemini Pro 3.1 was noticeably behind other options.


> Google's harnesses are so underwhelming compared to Claude Code,

Could you please elaborate? A heavy user of Antigravity myself I had the opposite impression. Quite possibly I only scratched the surface of what Claude has to offer. For example how would you compare `/remote-control`? Would you say you prefer the Claude version ?


Have you tried running antigravity without?

  agy --dangerously-skip-permissions
Claude Code auto-mode works fine, no need for yolo mode.

Yes I run Antigravity without. Note that AGY auto mode is disabled by default. If you find it asks unreasonably often that's most likely the issue.

(It could also be that the classifier has a higher rate of false positives. Please let me know if that's what you meant. This tricky to reason about though, because eg users won't typically complain about the false negatives.)


Argon is slow but surprisingly my progress is noticeably faster. If you aren’t prompting extra ambitiously with top tier models, you should probably just use deep seek.

Not quite at the build me a whole app level but you need to definitely zoom out a few times and prompt from either a feature set or many overlapping details at once.


Yep, I'm on Pro as well, and Argon been hugely useful, but I get about 10 prompts with it a week. And that means that I have to use 3.8 flash for most of what I'm doing, which is obviously not a great experience for any kind of long horizon tasks.

I had a similar experience yesterday with Argon (in Antigravity), but unfortunately it didn't come up until I explicitly asked it for a security audit. It had previously stored a secret API key in plain text [because it thought it made local testing easier], and didn't warn me before I'd committed to GitHub and deployed to Vercel. So, 50/50 but I've still added a note in a skill file to never do this again.

HN reached it's Eternal September[1] a while back (probably ~2yrs ago).

https://en.wikipedia.org/wiki/Eternal_September


This is why ClusterMax (from Semianalysis) was created. Not all hosts are the same, even with the same GPUs.

https://newsletter.semianalysis.com/p/clustermax-30-the-indu...


Oh nice, did not know about this.

Looking at the report, I didn't even know one could use CoreWeave without an enterprise account, seems it could be cheaper per hour than the same cards elsewhere. Might have saved me a few hundred bucks, thanks!


I didn't know you could buy pieces at Fred Meyer, but I am also in the US and was 12 when the wall came down. I, too, have a piece (with graffiti!). It was a gift and I don't know where it came from, but my impression at that time was that it wasn't really much rarer than pumice from the Mt St Helens eruption (I have a piece of that, too, or a capsule of oil from the Prudhoe Bay disaster, which I also have in my collection from that era).

I would suggest there are 4 kinds:

1. People who need them for work. 2. People who need to carry bulky loads 3. People who need to tow. 4. People who buy them for some form of self-expression.

The only real use case for electric trucks, imho, is construction site supervisors who do most around-town driving but may occasionally need to haul stuff. Their towing range is absolutely abysmal (F150 Lightning range dropped to about 90 miles when towing a moderate trailer!).


Every contractor in my area has one and raves about it. Plumbers, electricians, framing guys, concrete guys.

They have a rack or canopy on the back, tow modestly and drive a few hundred km a day at most to and from the job site, the supply store, etc.

Every single one says they slashed their fuel bill by at least half, and they’re staggered how good they are.


Not just construction site supervisors, but the actual workers also do around-town driving. Range is a nonissue for them. Driving from your home to the supply store to the customer site and back does not usually require 90 miles of driving.

Heck, my experience lately has been that recruiters (or independent headhunters) are completely up front with the salary range explicitly because they don't want to waste anyone's time... and because there -- in tech especially -- can be enormous ranges of compensation for similar responsibilities.

That matches my experience - and I'd treat a failure to give a straightforward answer as a strongly negative signal, and would immediately concentrate my efforts on other opportunities.

I suspect we're pretty lucky in tech, though. Anecdotally, I've heard that in fields such as sales and marketing it's much more the norm to treat potential new hires in a much more adversarial manner.


It's a bureaucratic problem. Getting a headcount approved for a specific role is a non-issue. Getting HC approved for something brand new might be impressively complicated. Especially at large companies, listed postings persist for many months sometimes and stagnate because functions, dynamics or org alignment shifts before anyone is hired. It's much easier to write a generic-ish job posting and just coach the recruiter/screener on updated specifics than it is to retract a posting, rewrite it, and repost it. This happened to me frequently when I was a hiring manager at Google, for example.

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

Search: