What exactly do you propose they do? Do you think they are holding back supply? Should they sell at less than market price? That's just handing the profits to scalpers/middle men.
I'm sure NVIDIA, AMD, Intel, Qualcomm, etc. would sell more hardware if they could, but they can't.
Not if you reach for something open-source and use that as the starting point. Most B2B customers are small businesses and once they build bespoke software that works with their business, they won’t need loads of tokens to keep it running.
Is it actually from the cloud section or are they doing like IBM where the marching orders came down that cloud was the way and every mid level manager saw which way the wind was blowing and then worked real hard to get their calculator app moved into the cloud silo.
We use a self hosted gitlab-ce instance which has pretty high up time running on a 10 year old server (and its backup)
Takes a few minutes a month to update and babysit. We only basically use the CI and the repository functionality though so gitlab has been "feature complete" for us for a while. Probably I we could swap to something like gitea or forgeo but the gitlab CI seems like a nice balance between powerful when it needs to be and simple otherwise for our use case so there is nothing driving us to swap.
It is. Any 3DS can be jailbroken with CFW with a simple Internet guide and no physical modifications. As far as I know, the Switch CFW is locked to only V1 motherboards or modchips, making it far less accessible even if it is more powerful.
Jailbroken 3DS scene is usually for modding the console OS itself given how easy it is to run custom firmware. And for ports, and emulation. While the GBA has a pretty dedicated community for custom games and romhacks, people often create games for the platform at gamejams because of how great the dev tooling is. It's a bit lackluster on the 3DS, but I did find the Love Brew[0] framework to be really nice. Even has simulator support[1] for testing your builds locally, though fonts will look much different on real hardware, with likely a bunch of other gotchas. Running out of RAM being a big one.
edit: compared it to the GBA homebrew scene since it's a large dedicated community to derive pros and cons between the two from. Switch is still receiving updates from Nintendo to brick your system.
They can already do that with most of the information they already have, they don't need to listen for that type of thing (though they still might be as you see here, data is data after all).
Most people are not that unique. They know where you are and who you are with and any searching or sites you have been to and what is in your text messages or whatsapp as well as that same information for all the people 6 degrees away from you. They know people like you, who are your age and like the things you like and are where you are with friends like yours etc etc it goes on and on.
People rarely talk about things unprompted and you will only notice when you think you talked about something and then see an ad for it so there is a confirmation bias as well.
Vibe coding as in "Make me a postgres" is poor but if you think it hasn't affected CRUD feature work you would be wrong.
Most developers don't work building low level high performance scalable systems for a large tech firms, they are making CRUD back-ends for phone apps.
This section of the industry is definitely contracting. Even more obvious is the dev tooling part of it. Dev tooling companies are disappearing or being "bought" all over the place because what might have been a product before is now an hour or two with someone with CC.
As someone in what is relatively the equivalent of Raven's Call of Duty mines compared to past work...
Yeah, 100%. Even for relatively complex scenarios (i.e. over-engineered for purpose) as long as the engineer can prompt coherently and tweak it's a big increase in productivity, at least for those people.
The gap is in things like contract houses where you might see better code on code review from the people submitting but if you actually use the tools, you know that the hours billed are even more inflated than they might have been before.
>but if you think it hasn't affected CRUD feature work you would be wrong.
the mythical man month lesson holds for CRUD apps as well. I'd be careful to equate churning out lines of code with the health of a piece of software down the road, even a relatively straight forward one.
Keep in mind in any real world software what matters is maintenance of a system, not just how many features you can add, regardless of human or machine generated code, some badly glued together codebase that's rapidly growing is going to haunt you.
Which is also why replacing sound dev tooling and with a magical prompt genie is incredibly irresponsible and short-sighted. You could cheaply produce code by outsourcing it years ago.
Plenty of businesses want in local inference and are priced out.
reply