• 14 Posts
  • 28 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle




  • This. The guessing part comes from the time it takes to do the tasks, but you know the number of tasks. So a progress bar should only reach 100% when all the tasks are completed.

    For example, you might have a big process that performs 3 other small tasks and then finishes. You could reasonably assume that each small task is 33% of the big process, so after the first finishes you get 33% progress, then 66% after the second and 100% after the third. When the bar reaches 100%, the third task has finished, so your process has finished too.

    What you don’t know is how much time each small task takes, so if the first task needs 20 seconds and the following tasks take just 5, you’ll spend 2/3 of the time on the first 33% of the progress bar, and then the remaining 66% gets done in 1/3 of the time.


  • The launch was terrible, but there are some things that keep them apart from the rest of terrible launches.

    Cyberpunk 2077 was a really ambitious game, with a lot of new mechanics and incredible graphics. Beasts like that are really difficult to optimize for a large range of computers with different specs, so at first it ran poorly on some.

    The most notably buggy release was the PS4 one. And rightfully so. They were trying to run a truly next gen game on a console which was more than a decade old. They not only had to optimize the game, but they basically made a completely different game, with different assets and engines, which was really difficult to do. Still, it was too much for the console, especially old PS4s that were full of dust or had old fans and were overheating.

    Another important fact is that users were also pressuring CDPR into releasing Cyberpunk 2077. It was delayed at least once (maybe twice, I don’t remember), and people wanted to play the game. They probably had to choose between delaying it another time or releasing it without polishing it that much.

    I believe it was Cyberpunk 2077 that started the trend of “release now fix later” games. However, I don’t think they really did it on purpose. The game was too ambitious for its own good, and having to develop, optimize and test two basically different versions of it was too big of a task for a studio that in today’s terms wasn’t even that big. The rest of the AAA producers just realized that CDPR still won loads of money at launch, and decided to release incomplete games on purpose, after seeing that CDPR could make profits that way.

    But must importantly, CDPR did an amazing job at fixing the game, unlike many other studios releasing broken AAAs. They optimized the code, fixed most of the bugs, improved the AI massively and made the game really stable, to the point where I’ve seen it running at 40 FPS on 10+ year old overheating laptops. Even though it took a while, they still delivered the game they promised to their buyers.


  • Master/slave indicates a relationship between two things. You can have masters and slaves in mechanics, for example. We’ve also had masters and slaves for decades in the tech field. Drives and floppy readers used to be configured in a master/slave setting. And of course, you have masters and slaves in programming.

    None of these examples have anything to do with race or human slavery. They’re just a way to describe how two things interact with each other. Human slavery is called that way because the relationship between the slaves and the masters can be described by that word, not the other way around.

    It’s clear that we should stop using racist words with racist intentions. No-one argues that human slavery should be allowed. However, in this case, there’s no intention of racism in the words, and we shouldn’t stop using words just because they can be used in a racist setting. Same thing goes with black paint. It’s clear that the word black is describing a color, and it is needed to correctly describe it.




  • black0ut@pawb.socialtoMemes@lemmy.mlYes, but
    link
    fedilink
    arrow-up
    3
    ·
    9 months ago

    Afaik, they are unblockable. They are served from the same domain as the video, so if you block them you can’t see the video either.

    Instead of blocking it at the domain level, you can install adblockers on almost any platform. I recommend uBlock for Firefox and ReVanced for Android. ReVanced is also supposed to work on Android TVs, iirc.


  • The thing about parallel booting is it’s only faster in systems with lots of cores, and the overhead of the parallelized code is sometimes enough to negate the benefits in older processors.

    My machine is a Core 2 Duo lappy, which allows me to run most modern programs cheaply. However, it’s slow (even though I don’t use DEs either), and laptops are the kinds of computers you boot multiple times a day. That’s why I care about boot times. And in this case, you can see that booting with a parallelized init system is slower than booting with a “regular” one.

    Yeah, Systemd might be the new fad, but I still believe there are lots of things to learn from the simple init systems. After all, an init system should only focus on initializing a system, and it shouldn’t be as complex and complicated as Systemd is.

    I might be just another old man yelling at clouds. But hey, that makes two of us now.


  • I run Void with runit.

    I’ve tried to completely avoid systemd, and so far I think I’ve managed. It’s still a pain in the ass, because a lot of software depends on it.

    As an upside, startup time on my old lappy went from 2+ minutes on barebones Arch with systemd to just under 40 seconds on Void with runit.


  • It’s slow and heavy, and it does too many things. It’s a monolithic piece of code so big it’s getting too difficult to maintain, so it has more vulnerabilities than other alternatives. It’s also taking over the whole system, to the point where Linux systems will soon be Systemd/Linux instead of GNU/Linux.

    It’s also developed and funded mainly by Microsoft, which is also something people don’t really like. Microsoft are trying to make it similar to Windows in some ways, which makes it way more difficult to debug random errors.

    And it doesn’t follow the UNIX guidelines, which is just the cherry on top.


  • black0ut@pawb.socialtoMemes@lemmy.mllove is in the air?
    link
    fedilink
    arrow-up
    34
    arrow-down
    1
    ·
    9 months ago

    If you use Arch, you aren’t really affected. As far as we know, the backdoor only affects SSH if it is linked against liblzma, which is a requirement for libsystemd. However, Arch doesn’t use that, so SSH has probably been safe. However, you should still update, because we don’t know if the backdoor could’ve been used in other ways.

    Note that if you update, xz 5.6.1-2 will be installed. This is a safe version. However, if you run xz --version, it will still report version 5.6.1.



  • Obligatory “I use Arch, btw” comment. I’ve been using Arch for years and, honestly, it isn’t that much of a pain. It mostly works with the defaults, installation is really easy now with archinstall, and there’s a ton of software ready to install from the repos or the AUR. Besides, the arch wiki is amazing and has solutions for many of the problems you’ll ever have.






  • black0ut@pawb.socialtoMemes@lemmy.ml¡auxilio!
    link
    fedilink
    arrow-up
    2
    ·
    11 months ago

    Yes, we use it. However, it’s more common to say “hubiera”. There’s no specific rule to differenciate between both, but at least in the center and north of spain we mostly use “hubiera” for first person and “hubiese” for third person.

    “Ojalá hubiera podido ir, pero tenía deberes” (yo)

    “Ojalá David hubiese venido, se lo habría pasado bien” (él)

    As I said, both options would be correct in both cases, and probably in other places they use the words differently.