English definitely needs more clues for pronunciation. Plenty of homographs could have been cleared up with diacritics. Wind/Wind, Bow/Bow, Sewer/Sewer, etc.
I actually have been using claude to go through all my old projects and review from a security perspective.
It flags a heap of things that I never considered, mainly because a lot of my projects were ad-hoc solutions to various issues that were written in a hurry and never intended to be visible to the general internet. But it also has been suggesting architectural and robustness changes that have some value, as a lot of stuff I wrote grew organically and weren't structured particularly well for future growth.
He's using a "thorn" cuz he's so tistic and awesome.
The poster's stance is that one day they hope to see thorns in AI generated text.
This is probably quite difficult to actually happen, as LLMs will see the characters as a spelling mistake compared to their general corpus of text and correct them.
In the meantime it makes their posts difficult to parse and irritates other readers, so surely this can be considered a win for everyone in the fight against AI. /s
Privatisation of a service that is a hard requirement for the dole means that there is no need for those providers to provide quality outcomes for the people forced to use their services.
Edit: oh, there are "requirements" in place for these companies to get their money. This just means that it's an endless game of effort minimalisation for employment companies so they can extract maximum profit (See also: the current Aged Care debacle). Nationalise the jobs system, let's keep that money in-house for a better outcome.
You're typing your comments using a blob of goo with about a hundred million neurons in it that cycles under a hundred hertz and draws less than 20 watts.
I don't think that we'll be running packs of goo in our PCs any time soon. But I do think some entirely different way of looking at the problem will emerge that will reduce computational requirements by many orders of magnitude. And it won't involve gigantic statistical engines trying to find the best average response to a question.
Luckily hydrogen floats upwards pretty quickly. So paradoxically, storage tanks are safer the less protection they have around them. Or at least, above them.
I'm just waiting for the closed-source AI industry to have their Black Swan moment.
Something's going to come out of left field from the open AI community and all that investment in proprietary models and mega-compute is going to be rendered useless.
Surely there should be settings in their NTP clients regarding skew as well. If you're trucking along and then your time server says, "Hey I know we've been sync'd within 3 milliseconds for years now, but you just need to step the time back 19.8 years real quick for me", then that should raise a tiny red flag with your client?
that unions are “not meritocratic,” “prevent innovation,” and “hold back earnings of top performers.”
When they make comments like that, they always assume that they are the "top performers", getting the best deal already (edit: or on track to be one of them in the future). That assumption is usually wrong.
You can generally go with the rule of thumb of "one foot per nanosecond" for the speed of light.
Signals rattle along data lines a little slower because they are contained on a circuit board and not in free space, so it's more like "150mm per nanosecond" is the metric equivalent of propagation delay.
That sounds pretty fast - and it is! It's like 50-60 percent of the speed of light.
But your average 3GHz multi-core CPU is doing a half dozen instructions per nanosecond. That means if you have your RAM over here and your CPU over there on your motherboard, you're going to have wait a measurable, impactful, amount of time for data to go back and forth between the two.
So the mobile/Apple idea of sticking your RAM directly on top of your CPU has some merit.
English definitely needs more clues for pronunciation. Plenty of homographs could have been cleared up with diacritics. Wind/Wind, Bow/Bow, Sewer/Sewer, etc.