Exporting = one-way door
File over app = two-way door
Do not mistake the map for the territory.
Many apps allow you to export your data. That's better than nothing, but not the same as editing files directly. An export is a representation of your data. It's an output of the source. It's a one-way door.
The file over app philosophy does not make a distinction between data and file. Both are one and the same. The source is the output, and vice versa. It's a two-way door.
Exports are useful if you want to exit the tool. Exports are not useful if you want to directly manipulate your data. Exporting requires your explicit intention, whereas file over app requires no intention at all.
File over app means you have possession of your data, it can be directly read and edited with multiple different tools at any time.
@colmtuite@Base_UI This looks so good. I've been wanting something like this forever.
I actually have a usecase for this right now, is this publicly available anywhere? Even if unstable?
This graph is from @Noahpinion's article on the subject. I agree that "It's the phones" should be our default hypothesis. Though it's not the phones per se; it's the apps.
https://t.co/8h7h8C6cis
We have been working on a couple of projects on which we would love to get your input!
The first one is a new Form primitive: https://t.co/mQAn08cTHh
The second one is a brand new project: Radix Auth:
https://t.co/GkQHFjBvYE
Please comment directly on the RFC PRs 🙏
I wrote up a detailed guide to some of the absolutely wild examples of Bing's new AI-assisted search feature that have started to circulate:
Bing: "I will not harm you unless you harm me first" (that's genuinely something it said to someone)
https://t.co/CS949Oa3HH
@adamwathan@stolinski and so I struggle to see a case for “use utility classes everywhere”. Yeah, co-location and quick to write, but at what cost? This seems more difficult to read, and takes conscious effort to write in a somewhat organised way (that is still less readable than just vanilla CSS).
@adamwathan@stolinski imo, utility classes are useful for general layout divs, but the example shown here doesn’t seem to be a “one-off pattern” - it looks like a reusable component. Using the class “alert-dialog__action” + CSS seems to sufficiently address both of your points and more readable (imo)
During our summer hackathon, #DataDriven@kormsen worked tirelessly to implement our long-awaited dark theme for the #SingleStore Cloud Portal.
https://t.co/BTf9PGYmCy