bdougherty

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.

The people in this video were mostly CollegeHumor people (I think there are 4 Vimeans in there), but the last one left about 10 years ago now.

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.

React is also extremely easy to get it wrong.

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.

We didn't have that in the article?

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)

I don't get it. What are people going to a website for if not for the content of that page?

Until the org chart is reorganized, then what?

Some people do not need the updates, some will pay a fair value for the updates. Nobody is asking for non-subscription software to be priced the same as the subscription.

Bottom line is that the App Store not having upgrade pricing has forced everything to become a subscription.

Because it is nearly impossible for it to be truly anonymous.

There is actually an iCloud Passwords app for Windows already.

It also benefits users in that you can implement more features and fix more bugs in less time.

This is mostly a bullshit answer that is hardly ever the case in reality and is pretty much always used as an excuse to favor developers over users.

Production is only as hard as you make it.

I don't see why it's so offensive to you that others are making different choices.

Because those choices have had a major negative impact on everyone, especially and most importantly and significantly on the people who visit those websites.

DRM is not good, but if they didn't specify DRM, it would still end up in browsers as proprietary methods, or it's possible proprietary browser plugins like Flash would have continued to exist. Unfortunately, you can't just make the people pushing for DRM go away by not specifying it.

What is the benefit of tRPC over built-in SvelteKit data loading?

I copied this from a specific project, so there might be a couple things missing, but here is generally what I use

https://gist.github.com/bdougherty/404b4ca33dfdbff48614b454f...

This is an opinion trapped in 2010. You can build both "simple arrangements of rectangles" and way more complicated layouts easily now. What would you propose as a replacement?

Ask the people who invented CSS why they built it in a way that is really really hard to understand - even for simple things.

Can you give an example or explain more about this?

I cannot agree with this comment any more. Every time I read any one of these Tailwind threads, I am yelling in my head "SVELTE!!!!" the whole time. Going against the current of the platform is a recipe for disaster every time, and Svelte is one of the few frameworks that is actually trying to go _with_ the current.

Whether you like it or not, the cascading part of cascading style sheets is an integral part of the web platform, and one is better off in the long run swimming with the current of the platform rather than against it.

Because previously you had to be blessed to get a bluecheck, now you just have to pay. Way more people have the means to pay than were blessed.

I only ever use it in the car with CarPlay.

Here’s a good article that describes some of the reasons: https://lapcatsoftware.com/articles/SystemSettings.html

It's not about System Settings being vertical now. Just look at any of the panels and tell me how the new version is an improvement on the old? The panels in System Preferences were meticulously designed and the new ones are just a list of checkboxes.

It is getting ripped up, but all the new people on the platform are unaware of how much better it was before. I don't think anybody has issues changing things to make them better for newcomers as long as Apple doesn't throw out all of their design principles to do it (which is what they have been doing).

Huh? How can you draw that conclusion from that data? Just because people are moving to the best option does not mean that option is not getting worse.

Telescreen, newspeak, mass surveillance, perpetual war, "officials" acting as if what they are saying now is always what they said, etc. It's almost easier to list the things that we don't have in common.