raoulj

How do you block users? Could be an interesting app to scrape HN and write some criteria to measure per-user SNR to then block

On this thread and similar, I'm noticing that some strong opinions about $LLM_PROVIDER are coming from accounts without much post history. With so much on the line, and the way that HN can influence developer behavior, I wonder what ways we can responsibly consume opinions in a thread like this.

Not to cast too much criticism. HN is extremely well-moderated (thanks team!). But think we-developers need to be very wary.

I like using atuin[1] but the capture mechanism here's pretty convenient! Cool idea. May give it a try

[1] https://atuin.sh/

For buying alcohol, I wonder if faceID will also somehow be required to verify the holder of the phone corresponds to the digital id

Is there any distributed polars for non Polars Cloud?

EDIT: nevermind see same question in this thread. The answer is no!

Counterpoint - the benefits of wireless are there but the worry of your unit dying in the middle of a ride now replaces the concern of whether your derailleur is tuned and ready to go. It's easy for a shop to assemble, but now I'm worried about shorting the control unit of my di2 which would be a pricey fix. I have two bikes: one with and one without di2. Both work just as well and one costs much more.

I do love disc brakes though.

Duckdb cannot plot on its own. You would need to bring in matplotlib or some alternative.

https://archive.is/0OXeJ

Is figure 4's legend correct from the NTU link? It would seem that the grey is the top 1%, not bottom 50%.

Flipped through the language overview on the website and noticed that matrices are limited in how large they can be because they're stack allocated [1]. Ergonomics of the language otherwise look solid but for my use case that would be fairly constraining

[1] https://odin-lang.org/docs/overview/#technical-information-o...

Seeing that too. Will change the title to: "United Healthcare Shooter Unconfirmed Manifesto"

Can change the link to the shooter's personal site: https://pepmangione.com/manifesto/

Yeah. It's too slow. Editable installs make application development much faster.

Can't give them too much credit ;) the task of counting r's in Strawberry was mentioned elsewhere as a "surprising" failure of LLMs

See previous thread: https://news.ycombinator.com/item?id=41058318

Goodbye, Jake. Thank you for your generosity in sharing your struggles, even now as it comes to its end. As a 20-something young man with hopefully many years ahead of me, your posts have encouraged me to live better, love more, and have more appreciation. Take it as some consolation that I and many others will read and reread your writings long after you're gone.

Bess and Athena and all your loved ones are in the intentions of my heart.

I've done this where I use python's ctypes library to write tests for a c codebase. This feels very similar in that it can be tricky to get the type interop correct the first time around. What other strategies/solutions do people like to use for testing their c projects?

In the defense of the SciPy response, while there may be some programming language zealotry behind the position, it seems to be from a lack of expertise in SciPy to maintain its Fortran code that's pushing SciPy to avoid new Fortran additions. Hopefully OP gets PRIMA through! Been admiring this effort, Dr. Zhang.

What is the reason to not have a central package index? I find that having one speeds up my development significantly. Is there more reason than decentralization?

Congrats to the team! Excited to see the community in full force. Looking forward to sending some PR’s your way :)

The biggest issue I can see with this approach is what happens if I’ve made a typo which changes the phonetics of the search input so that it gets excluded by the soundex prefilter, eg typing “Harrinbton” instead of “Harrington”

It doesn't look like it (from what I gather about `use-immer`). What's being suggested is updating React state via a mutable API on the data value itself. `use-immer` wraps the useState/useReducer functional updaters with a call to immer, whereas `use-structure` suggests mutating the data, which is what every React-beginner instinctively tries to do when they first get started with React. Same idea of using Proxies as immer though.

This is really interesting! Great idea.

This could be too high level, but I stumbled onto the founder's (crawshaw) website and found one of his blog posts very helpful for understanding basic fundamentals of the product (i.e. Zero Trust networks and microsegmentation)

https://crawshaw.io/blog/zero-trust

As long as you stay away from the bridge and the packs of tourists, sure. But I quickly found myself wanting to over the bridge to get different/more challenging routes.

I swam competitively for 15 years, including 4 years of D1 swimming, but I come from a family of rowers.

The effect of limited breathing in swimming forced the body to adapt. One Thanksgiving, my father (a former international-level rower), my brother (a currently international-level rower), and I found our way into a pack of balloons. We wanted to see who could inflate the largest balloon off of a single breath. Once we had breathed our hardest, got out the measuring tape, and argued about the best way to measure it at length, we found that I had won.

My brother and my dad are both around 8 inches taller and 50 pounds more than myself — much bigger people. But they didn’t have to hold their breath for hours every day :)

Obviously this is a poor man’s proxy to a VO2MAX assessment, which I’m sure they would win. But lung volume is certainly one of a swimmer’s greatest assets.

It has not, but they say that it's on their near-term roadmap.

While well-intentioned, Germany certainly does not.

I do this too.

Disclosure: I work for Streak.

You can major in humanities at MIT, albeit it's somewhat uncommon.

What mailing list? Would be interested to join!

Maybe it's just me, but while I find the graphics informative on the landing page, I wonder if they could be made to be more easily understandable.