<ar>
aleph-: but i still need to do some adjustments on the right half
<ar>
(like, remove all of the altgr keys except for the one under m)
cole-h has quit [Ping timeout: 258 seconds]
ldlework has quit [Read error: Connection reset by peer]
ldlework has joined #nixos-chat
elvishjerricco has quit [Ping timeout: 240 seconds]
elvishjerricco has joined #nixos-chat
Ashy has quit [Ping timeout: 240 seconds]
Ashy has joined #nixos-chat
hax404 has quit [Ping timeout: 240 seconds]
liszt has quit [Ping timeout: 240 seconds]
liszt_ has joined #nixos-chat
hax404 has joined #nixos-chat
spudly has quit [Quit: killed]
spudly has joined #nixos-chat
ixxie has joined #nixos-chat
Ashy_ has joined #nixos-chat
sdier_ has joined #nixos-chat
sdier has quit [Ping timeout: 240 seconds]
Ashy has quit [Ping timeout: 240 seconds]
sdier_ is now known as sdier
Ashy_ is now known as Ashy
tazjin has quit [Quit: Byeee]
tazjin has joined #nixos-chat
tazjin_ has joined #nixos-chat
tazjin has quit [Ping timeout: 272 seconds]
tazjin_ is now known as tazjin
spudly has quit [Quit: killed]
spudly has joined #nixos-chat
waleee-cl has joined #nixos-chat
__monty__ has joined #nixos-chat
spudly has quit [Quit: killed]
spudly has joined #nixos-chat
tazjin has quit [Quit: Byeee]
tazjin has joined #nixos-chat
spudly has quit [Client Quit]
spudly has joined #nixos-chat
spudly has quit [Client Quit]
spudly has joined #nixos-chat
spudly has quit [Client Quit]
spudly has joined #nixos-chat
spudly has quit [Client Quit]
spudly has joined #nixos-chat
tazjin has quit [Quit: Byeee]
spudly has quit [Quit: killed]
tazjin has joined #nixos-chat
spudly has joined #nixos-chat
spudly has quit [Quit: killed]
spudly has joined #nixos-chat
pinpox has joined #nixos-chat
ixxie has quit [Remote host closed the connection]
guest74637 has joined #nixos-chat
<gchristensen>
what a joke: aws only supports RSA keys for its key pairs.
<andi->
the other aren't sufficiently backdoored
<andi->
err I think it's called FIPS compliance not backdoored, my fault ;-)
<gchristensen>
ontahoentahou
<pie_>
Filly Intended to be Pretty Secure
<pie_>
*fully
<gchristensen>
also a shame you can't create an ipv6 elastic ip
<andi->
well the cloud is from the past.
<gchristensen>
now we're on to Edge Deployments
<evanjs>
Gah, probably a crazy idea, but PWAs for the options and packages search pages would be amazing. Or just the search section in general
<andi->
which is fancy speak for run your own datacenter.
<gchristensen>
=)
<evanjs>
Still don't have any experience with PWA myself, but I do find that, if implemented well, they can be just as useful, if not more useful than some "portal apps" that accomplish the "same thing" as the website (but usually less)
<evanjs>
Side note: I'm not always one to jump on new technologies right away, but it's always nice to be able to be able to keep up with random stuff I see in articles easily because NixOS has options for X already
<V>
Caddy is good, although v2 is a bit... not sure how to feel about it
<V>
I would definitely recommend it, however
<evanjs>
*sees Go* 😨🦀
<gchristensen>
ouch
<evanjs>
Nah but in all seriousness, I don't have enough experience with web servers lol. Only that I've seen nginx more and it seems to have better support on eg nixos, among coworkers, etc
<andi->
Anyone else getting a "slow" feedback from search.nixos.org?
<evanjs>
Nah but I've been trying to stay more open minded about go stuff, as I read more stuff about how Go and Rust can actually be used to work together. My thoughts on the ecosystem and whether I'll actually use it myself, aside 😝
<evanjs>
andi-: seems to be as fast as I'd hope for on my end. Have you used it since the elastic search upgrade?
<evanjs>
No clue if it would have any affect, but I wonder if a hard refresh would do anything
<andi->
evanjs: thats what I'm looking at. 100ms to return results :/
<evanjs>
I mean, is that slow? Or rather, is there something specific you're expecting?
<andi->
It feels slow. Like I have to wait for the results. Used to be instant
<andi->
(on the old page)
<evanjs>
To be fair, it's a bit more robust, now. Reflex support, etc. matches the new features of the new package search
<evanjs>
Regex** ugh
<evanjs>
But yeah I'm not sure if that has any performance implications
<andi->
What is reflex?
<V>
Go is plenty good for writing web servers in, booing anything written in it is a little... close-minded?
<andi->
and how is an active backend more robust?
<V>
Sure, Rust is lovely, but AIUI its current state doesn't make it particularly good at writing servers in
<evanjs>
V: no like that's what im getting at haha
<V>
Which is something that Go is designed for
<V>
ah okay
<V>
I'd definitely suggest checking Caddy out, though; it has a really well-designed config file format
<evanjs>
Not sure if my messages went though. I've had little experience with it and certain things really do irk me (go path, dep management, project build process, generics, etc) -- but I've been reading more about how the two can work together
<V>
gopath/dep management is much better now that modules are here, I'm not sure if you've used those? It was utter crap before those
<V>
Generics are a low point, yeah
<V>
I get mad at Go on a regular basis but the things you can write in it are pretty rock solid
<evanjs>
Yeah likewise with Rust in my experience. In the end, I think a lot of it comes down to preference, what the utility of the application is, blah blah blah.
<V>
I like Rust a lot!
<V>
It's something I've been trying to learn more recently since it fixes most of my gripes with C and C++
<etu>
The gomodules are lovely
<etu>
It flipped my entire opinion about that ecosystem
<V>
same
<V>
re Rust: I just don't think that its async story & support for writing networking code is nearly mature enough, yet
<evanjs>
Yeah I literally came to Rust (IIRC) because I ran into speed issues with Python, and had issues writing a similar applet (check the latest versions of the vanilla and gentoo kernels) in C/C++
<evanjs>
I bet it'd be even easier now that async/await is stable
<V>
async doesn't have support for iterators yet :/
<evanjs>
Yeah I would've said the same pre... I think 1.37.0?
<evanjs>
Don't they tho?
<evanjs>
Isn't that what futures streams are?
<V>
it's "stable" but like their 1.0 release where it missed a huge amount of stuff
<evanjs>
"If Future<Output = T> is an asynchronous version of T, then Stream<Item = T> is an asynchronous version of Iterator<Item = T>. A stream represents a sequence of value-producing events that occur asynchronously to the caller."
<evanjs>
Ah alright
<V>
look at "future extensions"
<evanjs>
I do love the are we sites
<V>
it's basically not done yet even though they're trying to promote it as finished
<V>
(like with the 1.0 release)
<V>
these have left a fairly sour taste in my mouth with Rust
<evanjs>
Yeah I've been confused about async stuff forever, but have slowly become more comfortable with it. Coming from C# as my first "real" language I've used, it's definitely something I'd be happy to see stabilized
<evanjs>
I've also seen both sides of the networking stability argument. Some think it's not ready and others have argued that it can/actually have written robust networking services or etc with it
<evanjs>
But anyway, picking on an easier target (:p) -- how easy has rust been to use over C/C++ for networking HTTP stuff? Holy cow. Wayyyy easier
ekleog has quit [Quit: back soon]
ekleog has joined #nixos-chat
tazjin has quit [Quit: Byeee]
tazjin has joined #nixos-chat
maxdevjs has joined #nixos-chat
<aleph->
ar: Yeah still tweaking my layout as well
<aleph->
gchristensen: Yeah quite weird they only support rsa
<ldlework>
drakonis: Is Saturdays at 7PM CST OK for you?
cole-h has joined #nixos-chat
sphalerite has quit [Quit: boot, boot, boot, boot, reboot the outdated server]
sphalerite has joined #nixos-chat
rajivr has quit [Quit: Connection closed for inactivity]
<cole-h>
Somebody talk me off the ledge: it's 4 days before AMD's CPU event -- what are the odds the price of an r7 3700x drops after the event, and by how much (do you think)?
<cole-h>
I'm really close to just buying all my parts right now...
<MichaelRaskin>
I guess you could lookup the previous event?
<MichaelRaskin>
Hmm, 30% price slide observed last time?
<MichaelRaskin>
(Although a part of it was _before_ the announcement)
<cole-h>
Where'd you find this info? My Google-fu is weak, it seems.
<cole-h>
I'm just paranoid about going to buy them and then them being OOS for whatever reason (Zen 3 not as good as anticipated? Prices too high for the increase in performance? idk)
<cole-h>
(them = the processor, no idea why I put that)
<cole-h>
MichaelRaskin++ Thanks for the help.
<{^_^}>
MichaelRaskin's karma got increased to 46
<MichaelRaskin>
You could wait for benchmarks, too
<MichaelRaskin>
I guess I would be tempted if there was something BRIX-like for Threadripper. Being a Postdoc and moving between countries from time to time means I am immune to the temptation of getting an actual ITX build
<samueldr>
MichaelRaskin: for ryzen (not threadripper) NUC-likes are coming
<samueldr>
though yeah, it would be interesting to have some with moar cores
<samueldr>
it looks like someone, either AMD or OEMs didn't think the mobile solutions would end up selling as well as they do
<samueldr>
as apparently all OEMs have trouble getting chips
<MichaelRaskin>
Yeah, true, but I cannot get around fixing the reflow-needing second RAM slot on my BRIX, and I guess a quad-core would mean just 1.5x boost in performance or so? (and BRIX is not much faster than my laptop now)
<MichaelRaskin>
Yeah, i7-4470R is nice that it was more or less mid-range desktop at the time, but BRIX means it is in an easy-to-carry formfactor
<samueldr>
yeah
<MichaelRaskin>
It might be that AMD just prioritised «let's sell as many EPYCs as we can first, the rest can wait»
<samueldr>
hopefully the situation gets better for access to the chips, and less "thriftier" product lines get AMD chips too
<MichaelRaskin>
Yeah. I guess AMD did not want to precommit to too much manufacturing in advance, but now they know they can sell a ton more
<samueldr>
it's just as likely as OEMs not wanting to commit to using those "unproven" [in the market] chips
<samueldr>
and is likely to be somehwere in-between those two statements
<MichaelRaskin>
Sure, if the OEMs agreed to precommit from the beginning, AMD would book some more fabbing a bit earlier
<MichaelRaskin>
But once the situation started, I bet on fabs having longer planning horizon than assembly
<samueldr>
yep
NinjaTrappeur has quit [Quit: WeeChat 2.9]
NinjaTrappeur has joined #nixos-chat
<cole-h>
OK, I took the plunge. Wurf it.
<bqv>
did someone here mention hive.blog to me?
<bqv>
logs are being inconclusive
<bqv>
but i've rarely trusted my own memory much these days
__monty__ has quit [Quit: leaving]
<cole-h>
I didn't find any hive.blog mentions in here, #nixos, or #nixos-dev
<sphalerite>
ah, that would explain why the amd thinkpad t14's availability fluctuates so much as well.
<samueldr>
it's the same for all recent AMD laptops
<samueldr>
good thing I'm not in the market for one right now
<bqv>
cole-h: fair enough. guess i'm going nuts again
<cole-h>
(I used samueldr's logs to check)
<samueldr>
gotta love how opening a <select> with ~80 000 options on firefox locks up on a xeon "really not a slouch" cpu
<cole-h>
wat
<samueldr>
locked up for multiple minutes
<cole-h>
oh
<sphalerite>
huh, lenovo's german website has barely anything on offer right now
<samueldr>
am I alone where loading a github project's main page with firefox seems to lock-up the tab for a while while it "lazily" loads the commit data?
<samueldr>
it seems to be hit or miss, and not necessarily for huge projects only
<cole-h>
I've seen that too.
<cole-h>
Sometimes click on anything, and you see the "fake" loading bar at the top go to the end, and never succeed
<cole-h>
Or even better: the URL changes, but the page contents don't
<samueldr>
a bit different for when you follow a link with that fake loading not working
<samueldr>
what I'm seeing is really the browser locking up when "lazy" loading information from the main page, while the latter is just buggy behaviour that doesn't lock-up
<samueldr>
it's annoying having to wait a good minute to follow a link that's already on the page
guest74637 has quit [Ping timeout: 240 seconds]
<pie_>
infinisil: so my "restic the zfs snapshots" might be getting a bit more complicated, observe #zfsonlinux