I hate to say it, but unless there’s a really well-funded foundation involved, Compiler Explorer and godbolt.org won’t last forever either. (Maybe by then all the info will have been distilled into the 487 quadrillion parameter model of everything…)
I hate to say it, but unless there’s a really well-funded foundation involved, Compiler Explorer and godbolt.org won’t last forever either. (Maybe by then all the info will have been distilled into the 487 quadrillion parameter model of everything…)
We've done alright so far: 13 years this week. I have funding for another year and change even assuming growth and all our current sponsors pull out.
I /am/ thinking about a foundation or similar though: the single point of failure is not funding but "me".
Well, that's true, but at least now compiler explorer links will stop working when compiler explorer vanishes, but not before that.
I think the most valuable long-living compiler explorer links are in bug reports. I like to link to compiler explorer in bug reports for convenience, but I also include the code in the report itself, and specify what compiler I used with what version to reproduce the bug. I don't expect compiler explorer to vanish anytime soon, but making bug reports self-contained like this protects against that.
Thanks to the no-hiding theorem, the information will live forever. ;)