the fact that the Cyc organisation "failed" to create a general knowledge graph of all human knowledge does not mean that GraphRAG is "not a promising approach". their efforts predate GraphRAG by a _long_ way, and is not related to modern efforts to augment LLMs

i also did not say that this is "easy". indeed i explicitly said that it's "not a magic bullet", and that you need a "high quality knowledge graph" that "requires careful work to prepare and curate".

modern systems using the GraphRAG approach generally are using much smaller knowledge graphs, carefully prepared based on a very specific set of knowledge, such as a support knowledge-base. when done right they produce significantly higher quality results than an LLM alone.

it's still early days for the GraphRAG approach. the first research papers only came out a year ago. it is far too early to decree the approach as "not promising"

An LLM by itself is indeed inherently limited. They are essentially language prediction systems, so their base functionality is to predict what word should come next.

Couple an LLM with RAG (Retrieval Augmented Generation), an approach for combining an external knowledge store with the LLM's ability to generate responses to statements, and you can enhance LLMs quite effectively. Research in this area has been happening over the past 4 or 5 years.

A very promising technique that has emerged this year is GraphRAG, which uses graph databases as the knowledge store.

When you have a suitable graph knowledge-base, your LLM can cite its sources - this greatly reduces problems of hallucination and helps address issues of "accountability".

It's not a magic bullet - you need a high quality knowledge graph as part of your system, and that requires careful work to prepare and curate.

Maybe that's the case where you live but in most of the civilised world a salaried employee works for a restricted number of hours. In Europe (including the UK) that is legally restricted to 48 hours per week. (Overtime is possible, but mandatory overtime is, essentially, illegal.) See the European Working Time Directive.

Are you a fossil fuel shill? Because this comment really reads like that, and I'm surprised it's been moderated so highly.

By itself, yes, wind power isn't a great source of electricity. Neither is solar. Both are by their nature unreliable and incapable of providing a sustained supply. That does not make them useless. Instead this is why they should form part of a mix of renewables contributing to an electricity grid.

A grid should have ways of storing excess generation to put that power back into the grid when renewable sources aren't able to contribute. Historically this has been pumped hydro in many cases, but there are other options now available including, but not limited to, battery storage.

Another aspect of having an electricity grid is to send electricity over very long distances, potentially thousands of miles, which reduces the need to store excess power as via the usage of the grid power needs and production can be balanced.

This balancing may not be perfect, and some of the captured power may be wasted, but is that really a problem? Capturing wind is effectively free whereas burning gas has a high cost in terms of the gas input and the carbon dioxide output. (Yes, wind isn't completely free - there's sunk cost for the windmills, and ongoing maintenance costs, but you have similar costs for running fossil fuel plants.). Does it really matter if some of this captured electricity gets thrown away?

Microsoft ported their BASIC to loads of different CPUs. Commodore BASIC and Applesoft BASIC were both produced by Microsoft. They covered all the popular CPUs back in the day (8080, Z80, 6800, 6809, 6502, etc).

So yes, they started by selling a BASIC that ran on the 8080, but they didn't just stay there.

Interesting side-fact here - Windows NT started out targeting platforms other than the x86 - the x86 version was a port. They did this because they didn't want to be locked into Intel.

Ctrl-+A and Ctrl+E work fine for me on the Mac version of VSCode...

I wonder if you've installed some kind of extension that's re-defining those key combos.

Apple Maps works just fine on the web - although Apple themselves don't really seem interested in hosting a site for it, in part because they want to sell iPhones, sure, and probably they'd also rather folks use the app version as it offers slightly better OS integration.

To use Apple Maps on the web just go to Duck Duck Go, search for a place, and then click thru to the maps tab. Many other web sites use Apple's MapkitJS to show maps.

As for preferring Open Street Map, Apple is both a consumer and contributor to the Open Street Map dataset.

They told us the lag in their presentation - it's 18ms

The original iPod came out in October 2001.

At that time you could buy a Creative Nomad Jukebox C which was a HD based device with 6GB of storage, slightly more than the iPod, but it was about the size of a portable CD player, and did not have wifi. Creative had also released the NOMAD II C which had a comparable physical size to the iPod, but used flash storage, coming with 32MB. Both of these connected using USB, which was significantly slower than the firewire the iPod used.

If anything "one of the oldest Slashdot memes" here is that the iPod was in some way inferior to the competition.

An Intel-designed ARM chip could be as fast as an M1 Max... maybe a bit quicker, and have a similar power profile.

After all, part of the heritage of Apple Silicon is the team that built the StrongARM that, for a while, was owned by Intel.

Arguably Intel should never have sold that tech - but keeping it would have required them to admit that x86 was flawed, and they can't possibly do that. :D

Both things can be true.

ARM was indeed designed with a low enough transistor count and power usage to allow it to run cool enough to ship in plastic packages rather than ceramics. So yes, it was designed so that the manufactured chips would be comparatively cheap.

It was also designed to out-perform the other chips Acorn had considered as the CPU around which to build their next platform. So yes, it was designed for speed too.

FYI, pointer support on iPadOS includes mouse support too

Many of those kids however go to Instagram.

Which is of course owned by Facebook.

You're missing the point.

The "hour" that's been mentioned is a rough estimate for the amount of work that would need to be done to handle the visa application. It's not an estimated increase of the amount of time that it will take for passengers to travel through an airport.

There will be a significant increase in bureaucracy required to process all these visa applications, which has a significant cost associated with it.

As a potential visitor, having to deal with a more complicated visa application process is hassle, and not appealing. When the application process is draconian and unnecessarily invasive of the privacy of the applicant it is even less appealing.

iOS devices are not x86 based - they're ARM - so no "basic x86 code" will run on them at all.

The only place that iOS runs on x86 is in the simulator on OS X and such x86 code is not included in builds for iOS devices.

64-bit ARM is different from 32-bit ARM, and not even remotely like "extended 32-bit x86".