Ephera

Jujutsu is a Git frontend, from what I understand, much like there's tons of Git GUIs. So, you interact with it in a different way, but you still push to a Git repository and others can interact with your code by using Git.

I guess, it somewhat lessens the grip of Git, because they can hook different backend services (e.g. Subversion, Mercurial, Fossil) into this frontend, and from what I understand, they plan to develop an own backend eventually. But yeah, for now, the communication standard is still Git.

I also have to say, I feel like many people don't realize how much dexterity and skill it takes to constantly crank that camera.

The twin-stick camera controls are a terrible solution, even if they may be the best we have. They are a major barrier for entry IMHO. With 2D games, you could hand a controller to someone, who doesn't play games very much and they'd still typically be able to play along. But with 3D games, that's so much harder, because now you have to press buttons and move the camera at the same time.

So, I imagine, even when the hardware became available, that various studios still tried to find simpler solutions.

That uniform actually looks extremely binary...

Yeah, that is crazy to me. I understand them wanting to make other games in between and that making those games takes a few years each. Rationally, I'm on board with the decision-making and the math that leads to this.
But that the result is a generation who didn't have an Elder Scrolls part released in their childhood, that still feels like far too grand of a concept.

If you mean a DNS sinkhole, like Pi-Hole, then that shouldn't be a problem. Pi-Hole acts as a DNS provider, so:

• It could also act as a DoH provider. Someone seems to have done this for Pi-Hole here: https://discourse.pi-hole.net/t/can-pihole-act-as-a-doh-or-dot-server/56106
• You could disable (or not enable) DoH in Firefox to make regular DNS requests at your Pi-Hole, but then your Pi-Hole can use DoH to forward the DNS requests to outside DoH providers. Pi-Hole seems to support with either cloudflared or dnscrypt-proxy.

On Android, there's also ad blocking solutions that run a VPN server on your device, to terminate certain requests that way. I'm not entirely sure how those work, but if needed, they could presumably also run a DoH provider on your device.

Ah, stimmt, das ist natürlich Quatsch. Anscheinend führt JavaScript aber den Modul-Code aus, wenn man ein Modul importiert, also vermutlich kann man den Code einfach unten an die index.js anfügen.

Und er hat offenbar die Fähigkeit, sich selbst zu replizieren, indem er weitere Pakete infiziert und trojanisierte Paketversionen hochlädt.

Das ist schon krass. Wenn du selbst eine Bibliothek entwickelst, hast du natürlich die Credentials eingerichtet, um neue Versionen zu veröffentlichen, und das Veröffentlichen will man eigentlich auch leicht automatisieren können, also würde mich nicht wundern, wenn das bei NPM mit einem Befehl getan ist.

Im Grunde ist der schwierigste Teil, den Code der Ziel-Bibliothek so zu verändern, dass Schadcode ausgeführt wird, aber wahrscheinlich kann du das irgendwo an den Anfang der Main-Funktion packen.
Und spätestens mit LLMs lässt sich sowas wahrscheinlich auch in komplexeren Fällen lösen. Da ist es ja auch egal, wenn es nur in 80% der Fällen, das Paket erfolgreich kompromittiert.

Am Strand liegen? Ich glaube, das ist so der andere Grund, warum Leute irgendwo hinreisen.

Grundsätzlich kann man natürlich auch versuchen, die lokale Kultur kennenzulernen, indem man z.B. auf den Stadtmarkt geht oder ein Dorf abseits der Tourismusziele besucht. Aber ja, wird schwer, das anderen als erlebenswert zu verkaufen.

Gezeichnet: Jemand, der auch das mit dem Verreisen nicht so wirklich versteht.

Damn, those are some long maccheroni.

What do call an ork wearing jeans?

Kind of felt like that last week. Our web-UI would automatically reload when you switched tabs, clearing out what the user had entered into a form. I started debugging, but the build times of our web-UI have been abysmal, making it extremely tedious to sprinkle log statements over the code for narrowing down what triggers the reload.

So, I decided to fix the build times first. The solution wasn't complex, basically just pull out a module into a separate library to benefit from incremental compilation, but with all the import changes and some additional restructuring, it still ended up being around 2000 lines of code changed.

Then I went back to debugging the reload problem, looked at it for 10 minutes, maybe rebuilt 3 times or so, and then made a lucky guess where I just changed one word for another and that fixed it. 🫠

"Trignometry" might be my favorite typo.