516 karma · joined April 27, 2016
Not to mention that those superstars need to come from somewhere. If a career in music is basically like spending all your money on lottery tickets, society ends up poorer: many hard-working young musicians are going to see it for the exploitation machine that it is, and go sell advertising instead.
[1]: e.g., like this one from David Lowery of Cracker and Camper Van Beethoven: https://thetrichordist.com/2016/02/16/the-reality-of-touring...
However, I'm disappointed (but not surprised, this was listed as out of scope for 19) that triggering Suspense is still basically "use a framework that supports it." I have not been able to find any documentation or blog posts about the mechanism. I've tried to figure out how it works by looking at TanStack Query, but I've had limited success so far. I've found they're copying React's twist on Promises [1], but I haven't gotten this to work yet.
I know the general idea is you throw Promises, but Suspense explicitly forbids using promises created during rendering. This means you can't just interrupt the component's initial render to load some data, and then restart it when its data is available. This means the component needs to deal with null data somehow, instead of, e.g., being able to call a custom `useSomeData` hook and rely on it to first suspend and then return the loaded data. Not having to deal directly with loading states in individual components could simplify things quite a bit.
Has anyone explored this side of Suspense?
[1]: https://github.com/TanStack/query/blob/main/packages/query-c...
You're right about it accepting a path (and defaulting to a compile-time selected UNIX socket path).
I doubt there's a simple answer (I certainly don't have one), but the current system is not exactly a creators' utopia.
Have we solved it? Streaming platforms are great as a consumer, but they have serious drawbacks: some content is just not available there, content can disappear from your "library" or playlists due to licensing changes, and the economics stack the deck against smaller artists in favor of "unicorn" successes.
It would be interesting to see plan changes, if any, across versions.
[1]: https://www.postgresql.org/docs/current/sql-truncate.html [2]: I like to think I would have at least checked the docs because there's no efficient way for TRUNCATE ... CASCADE to work how you intended given how I know TRUNCATE is implemented, but who knows?
But separately, I don't want stewardship for my data to rest with whoever I transact with to acquire that data. Why not a digital locker standard, where you sign in with your digital locker when purchasing digital content, and that content is saved to your locker, with whatever metadata? You can then search and play your purchased content through whatever client you like, regardless of where you got it from. You can sort of do that today (to the extent that you can still purchase digital content--there's music that's available to stream that I have not been able to find for purchase) with files, but you lose the stewardship and it's a lot of work.
You can argue that the subscription model pays for the stewardship in a way purchases would not, but surely digital content is easier to work with than CDs and DVDs.
I think most consumers don't really care, though, and I'm guessing content platforms don't really see the point of supporting something like that.