It's doesn't sound like a successful business venture if you're having to increase operation expenses at this rate and not be raking in the revenue.
Yes, Google is profitable now. Tremendously so. But they're at risk of losing revenue and ceasing to be profitable as people cease using Google search and switch to asking questions of their AIs. So to retain their position as the place people go first for information, they have to stay ahead of the AI race. Well, they could also just sit back and wait to see if their competitors are overwhelmed by the query volume, but that risks losing traffic and then having to win it back. It's much better to keep it. And Google is better-positioned to win this race than its competitors both because of its existing infrastructure and expertise and because it already has the eyeballs.
In addition, you seem to be assuming that doubling serving capacity means doubling cost. Clearly Google is not planning to increase their annual operating expenses by 1000X. As the summary actually says in the third paragraph, Google is also going to have to improve efficiency to achieve the growth rate, with better models and better hardware. This is what the AI chief is challenging the employees to do; he's not challenging them to write bigger OPEX checks, that's his job.
I'm not in the homeschooling universe, but I have yet to meet a second-generation homeschooler. Like, anyone I know who was homeschooled sends -their- kids to school (public, private, parochial, boarding, single-sex, co-ed) - anything but homeschool. Thoughts?
I know a few. I don't know what it may or may not mean. It may be relevant that the ones I know used a community-based approach, where groups of homeschooling families worked together to create something akin to a school, with different parents teaching different subjects. This meant that while the kids socialization groups were small, they did hang out with and learn with other kids, not just their siblings.
That there is no evidence to support it does not mean it cannot be true. But it should inform your assessment of probabilities.
It's more than that. Research into the possibility of a link between vaccination and autism has been done, and no correlation found. This is evidence that there is no connection and it's entirely different from a case where no research has been done. One is evidence of absence, the other is absence of evidence. The GP is equating them, but they're not remotely the same thing.
...I want a statement that autism is created by the Flying Spaghetti Monster. For reasons only He understands, He sometimes reaches out with his noodley appendage and gives kids autism.
Is that true? We don't know, we haven't rigorously investigated it, have we now? Since there's exactly as much evidence to support the FSM as vaccines causing autism, the CDC has a duty to mention both possibilities.
Show me all of the studies that have evaluated the correlation between FSM action and autism. There has been a lot of research on the possibility of a correlation between vaccination and autism, and no evidence of correlation has been found. There is an enormous difference between "We've looked hard and found no connection" (evidence of a negative) and "We haven't looked at all" (lack of evidence).
In addition, there's no need for the CDC to debunk a claims that are not being made, or non-harmful claims. To pick a less-ludicrous example, there's no significant population claiming that eating grapes causes autism, so there's no need for the CDC to address it. Further, if there were an anti-grape lobby touting a connection with autism, the CDC probably still wouldn't need to address it because some people avoiding grapes doesn't create significant health risks to others.
But there is a significant population claiming -- against strong scientific evidence -- that vaccines cause autism, and that claim is causing them to reject vaccines, which does create significant health risks for others. So, the CDC absolutely does need to address it, since public health is their job.
Your analogy is terrible, in every way.
Compared to what was available before, it is quite impressive.
The negative feedback is prompted by the fact that AI is constantly being shoved into every one of our orifices 24/7 by every vaguely tech-related company as if it was the second coming of Jesus. To justify that amount of social pressure, it would indeed have to be quite a bit better than it actually is, and that's why people aren't impressed.
It's not intelligence. It is not acquiring new behaviors and ideas, but regurgitating old ones in ways it often cannot verify or test. That detachment from reality flies with management, but the rack-and-file can't afford such liabilities.
We don't need large-scale language models to generate sophisticated fabrications. We need small, efficiently fluent interfaces between humans and proven tools and data. The market is going to have to correct to the actual right-sized value of the technology.
In the US, you can drive 800 km as see little more than asphalt and coyotes between the beginning and end
Bullshit. I live in the western US and have regularly driven through some of the least-populated areas of the country, but I've never seen an area you can go 500 miles without encountering any infrastructure. You might be able to accomplish it if you take careful note of where the truck stops are and go out of your way to avoid them, but on any realistic route you'll encounter truck stops -- if not towns -- at least every 150 miles.
As for charging infrastructure, if you stay on the interstates I don't think there's anywhere in the country you can go more than 100 miles without finding a Tesla Supercharger. Those aren't designed for truck charging, but this demonstrates that building out the infrastructure isn't that hard.
"Whitehouse prepares document to force yet another fight in the Supreme Court."
These day's it's quite obvious that the only line in the constitution that any republican has ever read is the 2nd Amendement. And even then they didn't read it properly.
They certainly seem to have completely missed Article I. You know, the part that says that the legislature makes the laws? Even if you think restricting AI regulation to the federal government is a good idea, the right way to do it isn't with an executive order to set up a DOJ task force aimed at litigating state AI regulations out of existence based on complex legal theories about interstate commerce. The right way is for Congress to pass a law barring states from regulating AI. This is simpler, cheaper and should invoke public debate about the issue, which is how things are supposed to be done in constitutional republics.
I don't even think Trump is taking this route because he and his advisors don't believe they have the votes for it. I think they're doing it this way because they don't even consider governing through legislation rather than through executive power. Granted that Congress is fairly dysfunctional, but they actually can and do make laws... and the way to fix the dysfunction is to work the system.
"It's my estimation that every man ever got a statue made of him was one kind of a son of a bitch or another." --Malcolm Reynolds
(Ironically applies well to Joss Whedon himself. Kind of wonder if one of the show writers was thinking about Joss when they wrote that...)
The only single-source point of failure is me.
Why does he keep doing this?
You mean, why does Linus keep agreeing to be interviewed, and then reply to straightforward questions with the obvious answers?
What would you rather he do? Refuse to be interviewed, or maybe make up unexpected answers just to be edgy?
The above was already quite long, but allow me to add a bit
I spent a few minutes looking for the state of the art in C++/Rust interop for contexts that don't have a nice intermediary like binder. It turns out that the situation isn't as bad as I thought. The CXX project enables automatic generation of bi-directional definitions between Rust and C++ and is being used at scale by the Chromium project and that seems to be going pretty well.
There's also a Google-funded Rust Foundation project to define a better solution, though I don't see what, if anything, has happened since it was announced last year. Hopefully that's because there's a small group working too hard to waste a lot of time talking about it.
The reason I went to look is that my new team (I left Google a couple of months ago) might need such a thing. I've been asked to define an API that would benefit from being implemented in Rust and usable from C++ and Rust.
Someday your prints will come. -- Kodak