Is there really no way to use Cassandra for this use case? A distributed and relatively battle tested database? They didn't want to use SSDB because it lacked support. Okay.
I mean you're one-off vibe-coded distributed database isn't a database until aphyer puts it through it's paces, and until it encounters most CAP its edge cases over years of use.
Otherwise, this isn't a database. It's a black hole of uncertainty that will almost certainly drop writes and commits silently
They mentioned trying Scylla, but found it didn't do well with multi-megabyte blobs. I question why they need multiple megabytes' worth of JSON to store user preferences and metadata, personally, but that's neither here nor there.
We're on like a half dozen straight Republican administrations of tax cuts for the rich and massive deficit spending combined with unnecessary wars.
Everything you just described is an investment that has a substantial positive output economically, Even when implemented incompetently.
It's so funny to see economic "rationalism" always pop up as soon as Democratic political waves appear, while when Republicans have all the control of the purse strings: utterly unrestrained fiscal malfeasance.
And the disturbing trend with Republican administrations is that the corruption and incompetence gets worse every cycle.
Why are you pretending that there's no wind in the UK? Or Germany? In fact, all of Europe is basically surrounded by a coastline with huge amounts of wind resources.
Or just gas peak already.
But look, if data centers want to fund a whole bunch of advanced nuclear and wait 10 years for it to get built and will foot the bill for the cost overruns, okay I'm not going to stop them.
But let's face it all. This nuclear stuff which is going to be for data centers is all an externalized cost that's going to be dumped on the public.
I’m not pretending anything. I simply posted some easy to double check numbers. I’m pointing out that just this week the wind didn’t blow for 3 days, and that happens frequently during in European winter. So much that the Germans coined a phrase for it.
In my opinion all AI use companies should be attached to a specific employee, and that person is liable and so is the company of course for the actions of the AI
It's like saying "developers should be responsible for their own security so we will make them liable if a random node dependency in the application they are building gets pwned"
Firstly, liability and security are different things.
Employees should never be liable for something that happens if they are using a work-supplied tool at work in the manner in which it is designed to be used.
Secondly, it's just lazy thinking to say "oh it's hard therefore we'll make the human sorely responsible".
There are many things that can help - sandboxing, adversarial LLM inspection of prompts, separation of security contexts etc. Yes they are hard and might need new primitives.
> Employees should never be liable for something that happens if they are using a work-supplied tool at work in the manner in which it is designed to be used.
Architects and properly-designated publishers both have potentially long liability that is to an extent independent of their future employment. (The same is true of hospital consultants and others)
In significant cases, the way you provoke companies to do the right thing (security, sticking to the facts, not cutting corners in building plans) is to make someone legally responsible if they don't. That person's liability is limited by their actions — if they can demonstrate they discharge those responsibilities appropriately, they are in the clear.
That person takes on that designated role, does the job, and is rewarded properly for the responsibility it involves. They embody the push to reduce that risk.
So an average employee using the tool as directed by their employer, they do not have liability if the company has designated someone in this role. (And in this scenario, if they have not, there would be a punitive fine for that, independent of other outcomes).
I have no particular problem with the notion that a corporate AI safety/responsibility officer is a plausible way forward. If you are delegating responsibility to a machine, someone has to be on the hook. Without such things it's a wild west with lawyers. That's not sustainable.
> “developers should be responsible for their own security so we will make them liable if a random node dependency in the application they are building gets pwned”
Developers may not be liable today, but protecting company data and resources from supply chain attacks is their responsibility. At most companies, only the developer is in a position to understand how these supply chains work. Even at larger companies with security teams, the scanners and mirrors are trivial to bypass.
> Employees should never be liable for something that happens if they are using a work-supplied tool at work in the manner in which it is designed to be used.
The employers and prosecutors of employees who stole billions of dollars using Excel would beg to differ.
A particular c suite employee. Each company having a low level sacrificial goat doesn't solve anything. They must be responsible but also be in charge.
Eh, I think it's a continuum , small projects don't need standards, but large projects eventually need standards.
For example, Beyond All Reason recently added code format linting errors and static code analysis just to help alleviate the load on the small group of people doing code reviews. The project had been getting along without it, but with well-meaning-but-vibe-coded PRs being proposed at an incredible rate... There was value to be found in automated (non-llm-based) code review.
I mean you're one-off vibe-coded distributed database isn't a database until aphyer puts it through it's paces, and until it encounters most CAP its edge cases over years of use.
Otherwise, this isn't a database. It's a black hole of uncertainty that will almost certainly drop writes and commits silently
reply