No, basically. They would love to be able to do that, but it’s approximately impossible for the generative systems they’re using at the moment
No, basically. They would love to be able to do that, but it’s approximately impossible for the generative systems they’re using at the moment
No, I’m arguing that the extra complexity is something to avoid because it creates new attack surfaces, new opportunities for bugs, and is very unlikely to accurately deal with all of the edge cases.
Especially when you consider that the behaviour we have was established way before there even was a unicode standard which could have been applied, and when the alternative you want isn’t unambiguously better than what it does now.
“What is language” is a far more insightful question than you clearly intended, because our collective best answer to that question right now is the unicode standard, and even that’s not perfect. Making the very core of the filesystem have to deal with that is a can of worms which a competent engineer wouldn’t open without very good reason, and at best I’m seeing a weak and subjective reason here.
The reason, I suspect, is fundamentally because there’s no relationship between the uppercase and lowercase characters unless someone goes out of their way to create it. That requires that the filesystem contain knowledge of the alphabet, which might work if all you wanted was to handle ASCII in American English, but isn’t good for a system which needs to support the whole world.
In fact, the UNIX filesystem isn’t ASCII. It’s also not unicode. UNIX uses arbitrary byte strings, with special significance given to a very small number of bytes (just ‘/’ and ‘\0’, I think). That means people are free to label files in whatever way they like, and their terminals or other applications are free to render them in whatever way seems appropriate, without the filesystem having to understand unicode.
Adding case insensitivity would therefore actually be significant and unnecessary complexity to add to the filesystem drivers, and we’d probably take a big step backwards in support for other languages
That’s going to be a problem whatever solution you come up with, because of the federated nature of the lemmy system.
There’s no central authority to hand out usernames, so if two people sign up to different instances with the same username, any design which didn’t attach instance name to each username would fail. The only way around it would be for each instance to contact every other instance which exists, including the ones which haven’t federated yet, and negotiate ownership of the new username, and that’s just not possible
That’s deeply unwise. Nothing you cobble together yourself using a raspberry pi is going to be up to automotive safety standards.
Anyone who sets up one of these has nobody but themselves to blame when it misbehaves and gives them incorrect information, or no information, or starts flickering distractingly, and they get done for speeding/hit a pedestrian/fail whatever inspections the law requires in their part of the world
While that sort of analysis probably isn’t impossible, it is computationally unrealistic to do in realtime on a language which wasn’t designed for it.
It’s the sort of thing which is simple in 99% of cases, but the last 1% might well be impossible. Sadly it’s the last 1% you need to worry about, because anyone trying to defeat your system is going to find them
There’s no need to leave earth, just lift it into a medium earth orbit. There are literally thousands of kilometres in between low earth orbit (where there are lots of communications, spy, navigation and weather satellites) and geosynchronous (where there are lots of communications satellites), and outside of those two there’s virtually nothing there
In principle they could have pulled out slightly, if there’s jostling and tiny movements in skull then you’d expect them to work loose over time if they’re not securely anchored
The default is as long as it is because most people value not losing data, or avoiding corruption, or generally preserving the proper functioning of software on their machine, over 90 seconds during which they could simply walk away.
Especially when those 90 seconds only even come up when something isn’t right.
If you feel that strongly that you’d rather let something malfunction, then you’re entirely at liberty to change the configuration. You don’t have to accept the design decisions of the package maintainers if you really want to do something differently.
Also, if you’re that set against investigating why your system isn’t behaving the way you expect, then what the hell are you doing running arch? Half the point of that distro is that you get the bleeding edge of everything, and you’re expected to maintain your own damn system
The question you should be asking is what’s wrong with that job which is causing it to run for long enough that the timeout has to kill it.
Systemd isn’t the problem here, all it’s doing is making it easy to find out what process is slowing down your shutdown, and making sure it doesn’t stall forever
It might not make him wrong, but he also happens to be wrong.
You can’t compare AI art or literature to AI software, because the former are allowed to be vague or interpretive while the latter has to be precise and formally correct. AI can’t even reliably do art yet, it frequently requires several attempts or considerable support to get something which looks right, but in software “close” frequently isn’t useful at all. In fact, it can easily be close enough to look right at first glance while actually being catastopically wrong once you try to use it for real (see: every bug in any released piece of software ever)
Even when AI gets good enough to reliably produce what it’s asked for first time & every time (which is a long way away for quite a while yet), a sufficiently precise description of what you want is exactly what programmers spend their lives writing. Code is a description of a program which another program (such as a compiler) can convert into instructions for the computer. If someone comes up with a very clever program which can fill in the gaps by using AI to interpret what it’s been given, then what they’ve created is just a new kind of programming language for a new kind of compiler
Not exactly. There are some species which haven’t changed all that much for millions of years, and those have certainly managed excellent adaptability.
Others, though, might find themselves evolving to cope with the climate right now at the expense of being vulnerable to some future problem. Say the climate is very hot, but in a few tens of thousands of years there’ll be an ice age. An animal which is well adapted to the ice age will probably go extinct before it arrives, having all been eaten by an animal well adjusted to the heat which is here right now.
“In the end” isn’t useful if you get outcompeted in the meantime
Perhaps not, but it would make it far easier for any sympathetic brain surgeon you managed to find who was willing to try and fix the problem for you.
The key thing is not needing that specific company to help, but needing generic expert assistance is fine
The story I heard was that charging is taking far longer than usual because of cold batteries, and people are having to change much more frequently for the same reason, and between the two the demand for chargers has shot up
I find it makes my life easier, personally, because I can set up and tear down environments I’m playing with easily.
As for your user & permissions concern, are you aware that docker these days can be configured to map “root” in the container to a different user? Personally I prefer to use podman though, which doesn’t have that problem to begin with
The satellite uplinks these devices use is very bandwidth limited, and quite expensive. I can assure you that it’s not routinely sending anything without telling you.
Source: worked in satellite comms
Podman supports docker compose just fine. You have to run it as a service, so that it can expose a socket like docker does, but it supports doing exactly that
Because a container is only as isolated from the host as you want it to be.
Suppose you run a container and mount the entire filesystem into it. If that container is running as root, it can then read and write anything it likes (including password databases and /etc/sudo)
It is guaranteed, actually. US law imposes requirements on telecoms providers to support wire taps