Forgot your password?
typodupeerror

Comment Re:40 NVME ? (Score 1) 15

Yes, though I don't know about nvmeof. I feel like san style block is overall less popular than other sorts of software approaches to distributed storage nowadays.

Storage people keep pushing the way it was done with fiber channel attached controllers abstracting things to generic block devices. Shared sas, fcoe, iscsi/iser... Have seen so many tries at bringing the concept and being ignored in favor of things like clustered filesystems and object store.

Just like hardware raid controllers are nearly non existent in nvme world, and folks are managing multiple disk redundancy in the os, people are looking for more transparent storage solutions and I just don't think nvmeof plays a role instead of direct attached storage to open ended operating systems..

Comment Re:If it were me (Score 1) 86

And double it to get through the night.... I was calculating based on kwh per day of expected solar against kwh of consumption for a gigawatt (so... 24gwh).

It wasn't a random ass guess, I did the math.

5 miles by 5 miles is a huge installation. Far from the suggestion that they could just slap some panels down on their facility and even have surplus for the grid..

Comment Re:umm (Score 5, Insightful) 63

Actually, if anything he's saying his software package is so crappy that it *should* have found issues. He considers it's failure to find issues not a testament to how awesome his software package is but how lacking the tool is.

I've seen a few times where the curl developer has stood up to some asinine thing that most projects just roll with and I've appreciated his perspective each time.

His finding is consistent with another analysis I saw: Mythos was not good at finding issues at all. The one thing they could claim was that while other models found more issues, Mythos was able to craft a demonstrator to actually exploit the weakness, rather than just identifying the issue.

Comment Meanwhile, at Carnegie Mellon... (Score 4, Interesting) 193

Jensen Huang to college grads: "Run. Don't walk" toward AI

https://www.axios.com/2026/05/...

Nvidia founder and CEO Jensen Huang told graduates at Carnegie Mellon University in Pittsburgh yesterday that demand for AI infrastructure is creating a "once-in-a-generation opportunity to reindustrialize America and restore the nation's capacity to build."

Why it matters: With many college grads fearing AI could obliterate their career dreams, Huang pointed to boundless opportunity as a "new industry is being born. A new era of science and discovery is beginning ... I cannot imagine a more exciting time to begin your life's work."

Nvidia, which makes AI chips, is the world's most valuable company. Huang told 5,800 recipients of undergraduate and graduate degrees that the AI buildout will require plumbers, electricians, ironworkers, and builders for chip factories, data centers and advanced manufacturing facilities.

"No generation has entered the world with more powerful tools â" or greater opportunities â" than you," he said. "We are all standing at the same starting line. This is your moment to help shape what comes next. So run. Don't walk."

"Every major technological revolution in history created fear alongside opportunity," Huang added. "When society engages technology openly, responsibly, and optimistically, we expand human potential far more than we diminish it."

Full speech: https://www.youtube.com/watch?...

Comment Re:Programming graffiti (Score 1) 26

Getting their name on a project they are a fan of is a big factor

Also, they *truly* think they can *finally* be useful without having to actually understand things. They think a code request will be accepted more readily than they ever got attention on feature requests or behavior changes. They think their willingness to let CodeGen go nuts is a differentiation over the developers who mifroght even be using the same CodeGen tools, but with more care. If nothing else, they see tokens as almost like currency, so by generating the code it saves the developers from spending tokens.

So they mean well enough, but they flood folks with slop because they were never in a position before to do anything but slop, but CodeGen lets them realize their slop.

Just like the AI art is generally slop by lack of any artistic vision to start with. If they had sat down to actually draw the art, it still would have been slop, but now it just accelerates the process.

Comment Re:aaaand now I'm curious (Score 1) 26

Well, github seems to be throwing a fit, but I can say from my experiences:

- Uselessly verbose. One AI pull request I was asked to review was aiming to do a minor adjustment the layout of a singular webui element. The pull request was hundreds of lines of CSS because the LLM just started firing the random bullshit CSS cannon, often repeating itself probably because the operator said "no, it's still messed up" until by some miracle the one change he wanted managed to finally appear, alongside a whole bunch of other crap with side effects that the operator didn't bother to find out about. When getting to the heart of what they *actually* wanted, it was a single line one minute css tweak.

- Missing the glaringly obvious. Had a pull request seeking to adjust behavior to be compatible with newer things in the ecosystem. Ok, great, but adjustments had already been made and released a year ago, the operator had a stale container they had never updated. At no point in the clone/pull/mod/pull request flow did the AI stop and say "oh, it appears equivalent changes have already been made", but instead submitted different ways that were actually functionally broken.

- Operators tend to fire off just tons of requests to many projects. A relatively low traffic project I work with that might have a pull request every couple of months woke up with 50 pull requests from one guy that were opened over the course of an hour. The operator had pointed at the issue tracker (which admittedly had poor issue hygiene, resulting in issues open that should have been closed) and said make a pull request per issue to fix everything. One example was a 15 year old issue asking to change the project to support python 2.4, and since then the project had moved to require python 3.9, but the LLM still submitted patches around the specific examples of python 2.4 incompatibilities, despite it being ugly and also useless since so much more of the codebase was python 3 only. Several issues that had been fixed but not updated in the tracker had a pull request to 'fix' it.

- Fixing issues that weren't an issue. They pull a project and ask llm to do a code review and then submit pull requests based on what the LLM represents as needing changes.

So tons of volume, useless changes, changes with side effects...

The main issue is that CodeGen enthusiasts that were formerly intimidated by code syntax and toolchains think they can finally make an impact. The issue being is that code syntax and toolchains are the least of the challenges associated with good software. So CodeGen can significantly mitigate the tedium of those items, but now you have to contend with people that formerly were filtered by the intimidation.

Slashdot Top Deals

Basic is a high level languish. APL is a high level anguish.

Working...