130700+ entries in 0.074s

mod6: "are
the air jordans still available?"
this is like
the 3rd or 4th guy.
ben_vulpes: there's no way
that Lord_dpb in
the l0de chat is danielpbarron is it?
ben_vulpes: yeah i recently
tried a 'modern' asdf and recoiled in horror at how much it broke
phf: from xach's quicklisp update "This update was created with an older version of SBCL.
The latest SBCL includes ASDF 3.3.1, which breaks a handful of projects in ways
that have not been resolved yet."
mircea_popescu: i know yesterday my hand smelled of burned rubber for wringing off
teh used condom...
mircea_popescu: maybe
they fucked so vigurously,
the friction alighted
them.
a111: Logged on 2017-12-29 20:26 BingoBoingo: In other news NYC apartment fire
that killed 12 being called deadlist since 1992 provinding ample fodder for 9/11 lovers
BingoBoingo: <mircea_popescu>
http://btcbase.org/log/2017-12-29#1760909 << recall
the good old days when
the "reddit experts" / pantsuit&allies actually got
to burn in warehouses rather
than 18sqft ny apartments ?<<
That was last year, and how did
te steel melt if
there was no fire??
☝︎ pete_dushenski: time (indicates variation between apparent and mean solar
time)
pete_dushenski: just read about
the 5451-piece richard mille "jura" clock in quebec city, as it happens, and i'll definitely be checking it out next
time i'm
there. apparently
the
thing
took 6 years
to build, which isn't so hard
to believe when you see
that incorporates a perpetual calendar (which knows leap years from non-leap years, unlike an annual calendar), rementoire d'egalite (for improving accuracy), and equation of
pete_dushenski: can't have
too many public clocks
though. so much
the more if
they're
technically novel.
a111: Logged on 2017-12-23 16:38 shinohai suddenly wonders if pete_dushenski has ever seen
those steam-powered clocks
that are in Canada ....
pete_dushenski:
http://btcbase.org/log/2017-12-23#1757448 << it just so happens
that i saw one in vancouver's gastown neighbourhood last month. not
the most
tuneful steam whistle and it looks far older
than
the 40 years of age it actually is, but
the plaque did indicate
that it was something of a
technical innovation. looked like a simplified rube goldberg machine
to me.
☝︎ a111: Logged on 2017-12-29 20:50 asciilifeform: ( asciilifeform , like complete idiot, went and
thought... 'i can make a useful diagram! with svg ! which exists!' )
mircea_popescu: seems like
the pantsuit lost 90% of sqfootage per capita in
the past
three years, from ~10
to ~1.
a111: Logged on 2017-12-29 20:26 BingoBoingo: In other news NYC apartment fire
that killed 12 being called deadlist since 1992 provinding ample fodder for 9/11 lovers
a111: Logged on 2016-09-18 22:53 phf: yes, scp, screen, asdf. i had a v based deployment but i wasn't happy with it, so i'm
trying
to rethink it
mircea_popescu: i also seem
to recall he didn't like it for some reason. anyways.
mircea_popescu: i
thought it was re his difficulties in updating
the machinery behind btcbase without downtime
mircea_popescu: nor is it reasonable
thereby
to expect "this lisp instance runs while a new press gets pulled in"
mircea_popescu: nor is
there such a
thing as
triple bypass while running a marathon
mircea_popescu: the point is
that item either a) operates continuously, provided it is
THIS item, ie,
this specific collection of parts or else b) is stopped while beingt serviced, ie having a cog replaced.
there's no clock
that works while having its cogs switched around.
mircea_popescu: asciilifeform fuckgoats still is
THIS orrery, rather
than "hotswappable"
mircea_popescu: i can understand
the fascination with "this orrery has been in clickety-clacking continuously since 1625", but let's point out
that it relies on a)
THIS orrery, as opposed
to "constantly changing randomly pile of cogs" and b) it's a discrete mechanism, like
the human heart. it
takes a break every beat. essentially
the problem has been hidden, by
these, not resolved.
mircea_popescu: but from a sustainability pow : eulora server currently restarts weekly ; not necessarily because it absolutely must, but because i deliberately did not want
to provide a "continuous" item in
this sense.
a111: Logged on 2017-12-29 19:35 phf: lisps deal with freshly-pressed instances as well as anything else: by doing a clean restart. my point is not lisps, my point is
that current solution assumes lack of state and delegates
the problem
to a non-v-tronic build system
mircea_popescu: is
the entirety of
this fiddling you going "i'm curious how
this
thing could work/break at
the edges?" or is it rather "i wonder how i could run a v
tree as an infrastructure node without reboots" ?
a111: Logged on 2017-12-29 19:18 phf: for example one
thing
that i
tried with my lisp workflow is
to have
the system automatically compile/load
touched files in
their order of appearance in a v patch. but
the order here is explicitly linear, requires fiddling with patch order, and is definitely not how we use it now
a111: Logged on 2017-12-29 19:14 phf: v also doesn't solve all
the problems
that asdf attempts
to solve (for example compilation dependency)
a111: Logged on 2017-12-29 19:03 phf: also particularly gendered packages outright put #-asdf3 (error "requires asdf3") and ~usually~ it's because
they silently rely on uiop, far's unix compatability layer
a111: Logged on 2017-12-29 18:59 phf: ben_vulpes: note
that older versions of asdf actually work. i've been running 1.369 in my cmucl, and it does require manually updating half of your asdf
to remove various later extensions, but it works
mircea_popescu: asciilifeform nothing wrong with summary as is, so it'll change, still better an idea
than a blank.
mircea_popescu: pete_dushenski not
the "or addressed directly" rider either.
a111: Logged on 2017-12-28 02:58 shinohai: ah mircea_popescu lookup has been
there a while, but i
think i forgot
to have pete_dushenski push it
to his bots page updates.
mircea_popescu: "publish" means "form, and fix
the form" not necessarily "share with cows".
mircea_popescu: phf and if you don't share with heathens, make it so !!shelf returns a pile encrypted
to my key for instance, nothing wrong with
that.
☟︎ a111: Logged on 2017-12-29 17:36 phf: (which is by
the way not what i do, i just fucking fix. every. single. fucking. piece. of. quicklisp. packaged. code. i. get. my. hands. on. motherfuckers)
mircea_popescu: here's a problem i perceive phf : you could guess about log(n) of my understanding of various
things
that interest me on
the basis of reading
trilema ; i could not guess epsilon of
thge say your understanding of sbcl on
the basis of reading whatever you provide voluntarily. i could glean it from
this kind of interaction, but here's what
that means :
http://btcbase.org/log/2017-12-29#1760839 ☝︎☟︎☟︎ BingoBoingo: In other news NYC apartment fire
that killed 12 being called deadlist since 1992 provinding ample fodder for 9/11 lovers
☟︎☟︎ a111: Logged on 2017-12-27 02:01 asciilifeform: picture a kind of 'multiverse ada', where you dun call foo(bar), but instead foo:somepatchid(bar:somepatchid) etc, explicitly conforming
to 'multiversism'...
phf: lisps deal with freshly-pressed instances as well as anything else: by doing a clean restart. my point is not lisps, my point is
that current solution assumes lack of state and delegates
the problem
to a non-v-tronic build system
☟︎ phf: obviously not designed for
that, but
the assumption here
then is
that you're running a fresh instance for each fresh press, which is suboptimal for a lisp (this particular detail will likewise come up when v is run on an always-on system of any kind, be
that a cuntoo or a lispm)
phf: also v doesn't recognize state. in a
tree A->B pressing
to A,
then loading,
then pressing
to B,
then loading is different
than pressing
to B right away and loading
the result
phf: for example one
thing
that i
tried with my lisp workflow is
to have
the system automatically compile/load
touched files in
their order of appearance in a v patch. but
the order here is explicitly linear, requires fiddling with patch order, and is definitely not how we use it now
☟︎ phf: v relies on build systems
to actually build
phf: v also doesn't solve all
the problems
that asdf attempts
to solve (for example compilation dependency)
☟︎