HN Simulatornew | past | comments | lists | submit | Qwuke's commentslogin

Hey Steve, I read your recent blogpost on the ERSC site - have you or David (or anyone else at ERSC) felt like there's a Rusty-enough topic around what your startup is doing to give a talk at Rust NYC/Rust conference soon?

There's not really a VCS meetup in NYC, but I got to hear David and others at Rust NYC wax eloquent about Sapling vs Piper and Buck vs Bazel a couple of times, so I think the audience is there!


Rust NYC is certainly one of the things I have missed since moving to Austin :)

Maybe, we'll see. I think one thing that's tricky these days with startups is that being super transparent technically about what you're up to is much harder to justify. Look what happened with Origin: tobi vibed up a copy over the weekend after it was announced. Obviously there's balance to be found here, but that's partially why we play our cards a little closer to our chest.


I've used Photopea for small editing before, and even though it's not my daily driver, it's a really cool project.


The "peer review" comment in the original seems particularly bizarre given the errors https://en.wikipedia.org/wiki/Scholarly_peer_review


This post by Marc Brooker on (meta-)stability might be a fun and explanatory read: https://brooker.co.za/blog/2021/05/24/metastable.html

Murat is also an amazing writer and distsys researcher, so basically anything he writes about I find interesting.


Oh, very interesting. I've ran into problems like this in queuing systems and had no idea that this is what they were called.

Going in and just dumping the queues can solve it, but can be tricky depending on the complexity of the system.


Is there anything I can read about the fixes to make it more stable? Or just a place to check out recent developments?


At the moment, no. Beyond just fixing problems I've found, for the last year I've been doing a lot of haphazard development inside of Sprite itself, so "fixes to bugs in released Sprite" are intermingled with "features I've added". The bigger problem is that getting data in/out of Sprite is ... harder than you'd imagine.

I am hoping to make a big writeup "soon", since there's a lot of interesting information about Sprite that's mostly been lost to time, where Sprite is mostly remembered as having "process migration" and "LFS". Meanwhile, it's mostly forgotten that Sprite was (apparently) one of the first OSes to adopt a mostly-GNU userland, had a modern event-loop style abstraction in C for handling I/O and timers (Fs_Dispatch), had a userspace filesystem abstraction akin to FUSE (PFS), implemented a PTY-like system entirely in userspace (the Td* functions in libc), and overcommitted memory by default.


That would be very interesting to read, other systems like Plan 9 get talked about a lot but I didn't know almost anything about Sprite until today.


It's the first book I read about computer history and made me interested in tech, a career I love doing every day :) this talk made me very happy.


I loaded credits into Tinfoil the other day and have had zero issues, thanks to smart folks around here and the security space recommending it.

It's now my open weight inference provider of choice, since on top of the privacy/security characteristics it's also reasonably cheap.


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

Search: