There are plenty of places where not having a car isn’t even a possibility. If I didn’t have a car, not only would I be unable to work, I’d probably also starve to death, or perhaps have to eat gas station food the rest of my life.

Sa aide pas que 90% dla TV que ben du monde ont grandis avec avant l’internet etait en francais de france. Jte dis derniere fois chu allé a Montreal chu resté surpris comment lmonde parle ben. Pas comme en france, mais pas ben loin…

on la demandé, sa juste pas passé heureusement…

That’s fair, it’s personal preference I suppose. If ever you’re interested, remember that there are always cheats/mods that can make the game easier if you want to experience the world and story.

They don’t have to be, I feel like their reputation might be what stresses newcomers to the genre more than the game itself.

I played it when it came out and while it was a fun playthrough and I’m glad I played, it’s nowhere near factorio on replayability. It also feels a lot more shallow, like they put more time into the visuals rather than actual game mechanics. And in the end what killed it for me was the performance. On factorio you can still have decent fps/ups in a 1k hour megabase, satisfactory in the other hand gives up pretty quickly. Mod support is great compared to most games, but doesn’t really come close to factorio.

Which is exaxtly what I said, that it’s fast enough for most use cases.

In theory though, you will “gain performance” by rewriting it (well) in C for literally anything. Even if it’s disk/io, the actual time spent in your code will be lower, while the time spent in kernel mode will be just as long.

For example, you are running a server which reads files and returns data based on said files. The act of reading the file won’t be much faster, but if written in C, your parsers and actual logic behind what to do with the file will be.

But it’s as you said, this actual tiny performance gain isn’t worth it over development/resource cost most of the time.

How are they ignorant? It’s a known fact that java is slow, at least slower than some others. Sure, it’s still fast enough for 95% of use cases, but most code will run faster if written in, say, C. Will have 10x the amount of code and twice as many bugs though.

Back in my day people worked 16h days everyday and had no time for math or computers. And that was JUST FINE.

Which is fine, only it might confuse whoever then has to maintain your code.

Isn’t that guy to the left the same mexican kid that fed Eric a cum-flavored burrito?

n is genrally the max though. “From i=0 to n” is used in math all the time.

It still runs, for the time being

Which I believe doesn’t work on all GPUs.

Or at least run it in the test database first.

Or run your updates/deletes as select first.

If you’re using X11, you can use xkill: https://en.m.wikipedia.org/wiki/Xkill

You can bind it to a key in gnome/kde (not sure how they handle custom keybinds. Otherwise add a call to xbindkeys to your .bashrc or equivalent). It kills any window you want, responsive or not.

As for the terminal, I don’t think you can send SIGKILL, but ctrl + \ will result in a core dump if you’re using bash.

Is there any reason to use :w other than it being the default? I have mine mapped to CTRL-S and it makes sure to keep me in insert mode if I was in insert mode. Feels way faster and easier to spam than the 4 key presses it takes to execute “:w”.

deleted by creator

Cooked onions are fine, but raw red onions in salads give me terrible headaches, I always feel bad picking them out.

That depends how you “try to close the program”. Top/htop/btop often SIGKILL by default. As for closing it legitimately, it depends on your WM and xorg vs wayland. On my DWM setup, I have a keybind for a graceful shutdown and one for SIGKILL.