At least read the summary! "declining emissions in the travel, cement and steel industries."

I didn't get into P vs NP until my second year of college.

The real answer entirely depends on if they succeed or not.

If they manage to build real, strong AI, then it won't be a bubble. If they manage to replace a significant amount of the workforce with automation, then it won't be a bubble. The LLMs have already proved useful in some areas, but probably not enough to justify the valuation.

If it's mostly vaporware, then that bubble will pop hard.

In particular, I don't think there was any significant population that described themselves as woke. It was a pejorative from the beginning.

The al jazeera article means that births have been declining since the 1980s, which is true and obvious if you actually had read it.

Such as high-resolution image editing and high-definition video editing. Compared to a web browser, these aren't quite as amenable to splitting an application into numerous "content processes," each with their own separate 2 GB RAM.

For a while, Linux supported an x86-64 ABI called "x32" that limits each process's address space to 2 GB so that more pointers will fit in the processor's data cache. It didn't become popular, in part because of a need to load three versions of the system libraries: 32-bit i686, x86-64, and "x32". In addition, porting x86-64 applications to use less pointer-heavy containers gave most of the cache advantage that "x32" would have provided. This includes switching from linked lists to gap buffers (or other dynamic arrays), from B-trees to T-trees, or from pointers to indices in a pool. Rust in particular has encouraged use of appropriately sized indices as a workaround for the borrow checker.

There's a widespread misconception that a 32-bit operating system is limited to 3 GB of physical RAM. I think this comes from Microsoft's practice of requiring drivers for 32-bit Windows Server to support PAE as a condition for certification, but not drivers for 32-bit Windows desktop. I seem to remember 32-bit desktop Linux being more PAE-friendly. PAE and content processes are how Firefox for 32-bit Linux managed to hang on this long.

Each function could be loaded the first time the user uses it. The device has to be online to query what is in stock at any given moment anyway. And I'd be interested in others' speculation about why the client side of the most widely used functions can't all fit in (say) 5 MB, which is twice the size of Doom.

I accept that, adding a clarification that I suggested the solution for the purpose of asking other people what these companies might know that I don't.

Where are you seeing anti-china war mongering? I haven't seen it.

The population has been dropping three straight years, I don't know where you found that AI site.

As for the economy, the article and even the summary says clearly:

It's an indication of economic retraction.

Traditional Saudi Arabian architecture is based around keeping things cool. Like the high walls in this building complex keep everything in the shade, and retain the coolness from the night as much as possible (because hot air rises, the cool air stays in the building). At the same time, it still allows natural light which overall makes a very comfortable effect.

Having a line allows you to enforce hierarchy. The people at one side will never want to go to the other side, that's where the lower class people are.

Reflecting on that is instructive. Either:

• there is an easy way to verify that LLM output was real and verifiable and useful, and if we implement that, we eliminate the useless or incorrect outputs, making the LLMs way more useful,
• there is an easy way to verify that LLM output was real and verifiable and useful, but if we implement that, we show that all the answers are either incorrect or useless, and people lose confidence in the LLM, or
• there is no easy way to verify that the LLM output is real and verifiable and useful, and we're stuck having to verify the slop manually.

The fact that the verification processes haven't been implemented, means that either there is no way to verify the output, or the verification process would reduce confidence in the output rather than increasing it.

Now it's possible that there is *currently* no way to verify the output, but that we might come up with a good verification process in the future. Once we're in that future, we can then take the chance that we end up on the first possibility.

Wikipedia officially requires articles to summarize their sources from a neutral point of view. However, Wikipedia did become overtly political with the PROTECT IP blackout of January 18, 2012, in protest of a proposed law seen to threaten Wikipedia's existence.

The first time you add a website to your home screen, it installs the website's service worker. You have to use the Internet for that, just as you have to use the Internet to download an application from Apple's App Store.

And I'm curious about what the blockers for even a partial PWA implementation have been during each of these 12 years.

All I've been asking is what features of Grab combined with missing features of PWA likely led to their continuing to choose native apps.

I don't see where I "assume[d] to know better than Grab".

Even when you talk about users, it's only to dismiss them.