pstoll

7 ms·

31.
by pstoll 1y ago
I’d argue we aren’t solving those inverse kinematics / kinetics via “number crunching” - but rather that our neuromuscular systems are analog. Which I don’t usually call that “number crunching” in the sense current computers … compute.
32.
by pstoll 1y ago
> I can practically see it playing out now: there is some huge incident of some kind, in some system or service with an MCP component somewhere, with some elaborate post-mortem revealing that some MCP server somewhere screwed up Already
33.
by pstoll 1y ago
> Falling back to CPU only Patient: “Doctor, it hurts when I do this.” Doctor: “don’t do that”
34.
by pstoll 1y ago
The other thing is that Microsoft does not own the copyright for any of the code they used. Facing their work on code they don’t own the copyright to is incredibly messy from an IP point of view. It’s why con contributor licenses agreements
35.
by pstoll 2y ago
Please tell me you are at least aware that tremor exists and that you rebuilt it on purpose? https://www.tremor.rs/
36.
by pstoll 2y ago
> lol who is interested in this on hn? I’m guessing lots of people who are on HN. I’ll go with - me for one. Guessing I’m not alone. Remember - it’s a big world. Lots of POVs.
37.
by pstoll 2y ago
It was and always will be timsort-ly yours. iykyk.
38.
by pstoll 2y ago
Per second. Messages in the Kafka sense not the WhatsApp sense.
39.
by pstoll 2y ago
Meta (we) process many billions of messages per second. Finding enough randomness is a thing at scale.
40.
by pstoll 2y ago
Ah the "erlang = distributed" thing. The primitives of sending messages across a "cluster" are built in the language, yep. And lightweight processes with a per-process garbage collector is magic on minimizing global gc p
41.
by pstoll 2y ago
When a sample showing a new SQL thing has eg a) no id types eg for User, just a string b) uses i64 for “stars” C) any other of a million things… I quickly conclude it’s likely a cute toy by someone who wanted to write a thing, not ever lik
42.
by pstoll 2y ago
Yep - i thought / hoped / assumed it was about Optimizers aka Sat solvers, etc A la https://github.com/google/or-tools
43.
by pstoll 2y ago
Also +1 for cromulent use of “cromulent”.
44.
by pstoll 2y ago
Having debugged my share of autoconf setups..I assumed it had to be a new M4 and not the ancient quirky GNU M4 thing because no one in their right mind would wish M4 (and related GNU autoconfig / autconf) on any other sentient beings
45.
by pstoll 2y ago
It’s a question of risk. Full disk encryption targets a different threat model - disk encryption protects against someone grabbing your computer. Writing into an encrypted blob on disk adds a layer of protection against bad actors exfiltrat
46.
by pstoll 2y ago
Came here to mention Malloy. Which is from the team that built Looker, which Google acquired. The Looker CTO founder then started (joined?) Malloy. And … he recently 6mo ago moved from Google to Meta. https://www.linkedin.com&#x2
47.
by pstoll 2y ago
I also wonder what the perf overhead will be for programs that only need i32. I didn’t dig deep enough on the implementation, but these type of variadic runtime options often cause perf regressions because of all the “ifs” / lookups of
48.
by pstoll 2y ago
If it ends up living up to the promise of the quality of the documentation (ie the README), I can’t wait to try it. Also screenshots of the display look cool.
49.
by pstoll 2y ago
> The work would be a multi-person-year effort, requiring concomitant funding. > It is not clear to me how this work might begin. To me that screams for - develop interest in a US public sector (aka government) funding agency and star
50.
by pstoll 3y ago
I get where they are coming from though. If the people building the product view building and using it as a chore, it’s going to show. So I took “love” as their brand of Amazonian “customer obsession”. There needs to be someone (often a f
51.
by pstoll 3y ago
The classic “big reveal” style of communication - hiding the important thing until half way through. Don’t bury the lede! It confuses and distracts the reader who is looking for how to frame and read everything else. “SLC = simple, lovable,
52.
by pstoll 3y ago
That cpu implementation is screaming for a cython implementation with all that bit twiddling. Would love to find a spare weekend.
53.
by pstoll 3y ago
Yep I know. It was easier to do in the same window with the program in the foreground vs opening another window to send the kill -HUP to this one. Double control-c still killed the process.
54.
by pstoll 3y ago
Random aside - I know formatting discussions border on the religious (and why something like gofmt is the only correct answer & yet I am also good with spaces for Python) but.. Did anyone else look at the code and ask themselves- what i
55.
by pstoll 3y ago
Cute, clever. There may be edge cases it doesn’t get right (parallel downloads/copies) but pretty useful when you’ve launched a job and didn’t think ahead of time to ask for progress. I’ve used a signal handler (SIGHUP aka control-c) b
56.
by pstoll 3y ago
It is the copy editors one ought to excoriate. If they still have any.
57.
by pstoll 3y ago
Neat. But I suggest moving the summary to the top. There is a reason summaries / tldr are at the top. They help your reader understand / digest all the details that follow.
58.
by pstoll 3y ago
Have you ever operated a fleet of critical JVM instances and needed more memory? Don’t go over 32GB ram in an instance or the operating characteristics of you entire app change. Compressed memory pointers - oops. They are a blast to debug &
59.
by pstoll 4y ago
Not paying too close attention, but this sounds a lot like the Gabor filter stacking from days of yore. Ah looks like people are still looking at them. https://bihy.medium.com/improving-convolutional-neural-netwo...
60.
by pstoll 4y ago
You mean the “contributing” part of OSS?

More ›