<colemickens>
I am also somewhat interested in packaging Firefox Nightly to enable Wayland and see if it works better without involving Flatpak in the mix.
<drakonis_>
sway's author is very... impolite
<drakonis_>
simpson, sircmpwn's opinions on nvidia are very rude and bad
<drakonis_>
also his opinions on software
<simpson>
Drakonis_: I was a mod in the Minecraft reverse-engineering community when he was merely a toxic newbie, and he was a PITA back then too.
<drakonis_>
he wrote his own git frontend
<drakonis_>
own git hosting service lol
<drakonis_>
it is a exclusive club
sir_guy_carleton has joined #nixos-chat
jasongrossman has joined #nixos-chat
<emily>
simpson: I probably should have updated my expectations of its code quality based on how I feel whenever I see a blog post by him
<emily>
but I like i3 and I like Wayland, and what's the chance that there's going to be a *second* project to do i3-on-Wayland given that sway happened in the first place because i3way or whatever it was was vapourware
lassulus_ has joined #nixos-chat
<emily>
colemickens: I think I'll probably just stick with i3 for now at least until the meson update hits nixos-unstable, but maybe I'll see about writing that patching for Xwayland when I'm less busy
lassulus has quit [Ping timeout: 244 seconds]
lassulus_ is now known as lassulus
<simpson>
emily: Sure, and after all I'm pretty grumpy about anything GPU-related so I should be taken with a grain of salt.
<emily>
sadly attempting to make a Linux distribution out of software entirely developed by pleasant people to work with is a bit of a contradiction in terms anyway
<gchristensen>
("better") emit: lib.types.listOf lib.types.str so the user can quickly find the docs for those types
<samueldr>
[21:39:53] <samueldr> wondering if those description shouldn't mirror their type names?
<samueldr>
[21:40:03] <samueldr> though bad UX for the end-user
<gchristensen>
yeah
<gchristensen>
well, it depends on who the end user is
<samueldr>
someone looking at options.html
<gchristensen>
yes, but who is the someone
<gchristensen>
do we expect them to be able to infer from that what it means? (many probably could, not all -- is my question)
<samueldr>
I would assume some level of inferrence, but not that much
pie___ has joined #nixos-chat
<samueldr>
e.g. I have a friend, used to linux, knows about nothing in FP, some programming knowledge, just started using NixOS
<samueldr>
though in a way, the verbose descriptions may not be that useful in that case either :/
<gchristensen>
a smaller step even is properly documenting the types and merge behavior . a friend/coworker "got" what lib.listOf meant but couldn't find any published docs about how they merged (maybe listOf is documented, but many aren't)
<samueldr>
the question is: would the descriptions be better to disambiguate than the verbose descriptions, which I'm not sure they would
<jasongrossman>
gchristensen: That sounds right to me.
<gchristensen>
I'd rather expose the machinery here to be very precise and shore up the docs to help understanding, before trying to make smart english descriptions
<samueldr>
that's a sane idea I think
<gchristensen>
b/c if someone comes for help with "it says it isof type lib.types.listOf lib.types.attrSetOf lib.types.str" then that is super easy to answer
pie__ has quit [Ping timeout: 252 seconds]
<gchristensen>
and then we arm them with docs for reference
<samueldr>
for the first PR for the feature I was working on I'll uh... forget about fixing the smart descriptions... not making it much worse :/
<gchristensen>
hehe ok
<jasongrossman>
And also because it's good to keep making the docs better and better for all sorts of other reasons.
<infinisil>
TIL that `git cherry-pick a..c` is not the same as `git cherry-pick a b c`
<infinisil>
I think
<gchristensen>
I think a...c will be
<infinisil>
Hmm, I think my a..c applied the changes from a to c in one go, as if it did `patch $(git diff a..c)`, not sure, I'll try out ... next time
infinisil has quit [Quit: Configuring ZNC, sorry for the joins/quits!]
infinisil has joined #nixos-chat
infinisil has quit [Client Quit]
infinisil has joined #nixos-chat
Synthetica has quit [Quit: Connection closed for inactivity]
infinisil has quit [Quit: Configuring ZNC, sorry for the joins/quits!]
infinisil has joined #nixos-chat
infinisil has quit [Remote host closed the connection]
infinisil has joined #nixos-chat
infinisil has quit [Quit: Configuring ZNC, sorry for the joins/quits!]
infinisil has joined #nixos-chat
infinisil has quit [Client Quit]
infinisil has joined #nixos-chat
infinisil has quit [Quit: Configuring ZNC, sorry for the joins/quits!]
infinisil has joined #nixos-chat
jasongrossman has quit [Quit: ERC (IRC client for Emacs 26.1)]
siers has quit [Ping timeout: 245 seconds]
<sphalerite>
Battery 1: design capacity 2137 mAh, last full capacity 1408 mAh = 65%
<sphalerite>
Battery 1: design capacity 2151 mAh, last full capacity 1417 mAh = 65%
<sphalerite>
Battery 1: design capacity 2153 mAh, last full capacity 1419 mAh = 65%
<sphalerite>
I have a variable-design-capacity battery!
<joepie91>
lol
<joepie91>
sphalerite: was it made by Tesla
* sphalerite
lacks context to understand that one
<joepie91>
sphalerite: Tesla ships cars with batteries that are bigger than the customer paid for, and then software-locks them to the paid-for capacity
<joepie91>
:P
<sphalerite>
wow
<joepie91>
so, variable design capacity!
<sphalerite>
on the bright side they'll take a really long time to drop from the design capacity!
<joepie91>
lol
<joepie91>
sphalerite: Tesla's rationale is that it simplifies manufacturing
<joepie91>
which, like, sure, I can understand that
<joepie91>
but then just don't sell an upgrade from a non-existent model to an existent one...
<sphalerite>
yeah…
<sphalerite>
"any colour you like, as long as it's black " worked for Ford
<joepie91>
lol
<joepie91>
sphalerite: or just do it how OVH does it
<joepie91>
you buy a server with a 1TB HDD
<joepie91>
"oh we actually have a pile of 2TBs and no 1TBs, congratulations, you now have a 2TB drive"
<sphalerite>
:D
<gchristensen>
if your battery is soft-locked to a lower capacity does that mean it'll last longer, as the cells get less use?
<sphalerite>
but then the people who paid for 2 will be irritated?
<joepie91>
sphalerite: well, you always get at least the advertised capacity
<joepie91>
:P
<joepie91>
beyond that it's potluck
<sphalerite>
I guess
<joepie91>
and it's not led to customer revolt, so...
<joepie91>
gchristensen: ... possibly?
<gchristensen>
sphalerite: SoftLayer would do a similar thing and people would play the Softlayer Lottery: buy 100 X-sized servers and then cancel the 90 lowest specced.
<sphalerite>
hahaha
<gchristensen>
for a datacenter, it is just reality that you can't offer exact hw forever.
<joepie91>
gchristensen: ouch. that must have caused a ton of churn
<gchristensen>
yeah, but it is just part of having bare metal hw rentable via api with no lower limiton duration
<gchristensen>
when doing some testing for NixOS on Packet I'll deploy dozens of servers for just 5min
siers has joined #nixos-chat
<joepie91>
gchristensen: oh, these were cookiecutter models rented through an API? so no expectation or guarantee of new hardware?
<__monty__>
Now if only they could predict when I'll get hungry and send an appropriate meal to arrive at that time at the place where I'm going to be...
drakonis1 has quit [Ping timeout: 252 seconds]
drakonis1 has joined #nixos-chat
drakonis1 has quit [Read error: Connection reset by peer]
drakonis1 has joined #nixos-chat
drakonis has joined #nixos-chat
drakonis1 has quit [Ping timeout: 252 seconds]
drakonis has quit [Ping timeout: 260 seconds]
drakonis has joined #nixos-chat
pie___ has quit [Ping timeout: 245 seconds]
drakonis has quit [Ping timeout: 252 seconds]
drakonis has joined #nixos-chat
drakonis_ has joined #nixos-chat
MichaelRaskin has joined #nixos-chat
<gchristensen>
+ <title>A contrived example of using <function>lib.attrsets.mapAttrsRecursive</function></title>