Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)E
Posts
3
Comments
174
Joined
6 mo. ago

  • Yeah that sound is always horrible and makes you jump and look what's wrong, while actual problems often aren't as loud or even noticeable lol.

  • I've always had either problems with schedules or problems with environment because it has it's own. Cron is fine as long as you are lucky. That isn't to say there never were problems with timers, on debian 9, I think, shipped version of systemd had a bug where systemd-analyze parsed schedule correctly and timer just shit itself. But only for some specific case I can't remeber which, but it was extremely frustrating to debug.

  • I really dislike dumb and entitled takes like this. First he somehow complains about both GNOME and KDE when literally none of the complaint apply to KDE, second switching between different operating systems will break the way you are doing things anyway, and third - who cares.

  • You can explain timers the same way.

    And then with your explanation it goes: cron job doesn't execute for reason, crontab -l lists not all jobs, someone else put cron job in whatever directory like cron.daily, you've added or removed empty line at the end and now nothing works, debian crond and redhat cronie ahave different quirks, etc., etc.

    I've dealt with insane cron problems for so long that switching to timers was like whoa i don't need to suffer?

  • First, it is usable just not the way Talon requires (and its developer doesn't want to support wayland). Second people can use LTS distributions that will ship X11 for many years, and by that time it will either be good enough or won't.

  • There is wdotool, it's not complete re-implementation yet, but it works.

  • Which all of them, which cron implementation is simpler and better? Do you even use cron? It's not a joke, explanation on how to use cron takes > 8 pages. It should be in the hall of fame of the least accessible and hard to learn programs. Lennart cancer is one of the greatest things that happened to linux.

  • It's not so bad like the article author describes, there is work being done to address the input issue e.g. libei and wayland protocols. (also N.Graham answer that says that it should be done on wayland level if they require universal solution is right if a bit unkind)

  • get acquired

    Why in passive? Weren't they actively participating in acquisition?

  • It depends, what do you want to print?

    I would buy another Elegoo CC or Sovol unless there is a multicolor requirement.

  • Why did it make you angry? Do you believe that there are other implementations that do the task better and simpler?

  • It was made by mscovites in mscovia with fsb money, by the same guys that tried to copy facebook.

  • Well, you know, horses, grasslands, Wormtongue - Rohan!

  • Rich vampires would even subsidize it, because it will be a hellhole, due to it being an extremely controlled environment with alternative being death.

  • So they feel that surveillance isn't so great when it directly affects them? Poor ghouls, I'm going to cry for their plight in the next never.

  • Zero useful information.

  • Racoons are cool, good thingn that I'm not using it.

  • Npm having a lot of packages at least partially a problem of lacking standard library, no? And partially developer culture where every trivial thing is a package. Anyway, similar thing will happen to rust soon enough (looks at 1 gig of dependencies for a cli program).

  • Cool, been looking for something like this.