992 karma · joined March 23, 2022
email: eliot@eliot.sh
[0]: https://www.unoosa.org/oosa/en/ourwork/spacelaw/treaties/int...
(FR24 makes it difficult to see on mobile & in general)
[0]: https://developer.apple.com/tutorials/swiftui [1]: https://www.hackingwithswift.com/
Inspired by an iPad-style layout, along with some other personal sites I admire. Not too fancy, just a home for my photos and some (not very much) writing.
[0]: https://shokz.com/
Also: Kindle users should check out Libby[0] - it's like a public library but for eBooks, and you can probably sign up through your local public library. It's great for books that might be interesting, but aren't an immediate read.
Other than the pencil, maybe my Peak Design everyday backpack? I got the v1 used on eBay for ~$100 and I've used it for maybe two years now. It's still a decently student-specific purchase, though.
- Twitter doesn't "die", but social media does get a lot more diverse. Journalism gets better because of this
- Generative AI like ChatGPT goes mainstream (this may have already happened with ChatGPT, to an extent)
- Some large earthquake in CA
- Apple finally rids the world of the lightning port
Creating art is not that much harder than programming, creating good art is much harder than programming. That's the reason that a large majority of art isn't very good, and why a large majority of Artists don't make a living by creating art.
Just like the camera didn't kill the artist, neither will AI. For as long as art is about the ideas behind the piece as opposed to the technical skills required to make it (which I would argue has been true since the rise of impressionism) then AI doesn't change much. The good ideas are still required, AI only makes creating art (especially bad art) more accessible.
I would say the documentation adequately responds to your complaints about re-usability then? Use a component, use the IDE, or use @apply. The notion about needing to change classes 1000 times for a small edit just isn't true (I've never had to do this w/ 2+ years of tailwind).
> I think you're too narrow minded to accept any input so I won't bother.
Making some sort of ad hominem attack about how I'm narrow minded is useless. I'd love to hear your input.
As opposed to what? This is still an issue with any kind of utility class, where the alternative is inline styles or CSS-in-JS, both of which are substantially worse.
> Conflicting utility classes aren't clear, and sometimes the order cannot be trusted;
This is fixed in the IDE with tools like ESLint. I have VSCode setup to automatically reorder Tailwind classes, and it works great. (It even moves broken classes to the front of the list, so you can immediately identify if they're working or not)
> Replacing `p-4` with `p-4` will require you to replace its occurrence all over your app, sometimes affecting thousands of matches. And since there is no context to it, it'll be hard to JUST replace them where you would want them to.
This is an issue with CSS in general, especially CSS modules. Plus, if you use tailwind correctly (with @apply) you only have to update it once.
> Vanilla CSS using `:root` declaration, a fixed base size (using `rem` and `em`), CSS variables and `calc()` are SO powerful.
With tailwind, you still have access to `calc()` and variables with their bracket `[]` syntax. It's just much easier to do everything else.
The US is obviously bad at public transit, but the solution isn't to build tunnels for cars.