they rely on being closed source to survive penetration
M$ always has.
But even open source relied a great deal on the volume and complexity of their code base to survive penetration... until now.
MangoCats
joined 2 years ago
its great at creating this busy work but not so much with fixing it
Actually, if you know what needs fixing, LLMs can accelerate the fixing process quite a bit too.
The problem is: LLMs don't know what they don't know, so they'll declare "good enough" and it's up to the LLM operator to call BS and give them additional context to ensure they keep going until ALL the applicable concerns are addressed.
It it is unsafe to code, full stop.
The things we're expecting our code to handle, with the lack of formal verification testing we're expecting our code to ship with, there's no such thing as safe. It took 50 years to "build the stack" to where we're at, and we did it fast and cheap. There's so many bugs hiding in the lasagna it's amazing it doesn't eat itself.
If you re-build your system from first principles, open source silicon with peer review and constant scrutiny, then the BIOS, then the OS, then the application compilers, and the libraries, all open AND reviewed by multiple concerned parties with formal demonstration of correctness all the way up - the entrenched bug filled lasagna stack owners will smother you, they can't withstand that kind of competition on an open playing field, your project will die of financial starvation, regulation, buyouts and treachery.
The picture of the past / questions of character give a sense of what they might do next, but the real questions are what are they actually doing next? Those are the things that need focus, and I get the sense that the current ruling class has learned to manipulate the masses with distractions about the evils of their past in order to get what they want in the future.
Idle hands being the devil's workshop and all that... can't let people do what they want, most people don't even know what they want, and of those who think that they do - if they ran around doing that they might "change the world" - and that would be bad for the status quo, so those in power in the status quo are certainly going to try to stop that...
Yeah, I'm in a bigger company, so I have the conversation with the local group, then the various other "Subject Matter Expert" groups that touch the same project in their own way, and just when I think I'm done having it there's some group that submarines up and says "but we haven't qualified our code to run on 8 so if you're going to use it you'll have to pay us to do the qualification, but we're really busy so that's going to be about 6 months before we can get to it..."
adding a preprocessor directive
Yeah, I've had to do that a few times lately. Really tweaked me when gcc transitioned things from warnings to errors.
Migrating from 4.6 to .NET Core.
Are we on .NET 7? No, only 8 is available here without unreasonable effort to backdate. Does the .NET 7 code run in 8 without mods? Yes, but that doesn't change the hassle of talking endlessly about it.
Yeah, 0.5% was what I was offered as Director of 50% of new startups... 0.005% is more realistic - and could range from 0 to outrageous.
More reasonable: roll back to before the datacenter was permitted for construction, find substantially equivalent houses in the general area - 20% more square footage, 20% higher value per square foot, and track their values over time until the present, and whatever the peak was, offer 20% more than that plus moving expenses... effectively 175% of "fair" value + maybe $20K.
There's the thing: what's a woodpecker's property rights on his dead tree? I mean, you can offer him any amount of money and he isn't likely to just give up the nest he carved in it and move on to try to find another. Ask a colony of bats what they want to move to a new roost?
Same for people's homes, there's a price they could get for them if they tried to sell on the open market because they want to leave, but there's a very different and often much higher price that would be required to compensate them for the downsides of moving.
When a corporation wants to entice a new hire to move to a new city, they will buy the home at high-end market value, pay the real-estate commissions on both sale of the old home and purchase of the new home, pay for professional movers, and bulk up all of these benefits to cover increased income taxes where applicable. And that's for a new hire who wants to move.
If China manages to scale their hardware production, this could finally be "their day in the sun" where they clearly surpass the West in the way the West has outshone them for 100 years. MoE has its place, but a MoDE where each E is itself a dense model would be more powerful still, mostly you need the silicon gates and power to drive them.
Three Gorges makes hydro-power, right? 22MW -> 100 TWh per year, just from that one structure, I bet that will run at least one AGI... https://www.fredgao.com/p/deepseeks-liang-wenfeng-breaks-his
Tiny little example: Azure DevOps supports ssh key access, but only the old - now considered insecure/inadvisable for continued use - RSA ssh keys.
Their priorities for providing that kind of convenient secure access lie elsewhere, in activities that generate more revenue for them.