Live data from Hacker News

NASA can't figure out what's causing computer issues on the Hubble telescope

npr.org

331–333 of 333 posts

Re: NASA can't figure out what's causing computer issues on the Hubble telescope

#331

Earlier quoted context omitted.

> while your "average" Lisp might be unsuitable for hard real-time applications (due to the presence of a garbage collector, usually without the hard real-time constraints that you can get out of garbage collectors with extreme effort), I wonder if they have some equivalently interactive system on-board the while your "average" Lisp might be unsuitable for hard real-time applications (due to the presence of a garbage…

As long as there aren't cycles of course you can do deterministic GC, it's just reference counting. It also helps if the program is single-threaded since otherwise any memory allocation/freeing can be unpredictable (since it probably locks.)

I've seen Prescheme (a subset of Scheme used to bootstrap a full-fledged dialect of Scheme) that seems to allow only stack-based allocation and therefore forbids certain types of closures that cannot be reduced via hoisting at compile time.[0]

Lisp with ref counting (assuming acyclic references) instead of GC could also be interesting to try to hack together. I have a feeling closures would be a particularly quick way to get reference cycles, so some concept of weak references may be necessary.

[0] https://thintz.com/resources/prescheme-documentation

Re: NASA can't figure out what's causing computer issues on the Hubble telescope

#332

Earlier quoted context omitted.

It's more than annoying. It comes part and parcel with the dumbing down of society.

Most of my work could benefit from a journalist > Overworked Engineer misses semicolon. All night review session finds it, data gets loaded! > Management insists Jira stories be routed to new Epic. Team Lead spends hours learning Jira API before giving up and doing it "the hard way"

> Management insists Jira stories be routed to new Epic.

Agile expert called in, who saves the day(night?)...

Re: NASA can't figure out what's causing computer issues on the Hubble telescope

#333
post #262
post #218

Earlier quoted context omitted.

Then maybe lookup "stack overflow" in rust, and you will be delighted. https://github.com/rust-lang/rust/issues?q=is%3Aissue+is%3Ao... 583 closed, 156 open. That much to "memory safety" in rust.

I'm not sure you understand what "memory safety" means.

Ok, teach me about https://github.com/rust-lang/rust/issues/82457 then. Unchecked alloca() calls have a pretty bad reputation with non-rust folks. But this is the preferred allocation scheme in Rust. I'm sure our understanding of memory safety is incompatible
Post reply on HN