help explain the relationships in a complicated codebase succinctly
It will offer an explanation, one that sounds consistent, but it's a crap shoot as to whether or not it accurately described the code, and no easy of knowing of the description is good or bad without reviewing it for yourself.
I do try to use the code review feature, though that can declare bug based on bad assumptions often as well. It's been wrong more times than it caught something for me.
No, just complete. Whatever the dude does may have morning to do with what you needed it to do, but it will be "done"
Well, yes, it's just interfacing with chatgpt... It's not packing a big gpu to run a model locally...
Note that this outage by itself, based on their chart, was kicking out errors over the span of about 8 hours. This one outage would have almost entirely blown their downtown allowance under 99.9% availability criteria.
If one big provider actually provided 99.9999%, that would be 30 seconds of all outages over a typical year. Not even long enough for people to generally be sure there was an 'outage' as a user. That wouldn't be bad at all.
One this is all speak to convince investors to throw money, so they'll cheer pick their interpretation.
In this case I think they refer to already having the real estate, buildings, power and cooling. So "all" they have to do is rip out their rigs and dump a bunch of nVidia gear in. All they need is just a few hundred million from some lucky investors and they will be off..
Same way a lot of the "ai" companies make money, investors that have no idea but want to get in on the ground floor of the next nVidia or openai.
I'm thinking this dog:
I get the sentiment, but the steam machine will have an x64 processor...
The VR headset won't, but the PC will...
Well even with your observation, it could well be losing share to Mac and Linux. The Windows users are more likely to jump ship, and Mac and Linux users tend to stick with the platform more, mainly because it's not actively working to piss them off. Even if zero jump to Mac or Linux, the share could still shift.
The upside of 'just a machine to run a browser' is that it's easier than ever to live with Linux desktop, since that nagging application or two that keeps you on Windows has likely moved to browser hosted anyway. Downside of course being that it's much more likely that app extracts a monthly fee from you instead of 'just buying it'.
Currently for work I'm all Linux, precisely because work was forced to buy Office365 anyway, and the web versions work almost as well as the desktop versions for my purposes (I did have to boot Windows because I had to work on a Presentation and the weird ass "master slide" needed to be edited, and for whatever reason that is not allowed on the web). VSCode natively supports linux (well 'native', it's a browser app disguised as a desktop app), but I would generally prefer Kate anyway (except work is now tracking our Github Copilot usage, and so I have to let Copilot throw suggestions at me to discard in VSCode or else get punished for failing to meet stupid objectives).
"Agentic" is the buzzword to distinguish "LLM will tell you how to do it" versus "LLM will just execute the commands it thinks are right".
Particularly if a process is GUI driven, Agentic is seen as a more theoretically useful approach since a LLM 'how-to' would still be tedious to walk through yourself.
Given how LLM usually mis-predicts and doesn't do what I want, I'm no where near the point where I'd trust "Agentic" approaches. Hypothetically if it could be constrained to a domain where it can't do anything that can't trivially be undone, maybe, but given for example a recent VS Code issue where it turned out the "jail" placed around Agentic operations turned out to be ineffective, I'm not thinking too much of such claimed mitigations.
My career is supporting business Linux users, and to be honest I can see why people might be reluctant to take on the Linux users.
"Hey, we implemented a standard partition scheme that allocates almost all our space to /usr and /var, your installer using '/opt' doesn't give us room to work with" versus "Hey, your software went into /usr/local, but clearly the Linux filesystem standard is for such software to go into /opt". Good news is that Linux is flexible and sometimes you can point out "you can bind mount /opt to whatever you want" but then some of them will counter "that sounds like too much of a hack, change it the way we want". Now this example by itself is mostly simple enough, make this facet configurable. But rinse and repeat for just an insane amount of possible choices. Another group at my company supports Linux, but just as a whole virtual machine provided by the company, the user doesn't get to pick the distribution or even access bash on the thing, because they hate the concept of trying to support linux users.
Extra challenge, supporting an open source project with the Linux community. "I rewrote your database backend to force all reads to be aligned at 16k boundaries because I made a RAID of 4k disks and think 16k alignment would work really well with my storage setup, but ended up cramming up to 16k of garbage into some results and I'm going to complain about the data corruption and you won't know about my modification until we screen share and you try to trace and see some seeks that don't make sense".
Yes, just some people figuring out that Grok was steered toward ass-kissing Musk no matter what, and exploited that for funny output. So the takeaways are: