It’s done, it’s great, fantastic and even unparalleled. Thiel is gonna do the same with Argentina, the acronym even remains the same so the China-made hats can be reused.
it's still a work in progress for the Thiel-Yarvin crowd.
part of their goal for domination is/was eventually pushing for a civil war and abolishing the US Fed gov. that's gonna be a... messy... process, and one that will probably involve lots of groups purging one another, Robespierre-style.
presumably, he'd prefer to sit that out. gotta worry about the Roth IRA money but otherwise can chill out in a different hemisphere while his minions do the dirty work.
put another way, if you're doing be renovations of your house you move out to a sublet for a few months while they demo the place.
Since everyone hates Plex here apparently here's a positive feedback. I bought the lifetime pass for $90 a few years ago and didn't even use it that much at first. I just launched Plex Server from my MacBook from time to time to watch movies on my TV that were not available on Netflix, Prime Video or Disney+ (I subscribed to all three), because it was apparently the easiest way to watch a movie on TV from a laptop without using an HDMI cable.
With time passing and the pricing of 3 platforms becoming more and more ridiculous for less and less convenience, I completely migrated to Plex 2 years ago. It's been working flawlessly so far. The UX is not perfect but good enough, it syncs with my phone and iPad, I can download episodes in advance when traveling, I can share access with friends easily... Probably the best $90 I've ever spent for a lifetime pass.
Maybe Jellyfin or Emby would work just as well, I honestly don't know. But Plex is fine.
> Plex is dead simple to setup (minus maybe GPU passthrough to a container)
Even the GPU passthrough is simple these days in Docker. For 99 percent of people its one extra line in a Docker compose file or one extra arg passed to docker run... etc.
Say what?
I open it, i have the list of movies, i select one. What else do you need?
You can also install alternate UIs. There is one that makes the whole thing like an android TV, and another that looks like netflix, also offering you stuff you don't have on your drive. I tried, i removed it. I prefer the stock Kodi interface (not perfect, but doesn't try to sell me anything.)
That’s not possible either with the style attribute.
Now your first instinct might be to "that’s unreadable", but keep in mind HOW you actually read and write this code. You’re not actually reading it to understand what it does like you do with iterative code. You see how the browser renders it, and you just adapt the code. Tailwind code is mostly write-only and maintained by viewing what the component looks like. This code doesn’t need to be reusable either, the whole component needs to be. The Tailwind code inside is unique.
> Now your first instinct might be to "that’s unreadable", but keep in mind HOW you actually read and write this code. You’re not actually reading it to understand what it does like you do with iterative code. You see how the browser renders it, and you just adapt the code. Tailwind code is mostly write-only and maintained by viewing what the component looks like. This code doesn’t need to be reusable either, the whole component needs to be. The Tailwind code inside is unique.
I think this helped me finally understand the chasm between tailwind proponents and me. I just don't think I'll ever be part of the "keep painting each room a slightly different shade until it looks right" camp, when there's the "you can buy all the same color paint ahead of time, and even have some left over for the next five rooms you build" option right there.
Yeah, tailwind as write-only code definitely tracks. I guess some people like that. Not my bag though.
> keep painting each room a slightly different shade until it looks right
You’re still not getting it. That’s NOT what Tailwind is, because Tailwind works in a design system way, so when you use text-sm or bg-sky-400, you’re using variables that can be configured to suit your needs and keep a consistent design everywhere. Tailwind defaults and configurability played a huge part in its success.
> Tailwind code is mostly write-only and maintained by viewing what the component looks like.
I’d add that almost all code is like that, if you mean you only write it once and only look at it again if you need to make a change. And with Tailwind you generally only need to look at the one component, instead of having to go to a separate CSS file to look, and then look through the codebase to see if that code is used anywhere else.
Can we stop with this kind of trash opinion? Do you genuinely believe people use Tailwind because they don’t know any better? I understand why many people have a visceral reaction against Tailwind when learning about it for the first time, but when you actually use it, you really can understand why some of the "anti-pattern" stuff you learned about CSS doesn’t really apply with Tailwind.
Because it’s a made up rule, not a law of nature. Having the styles inline on a component is very easy to reason about, it was just extremely impractical with CSS and the style attribute. Tailwind makes it easy, practical, and is actually well designed regarding its support for variables (ie. you can have a sane design system easily).
What you want to share/cascade is variables, not styles. Styling components makes it easy to make sure the styling of each component is isolated and doesn’t have unintended cascading effects. When working this way, using Tailwind is as much a good pattern than, say, CSS modules (which I like too).
I don’t believe Tailwind is inherently worse than pure CSS. If Tailwind had existed from day 1 on the web and you had learned it first you probably wouldn’t say this. In fact, if Tailwind had existed first somehow, and someone came up with CSS as we know it as a new revolutionary library, I’m not sure it would have succeeded.
Well, the old-school way was something like this: h1.font.size = 24pt 100%. Tailwind has its own syntax, so you need to learn it first, which adds extra cognitive load. For things like * { color: } in Tailwind, you have multiple options: text-color, stroke-color, etc. With FCSS, you simply have color--[colorname] { color: … }. It’s simpler and avoids unnecessary cognitive load.
reply