this post was submitted on 30 Jan 2024
578 points (98.0% liked)
Technology
60112 readers
2096 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
We're maintaining and developing OpenVMS OS, and both we and our customers need Cobol, Fortran, and other half-dead languages coders.
Many large companies maintain their old systems and use them for production or data processing purposes. Sometimes it's too expensive to migrate off, but im many cases "it just works"
I'm a COBOL developer. For old COBOL systems it's not just a case of it being expensive to "migrate away", it's extremely risky and for no significant benefit.
Businesses have essentially two options, modernize what they already have, or tear everything apart and start from scratch. COBOL programs don't "just work", they're good at what they need to do (business transactions). Therefore, there isn't a significant need to rewrite everything, especially when it's possible to modernize and reuse existing business logic contained within COBOL programs. For example, COBOL programs aren't tied to old hardware, you can run your COBOL applications on the cloud instead. This is much safer and cheaper than rewriting everything.
I work primarily in a Long Tail language (languages don't die, but they have a long tail where usage slowly creeps away). I tell the business that we could ultimately solve all the problems with the platform except for one: finding new programmers to hire for it. That's what will ultimately force us to migrate. Doesn't have anything to do with cost or ability to take on new features or handle new ways of doing things.
When it comes to COBOL developers, there are a lot of developers retiring but there are also a lot of programmers being trained in COBOL every year. It's for this reason that the average age of COBOL developers has stayed roughly the same for the past 2 decades despite retirements. But that said the total number of COBOL developers is decreasing.
It is certainly an issue. Not many young programmers want to learn COBOL. COBOL isn't taught in many educational institutions. There are very few online resources that programmers can use to self-teach COBOL. More often than not people are trained in COBOL by their employer. I didn't know how to program in COBOL until I started at my current company (and even then I stumbled into this position accidentally because I wasn't aware that junior developer jobs in COBOL existed when I graduated university).
It's a shame.
I feel this way about mainframes sometimes too, I had a class in mainframes but we weren't really taught about job options or where they still fit in the industry.
Isn't pretty much all airport scheduling based off software from the 80s or something?
Edit: Found a video about it.
Why change what isn't broken, right?
I've worked in that area. It was broken back in the 90s and I doubt the crusty old parts of the system have gotten any better. I was tasked with writing a more modern wrapper for part of the legacy system, and when I asked for documentation I was told they had literally nothing to give me.
I was just an intern at the time so maybe someone with more clout could have gotten sometime to dig in a forgotten closet for old technical docs, but it still strikes me as a very bad sign when technical docs for a system every agent uses all day every day aren't immediately available on the company's intranet.
That's the thing though, it is.
Here is an alternative Piped link(s):
it is.
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
Probably! APOLLO and SABRE and stuff look ancient.
I know for sure several airports are using OpenVMS, and there are more we don't know about, as some companies keep running yheir stuff for decades not asking anyone for support.
And I'm sure There are multiple other old systems out there, it's too hard to replace them.
And they work! Our VMS stuff runs great, it's fast, and the uptime is measured in decades sometimes. So the problem is hardware: we rolled out the first production x86 version this year, so our users are fine (it's still an issue of porting your software, but it's not as terrible as building everything from scratch), but before that OpenVMS could run on Itanium servers at latest, and the platform was dying off since the beginning of 2000s, so it is a problem to find a normal replacement machine now.
And in many cases if it gets replaced it's for a system that looks fancier but actually has more problems than the original... See Phoenix for the Canadian government employees pay.
I've seen those postings and some executive is living in dreamland thinking they can hire someone to do that for $25/hr.
My bosses tried to ask me if I knew anyone the could hire for a full time position at a hospital. I ask for more details and eventually they relent because they aren't having any luck on indeed/craigslist/temp recruiter.
It's a 24 hour on call position for 'up to' $55,000 to be the sole IT staff for a 100 bed hospital in upstate NY.
I literally laughed at them, but they seem to insist they are gonna find someone to take the job.
I actually think the job isn't even legal as described.
Hahahaha, what a joke.
Sorry, not interested in 24hr on call until they start talking $100k+. That's asking a lot of someone.
Sounds like they need multiple staff, actually. You can't do on-call without having a rotation. What happens if Bob gets hit by a bus? This tells me all I need to know about them. Typical SMB "leadership", they lack any concept of managing systems - be it IT, finance, mechanical, whatever. All systems have their management models.
Fucking delusional pricks.
With those requirements I would expect $500k with 6 weeks paid leave. What a bunch of clowns.
You mean I can use my decades of Fortran knowledge somewhere?! If I could get a wfh position in about 3 years, that'd be awesome.
If you actually do have decades of fortran experience, work for NOAA. Their weather models are mostly fortran and they need engineers. Specifically the NOAA EPIC contract that i worked on previously definitely needs people knowledgeable in fortran and was 100% work from home. Feel free to DM me if you want more details.
Visual Basic? (fingers crossed)
Oh, I'm sorry man. I don't know everything, I'm working there less than a year, but I only heard of VB a couple of times. In order of popularity it's like: C, C++, Java, then everything else
I was just kidding - I haven't touched Visual Basic in almost 20 years now. I'm not sure I could still code in it even if I wanted to.
Such things make me angry. LoL
It can be viewed as a success. A bridge or building that only lasts five years wouldn't be considered successful, especially if it took monumental effort to make it in the first place. For some reason, we don't value that in software.
I wrote a Classic ASP app in 1999 that placed a web UI atop a mainframe application that dated to the late '70s and allowed easy navigation of really enormous data structures. I learned last year that it's still in use at that company; amazing not just because my code is still around but because that fucking mainframe code is still running.