Also, where did you find the invite to that Discord? It doesn’t seem to be related to the instance
Did you respond to the right person?
Also, where did you find the invite to that Discord? It doesn’t seem to be related to the instance
Did you respond to the right person?
Then I think you’re misinterpreting OP’s post. They don’t want to create a “pro Palestinian server”, they want an Arabic server. They mention Palestine because of the timeframe: more active Arabic speakers –> possibly more active Arabic lemmy users. Hence my question about Ukraine.
Would you be against a Ukrainian lemmy server too?
Just create the server dude. There are a bunch of instances related to specific languages, games, TV shows, countries, regions, what have you. It’ll show up at https://join-lemmy.org/instances and Arabic speakers should be able to find it. You can then promote it on other social media. You can also suggest it on other social media if you don’t believe you can be an admin :)
Good luck!
Pulling an Apple without the infra
Probably easier to archive as well without all the bs javascript stuff that new reddit is doing.
Space Karen? Is that a user?
Have they postdated their toots? Their first toot is from 27 july 2021?? @ltrlp have you been on mastodon that long?
Don’t need one. If you can read C/C++ you can read the kernel code. And in most cases, you won’t have to, as the problem is probably in a component in the distro. Those are written in python, ruby, or bash, which are all much more readable than C/C++.
No such luck on windows
Indeed, nothing is perfect, but closed source stuff doesn’t provide a lot of recourse. If you have a linux expert in your team, they can investigate and if need be even dig into the code of linux itself to find the core issue. Microsoft doesn’t provide anything even remotely similar.
With these updated routing tables, a lot of people were unable to make calls, as we didn’t have a correct state
You’re relying on windows for critical infrastructure? Are you nuts?
Here’s the difference between virtualisation and containerisation:
virtualisation –> virtualise / emulate an entire machine (including hardware). Meaning you’re running a second virtual computer (called a guest) within your own computer (called the host)
containerisation –> cordon off parts of your system for a group of processes aka contain them to parts of your system.
Imagine if you’re in a factory and you have a group of workers that handle generic tasks (CPU) and another one graphical tasks (GPU), a storage room (RAM), and an operator (the operating system)
Virtualisation is the equivalent of taking some generic workers, letting them build a separate factory within the existing factory, and act like another factory. They may even know how to translate instructions from the host factory to instructions understood only in the guest factory. They also occupy a part of the storage room. And to top it off they of course have their own operator that communicates with the host operator before doing virtually anything.
Containerisation is the equivalent of the operator starting processes that either do not know how large the storage room, generic worker pool, nor graphical worker pool are, or only having access to a section of the aforementioned. Basically contains them in their own view of the world with very little overhead. No new factory, no new operator, no generic workers that behave like graphical workers or can only understand certain instructions.
In terms of distribution, virtualisation is like passing around mini-factories to other factories (or optimally descriptions of the factories needed to execute the instructions within the file). Containers are really a bunch of compressed directories, with some meta information about which process should be started first (amongst other things) and that processes and its subprocesses having a limited view of their world.
Containerisation was popularised on linux (even though BSD had it first IIRC), which is where the operating system primitives and concepts were made to enable what we now know as Docker. Since virtually all containers in existence these days require linux due to how they are created and the binaries they contain, running docker (or anything that supports containers) requires virtualising a linux machine within which containers run.
This comes with its own hurdles and of course is slower than on linux.
With vulkan support and wine, running windows games on an M1 using linux is already possible. How fast that will be is another question.
It would reduce the amount of work needed by developers as at minimum all they’d have to do is build something that uses Vulkan and it would run on Mx hardware thans to linux. For better support, they could compile their games on any ARM64 hardware and that’d remove the need for an emulation layer (x86 -> ARM).
I’d say this might actually be what unlocks a real gaming experience on Apple hardware without relying on (DX ->) Vulkan -> Metal for graphics, x86 -> ARM, and windows -> darwin. Nothing would have to be done for graphics (vulkan), x86->ARM (if it’s only compiled for x86), and windows -> Linux (which already has tons of work and the major support of Steam, while Apple just started with their wine fork for this).
It wouldn’t surprise me if an “apple gaming” community would have a post pinned “install linux to game on Apple” in a year or two.
Is it running in a single docker container or is it spread out across multiple containers? Maybe with docker-machine
or kubernetes with horizontal scaling, it could absorb users without issue - well, except maybe cost. OVH has managed kubernetes.
Oooh, I had no idea https://jlailu.fr linked to a discord! It really was just supposed to be jlai.lu :D No idea who owns the domain but it just redirects you to discord for /r/rance . Must be some jokester.