Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Re:Seems healthy. (Score 1) 25

I can see the argument that Nvidia has no obvious advantage in LLMs that would make them want to set up their own operation; it's basically everything else about the situation that would make me jumpy if I had bet on Nvidia.

"Investing $100 billion in OpenAI's spend $100 billion on Nvidia stuff initiative" sounds, at worst, like a slightly more legal version of the trick where you shuffle stock around between business units or stuff the channel and book that as sales because you suspect that your real sales numbers will disappoint; and, even if it's not quite that dire, Nvidia being willing to get paid in faith rather than in other people's money (or shift the stock to one of their customers that actually has money) looks very much like an indirect price cut, which gives the impression that either demand is outright softening, and Nvidia has units that it can't simply immediately shift to customers who are actually paying cash right now; or that Nvidia feels the need to help fill the gap between OpenAI's seemingly unlimited appetite for doubling-down money and the, sooner or later, limited supply of VC nose candy.

That said, it's not entirely novel; Nvidia's current holdings are something like 90% Coreweave(under 10% of Coreweave's total shares; but Coreweave shares are the bulk of other-company shares Nvidia holds); and they have an agreement with them obliging them to purchase any unused capacity through 2032; so they've been expressing confidence in AI-related companies and/or trying to keep the music going by paying some of their more fragile customers' bills even before this.

It could be that Nvidia isn't even trying to diversify; but the history of bad things happening when people underestimate correlated risks also doesn't make me feel great about the situation: Obviously it's going to be a bad day at Nvidia if 'AI' cools; stock price will take a hit and they will be left holding at least some inventory and TSMC and other vendor commitments; but it's going to be a worse day the more of their hardware they sold in exchange for stock in 'AI' Nvidia buyers, rather than in exchange for money, since the fortunes of those companies are going to be fairly closely correlated with Nvidia's own, albeit likely to swing harder and have further to fall.

Comment Re:Return to office (Score 2) 109

Fairly obviously, this almost certainly won't result in many thousands of H1-Bs each paying $100k to the US government each year; it'll result in many thousands of jobs that would have been paying US taxes on their wages, and then paying for accommodation, a car, for leisure, and whatever else into the US economy paying their taxes and spending their wages in wherever the new (or expanded overseas) office is instead.

Yep. Google, at least, started this transition during Trump1.

The company has long had engineering sites in various other countries, but until Trump1, the primary focus was always on cities where Google thought the global talent would want to live. Low cost was clearly not the driving factor in the selection of London, Zurich, Munich, Tokyo and Sydney, to name a few of the ones I visited. US sites were similarly not located in low-rent areas. The workforce was definitely global, because Google wanted to hire the smartest people and while the US does have its share of brilliant minds, the US has only 4% of the world's population, so most teams -- even in the US -- ended up being minority American.

During COVID, Trump leveraged the health crisis to essentially halt H-1B approvals and renewals. This caused significant problems for Google. My own team lost a few people because they couldn't get their visas renewed and had to go back home. Some chose to move to other Google sites overseas where Google could get them a work visa, others simply went back to their home countries. One trans woman on my team was in a particularly tough spot because her home country (India) refused to renew her passport because it didn't recognize her new gender. She couldn't get her visa renewed, couldn't go home to India, and also couldn't move to any other country with an expired passport. Luckily, she had a lot of nVidia and Google stock she'd been saving up to buy a house, and by cashing that out had enough free cash to get an EB-5 "investor" visa. It's good to be rich, of course.

Anyway, Google saw what was going on and, anticipating future troubles of the sort, refocused its overseas office plans on building up teams and infrastructure, especially in India which provided so much of Google's engineering talent anyway, with the intention of shifting whole projects and workstreams there. The company had long required a significant percentage of all staffing growth to be in the US (and especially in the bay area), but that policy was scrapped and replaced by its opposite: A certain percentage of all new roles must be based overseas.

It's still the case that the center-of-mass of Google is in the bay area, but the company is actively working to change that, to build up overseas capacity, and not just groups of junior engineers under a manager whose role is to pass them detailed requirements for implementation, but instead full teams with highly-skilled and experienced senior engineers and managers able to take full ownership of major product areas and move them forward.

Trump's latest moves will just accelerate this transition. The result will eventually be a hollowing out of the company's US capacity, and therefore a reduction in the need to hire American engineers. Lucky for me, I'm leaving Google for a startup and anyway am not far from retirement. Between this stuff and AI being poised to replace junior engineering staff it's a good time to be getting out.

Also, I think it will soon be time to start shifting investments out of the US.

Comment Re:Problems (Score 5, Insightful) 103

That's about the only thing that such a centrally-managed setup gives, it forces a shift in the bureaucracy to make the oligarchy's mandate happen. The problem is that this may not account for things like environmental degradation, harm to the general population and other issues surrounding personal rights, etc.

Something of a compromise approach can be reached in democratic countries, but it requires all of the stakeholders from the federal officials down to the local building code inspectors during the construction process to be onboard.

What China does for 'the people' may well not be good for individual Chinese persons. Similarly to what the Soviet Union did for 'the people' was often quite harmful to individual persons.

Comment Re:Please stop... (Score 1) 35

Note to CNN editors: You really should recognize that the figure of "186,000 miles" is approximate. Translating it to "299,337 kilometers" implies a degree of precision which in this case doesn't exist. Calling it "300,000 kilometers" would be much better.

It just occurred to me that the literality of the conversion may be an AI artifact, in which case we can expect a lot more of this crap.

The same goes for the size. It's pretty clear that scientists were ballparking its size in metric units, and converting the fractional units with that much precision was stupid. Calling it "about a hundred feet or thirty meters" would have been a lot better.

And this sort of thing happened long before AI was in the picture. People don't understand significant digits, and it's worse when it comes to estimates.

As for distance away, it would have been better to include something like its closest approach puts it around 3/4 of the distance to the Moon.

Comment Re:The ultimate spy tool (Score 3, Insightful) 22

Perhaps more troublingly; they'll allow facebook to see what the people you see do.

My good-faith advice to anyone who is considering letting zuck into their refrigerator just to solve the crushing problem of what to cook with available ingredients or whatever would be "probably not worth it"; but that's ultimately a them problem one way or the other.

The trouble is that much of the pitch here is that you are supposed to provide footage as you wander around; merrily making the you problem everyone else's problem as you do so. And, yes, 'no expectation of privacy, etc, etc.' but there's a fairly obvious distinction between "in principle, it wouldn't be illegal to hire a PI to follow you around with a camera while you are in public", which involves a typically prohibitive cost in practice and "you paid them to upload geolocated footage, nice going asshole", where the economics of surveillance change pretty radically.

If people want to outource their thinking to facebook themselves I'd have to be feeling fairly paternalistic to intervene; but given that the normalization of these is, pretty explicitly, about facebook having eyes on everyone I can only hope that 'glasshole' continues to be a genuine social risk to any adopters.

Comment Come now... (Score 1) 72

Anyone who puts their money behind wildfire smoke as the leading public health threat of 2050 is just showing their abject lack of faith in the potential of malice and incompetence. Who are these faithless degenerates to tell us that we can't re-introduce enough trivially controllable infectious diseases or deregulate enough toxin smelters to outmatch some trees?

Comment Re:Sounds doomed... (Score 1) 19

Sorry if I wasn't clear; that's the part I have deep concerns about getting done. My impression has been that(while, in theory, people are supposed to be averse to spending money) it's much easier to get funding for novel or sexy initiatives, especially if they promise to be magic-bullet solutions, than it is to push through money for boring stuff, even if it's low risk and abundantly proven; and the risk these recommendations address seems to sit firmly on the unfavorable side of that.

"We need to do a bunch of fiddly changes to eliminate quirks of build reproducibility, and generally have more eyes on important software" is not a terribly intimidating project in terms of novelty or risk; but "basically, just spend more on reasonably competent, reasonably diligent, software engineers than it seems like you strictly need to, in order to make improvements that outside observers could easily mistake for status quo, forever" is a deeply unsexy project. It's a much better project than "Agentic digital transformation" or something; but that's the sort of likely failure that someone looking to spend company money to look like a thought leader on linkedin will practically trample you in their eagerness to approve.

Comment Re:smoke and mirros (Score 3, Interesting) 62

As best I can tell; most of the complaining about freeloaders is sideshow in the battle over who deserves subsidies, not objections in principle. I'm less clear on whether there's also a positive correlation between whining about the subsidies going to people who aren't you and actively seeking them yourself; or whether the cases of people who do both are disproportionately irksome and so appear more common than a dispassionate analysis of the numbers would reveal them to be.

Comment Re:Do it yourself (Score 1) 85

Cppcheck apparently knows "hundreds of other rules covering a multitude of language aspects" so you don't "have to mentally apply against every single line of code you write."

Cppcheck doesn't flag anything in Waffle Iron's example.

It also doesn't find anything wrong with:

std::vector<int> vec = {1, 2, 3, 4, 5};
auto it = vec.begin();
vec.push_back(6);
std::cout << *it << std::endl;

Which is another common example of how you can write memory errors without using C++ pointers.

Comment Re:There is already a safe subset of C++ (Score 1) 85

In the sort of places where MISRA and similar coding guides apply, yes, never allocating memory is expected, because once dynamic allocation exists you can't guarantee that you won't die with an out-of-memory error and similarly can't guarantee any time bounds on how long an alloc and dealloc will take.

Sure, so C++ is safe as long as it's used in a way that makes it incredibly painful. Sounds good. Let's just require all C++ code everywhere to be written that way. Rust usage will skyrocket overnight.

Comment Re: Is there anyone here that voted for Trump (Score 1) 263

It is hard to have fair democracy with winners take it all.

For a really rigorous definition of "fair", it's impossible to have fair democracy at all. Arrow's Theorem demonstrates this to a large degree, although many have argued that some of his fairness axioms are excessive. More recent research has concluded that fairness is the wrong standard, because there's no way for an electorate's "will" to really be fairly represented by any electoral system, not in all cases. Some systems can do better most of the time (and "winner take all" is particularly bad), but all systems fail in some cases.

What we need to aim for instead of fairness is "legitimacy", which is more about building broad acceptance of the system than about fixing the system itself, though it's easier to build acceptance for better-designed systems.

Having the country's top politicians continually claiming the system is unfair and rigged is, of course, the worst possible thing to do if you want to build support for the legitimacy of the system.

Comment Re:Jokes on you (Score 2) 263

Precisely none of those books were ever banned.

I decided to check :-)

