Spot pricing and instance availability don’t apply to on metal hosting. You’d have your own machine dedicated to your own use only, at a locked in price.
That's too small. I was quoted a machine with ~1.5TB of vram, for $10k/mo. This was the minimum node size in the AI data center I was talking with -- they don't make smaller nodes that you can lease as bare metal. There is no public pricing though, and you had to know people to get in.
Worse, they often aren't even relevant: we searched "passport renewal" and you had to go the the second page to even get the government site that renews passports, and not ad scams masquerading as the real thing. Optimized for engagement, presumably.
Edit: come to think of it, I don't know why I still use Google. I don't care if they track me. But when they have been actively try to prevent me from finding the information I'm looking for, and instead try to scam me?
A good guess for any phone or tablet user, but I’m technical enough to change that default. It was because their results used to be objectively better. It’s also not the default on Windows Edge, and I still remember the experiences just after reinstalling a Windows VM that I’d be confused why search results were suddenly so unreliable until I remembered I was getting bing by default.
Small update: two thirds of my device browsers no longer default to google anymore. I’ll change the rest when relevant.
Even after that, for whatever reason, the next tranche of links is a mixture of AI slop and shopping links. If I'm looking for information about something and not a product to buy, I often have to, gasp, go to the 2nd page of results.
I didnt say that I solved the problem, merely that I, myself, know that I am concious.
If we go falsifiability, again, I can equally say how do I know your concious, or even that how do I know youre alive and breathing beyond the moments that I myself am observing you?
Eh writing software for healthcare, or aircraft or self driving cars is more rigorous than an EE working on industrial lighting or toys.
Im sure for the most part, engineers in physical space deal with the same kind of tradeoffs software engineers make, where you try your best based on industry standards, personal past experiences without some way to prove what youve done is right
> Eh writing software for healthcare, or aircraft or self driving cars is more rigorous than an EE working on industrial lighting or toys.
That’s a relatively small field within the software industry.
Most of the work being done (adding new fields to CRUD apps etc) is glorified clerical work, where the people doing it are rightfully fearful of being automated out of existence by AI.
Imagine you went back 100 years and someone was like "Come up with a mathematical system that can express any sequences of logical steps" do you imagine what you would deliver is a few primitives and a few simple rules and said "here you go!, this is fully complete". Its actually quite remarkable that Church/Turing didn't start off from primitives like if statements, loops, etc.
Lambda calculus is from the 1930s and predates computers, its point is that it is bare bones model of computation. It doesn't make much sense to compare it to modern languages in efficacy, as that seems to imagine someone came up with lambda calculus in 2010 along Java, C, Python, etc.
The super cool thing about it is that it is capable of expressing ALL the computation you know today, from the few primitives. An "If" statement for example is λb.λx.λy. b x y
With AI now writing queries is a joke. But you can just create a two column table: key, JSONB and call it a day and you get your easy document store + indexes, json search, relationsl goodness, and atomicity, consistency for free
We used DynamoDB pretty much exclusively at Tinder, cause it was the founders choice early on. Horrible horrible choice and after 4 years working on it I dont see why you would.
1. you have a limited number of global supported indexes, 5 iirc, which means your queries are very limited. If your use case ever expands beyond that you're pretty screwed.
2. You will have race conditions. Strong consistency is 2x the cost, and not supported on global indexes.
3. Data is split into 10GB partitions and all the read/write quotas are split evenly by the number of partitions. 100 reads you're paying for is actually 10 reads per partition if you have 10 partition. Hot sharding becomes a real problem.
Take your document data, stick it in a JSONB and you get the same performance way cheaper + query able/indexable columns. The only time Dynamo wins I think is it scales well globally, but you probably dont need it
IMO if you've got a use case that requires querying in so many ways that you need several indexes, then DynamoDB is probably the wrong choice. It excels at stuff like user specific histories that are well partitioned, read back in one way, and ideally can be written asynchronously by a separate writer process.
At the beginning there was only one query, it got expanded over time with new features. It wasnt well thought out, no.
If you need high scale globally distributed persistent data, uniform distribution of hash reads/writes, dont care for schema, and know your query will remain simple yeah its a fine choice.
I just wouldn't consider it outside of enterprise level
> you have a limited number of global supported indexes, 5 iirc
you can create 20 global (GSI) and 5 local (LSI) indexes per table[1], I think the number must have been lower at some point in the past, because it's not the first time I hear this complaint
reply