privong
Janus (reversible computing programming language)
Isn't this what people said pre-Snowden? Not that NSA spying is the same as corporate "surveillance capitalism", but if companies can make more money off it and the technology exists, it seems prudent to assume companies are trying it.
Juno to Establish Virtual Supercomputer Network (2001)
Agentic Research Is Oxymoronic
> Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.
Racket v9.3
NSF, National Radio Astro Obs, and U.S. Naval Obs Partner on NgVLA Pathfinder
One would need to put the telescopes into fairly high orbits in order to avoid the interference. I think that even images made with the Hubble space telescope have sometimes seen the impact of satellite constellations.
Radioastron required cross-correlating the signal with ground-based radio teleacopes in order to do science. The collecting area, dish distributons, etc. would need to be fully replicated in space if one wanted to avoid using ground-based facilities entirely.
1. many astronomical observations are long integrations (many minutes of open shutter) and you often cannot read out the pixels during the exposure. So you can't selectively ignore pixels on a "by moment" basis. And with enough satellites, enough pixels could be affected to render an entire image effectively unusable
2. It seems you're thinking only about optical astronomy. There's also a ton of radio/millimeter wave astronomy that's done from the ground. Satellites have radio-wave downlinks that can be powerful enough to destroy the electronics used in radio astronomy receivers. The US's National Radio Astronomy Observatory has been working on data sharing with Starlink to mitigate this, but it's basically up to companies to agree to work together. Other satellites / companies don't engage in this coordination and so some radio telescopes need to go to a "safe"/stow position to protect the electronics. This costs valuable observing time.
Simplify: Move Code into Database Functions
Email triage with an embedding-based classifier
I see this mentioned often, and it sounds amazingly useful (especially the part about fixing in production!). But how truly widespread is it among the Lisp dialects to be able to connect to a running program, debug, and hotfix it? I understand Common Lisp has it, but I struggled to figure out how to do it in, say, Racket. Admittedly I'm am relatively inexperienced Lisp programmer, so maybe I wasn't looking in the right place or for the right words. Which Lisp dialects do indeed support the extreme version of this capability to inspect and edit running programs?
Can you elaborate on the assertion you made here? In addition to the important points @elbasti made about tests performed approximately a century ago, what does it even mean for a scientific theory to be "fully backed up"? Such theories can be tested and the tests either passed or the theory disproven but it's not possible to _prove_ such a theory. And to some extent we already know that relativity cannot be the final answer because it doesn't mesh well with quantum mechanics (which has been experimentally tested substantially, arguably even more than relativity has).
One would need to go to space for that of course.
In addition to what @tokai said, I think it's also important to keep in mind that before Open Access the journal publishers charged subscription fees. The subscription fees were paid by universities and that was also likely largely taxpayer funded (e.g., using money from overheads charged to grants).
github repo: https://github.com/lexi-lambda/hackett
Documentation: https://lexi-lambda.github.io/hackett/