Hacker Timesnew | past | comments | ask | show | jobs | submit | nhinck2's commentslogin

Yeah probably, the outlook for their kids ain't looking so great.

You read that line wrong.

That's an exceptionally fast output you have there...

Mind showing your working out?


Lotr ~1.4k pages 1 page ~1k tok -> ~700k tok 1tok ~0.5J -> 350kJ ~100Wh ~1 cup of tea

Well, one person moved and then brought a bunch of people with them.


Good point.


It's also important to note that it beat doctors in diagnosing in a way doctors do not diagnose.


> a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code

Literally who?


I could easily see companies, especially enterprise-level companies, expect code that was generated with AI to have some level of ownership attributed to that AI. Whether a simple "Co-Authored-by Copilot" byline on the commit is the right way to do that is another question though.


Correct, this was the ask.


And thank you for this. In my professional setting, this is a very valuable addition -- provided it works correctly, of course ;-).

Now if we could also have comments inside the code ("BEGIN/END snippet by Copilot"), that would also be great!


No one, which is why he refuses to reply further to any of these inquiries.


I don't refuse - what would you like to ask?


they do, at least to some degree, but their comments are dead. You'll see them if you turn on show-dead somewhere


Can you just add power from the front and rear wheels like that?


I don't see why not, it's all contributing to acceleration, although it's going to be rough on the tyres.


And hey, even fairly modest EVs are rough on tyres, so no one is going to mind that tradeoff if they are looking for sporty acceleration


I think the tyre problem is not really a thing. EVs use synchronized motors and traction control to avoid extra wear due to uneven torque during normal driving.


I can't remember if it was here or on reddit, but I read from a tyre shop / mechanic, that some EV users replace their tyres very often, because EV cars make it easy to drive very aggressive.


And others don't. We replaced our EV tires at about 80 000 km.


The increased weight due to the battery is the bigger issue for wear on tires. A lot of EVs weigh a good 500kg more than their ICE counterparts.


I think bigger issue is torque. EVs have lot more torque and it is easier to use, so they can slip more often which then leads to wear.


My understanding is that the torque control speed is much faster though, so it's actually difficult to get the tires to slip. I can't screech my tires in my EV, but it'll do 0-60 ridiculously fast.


Anecdotally, my Kia Niro EV goes through tyres a lot faster than the two equivalent internal combustion vehicles in the family.

That said, the Niro weighs ~50% more than the other vehicles, and it has significantly higher acceleration/braking, so I'd hazard it gets driven harder on average.


Yeah, "we're going to remove copilot" only to remove the literally word copilot


And as the person who raised the issue said

> The frustrating part is that it's not a workflow _or_ model issue, but a silently-introduced limitation of the subscription plan. They switched thinking to be variable by load, redacted the thinking so no one could notice, and then have been running it at ~1/10th the thinking depth nearly 24/7 for a month. That's with max effort on, adaptive thinking disabled, high max thinking tokens, etc etc.

So Boris' explanation isn't really an explanation.


> ~1/10th the thinking depth

While simultaneously drastically reducing the amount of work you can get done even at $200 a month. I've cancelled my subscription, it's not worth it anymore.


“So squeeze, Rabban. Squeeze hard.”


Also taking a dirty foggy environment and sanitising it.


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

Search: