Heck you could even scrape + convert to static HTML like what they did with the original Processing forums. Which is run by volunteers.
I totally get your point and am pro non-deletion, but it really is way less work to just delete it all.
It's probably a month of work for anyone competent to produce a static version of ALL of the posts.
But f00kin'AYE on wget.
I can't say for certain (please pard0n) but if there was anyway to (ya, right) find we'd learn way back when 'AutoCad' was originaly built (and for) UNIX.
Because LISP (Lost In Stupid Parentheses) was an emacs dealio, Richard Stahlman stuff but I suspect even before Torvalds built Linux...
When 8086/88 machines went viral there was a (hardware) limit <640K (kb) RAM.
To escape this we used 'PharLap' to make a 16mb (megabytes) Ramdisk look like "REAL" to Autocad...
It'd be amusing to know how the UNIX app was ported to 8086/88 (before 'Windows' 3)
Why is that the very least? If keeping a forum running a full time job?
It's not a passion project, and that's why I find it very unlikely that they are not using some off-the-shelf forum software. I doubt Autodesk would be paying anything near a full software engineer salary for anyone working on the forum. Of course there will be some developer integrating the forum with the rest of their website, but that is hardly a full-time job. Moderation is probably also not done by engineers but by support staff that doesn't receive a salary at the level of an engineer.
Corporate cheapo strikes again.
It cost at the very least the salary of a software engineer, though most likely a lot more. Autodesk is not some passion project of a group of volunteers who just want to keep it up. At large companies, I have seen few models of how to run public facing legacy services that don’t “align” with the company any more and as a result there is very little interest in them. They are all expensive in terms of personal and always a potential PR disaster to manage. Doubly so if it’s something that requires moderation like a forum.
You have the “there is a dedicated team for ‘legacy stuff’. They just inherit all dead end projects in the company”. If you are gonna have that model, that teams scope is ever growing, and so is their size. It’s not a shiny job either. “I maintain projects no one cares about” is not interesting or shiny and most good people will move to something else.
There is also the “since you started it, you own it now” approach. Where the virtual team that started a service, will sort of own it forever. It’s this thing that just hover over a team’s shoulder forever. Though “forever” usually means until a manager comes along who is loud enough about not wanting to deal with that shit anymore. It only causes issues when things go down, break, need updating, etc and they don’t want to work on that anymore.
There is the “the ownership of this random ass service will fall wherever we randomly draw and redraw random organizational lines. It’ll keep forever bouncing between random teams as no one cares about it, and no one wants it, and everyone argues that “it actually belong in fabric because it’s the only remaining consumer of their v2 APIs”, “fabric thinks this is more business layer because its main audience are end customers”, “business unit thinks it’s actually more UX as it’s running on the same domain”
And there is always the looming PR issue when an eventual issue happens, a ton of infighting over the lack of clear ownership and once they are over that, the person who has to fix it has no idea what this thing is and needs to get up to speed. Then you get a post on top of HN or Reddit or twitter etc saying “{Insert multimillion/billion dollar company random service} has been down for a week” and a lot of people like “seriously, they can’t figure out how to run that? I run one just for my ham group and it never goes down”
Why bother is usually the final approach.