I’m actually very surprised this happened at Walmart.
I worked on an adjacent project with one of their teams many years ago. I was very surprised by how zero tolerance their policies were about receiving anything.
It may have been the team I was working with, but I remember none of them allowed us to buy them coffee from the shop in our lobby when they visited.
If you're using these for purely inference (which is what the 5000 seems like it's tuned for) the vram's the real bottleneck so you get a similar bang for your buck using last gen's cards vs. the bleeding edge.
I've also found the crypto crash has dumped a bunch of these well-worn cards on the market you can pick up a bit cheaper.
As a Canadian, I find the whole saga of how our government works with the technology sector bat-shit crazy.
All of the media's coverage up here is disingenuously about tech overreach and not about how their lobbyists tried to double-dip on revenue (both demanding an estimated $329M/year[1] from tech companies, while also receiving the ad revenue from ++1.9B pageviews[2]).
The problem is there'll probably be some kind of settlement between the government, news companies, and tech. But while this drags on, the larger oligopoly of news outlets will come out alive, while smaller news outlets are really going to suffer financially.
If you want to read more about our government's recent brain-dead policies on technology you can look up:
C-11: A streaming services bill that mandates Canadian content on foreign streamers. Not horrible, but also a great way to have "This service is not available in your region." notices in your country.
DST: A "just because" global digital services tax of 3%, which will definitely be passed onto consumers, if not lead to service blockages in Canada.
C-18: ↑ This bill. Pretty much a shakedown by the government and media companies.
> This is coming from a registered liberal party member, who's socially liberal and is consistently confronted with the thought that I may actually be conservative.
Disclaimer - I work on Hasura, so I won't comment too much on which is better.
They're all similar flavors of producing realtime results - which take similar, but different, methods to their approach.
My understanding (please feel free to correct me if I'm wrong):
- Supabase Realtime uses WAL.
- Hasura Streaming Subscriptions uses a query which will be append-only (could be a sort-by or also WAL).
- Hasura Live Queries uses interval polling, refetching, and multiplexing.
- Supabase uses Postgres RLS for authorization, while Hasura uses an internal RLS system which composes queries (which allows for features like the multiplexing above).
- All 3 use websockets for their client communication.
I worked on an adjacent project with one of their teams many years ago. I was very surprised by how zero tolerance their policies were about receiving anything.
It may have been the team I was working with, but I remember none of them allowed us to buy them coffee from the shop in our lobby when they visited.