The spinoff definitely came at a particularly bad time, but that was always how it was going to end up because that is how IAC operates. Vimeo was probably doomed from the moment IAC acquired Connected Ventures. It was never going to be the kind of business that could really operate as a public company, but totally could have been a profitable private company.
The custom stuff was all on the transcoding and player sides. Actual video file storage and delivery was using a variety of well-known CDNs depending on when and where, but primarily Akamai.
I miss the days when interfaces didn't have to be light white on white or dark black on black. When people thought about contrast and things looked interesting. Discord is my go-to example with this. Before the dark/light craze, their sidebar had a dark background and the chat was a white background. It was great and provided contrast and delineation between different parts of the app. When they added "dark mode", they changed it to be light gray and white, making everything worse. Luckily they added an option to bring back the previous theme, albeit buried in the accessibility section.
This whole "dark mode" thing only happened because Apple removed all color and affordances from their interface in iOS 7, and then Mac OS later. They set computer interface design back decades with that decision.
For people complaining about "light mode", please just turn down your brightness. Your screen does not need to be at 10,000 nits when you are anywhere but in direct sunlight.
Can you give an example? I mean I know you can shoot yourself in the foot with any UI framework, but jQuery has no way of managing state, everything just leaks by default. Unless they’ve added something.
Screen readers actually do generate a couple of different things that you could consider a ToC from the semantic meaning of various tags. If you structure your document properly, it's not a terribly difficult task for the browser to generate it. Apple showed that Safari 18's reader mode is going to have one, actually.
Nope, that results in significant extra complexity because now you have to implement all the stuff that the browser does for the other tags so that your website works the way people expect. (and you will get it wrong)
Then you reorg the system. Note that this can go either direction - you can also change your system to how you want the org chart to look. Generally it goes one way because engineers rarely have the power to change the org chart, but sometimes we are consulted and can suggest 'improvements'.
