The one thing to criticise about steam (and that they’re slowly, but surely, losing a EU court case over) is inability for customers to sell their games.

Their marketshare is organic, based on being the choice of store both from the customer and developer POV. As a customer you get the usual painless returns, great interface, community features and whatnot, as a developer you get plenty of store features which make life and customer acquisition and gamedev a lot easier (things like playtesting, next fests) and most of all you get customers because steam has lots of customers and a real, I mean real good, recommendation algorithm. Sure, Epic wants a smaller cut but you’re also not going to sell much, there, which is why they had to lure devs in with advances, guaranteed sales, etc. Larger publisher might not like steam so much because they have gigantic marketing budgets in the first place so all the discoverability/recommendation stuff is not as relevant but, well, fuck EA, Ubi, etc IDGAF, I don’t want to hear it, cry silently.

As to the “can’t sell games for lower prices elsewhere” myth: That applies to when you’re selling steam keys in places that are not steam. Which is fair, if you’re selling steam keys then that’s incurring costs for them (if nothing else, bandwidth) and they don’t even get their usual cut when you sell a steam key off-steam, least you can do is not undercut them.

Oracle is not a tech company it’s a racket run by an army of lawyers. Obligatory link to Bryan Cantrill’s talk.

I’m not enough into that industry to actually give a good estimate, here, but the amount of COBOL systems still up and running is certainly not even close to non-zero, and it’s going to stay that way for a while. From what I gather for companies moving away from COBOL is more of a “programmers are hard to find” situation, not “these systems absolutely must be replaced” one. It’s well-supported and scaled with their business, as in, in places they’re running the same 60 year old code on new mainframes because if there’s one thing that IBM mainframes are then it’s excessively backwards-compatible.

As far as the language is concerned: It’s not hard, it’s just weird, dating back from an age where people thought randomly calling things “divisions” would make businesspeople capable coders. The reason I’m not in that space isn’t because of the language but because of the type of software you write there, it’s all bookkeeping and representing business procedures, as said: Bureaucracy.

Also I’m not sure what “modernising” actually meant, there: SEPA instant payment was introduced, meaning that mainframes won’t batch up the day’s transactions and then talk to each other every night so cross-bank transfers took a day to process, now they’re doing it in ten seconds. Most banks already supported instant transfers within their own systems so they should only have had to rewrite the external interface as the rest was already up to the task.

I mean yes but no. Back at some old job all the devs had the local admin password so we could do things like install drivers for bluetooth dongles on our own (I said “old job”, didn’t I) and usually everything was fine but at some point my machine just barfed, it would neither install nor uninstall drivers. I called an admin because I have no idea about windows internals. They were ecstatic, finally, an actual problem, and not walking someone in marketing through how to write an email. Some arcane regedit magic later the problem was solved, and yes I had layout switching ready on the taskbar.

COBOL is the career advise you hear people give for people who want to make money but don’t want to deal with the VC clownshow. COBOL btw is only 13 years older than C and both language’s current standard dates to 2023.

It’s at its core a bog-standard procedural language, with some special builtins making it particularly suited to do mainframe stuff. Learning COBOL is no worse a career investment than learning ABAP, or any other language of the bureaucracy. Sure you’ll be a career bureaucrat but that’s up sufficiently many people’s alley, no “move fast and break things”, it’s “move slowly and keep things running”.