I'm glad to see Ember is still in development. There are a lot of good architectural decisions in there that I miss when I'm in React, and there's a lot that casual React developers could learn from it and other opinionated frameworks. It was sad to see that Ember was held back by obsolete design choices for so long (Vite took years!! And AMD modules are only being deprecated now in this release)
I'm observing recurring patterns in Tailwind-only users: they learn a lot of non-transferable and bad habits, especially when the codebase scales up:
- Engineers never learn to properly use developer tools to debug CSS
- Components get gigantic bloated piles of classes that are not human readable
- Those gigantic piles of classes get logic in them, that often would have been easier to write as a CSS selector. Tailwind developers learn to write a JS ternary operator with a string of classes instead of ever learning how CSS selectors work
- Those ternary operators get too complicated. The engineers write object maps of Tailwind classes, or export consts of strings of Tailwind classes to use later. Those object keys and const names are what the CSS class names could have been if they just used CSS. They literally re-invent CSS classes, but worse.
- Tailwind classes can't be migrated. You can migrate CSS to Sass to CSS modules to Emotion CSS to etc mostly just by copying them over, because all of those are CSS (with some quirks). Tailwind classes are non-transferable
The happiest medium I've found was in an organisation of around 200 UI engineers: scoped CSS so that engineers can work with autonomy without colliding with other engineers, plus Tailwind for quick band-aid fixes.
> You can migrate CSS to Sass to CSS modules to Emotion CSS to etc mostly just by copying them over, because all of those are CSS (with some quirks). Tailwind classes are non-transferable
Tailwind classes are literally vanilla CSS classes. You can copy-paste their definitions directly
I don't know you either, but I feel weirdly and unexpectedly connected to your message too. I'm 4 months into a layoff, still hunting. Appreciate your message!
The author began to realise the truth: that the quality of his writing is very low on average. Then he moved away from that realisation to the thought that Roam or some other kind of automation could somehow save him.
Perhaps what he needs is for the tool to automatically ask him "Is it okay to delete this note from 60 days ago?" That should be long enough for him to lose any attachment to what he wrote and a lot of the time he should say yes, and delete the crap.
Thanks for the recommendation. I just had a quick try, it's nice, seems like a very polished Firefox. It seems to have a bunch of features I don't want in a browser so not sure if they'll get in the way.
Yes, but a while back. I settled on Scaniverse for 3 reasons: It worked well, it had a high App Store rating, and no in-app purchases. A couple years on, it still works great and gets regular upgrades.
BTW, it's not just sculptures. I've scanned rooms (mixed results), relief paintings, loved ones (mixed results but if my children weren't already grown I'd be scanning them at least once a year), and even food.
Food can be quite fun. I showed a restaurateur a scan of one of his appetizers (served on a round stone so it made for good scanning). I used the AR view to project it onto our table and joked "Now I can enjoy one whenever I feel like!" He was so excited that he downloaded Scaniverse on the spot and I showed him how to use it. After that, he took us under his wing and recommended all the dishes he was proudest of. (We still had to pay for them though ;-)
In general, regardless of what AR/VR device you have or plan to get, if you see one in your future, it's good to build a collection of 3D / immersive content.
> Taildrop is currently limited to sending files between your own personal devices. You cannot send files to devices owned by other users even on the same Tailscale network.
reply