Re: Only?
That's ultimately it. The fact that email and facebook machines struggle with 8GB really is a quality issue
151 publicly visible posts • joined 26 Jun 2010
> There are no isolated decisions," he said. "There are decisions that pertain to this particular investment. There are decisions about others. I think we need to have a commercial discussion and put them all together
It's got to be both. You can't have the guy look you in the eye and say "shame if something happened to the rest of your outsourced public sector functions" and leave it at getting your overtime back for fixing one disaster
Government is sleeping at the wheel if they don't disentangle themselves urgently after that performance
> There are no isolated decisions," he said. "There are decisions that pertain to this particular investment. There are decisions about others. I think we need to have a commercial discussion and put them all together
It's got to be both. You can't have your supplier turn up and say "shame if something happened to your other outsourced public sector functions" and keep thinking of it as getting the overtime back on one bad project
Government needs to react to signals like this
It seems like the kind of conflict a competition authority would handle. Consumers get worse software because the other arm makes money whether you improve your product or not
The economic solution is to separate them and leave the software team to compete in the market by making the best database software
I always liked the sqlite guys talking about why they don't accept third party contributions- they talk about free as in speech, as in beer and as in puppies. It's nice to contribute to open source but once you hand it over the project has to maintain that code for the rest of time
The idea of big tech firms contributing to open source projects was always nice in the assumption that they were donating high quality code because they were pros with lots of resources. Firing mountains of AI generated PRs at volunteers seems to completely change that dynamic
If you treat it as expensive software engineering device then having it on prem could change the calculation. You could find it justifies experimentation outside business hours better than the usage based models do. The economics of selling executions don't change but you're actually trying to get value out of your TCO instead of trying to find profit after the provider's fee
It's the same argument as databases- a serverless database costs you more the more you use it which is an interesting exercise in whether a query was worth the candle, as opposed to amortising queries across the life of the hardware - you simply wouldn't interact with systems on the different pricing models the same way
A lot of iphones have found themselves on photocopiers to produce a really neat court production - you can have cases like sexual harassment spelled out in one screen of messages and a photocopier turns that into a sheet of paper to distribute very quickly
There's so much to say for just putting a picture of something on a sheet of paper
That's tail wagging the dog. Your business processes got you to the scale where you can afford this stuff. Changing them now just because you bought some software is its own risk
You're meant to work with some sort of functional expert to get the software aligned with your process without having to customise the thing into a unique artifact that no one can then get you out of
There's an angle of "go to a food bank" apparently
When you bought brioche, as opposed to bread, you could choose to donate a portion of it to the poor as a way of symbolically sharing your good fortune. Qu'ils mangent de la brioche is therefore, wow, I really don't know how the world works combined with why are you mad, I *did* the wee charity ceremony
It's meant to be a crafted line against the aristocracy and you can see that in how it hits all these different points
There will professionals out there pretty annoyed at how bad this almost pointedly half-assed approximation makes their methods look
People making the effort to have their clean room implementations survive all the hoops will hate having this example of how badly it can be done in the news
It's beside the point, though. This stuff hasn't been carefully maintained through the decades because you were happy to mess with it. It's exec bait because everyone hates their ancient cobol that keeps the lights on but it'll never happen for the same reason it never happened before
It's going to be a real block - summarised emails where you've still got to read the email because if the summary missed something that's still on you
It really highlights the careless people thing- "this stuff works alright but if it breaks it breaks and you should have checked it, I guess"
Part of the madness of unconstrained compute demand and the blank cheques for building data centres is these chips have longer lives - run it to death alongside new infra instead of tear out and replace
The fundamental issue of sweating an asset that was never profitable in the first place remains