Another selling point has been a guarantee of 1:1 api feature and design parity between Anthropic and this Claude platform. Helps if you have workloads you want to balance between providers.
minimum wage is minimum wage (IMO?), the business losing money only dictates how long that position will exist for, not change the compensation owed for performing employed work.
in minor league baseball, who's indepent teams may be anywhere on the spectrum of losing or making money but who are also affiliated with parent organizations that make hundreds of millions, there is a plethora of literature lately that accuses them of paying significantly less than US minimum wage. In many cases it appears the players pay them for the right to play when it's all done.
in the college hockey example i referred to, the D1 teams/leagues usually have decent revenue from tickets and tv deals but it's not a ton and i'd take a shot in the dark that most programs are pretty much breaking even after scholarships, staff, and facilities are accounted for. In that environment, having an athlete get "paid" maybe a $40k/year total package in scholarship, room and board, playing equipment and facilities use, and cash per diems on road trips is both above minimum wage and probably no more than they could reasonably expect if the league was "pro" and had nothing to do with college.
baseball arguably does a terrible job at solving this.
the minor league system pays significantly less than poverty wages. incentivizing kids to go that route instead of getting an education is terrible.
which is why so many dont, and go to college on scholarships anyway, which leads us right back where we started.
the right analogy to make IMO is ice hockey, especially the canadian model. There, you have well funded and professional-like "minor leagues" (called juniors close to same thing). you can't get paid but in the tier 1 leagues you have very little if not zero personal living expenses, it's like being on a full-ride at a big college program with room and board included. In canada, it's seen as the route potential NHLers take instead of continuing with school. you're not allowed to be paid, but there's a rule in place that for every year you play in that league you're owed one full year of college paid for. If you age out of the league and dont make it as a pro, you at least get 2-4 years of free college to go get the rest of your life together as compensation.
The US Junior system has some of those attributes but is more geared towards getting kids into NCAA scholarships. The thing there though, IMO, is that the money involve in that sport is right about at that sweet spot where i'd argue a full ride to school like notre dame or penn state is about right for the level of compensation owed.
all opinions above are my own, in the context of a former D1 ice hockey athlete who thinks the football players should probably be paid.
you kinda can in a lot of universities with big programs. There's a lot of "sports marketing" and "sports science" majors now that get a little loose with requirements and rigor. when done right, they can be good tools to prep athletes for life after playing (agents, marketing, phys ed instructors and coaches, etc.) but they also run the risk of being places for the football team to sleep through class and get an A for working out and attending video.
when people are living (and budgeting) paycheck to paycheck, with low interest rates, the prices go up a bit more than 1:1. It becomes all about what monthly payment you can afford.
that's not true at all in my experience. In the past we've had "bug bash" type activities, or used that lower-hanging fruit as training opportunities. As an architect i've sometimes grabbed tasks like that just to stay fresh but also out of the way of the prioritized team backlog.
I work in an org that is looking to provide a lot of the same experiences both within salesforce and outside of it, and I'm looking at this make sharing those components easier. Imagine if you have a calculator and it could be used by both your client relations team (working in salesforce) and on your retail-facing web site.
right now we write two UIs and hook them up the same service. now maybe we get to write one UI.