As someone with a partner who’s an accountant, I love seeing technologists be confidently wrong about accounting fundamentals vs. the type of technicalities that she has to deal with. Your comment highlights the absurdity of their confidence; kudos.
Give an example don't leave us hanging. I'm really curious how you can find an example of a temporary market liquidity move turning somehow into a long term adverse event for a company. Never heard of it
> To get the remaining 15%, which they are contractually obligated to acquire, they must purchase from the founder. As they are in violation of their contract if they fail to acquire the remaining 15%, the founder now has complete control to dictate any price they want.
This is not correct and I'm surprised this comment is upvoted to the top. The float is the float, nobody goes to buy shares that aren't available in the float.
Hey guys I rooted my humanoid and it killed my mom when I disabled the "slow limb motion" mode. It just wacked her in the head as she walked in the kitchen and she's not moving what do I do??
You should @linustechtips and hope he picks it up, then you have a good chance of getting a voucher for the funeral and getting a shout out in the manufacturers next demo when they talk about their new safety features.
You misunderstand, (continued) runtime is dependent on the ability to deploy. For instance: a vulnerability is realized or a customer needs something (availability, feature, who knows), you'll appreciate handles under your control. Service can easily degrade, without.
I've done this same thing, GHA as a control plane. It was for people who could wait; the actual operators regularly skipped the middleman. Preference or necessity, take your pick.
Runtime is separate from deployment. An incident in your deployment infra doesn't affect production. The fact that you may have to deploy to change what's live is what defines it as an incident, but it's still a different thing from a production incident.
From "nothing to do with" to "separate", I'd say we're making progress.
Deployment is how you fix problems with the runtime. Not just availability, shortcomings. I'm not going back and forth about this, there is a relationship here. Man architects, God laughs.
Here's a fun phrase to latch onto: 'escape', production is the test environment we all share.
GitHub goes down, yes, your service remains. For now. We chose to not wait, suggest others don't either. I agree in spirit with the GP. Misfortune is the fortune that never misses.
Except for when GHA is down, which is (from my own experience) waaaaay more often than our self-hosted GitLab, with it's much better CI system, ever was :)
When "me" is most classical music and this is a music platform I think the critique is not unwarranted. They could adapt it with special system prompts for classical.
Probably 50% of my listening is classical. If I want to listen to classical I just listen to albums. I’ve never had a problem with this. The concept of a DJ for classical music is just kind of weird.
Spotify is still bad for classical music because you can’t ex. search by composer or label of find alternative recordings of the same piece etc. If you know what album you want already its ok, but if you like classical you should really consider IDAGIO.
Isn’t fundamentally the issue that for any symphony by Beethoven or whoever that there are thousands of recordings of performances? So if I decide I want to listen to a certain one then I also need to pick a particular performance that a particular orchestra did a certain time?
As mentioned above, they bought Primephonic, which already had all those features. For myself, I used Primephonic until Apple bought it, then switched to Idagio, in order to minimize my connection with the Apple machine.
I love that app. They have Dolby atmos mixes which seem like overkill but I was completely floored putting on a double bass work and being completely immersed in the center of the sound. Obviously great for large ensembles but surprisingly awesome at solo works
And the play history integrates with the main Music app
building recommendation systems for classical music has a simple data problem- most recommendation systems (for spotify and others) are based on simple user listening histories that look at "people that listened to X also listened to Y".
this is a problem for classical (and jazz) for two reasons a) these genres are not particularly popular on the platform so there are few unique users and b) the songs are LONG so listening sessions contain fewer songs.
track cooccurance based recs work well for popular genres, but these other genres need a different approach to recs and that's actually where AI could do really well by digging into the unstructured data associated with the tracks (sonic analysis of the song, biographical information about the composer, details about featured soloists, etc) rather than relying on piles of user behavior.
I’m British so I guess the equivalent would be Radio 4. But no, not really tbh. I just find what I want and listen to it. I know some people really like Radio 4 though.
You also get less frequent CPU usage % datapoints when you want to be sure about usage? That makes no sense at all.
reply