What a completely rude comment that tells me everything I ever need about you and whether I'd want to interact with you. They're not asking for the literal answer. They're asking a question about why that is important to surface at all.
Absolutely, you're hitting the same conclusions I've reached. The algorithms are optimized for the lowest friction users that just replay the same music they like over and over again and accept whatever the popular music is. If you're a user that likes music discovery you're fighting against the system to get what you want.
I don't think the recommendation engines behind Spotify, Youtube Music, etc compare to the recommendations I got from last.fm over the years. The algorithmic ones seem to have a bunch of issues that bug me as a long time music listener and someone with a large music library.
- their memory is short as hell so you can listen to something for a while, stop and then it'll suggest it to you later as something to "discover"
- they are way too biased towards recently listened music and will replay things over and over if you're not actively managing your queues.
- because they're so based on what you have listened to (recently) they suggest things that are extremely obvious music no one is "discovering"
- they suggest the "top" songs from artists, albums, etc, it's very hard to get it to play a "deep cut"
- if you have a large library you'll inevitably hit playlist song limits and other things silently. Each service handles this differently, Youtube Music seemingly kicks things out of my library or liked playlists each time I add something else.
I've literally just gotten in the habit of never using the autoplay features and just starting whole albums from start to finish again because the algorithms annoy me so much. Youtube Music has been getting worse about it too where now it often ignores the music you chose to start a playlist and starts playing things you've listened to recently regardless of it doesn't match the genre/vibe at all.
I was wondering that too. They explained the differences between the tools but didn't really qualify which was doing things "right" just that they differed.
These days it's hard to tell and there's always a mix of both with any high demand items so it makes the stock limits even more pronounced. With how Valve has done hardware releases lately though I imagine it's more a stock limitation.
Yeah I can see that. I probably wouldn't be subscribing to issues that weren't feature requests/gaps very often. Ones that are tied to bugs are the only others that come to mind that I'd subscribe to but just thinking about my own dev experience in various jobs and how even there our internal backlogs of issues would have unclosed, out of date stuff, I think some portion of issues in public projects would be too.
Context usage is in an open PR now! https://github.com/zed-industries/zed/pull/54881 give it a week or two depending on if you want to use stable vs preview releases. I haven't tried pasting images yet either but I have used their context menu that lets you add images.
1. That's a pref, turn off "format on save" lots of editors and IDEs have it. Maybe they should default to off but it's not an unheard of option with no way to turn off.
Entirely right it's a limitation to the ACP side. They're in the middle of adding functionality where you can have terminal/CLI threads and ACP threads too. https://github.com/zed-industries/zed/pull/54729
Go look at any large project, they have 500+/1000+ issues and many are ancient. Chrome, Firefox, you name it. I wouldn't be surprised if many issues have even been solved or need new reproduction steps but there's a difficulty to triaging all the issues as well.
I feel like it doesn't support some of the commands that manage Claude itself so think `/mcp` `/plugins` etc. Most of the common ones are configured to work though from what I've seen but the ones that do more configuration of Claude seem to be blocked.
Plus they'll position them close to an intersection in the parking lot of a business so they can get around something like the restriction Austin put in.
In Counter Strike I've seen it be an actual issue too where a player's view is blocked by a body and their teammates don't have the same issue while spectating them.