<elvishjerricco>
How good would a raspberry pi be as a factorio client? I figure its weak CPU is probably not good enough for any kind of complex world, so it can't handle the server logic. But the graphics requirements of the client are probably pretty low, so if the client doesn't do much of the CPU work then I'd wager it could be a pretty good client.
<elvishjerricco>
I guess the more general question would be: Does the factorio client use as few resources as I'd guess it does, both CPU and GPU?
<elvishjerricco>
Lol nevermind. Of course they don't support Arm, and obviously you can't compile it yourself.
<elvishjerricco>
Still, I guess the same question holds for any small intel SBC
drakonis_ has joined #nixos-chat
<samueldr>
for some game-y workload like that, it might hang solely on whether the GPU is involved or not on those SBCs
<etu>
My first blogpost on that site that isn't hello world
<averell>
nice :)
<etu>
I've heard that gchristensen likes when people make blogposts and stuff about nix, so it's been on my list of things I want to start doing and do more
<gchristensen>
I do like that =)
drakonis has joined #nixos-chat
drakonis_ has quit [Ping timeout: 252 seconds]
eyJhb has joined #nixos-chat
<eyJhb>
To make dinner or not to make dinner..
<adisbladis>
make: *** No rule to make target 'dinner'. Stop.
<eyJhb>
s/rule/food/
<eyJhb>
I got cookies
<etu>
eyjhb: Where are you at now?
<eyJhb>
Simmershavn :p Found a place for 1250 SEK/night
<eyJhb>
.......
drakonis_ has joined #nixos-chat
<eyJhb>
And I am only staying till tomorrow. And just arrived after I think around 8 hours in car :D
<eyJhb>
ffs, if I don't go now I never will.
drakonis has quit [Ping timeout: 272 seconds]
<eyJhb>
Anybody seen "The Queens Corgi"?
__monty__ has joined #nixos-chat
kraem has quit [Quit: outta here]
Synthetica has joined #nixos-chat
kraem has joined #nixos-chat
<samueldr>
I love to build outdated webkit for a random SDK I'm trying to package :/
<samueldr>
before finding that chapter I was a bit lost about naming things and what they meant
<eyJhb>
> let attrs = { a = 15; b = builtins.throw "Oh no!"; };
<{^_^}>
error: syntax error, unexpected ')', at (string):257:1
<eyJhb>
Am I blind?
<eyJhb>
samueldr: thanks, saved the logs :D
<samueldr>
eyJhb: blind about what?
<samueldr>
> let attrs = { a = 15; b = builtins.throw "Oh no!"; }; in attrs.b
<{^_^}>
Oh no!
<eyJhb>
samueldr: just no clue why it threq a error
<manveru>
> let
<samueldr>
let expressions need all parts `let ... in`
<{^_^}>
error: syntax error, unexpected ')', at (string):257:1
<samueldr>
and I guess that the "unexpected ')'" is from the "harness" of nix code to make this work behind the scenes
drakonis has joined #nixos-chat
<eyJhb>
Ahh, thanks :D
<eyJhb>
> let attrs = { a = 15; b = builtins.throw "Oh no!"; }; in "The value of 'a' is ${toString attrs.a}"
<{^_^}>
"The value of 'a' is 15"
m3thos has joined #nixos-chat
<tazjin>
eyJhb: if you find something is missing in the nix-1p doc, please file an issue!
<tazjin>
most of us suffer from the curse of knowledge, we don't know what people who aren't as experienced with Nix don't know
<tazjin>
missing and/or unclear
<drakonis>
write a book, thanks in advance
<samueldr>
books are outdated, at best, in my experience
<tazjin>
I wouldn't be a good person to write a book because I can't read most technical books, they're too verbose
<drakonis>
they're good for bringing people up to an expected level
<drakonis>
or rather, raise the bar
<drakonis>
i have tried experimenting with phoenix framework in the past and came out with the impression that it implicitly requires the book written by the framework's author in order to actually do anything decent with it
<eyJhb>
tazjin: soe just write to write. I keep finding some of my friends writing wall-of-texts, which are not needed
<tazjin>
I realised nix-1p is missing a section on operators
<tazjin>
particularly `//`
<tazjin>
TIL about `->`
<tazjin>
does anyone use that?
<samueldr>
I've often seen it in assertions IIRC
__monty__ has quit [Quit: leaving]
<drakonis>
nix-1p would make a fine nixlang in a nutshell chapter in the new docs
<tazjin>
which new docs?
<drakonis>
we talked about this last month, not sure if it has gotten off the ground yet
<samueldr>
ah, the whole "let's move off docbook but stall on the biggest bikeshed" high level convo there was
<drakonis>
what color is the bikeshed
<drakonis>
okay, that didn't go anywhere
<tazjin>
on the bikeshed, I think that using anything other than Markdown in 2019 is documentation suicide
<tazjin>
it excludes almost all driveby contributors
<drakonis>
that's the same problem as not using git in 2019
<tazjin>
hi, I work for a company that doesn't use git
<tazjin>
well, mostly
<drakonis>
your company uses a git wrapper
<drakonis>
and svn
<tazjin>
no
<drakonis>
google changed that?
<tazjin>
I haven't seen any svn around, but I can't conclusively say that there isn't any
<tazjin>
the monorepo itself is run on an internal system that is API-compatible with perforce (there's a public whitepaper about this somewhere)
<tazjin>
anyways, that's going off-topic
<tazjin>
what I wanted to say about the markdown thing is that yes, I understand that docbook has all sorts of theoretical fancy features
<tazjin>
but we don't actually use them for much
<eyJhb>
Does tazjin work for Google?
<drakonis>
yes
<samueldr>
maybe let tazjin answer?
<tazjin>
and having up-to-date, easily editable content is more important (to me) than running doctests or some such
<tazjin>
eyJhb: yes
<eyJhb>
tazjin: why no git?
<samueldr>
hrm, having a hard time understanding what's missing for the simulator to work... I think it's likely that it needs some control software that's only in the eclipse plugin :/
<tazjin>
eyJhb: we store most code in a single repo, which is of a size that git could not scale to, also git is newer than the repo - https://ai.google/research/pubs/pub45424 for details :)
<tazjin>
on the reference manual vs. instruction guide thing
<tazjin>
I think it's possible to chunk it reasonably
<tazjin>
so each (small) section can be read like an instruction guide
<tazjin>
but without requiring context of the other sections in order
<tazjin>
that's how I tried to write nix-1p, but I'm not sure whether it worked out (difficult to get a 3rd-person view on it if you wrote it)
<eyJhb>
tazjin: Ahh I heard about that at one point. Seems massive to have a "monorepo"
<tazjin>
I think it's the right thing to do for proprietary code where you need to synchronise a lot of developers on a private project
<tazjin>
for open-source individual repos is easier
<tazjin>
Nix has this cool ability to make "distributed monorepos", you can trivially keep some code in the same repo as your build config, while also pulling in code from the outside (and still pinning it)
drakonis has quit [Quit: WeeChat 2.4]
<eyJhb>
tazjin: hoping you don't have to have it all locally :p
drakonis has joined #nixos-chat
drakonis has quit [Client Quit]
<tazjin>
eyJhb: that wouldn't be possible on most desktop computers :P
drakonis has joined #nixos-chat
<eyJhb>
Nope, just read it as 86 TB from the link jeg sent :p
<eyJhb>
Also if one thinks default Git workflow into it, it must be hell!
<eyJhb>
But, propelry not how it works
<samueldr>
oh, got it, and it works
<tazjin>
I'm changing the nixery.dev landing page to an mdBook that will explain concepts like "how to set up a Nix repo for your company" etc.
<tazjin>
this kind of thing is always exciting because Nix makes all sorts of things trivial, like I can just pull in nix-1p into a page in the book with a handful of lines of Nix
<tazjin>
<3
<samueldr>
I want to add some kind of `connectiq.mkDerivation` in the future, but this, at least, allows you to use the SDK https://github.com/samueldr/nix-connectiq
<samueldr>
though I think it's going to be annoying considering there's a signing key involved, not sure what's the best to do about that
<tazjin>
maybe make it a NIX_PATH entry?
<tazjin>
because I assume people would bring their own signing key
<samueldr>
I was thinking about how the key would end up in the store
<samueldr>
not sure if it is even an issue
<tazjin>
I remember some discussion about keys in the store from NixCon last year
<tazjin>
not sure what became of that 🤔
<samueldr>
it might not be an issue I need to concern myself with
<samueldr>
tbf, I'm not sure I'd recommend their hardware, but I didn't look the gift horse in the mouth too closely
<samueldr>
(if only for the fact that I can't just replace the firmware outright)
<samueldr>
though they are interesting
<samueldr>
a completely different world
<samueldr>
it's not just slapping some linux, and adding more cruft to it