According to the Book Censorship Database from the Every Library Institute, both "Of Mice and Men" and "Adventures of Huckleberry Finn" have been challenged, but only "Of Mice and Men" was removed, though "restricted" is more accurate. The Birdville Independent School District in Texas removed the book from general access, allowing access only to the AP English class, and the Indian River County Schools in Florida restricted it to high school students.

No Doctor Suess books were banned, although Suess Enterprises voluntarily ceased publication of six books.

Comment Sounds doomed... (Score 2) 19

This seems like the sort of advice that is going to be exceptionally hard to get followed because it's mostly so dull.

There can be some interesting futzing in principle to keep unnecessary sources of variation from getting folded into build artifacts, normally followed by less-interesting making of those change in practice across a zillion projects; and basically anything involving signing should at least be carefully copying the homework of proper heavyweight cryptographers; but most of the advice is of the "fix your shit" and "yes, actually, have 10 people, ideally across multiple orgs, despite the fact that you can get it for free by pretending that the random person in Nebraska won't make mistakes, get coopted by an intelligence agency, quit to find a hobby that doesn't involve getting yelled at on the internet for no money, or die" flavor; which is absolutely stuff you should do; but the sort of deeply unsexy spadework that doesn't have magic bullet vendors lobbying for it to get paid for.

Slashdot Top Deals

In any problem, if you find yourself doing an infinite amount of work, the answer may be obtained by inspection.

Working...