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

I prefer the casino.

What model are you using? Llama 3.1 8b? This has not been true for years.

Well, in another comment he said that LLMs haven't improved in 3 years. So this puts him at Llama 1 7B.

I hope I never have to work with you.

get back to API calling whip noises

Do you have an example of any company ever doing this?

No, but if you run this non judiciously and burn 100x the next guy with no output, maybe they would want to know how

It's primarily used by people who tend to sit on the cutting edge e.g. startups and developers who follow the latest tools. It's not well worn enough to be adopted by slower enterprise environments. Bun is well known within web development but if you don't work in the space and don't keep up to date with modern tooling it's unlikely you would have awareness of it.

It is not "absolutely" something that can lead to injury. Injury itself is difficult to define, and often the reason one experiences pain sensation is multifactorial. Within lifting contexts, generally the factor which has the strongest evidence for injury prediction is how sharply an athlete increases intensity compared to what they have previously adapted to.

No offense, but this post does come across as you only having a surface level understanding of the field. Especially surrounding injury/pain perception, I would be more careful of what you assume is true, there's far more nuance.


As someone who has been very deep down this rabbit hole and hacked together multiple path and velocity trackers over the years (specifically for olympic weightlifting), there is no extra information that tracking bar path will give you that simply looking at the video won't, and often just adds more clutter. You don't need to graph bar path to see that the bar is looping too far forward after hip contact in the snatch.

Velocity on the other hand is a great metric to track and is used as a proxy for RPE. Mike Tuchscherer was the first one to systematize it for powerlifting a while back, if you've been lifting for 20 years you're probably aware of the name.



Looking forward to finally getting HL3 /s


"our"?


In my opinion, the IDE interface still has not been beaten if you are working on a serious codebase where you are reviewing each diff.


I agree with you and I personally use Cursor. Just don’t see how there’s a moat that makes it worth $60b.

A team could build an AI IDE in a week, this could be a race to the bottom


As someone put in the unfortunate position of building an AI IDE in three weeks, I assure you it's much more difficult than it seems. Sure, we were able to get something working with all the features you would expect, but the performance was awful. Claude Code, Cursor, and others do a lot of tweaking based on a lot of experience in order to make their systems give good results. There is more to getting good results than just using a good model.


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

Search: