https://www.patagonia.com/stories/culture/design/on-tumpline...

What really took it to the next level for me were adding chord mappings. For example I can hold right mouse button + scroll the thumb wheel to adjust volume. So convenient!

In the early days I feel it was more apparent. You would frequently see the model making failed tool calls etc.. but now that feels so rare. I'm not confident I can perceive whatever shortcomings of the harness remain.

Comments URL: https://news.ycombinator.com/item?id=49264348

Points: 1

# Comments: 0

Agents need clean/current context from the web, and this is the best way I’ve found to give it to them. The internet is clearly moving in this direction: companies are starting to realize their sites need to be legible to agents. Some are already adapting but many haven’t yet. Context feels like an important part of that transition

Yahia is a great builder. His pace of expansion has been impressive, excited to see where he takes Context.

One of the core ideas is that later climbers should respect or improve upon the style of the first ascensionist. e.g. if a climb was first done using siege tactics, then doing it in a single day is celebrated. But making a climb easier or safer after the fact is much more controversial, because it can feel like changing the nature of the route itself.

Snake Dike is a good example that’s flared up recently in the climbing world. It’s a classic, relatively easy route up Half Dome, and many climbers free solo it. But because it’s a face climb, protection mostly comes from bolts drilled into the rock. The first ascensionist placed very few bolts, which left long runouts and real consequences if you fall.

To many old school climbers, adding bolts to Snake Dike is disrespectful because the risk is part of the route’s character. Their view is basically: don’t bring the mountain down to your level. The new generation of climbers don’t seem to feel that way at all - they think you shouldn’t have to take unnecessary risk to climb a classic route.

https://gripped.com/news/first-ascentionist-pushes-back-on-h...

The biggest pain point I've had is that both tools will try to guess the API of a crate instead of referencing the documentation. I've tried adding an MCP for this but have had mixed results.

https://github.com/d6e/cratedocs-mcp

Comments URL: https://news.ycombinator.com/item?id=39708404

Points: 1

# Comments: 0

One small feedback- the motion design is waaay too much. You should consider dialing it back 2-3x.

Regardless, need to see more benchmarks to better understand its true performance. If it holds up it would be a big win for time forecasting.

[1] https://www.youtube.com/watch?v=n7luRRyxLoQ

LingQ's killer feature for me is that as you click on words (or phrases - which I find really helpful btw) to translate them, they are added to your vocabulary list. It will automatically create flashcards for you from this list for SRS. Plus when you're reading a new story, words that are in your vocab list are highlighted yellow and new words are highlighted blue.

Some companies have made headway in eyewear and shoes (https://www.amazon.com/b?node=23595320011). Clothing is much more difficult - a lot of variety in body shape to accommodate.