That’s what I was trying to say is they have everything they need mechanics-wise built into these game development environments. The difference between AAA and indie is more on the scope of how much artwork, sound design, writing, voice acting, Foley work, etc. goes into the game
A solo independent developer can pretty easily recreate the mechanics of GTA V in Unreal for example, but they can’t realistically recreate a selectively compressed representation of the entire LA and San Bernardino counties plus a 14 hour (or however long it is) single player campaign
To be fair, an indie dev just tossing stuff together on the weekends and evenings has everything needed in these accessible game engines to build a AAA title of 15+ years ago.
I think the saddest part was observing a clear wind down of Sims 4 then last second “lol JK we’re not releasing another sims game” and the entire player base seemed to release a collective sigh that some of the structural problems that have plugged TS4 are here to stay
This is my second season. I’m biking about 5 hours a week right now, averaging about 40-50 miles per week. I don’t know how obvious the toning would be to others but I can certainly see it, since y’know I’m the one who sees myself the most
I’ve been biking so much lately that my legs are getting hella toned, the rest of my body is starting to tone too and I’m feeling much more alive and healthy than I have at any other point in my life!
The big problems is outlook like every mail client from the early 2000s collected tons of features during the mail client wars where every client needed to do a billion different things, so now there’s dozens of random little features baked in that very few people use but those who do have built entire business processes around.
For example I observed while working at a bank that the backend finance people would use the voting feature to vote on whether to bundle certain loans together. I’ve never before or since seen anyone in any business actively use that feature. There’s lots of other little features and tunables buried deep in Outlook and it’s a royal pain as an IT person to quickly learn about whatever obscure feature a user is complaining stopped working and of course figure out what the intended workflow for the feature is to begin with before I can even start troubleshooting how to fix it
I can’t blame Microsoft for wanting to greenfield Outlook development to a new standard base that’s shared between webmail and the application, but holy crap the amount of technical debt Outlook accumulated is going to take ages to escape from.
Personally, I don’t mind Outlook (new). It sends and receives emails, it shows my Teams meetings on the calendar, and it lets me easily schedule calendar events and Teams meetings, which is all I really need. Most importantly it bypasses a ton of annoying quirks of Outlook (classic)'s license verification and M365 authentication so I generally encourage my users to use it if they don’t otherwise have a strong preference, because it saves me tickets (especially the dreaded “outlook lost teams integration” complaints where Outlook (classic) misplaced its own extension for communicating with Teams (new) and usually involves uninstalling all versions of Teams then installing Teams (Classic) and upgrading it in-place 3x to resolve)
Honestly Microsoft could’ve had a killer product with Access if they made an easier pipeline from Excel -> Access -> Win32 application/webpage with an SQL backend. Like there is some of that pipeline present, but if Microsoft actually followed that vision, created easy wizards for each step that your average office drone can complete and marketed the shit out of it, they could completely own business processes instead of a cottage industry of spreadsheets turned SAAS apps for every niche usecase that could’ve been handled by a common database frontend.
On the other hand, now we have a super easy jumping point for anyone in a large business who can program a little to spin up a new startup. Find a business process that’s currently a spreadsheet/on paper, write a database frontend to easily handle that then sell your solution to businesses looking to remove load bearing paperwork and spreadsheets