<pie_>
abathur: i wish stuff like this would get standardized
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-chat
<abathur>
phrased the other way around, I'm trying to figure out what to replace 'blah' with in `resholve --blah "find:/usr/bin/find xargs:/run/current-system/sw/bin/xargs"`, with an interest in re-using an existing pattern if there is a familiar one that doesn't clash with my existing names/concepts
<energizer>
what does find:/usr/bin/find mean?
<abathur>
(roughly) that `find` should come from this specific path, instead of whichever find was first in PATH
<abathur>
unless there is no PATH, or no directory on PATH with find in it
<colemickens>
I love that sometimes Linux just gets jammed up. No amount of restarting hte gpg-agent, of pscsd.service helps.
<colemickens>
any operation to it causes it to just start blinking non-stop. no idea wth is going on but it's useless until I reboot when this happens
<colemickens>
happens once or twice a month
<energizer>
colemickens: it might be oom killer slowly working
<colemickens>
I'm at 70% util right now, I don't think it's oom
numkem has quit [Quit: Ping timeout (120 seconds)]
numkem has joined #nixos-chat
das_j has quit [Ping timeout: 265 seconds]
das_j has joined #nixos-chat
<abathur>
testing some names for --blah... --paths --abs --absolute --abspaths --pathmap --preresolved --override-path? I can also technically fit it into an existing flag named --fix with the same <name>:<abspath> syntax, but the semantics feel a tad off
supersandro2000 has quit [Ping timeout: 260 seconds]
Raito_Bezarius has quit [Ping timeout: 260 seconds]
supersandro2000 has joined #nixos-chat
<abathur>
tentatively using `--preresolved 'name:abspath' | RESHOLVE_PRERESOLVED='name:abspath', then :)`
<colemickens>
boy it'd be cool if the clipboard worked reliably in firefox
Raito_Bezarius has joined #nixos-chat
<drakonis>
hmm
<drakonis>
centos is melting down atm
<drakonis>
this will be an interesting period as people flee centos for other distros
<gchristensen>
I sort of see it as evidence that LTS distros are dying because nobody wants them and tehy're an antipattern
<abathur>
figure out how to make a github bot that tries to spot people fiddling dumb CI stuff, potentially enraged, and offer them a quick fix for their firstborn
<abathur>
throw AI in for buzz
<abathur>
well
<abathur>
not like a github "bot"
<abathur>
but like, a bot that probably violates the TOS
<JJJollyjim>
there was a gitlab bot a while ago that just spammed everyone's repo with "hey, you have a ci job set to allow-fail: true, that's Bad Practice, change it"
<abathur>
bet that annoyed people who wanted to start declaring jobs they knew they couldn't pass yet
lunc has joined #nixos-chat
<infinisil>
Oh no, I just spent a bunch of time thinking a lot about nixpkgs overrides and what their underlying theory is
<infinisil>
And the oh no part is that it's hecking monads!
<infinisil>
It's monads all the way down
<infinisil>
a: b: c: b (a c) c
<infinisil>
You know life is good if you can write such a function
<infinisil>
s/you can write/you need
<infinisil>
10 points to whoever can guess what that function conceptually is
<infinisil>
Actually, it might not be monads after all
<pie_>
infinisil: overrides is actually mutation
<infinisil>
I think it's actually Arrows, which is like Monad's big brother
<red[evilred]>
Thank Haskell you didn't say lenses
<pie_>
infinisil: the bigger big or the smaller big :P
<pie_>
im being snarky but i legit never know in mathematical contexts what various "degree" indicators are supposed to mean
<infinisil>
red[evilred]: Ohh you make me get new ideas
<infinisil>
pie_: Arrow > Monad (not actually, but kinda)
<pie_>
yeah nix is really missinga lens library
<pie_>
infinisil: by which ordering? ;P
<pie_>
infinisil: subset relation or specialization?
<infinisil>
I think every Monad can be turned into an Arrow (with Kleisli)
<infinisil>
But not the other way around
<gchristensen>
I can't do anything without finding bugs
<abathur>
BREAM
<drakonis>
write a nix lens library with nickel :V
<pie_>
drakonis: a nickel for your thoughts
<drakonis>
yes
<drakonis>
a nickel for my thoughts
<drakonis>
go get yourself a real computer, kid.
<drakonis>
(its not a funny joke)
<pie_>
im gonna need a lot more nickels...
<pie_>
gchristensen: not sure if its software or just you being a seaoned developer
<pie_>
probably both
<pie_>
the only "solution" is to stop do.
<infinisil>
It's time to stop!
<pie_>
dont
<pie_>
now
<pie_>
me
<pie_>
stop
<pie_>
ᕕ( ᐛ )ᕗ
<abathur>
the faster you go the more bugs you find?
andi- has quit [Remote host closed the connection]
KREYREEN has quit [Remote host closed the connection]
<insep_>
my part 2 runs in O(n^4)
<insep_>
or whereabouts
<insep_>
O(n^9)
<insep_>
where 9 is amount of loops
<insep_>
i use 5 loops for part 1
<insep_>
plus there are potential out of bounds in it
<insep_>
no, not potential
<insep_>
definite out of bounds
<insep_>
i feel bad now
KREYREEN has joined #nixos-chat
<siraben>
insep: definitely can be done in linear time
<siraben>
you mean amount of nested loops? dang
<insep_>
i have 2 outer loops, first has 2 another nested loops and one of them has another nested loop, second outer loop has 1 nested loop that has 3 nested loops
thibm has joined #nixos-chat
<siraben>
insep: which language are you writing it in?
danderson[m] has quit [Quit: Idle for 30+ days]
cole-h has quit [Ping timeout: 265 seconds]
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
lunc has joined #nixos-chat
<insep_>
d
Baughn has quit [Ping timeout: 240 seconds]
FRidh has joined #nixos-chat
<eyJhb>
It's always nice doing a git pull on nixpkgs, and then just watching all the sweet sweet updates
__monty__ has joined #nixos-chat
<ldlework>
and then finding out what broke as things slightly changed configuration formats or options, etc
<patagonicus>
ldlework: or even better: that a package broke on 32-bit arm, because 32-bit arm is not fully supported by nixpkgs. Which also means you'll only find out after many hours of compiling if it doesn't happen to be something like coreutils, which is build early. :)
spudly1 has quit [Quit: killed]
lordcirth_ has quit [Ping timeout: 264 seconds]
waleee-cl has joined #nixos-chat
<pie_>
if i ran firefox in android in a vm on my machine it would probably perform better than actual firefox
<hexa->
huh
<viric>
)
<viric>
firefox in android is a pain
<viric>
(fennec at least)
<adisbladis>
s/firefox in//
<bbigras>
how so? It's pretty nice to me. the new version.
<viric>
I use Lightning in android
<viric>
maybe fennec has improved these last years
<bbigras>
last years? is fennec the faster new one?
<pie_>
caveat, my firefox usage is pathological
<bbigras>
or is it fenix?
<viric>
fennec is how I get firefox in android
<adisbladis>
Firefox is still the only usable browser on android
<adisbladis>
At least if you care about such pesky things as privacy
<adisbladis>
I have mixed feelings, but I think this _might_ just be a good thing in the end.
<srhb>
adisbladis: Why's that?
<adisbladis>
If it brings a few organisations off horribly outdated software that's a net positive
<srhb>
Ah :)
<gchristensen>
LTS (claps interpolated) is technical debt
<adisbladis>
gchristensen: Long Term Stale
<insep_>
red[evilred]: imagine c++ but with easier (and perhaps more powerful) metaprogramming, reflection, (optional) safety, boundaries checks, arrays that actually have their length stored (aka slices), easier syntax, rich standard library, modules, gc and no namespaces
<insep_>
this is d
<insep_>
there's more, but i don't want to spell it all out
<gchristensen>
Long Term regretS
<insep_>
read tour.dlang.org/ for a quick overview
<insep_>
oh, also with compile-time stuff execution
* srhb
wants to track nixos-unstable but for the lack of release notes
<adisbladis>
insep_: I _love_ the compile time exec stuff
<adisbladis>
It's magic
<insep_>
same
<insep_>
especially when i parse aoc input at compile time :)
<adisbladis>
insep_: You make me realise I need to write more D :)
<LinuxHackerman>
srhb: yeah, it would be great if we could get release notes for incompatible changes in right off the bat… that might also avoid situations like the recent firefox breakage, just by forcing PR authors to think about the consequences of what they're doing actively
<LinuxHackerman>
srhb: also structured-data release notes.
<joepie91>
LinuxHackerman: FF breakage?
<srhb>
LinuxHackerman: Yeah. It's hard to remember though, I've done the bad thing too.
<srhb>
LinuxHackerman++ to that
<{^_^}>
LinuxHackerman's karma got increased to 5
<srhb>
joepie91: There was a change that erased all your firefox addons -- but I think that was purely a mistake that may or may not have been alleviated by writing a changelog about the intended declarative stuff.
<cole-h>
joepie91: A change in the package that dropped all addons
<adisbladis>
joepie91: There was some recent breakage causing peoples imperatively installed add-ons to be uninstalled
<srhb>
synchrosplainatron.
<cole-h>
all imperatively-installed addons* as adisbladis rightly points out.
<cole-h>
srhb++ adisbladis++ :D
<{^_^}>
adisbladis's karma got increased to 121
<{^_^}>
srhb's karma got increased to 139
<srhb>
<3 cole-h
<{^_^}>
cole-h's karma got increased to 114
<gchristensen>
and synchronized to all your devices logged in to the same profile
<srhb>
But, mistakes happen.
<gchristensen>
which causes those addons' data to be deleted
<srhb>
I do agree that reflection may help though :)
<LinuxHackerman>
and I'm absolutely not blaming the PR author, or PR authors in general!
<adisbladis>
insep_: I could have used D's regex engine the other day
<srhb>
LinuxHackerman: I know :D
<srhb>
Just being very explicit about it >_>
<srhb>
<-- me, that is.
<srhb>
But, back on topic, yeah, I'd love structured change-something.
<srhb>
Frankly the bi-yearly upgrade is mostly a hassle for us because.. Well, because it exists :P
<bbigras>
people seem to overreact to the CentOS change.
<abathur>
adisbladis: an obfuscator for shell scripts that just turns the WTF and horrifying arcana both up to 11
<gchristensen>
I get the feeling now is a good time to write about why rolling release is correct for nearly every use case
<drakonis>
write about rolling release and pinning is correct
<bbigras>
yeah you need pinning. or snapshots. imho
<drakonis>
it is absolute suffering to stay in some ancient distro release because it has the packages required for some old as fuuuuuuuuck software
<drakonis>
so you have to rely on outdated container tech to get newer software
<drakonis>
can't bump the kernel because the distro is old
<joepie91>
I would never use CentOS but I can 100% understand the anger
<joepie91>
apparently the migration to CentOS 8 was quite a bit of work, and then you get told "oh actually EOL goes from 2029 -> 2021, lol fuck you"
<joepie91>
I would be pissed too
<joepie91>
or well, not even 'told', exactly, you have to find out through other people because they conveniently danced around the matter in the press release
<drakonis>
i'm sitting on the centos irc channel and its melting down right now
<drakonis>
its a sight to behold
<adisbladis>
Hmm
<joepie91>
drakonis: where is this channel?
* joepie91
disaster tourist
* adisbladis
just joined #centos and hoping for some drama
<drakonis>
#centos-devel
<drakonis>
its there
kalbasit has quit [Ping timeout: 240 seconds]
<drakonis>
yesterday was much angrier
<drakonis>
how's the crystal-lang experience atm?
<adisbladis>
Iirc manveru was looking at crystal
<drakonis>
seems pretty interesting as a ruby replacement
<manveru[m]>
crystal is usually fine... using it a bunch still
endformationage has joined #nixos-chat
<manveru[m]>
it's just a PITA to keep updated with all the LLVM changes :|
thibm has quit [Quit: WeeChat 2.6]
<siraben>
I like me a good IRC drama channel
<siraben>
drakonis: no logs?
<drakonis>
it isnt irc drama
<drakonis>
it is filled with people furious about the changes to centos
<drakonis>
does crystal have a rails equivalent yet?
<drakonis>
given how similar its syntax is?
<drakonis>
among other things?
<drakonis>
i'm also curious whether it is worth using it over something like rust
kalbasit has joined #nixos-chat
Jackneill has joined #nixos-chat
<drakonis>
crystal's most popular packages are web frameworks lol
rajivr has quit [Quit: Connection closed for inactivity]
KREYREEN has quit [Remote host closed the connection]
KREYREEN has joined #nixos-chat
<manveru[m]>
i have no experience with rust...
<manveru[m]>
been using the Lucky framework with Crystal and it's not quite Rails :)
<manveru[m]>
but it does get a lot of things right and was pretty nice to use even with some heavy custom postgresql coding...
<manveru[m]>
for the past year or so i've mostly used it for smaller CLI stuff as glue between APIs and for infra automation
<samueldr>
manveru[m]: might be hard to answer, but are crystal binaries "slim"?
<samueldr>
I don't know if I will, but it might be something to look at for the Mobile NixOS init
<samueldr>
currently it's using mruby
<manveru[m]>
that kinda depends on how you compile it, you mean a statically linked version?
<samueldr>
not necessarily statically linked
<samueldr>
the question isn't good either :)
FRidh has quit [Ping timeout: 265 seconds]
<samueldr>
I'd have to explore to know I think
<adisbladis>
manveru[m]: Is it more on the Go end of the spectrum or something more reasonable ;)
<adisbladis>
I think is the question
<samueldr>
can you make its result closure fit in a tight disk space budget
<samueldr>
maybe that's a better question
<samueldr>
is there a big runtime that's hard to get rid of, or is it all added up as needed?
<adisbladis>
An even more pressing question: What should I have for dinner
<samueldr>
rubies and crystals
<etu>
adisbladis: tofu
<manveru[m]>
it's kinda like rust in that regard, the prelude is pretty big by default and depends on a bunch of libs
<adisbladis>
etu: Just plain tofu?
<etu>
adisbladis: With noodles
<adisbladis>
Nah
<etu>
adisbladis: And shiitake
<adisbladis>
I had that for the last few days already
<manveru[m]>
you can replace the prelude or statically compile, but by default your closure will be a couple megabytes at least
<samueldr>
good to know that, from what you say, they have that as a design element
<manveru[m]>
so hello world is like 3.4MB
<gchristensen>
samueldr: crystaline stage-1?
<samueldr>
keeping options open :)
<samueldr>
when time permits, so approximately at the heat death of universe, it'd be good to actually check for the "perfect" option for it
<manveru[m]>
both rust and crystal compile using llvm, so they have a lot of similarities :)
<manveru[m]>
but the support for embedded stuff is probably way stronger in rust due to the community
<samueldr>
yeah, the only "embedded-ish" part here is the tight space budget
<manveru[m]>
and now i wanna write my own prelude...
<samueldr>
that's because on some devices we have ~7MiB xz compressed total for everything in the userspace
<adisbladis>
How tight exactly?
<adisbladis>
Ah
<samueldr>
so not _that_ tight, but some deps are heavy already
<samueldr>
I wonder if it'd really help considering we already can compress the stage-1 stuff
<samueldr>
but a good idea to keep in mind
<samueldr>
tough maybe it wouldn't help as it's a .so that's big :)
<samueldr>
the real help would be digging into systemd and making a custom build to strip... whatever makes it big
<samueldr>
other udev weren't an option
<adisbladis>
Nah, we don't want "udev at home" :)
<samueldr>
I don't remember exactly the issues, but each had some
<samueldr>
one of them didn't support the same file format for the rules (booooo)
<drakonis>
manveru[m]: the crystal wiki says that amber and lucky are the closest to rails
<drakonis>
the syntax being so similar is certainly nice though
<manveru[m]>
it's really only similar at the surface
<drakonis>
you know, i'm baffled that i'm still using nix-shell
<drakonis>
instead of nix shell
<red[evilred]>
samueldr (IRC): if you want slim, you want zig
<drakonis>
i was wondering why it was downloading crystal 0.34 instead of 0.35
<energizer>
manveru[m]: what motivates you to use crystal instead of a more popular language?
<red[evilred]>
it;s ridiculous
<red[evilred]>
like hello world is like 1k
<drakonis>
i want to try zig too
<red[evilred]>
1k static
<red[evilred]>
because glibc is optional - they have their own (optional) which is slim
<red[evilred]>
so if you don't need glibc - you don''t need it
<manveru[m]>
energizer: mostly because i've used Ruby since ... 2005 or so, and it felt like a good compromise between scriptability and type safety
<energizer>
manveru[m]: ah i see, it's like an extension of your existing expertise
<manveru[m]>
yeah, just had to learn the type and macro systems, but i'd still not build something really big with it because of the dearth of available libraries for it
<manveru[m]>
but for your day-to-day scripting needs, it's pretty good :)
cirno-999 has quit [Ping timeout: 265 seconds]
ajs124 has quit [Quit: killed]
das_j has quit [Quit: killed]
<samueldr>
red[evilred]: I like to eat my cake too, so it has to be slim, AND batteries included
<JJJollyjim>
mmm i love the taste of batteries
<red[evilred]>
How were the edibles this morning samueldr (IRC) 《3
<red[evilred]>
Tee hee
<samueldr>
that was a partial use of having my cake and eating it too
<red[evilred]>
In all seriousness, I'm not sure you can have slim and batteries... they kinda contradict
das_j has joined #nixos-chat
ajs124 has joined #nixos-chat
<red[evilred]>
Partial cake function
<red[evilred]>
Curried cake?
<samueldr>
pretty sure it's possible
<samueldr>
easy? trivial? can't say
etu has quit [Quit: WeeChat 2.9]
talyz has quit [Quit: WeeChat 2.6]
<manveru[m]>
hmm
<manveru[m]>
`require "lib_c"; require "c/stdio"; LibC.printf pointerof("HELLO!\n".@c)` is 6k
<manveru[m]>
with glibc it's 1.3M
cirno-999 has joined #nixos-chat
<manveru[m]>
so yeah... gonna be hard to beat zig :)
<samueldr>
what I like from mruby, right now, is that there's just enough batteries laying around in mrbgems (either built-in or community) that I almost had nothing complex to deal with
<samueldr>
pretty much only had to build my damn app
<manveru[m]>
oh, got it down 512 bytes when skipping symbols :)
<manveru[m]>
but at that point you're just writing C...
<manveru[m]>
haven't tried mruby much yet
<samueldr>
mruby might have that drawback that it has the whole scripting runtime underneath still
<samueldr>
but right now it's convenient as you can trivially just add a bit of ruby as needed, no need to re-compile
<manveru[m]>
how big is it?
* samueldr
looks
etu has joined #nixos-chat
<red[evilred]>
Well, zig explicitly competes against C
<red[evilred]>
also - the author of zig also uses NixOS
<red[evilred]>
as their main platform so ...
<samueldr>
1.2MiB for the mruby executable as built for Mobile NixOS
<samueldr>
but it includes a GUI toolkit
<energizer>
isnt "slim and batteries" the whole point of zero-cost (dont pay for what you dont use)
<red[evilred]>
well, that's batteries optional, not included :-)
<red[evilred]>
but this is semantics I guess
talyz has joined #nixos-chat
<adisbladis>
samueldr: I wouldn't worry too much about scripting I think
<samueldr>
(continued looking) right, the actual .so for zeromq and the gui toolkit are independent
<adisbladis>
I hardly think you're doing anything performance critical?
<samueldr>
adisbladis: you're right, I don't care about performance (up to a point), mostly about correctness
<samueldr>
and here specifically, size
<adisbladis>
samueldr: Is there much point in switching from mruby?
<adisbladis>
I'm saying this as someone who.... Has strong words about ruby.
<samueldr>
not really
<samueldr>
about crystal, not really
<samueldr>
but I like to entertain the idea
<samueldr>
about switching to rust, there would be the point of more correctness
<samueldr>
(hopefully)
<adisbladis>
We were discussing D here earlier today, that might be a contender :)
<samueldr>
and more contributors nixos-adjacent
<samueldr>
the latter is more important
* adisbladis
likes writing D more than Rust
<samueldr>
I know Ruby isn't a well-loved language around the Nixpkgs parts :(
<samueldr>
(most likely due to not having used it, not for feelings against)
<adisbladis>
I wonder how small you could push micropython
<joepie91>
my experience with Ruby has primarily consisted of "why are the goddamn deps broken AGAIN"
<samueldr>
well, I don't do python, so I couldn't say :)
<manveru[m]>
that's my experience with python...
<joepie91>
to a lesser degree, but yes
<samueldr>
I won't talk about python since I don't really talk about things I don't have experience with
<samueldr>
but I've been avoiding it (due to lack of experience and familiarity)
<joepie91>
the problem that Ruby seems to have is that they're trying to do the "small modules" thing but without having a dependency system that can ergonomically support that
<joepie91>
(it's the usual flat-pile-of-deps stuff)
<samueldr>
I've never seen that
<samueldr>
but
<samueldr>
I don't mean that it's not the case
<joepie91>
my data is also limited but I've definitely seen more small-package stuff in Ruby than in Python
<adisbladis>
I think a lot of that is down to stdlib
<adisbladis>
samueldr: Btw I'm not trying to push python on you :)
<adisbladis>
I was just thinking out loud
<samueldr>
too late, you're in my "naughty" columns in the spreadsheet
<adisbladis>
=)
<samueldr>
if mruby hadn't worked, at the time I implemented it, it would have gone to lua, which I have experience with
<samueldr>
but there's quite a gap in what's included in the language and stdlib
<samueldr>
lua has... nothing... by design
<joepie91>
anyway, as a developer I don't have any experience with Ruby, I do have experience with Python, and honestly see no reason to use it over JS unless you really need a Python-specific dependency like scipy
neeasade has joined #nixos-chat
<adisbladis>
It'd be interesting to know what the "optimal" scripting language would be for Nix
<adisbladis>
I've been toying with the idea of reimplementing stdenv in !shell
<philipp[m]>
The second I posted it they corrected to 50 minutes.
<hexa->
ping again soon :po
<gchristensen>
is there a `growpart`-like tool that I can pass /dev/xvda3 to directly, as opposed to needing to convert "/dev/xvda3" to "/dev/xvda" and "3" ?
<samueldr>
energizer: in my opinion, it should be able to be more "ergonomic" with regards to composing complex behaviours... not that this describes any specific feature of functionality
<samueldr>
and, be _correct_
<samueldr>
gchristensen: I guess if there is one, it must do the same work itself
<gchristensen>
soundssmarter than my bash script
<energizer>
samueldr: what about haskell? nim? python?
<samueldr>
energizer: you're talking about which thing now?
<energizer>
samueldr: as a bash replacement for nixpkgs
<samueldr>
right, I don't know for now
<samueldr>
haven't played much other than trying execline
<samueldr>
but it also has to be simple enough for users unfamiliar with a particular language
<samueldr>
which bash kind of is because it's just a collection of commands
<energizer>
bash simplicity is an illusion imo
<samueldr>
and if it's part of stdenv, it needs to be bootstrappable from basically nothing
<samueldr>
energizer: an illusion that works for most cases
<energizer>
well imo bash fails an important test, which is that a newbie should be able to distinguish correct from incorrect
<samueldr>
I don't have the time to "debate me bash bad"
<samueldr>
sorry
<samueldr>
(I need to go back to what I was doing)
<energizer>
i'm not saying it's bad, i'm saying it fails one of the criteria you listed
<energizer>
but i guess one of the benefits of reproducibility is that if it coincidentally worked once, it'll continue to do so
<energizer>
so it doesnt really need to be correct/robust
<energizer>
it just has to do the right thing once
<samueldr>
sure, it fails one of the criteria, that's why I was playing around looking for _alternatives_
<energizer>
yeah i dont think you need to debate the point if you agree with it :D
<energizer>
but like i dont want complex quoting rules to be part of my day
<energizer>
on the other hand, the difficulty of writing correct bash means complexity doens't spiral out of hand because most people are too scared to write anything fancy
<energizer>
which might be an advantage
* joepie91
reminds energizer of the existence of Pmusic
<gchristensen>
it seems like there is no real way to go from /dev/xvda3 to "3"
<samueldr>
things under /dev are the files representing devices, under /sys is more of the API stuff
<gchristensen>
yeah
<samueldr>
not sure how to go from xxx2 to xxx
<gchristensen>
I was looking at blkid and lsblk --json -O --all | jq '.. | select(type == "object") | select(.fstype == "zfs_member") and other things like this and don't see any of them showing it
<samueldr>
you'd also need to validate against an nvme device
<gchristensen>
/sys/block/*/nvme0n1p2/uevent has PARTN
<samueldr>
I guess /sys/block/*/sdb2/partition is easier, gchristensen
<red[evilred]>
last call for pointy end up, flamey end down
<infinisil>
Oh no
<red[evilred]>
uh oh
<infinisil>
The anticipation continues!
<red[evilred]>
we don't know if it's a full scrub yet
<red[evilred]>
yes!
<red[evilred]>
new t0
<colemickens>
Gotta love a HN thread being completely indistinguishable from an /r/conspiracy thread. What a hellhole.
* colemickens
should take his own advice and stop hate reading
<red[evilred]>
17m!
<etu>
no?
<philipp[m]>
1:17 :D
<infinisil>
Nah just speculation
<etu>
yes
<etu>
Maybe 77 minutes
<philipp[m]>
22:40UTC as per official spacex stream
<infinisil>
Ohh
<infinisil>
420 ayyy
<etu>
philipp[m]: For me it says: "Tentative T-0 now 2240 UTC"
* etu
ain't waiting for that
<bbigras>
<insert musk blunt picture>
<philipp[m]>
Well, everything is tenitative with the launch of an experimental rocket, isn't it?
lunc has quit [Ping timeout: 265 seconds]
<red[evilred]>
I'm going to fall asleep before this thing launches aren't i
<hexa->
lmao
<hexa->
tuning back in
<hexa->
still says 50 mi ish
<hexa->
I feel like I've been here two hours ago
<philipp[m]>
Now they have an actual countdown again. 32 minutes on the clock.
<hexa->
21m ish
<infinisil>
I am hype!
* pie_
puts infinisil in a box
<hexa->
we were also hype yesterday :D
<gchristensen>
,launch 14min
<{^_^}>
14min: Ping for space stuff: infinisil Taneb ldlework etu philipp[m] eyJhb gchristensen
<philipp[m]>
Hahaha! Another boat.
<infinisil>
Get your snacks, this thing is about to blow!
<red[evilred]>
I have 3 different feeds running
<red[evilred]>
with SpaceX's sound feed
<philipp[m]>
Are three raptors enough to roast marshmellows?
<philipp[m]>
(I like mine as a very fine plasma)
<infinisil>
Fine choice good sir
<infinisil>
Dude, now that everydayastronaut explained what they want to do..
<infinisil>
Holy shit
<infinisil>
That's insane
<infinisil>
,launch
<{^_^}>
Ping for space stuff: infinisil Taneb ldlework etu philipp[m] eyJhb gchristensen
<infinisil>
1 minute!
<philipp[m]>
Let's gooo!
<infinisil>
HYPE
<infinisil>
WROOOOMM
<samueldr>
brrrrrrrrrrrrrrrrrr
<red[evilred]>
umm, that's one fire
<samueldr>
that looked... a bit flamey
<red[evilred]>
on fire
<infinisil>
It's fine!
<srhb>
Redundancy! woo.
<infinisil>
1 engine!
<infinisil>
Is this supposed to happen..?
<hexa->
hmmm
<infinisil>
It hasn't gone boom.. soooo maybe?
<srhb>
I am in doubt too, it almost looks like the remaining were centered each time
<srhb>
But it looked.. Very wrong :D
<samueldr>
my guess is it's to steer
<samueldr>
no need for the full fly-uppity power
<srhb>
Must be some docs somewhere.. It did look like the "off" nozzles were shuffled out of the way.
<infinisil>
Oh noo...
<infinisil>
HOLE
<infinisil>
HOLY
<samueldr>
it all depends on whether it lands or not
<infinisil>
It's fling!!
<samueldr>
(and where)
<infinisil>
It's flying!
<infinisil>
Well, falling I guess still
<samueldr>
is russia's anti ICBM thing aware of musk?
<danielrf[m]>
falling with style
<infinisil>
*silence*
<infinisil>
OH MY GOD
<samueldr>
oh no
<infinisil>
BOOM
<infinisil>
Wow dude, that was amazing, so close
<srhb>
It exploded in the exact right spot, looked fine to me.
<samueldr>
totallynotanicbm
<samueldr>
the fact it went exactly where it needed to, I guess for them it's great
<philipp[m]>
Daaaaamn, that was impressive.
<infinisil>
Green flame!
<red[evilred]>
yeah - the green flame is curious
<red[evilred]>
but yeah - that was SO close to nailing that landing
<red[evilred]>
(as opposed to nailing the landing pad)
<philipp[m]>
They hit that pad dead center though.
<red[evilred]>
they just showed the pad with the smouldering remains dead center
KREYREEN has quit [Remote host closed the connection]
KREYREEN has joined #nixos-chat
<srhb>
Mildly interesting that they have only two, then one engine near the very end, and in the opposite order of when they were turned off on ascent.
<srhb>
Want more commentary pls
<gchristensen>
that was pretty cool
<gchristensen>
I'm guessing that fire inside wasn't intentional :)
<srhb>
No, but definitely enjoyable!
<srhb>
At least on a test rocket :P
<philipp[m]>
I think it was intentional while turning off the engines.
<srhb>
Scott Manley says: "I'm definitly going with green exhaust = engine rich exhaust."
<srhb>
Lesson learned, don't put that much engine in your fuel.
<gchristensen>
hehe I mean the fire inside, on the edges of the cylinder
<philipp[m]>
While turning off the engines? I think that is planned.
<srhb>
Random stuff on the inner walls burning.. Probably not planned _against_ at least :P
cirno-999 has joined #nixos-chat
<philipp[m]>
I mean, they probably expect some unburnt propellant to end up there during engine shutoff. Those valves aren't binary and in the end you alway have some propellant and oxidiser leaking for a second when conditions aren't right for it to burn any more.