I needed a basic timer on Linux and so in installed gnome "clocks" via the program "software".
-
@aeva *i gasp for air, i am* (*rolls for initiative*) *successful!*
@lritter *watches with confusion as you pretend to drown and/or not drown*
-
@aeva it's so that even if you lose the argument, i don't seem like i really won something
-
@aeva it's so that even if you lose the argument, i don't seem like i really won something
@aeva "is he making fun of drowning people, what the hell?" no wait, it is metaphorical, expressing that i love pointless nerd debates but am simultaneously aware of how exhausted everyone is of them and so i tried to paint a picture that serves both sides equally badly
-
@aeva "is he making fun of drowning people, what the hell?" no wait, it is metaphorical, expressing that i love pointless nerd debates but am simultaneously aware of how exhausted everyone is of them and so i tried to paint a picture that serves both sides equally badly
@lritter I've gotta ask though did you(?) win or lose
-
@aeva the dice roll in the middle of drowning suggests that it was mere luck that we reached an outcome where you could not tell if the gnome clock was worse. it could have just as well gone the other way, and in fact, had you been slightly more informed, you would have definitely obliterated my little piece of driftwood.
-
@aeva I think it may come down to the biggest flaw in open source software - there is no unifying vision, devs do not really get to align goals with one another, it's just a bunch of people insulated from each other doing their own things and maybe posting in forums and mailing lists about it and arguing with each other.
Then again, Windows hasn't really felt like it has a unified design vision since like... 2000?
@pendell I disagree, this was a problem that was created by trying to have a unified vision (it's a gnome app using a gnome service and it works fine if you use gnome but i don't use gnome), and if it was designed to function well stand-alone it wouldn't have had this problem and wouldn't have required any broader coordination with anyone else's vision beyond the passive agreement that comes from using standard interfaces
-
@pendell I disagree, this was a problem that was created by trying to have a unified vision (it's a gnome app using a gnome service and it works fine if you use gnome but i don't use gnome), and if it was designed to function well stand-alone it wouldn't have had this problem and wouldn't have required any broader coordination with anyone else's vision beyond the passive agreement that comes from using standard interfaces
@pendell consensus and community input are important for foundational systems (eg display, audio, network, date time, etc) so that essential functionality is stable and implemented well enough that the rest of the ecosystem can be built on it, but it's not really important whether or not Crazy Bob's Chronometer Bauble fits into some grand brand vision
-
@aeva the dice roll in the middle of drowning suggests that it was mere luck that we reached an outcome where you could not tell if the gnome clock was worse. it could have just as well gone the other way, and in fact, had you been slightly more informed, you would have definitely obliterated my little piece of driftwood.
@lritter I could check after work if you want
-
@aeva go and hurt me! see if i care!
-
@aeva go and hurt me! see if i care!
@lritter ok ok but you gotta wait until I'm off work
-
@aeva i will insert a few hours of sleep here to prepare
-
I needed a basic timer on Linux and so in installed gnome "clocks" via the program "software". This works fine for that purpose, but when you open it it greets you with the time in your "current location". It gives me new york for some reason and I do not live in new york, and my time zone is set as America/Chicago so I don't know how it came to that conclusion. Naturally there is no setting exposed to change this. What.
@aeva at least you're not ranting on wayland 😃