[apercu]

Man, I started building websites and doing CGI coding in 1994 and 1995, which makes me a very early web developer and I don't remember this time at all.

In fact, I stopped coding as a job when it became expected that I would do back end database & business logic stuff AND fiddle with front-end code to make it work/look the same in 3 very different browsers, and update the code each time (I'm looking at you Microsoft) a browser vendor would do something stoopid.

[agedclock]

I am talking about the 2005-2015 era of web development.

[apercu]

Ah. I was managing teams of developers by then, and most of them had some front end skills, but we still needed dedicated people to deal with... I almost said "edge cases" but since they impacted every single project I guess they were not "edge cases".

[agedclock]

I was still working on Safari Compatibility in 2023. The bugs I was fixing in both CSS and JS were present in the iPhone 3GS or iPhone 4. I was utterly fed up of fixing the same stupid issues and decided to look for a more backend focused position. Unfortunately I am now working with AWS which has it own set of headaches.

[apercu]

Seems to be unavoidable in in the era of "move fast and break things" coupled with "let's make it proprietary so we don't have to defend our space with innovation" and incentives for staff to release features we didn't ask for nor want.

[agedclock]

Apple do this so PWA / Web Apps work poorly on their platform and pushes people to the App Store. It is why I no longer have an Apple Phone.

Running things on AWS is just foolish IMO. You data is locked and infra is locked into their platform.