46900+ entries in 0.35s

shinohai: From now on,
I shall only !!up if
I have rated you and the sum of 0.001 as introductory fee is paid to my deedbot coffers. ( trinque/foundation taxes may apply )
ben_vulpes: is there a point to that sort of spam that
i don't understand?
mircea_popescu:
i dun think this is avoidable outside of chemical castration.
phf: the matrix had a particularly bad fallout in moscow.
i mean americans got off easy with "
i'll show you the truth blue pill/red pill".
i've lived through 3 years of 8 year old "neos"!
mircea_popescu: wait,
i thought the hackers was some hbo/lifetime tv series.
phf: (unrelatedly,
i've read the backlog,
i'm muling over it)
phf: it very much reminds me of 2600 and related radios.
i guess it's the same brooklyn resistance scene. the east coast counterpart to west coast mondo holywood
phf: like
i'm that russian guy in a smoked out room on a tiny x60 "da. poyehali!"
phf: having this shit run in the background makes me feel like
i finally made it into The Hackers
ben_vulpes: yeah
i recently tried a 'modern' asdf and recoiled in horror at how much it broke
mircea_popescu:
i know yesterday my hand smelled of burned rubber for wringing off teh used condom...
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:
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!' )
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:
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.
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 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
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.
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)
a111: Logged on 2017-12-29 17:32 phf: can
i fucking finish?
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 ☝︎☟︎☟︎ 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 runs with a special case of sat solver.
i don't understand which part of "asdf doesn't have a sat solver" and "sat is never mentioned" is not clear.
i'm saying that whatever dependency resolution is always a special case of sat. you put some contraints on it (no cirlces, etc.) and then you can have special case solutions.
phf: and there's probably no formal sat in asdf.
i'm saying that bulk of dependency resolution problems would come from sat though
phf: fare claims somewhere that he solved a gnarly dependency resolution bug in asdf, but the nature of bug is never revealed, and SAT is never mentioned (
i suspect most bugs in asdf would be SAT related)
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
☟︎ ben_vulpes:
i started vendoring swaths of lisp code recently myself
phf: (not to mention what
i bring up all the time, that asdf itself is the horror now)
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)
☟︎ phf: can
i fucking finish?
☟︎ phf: asciilifeform:
i know this one, it's unix!
mircea_popescu: you'll ruin my idea of romanian difficulty and
i'll end up going "what, you don't get this kindergarten fare?!?!" at poor innocent slavegirls.
mircea_popescu: "maybe if
i sit really still
i cease to be ? no ? how about if
i also close eyes ? still ? plug ears as well, how about then ???"
mircea_popescu: asciilifeform
i very frankly expect exactly nothing to be done about it ;
i'm just bitter and that's all.
mircea_popescu: asciilifeform no,
i understand why the sins of the flesh make this unavoidable. but it's still fucking wrong god damned it all to heck.
a111: Logged on 2017-12-29 15:30 mircea_popescu: ll ANSI compliant CL implementations with specialized versions tuned for implementations that offer unboxed 64bit arithmetic, unboxed 32bit arithmetic and for implementations with efficient fixnum arithmetic,
i.e. requiring fixnums that can represent (unsigned-byte 16)."
a111: Logged on 2017-12-29 02:59 phf:
i mean, if you read norvig's python snippets you can clearly see they are written by a very experienced lispers. you literally never see python like that in the wild, but yet there it is.
mircea_popescu: ll ANSI compliant CL implementations with specialized versions tuned for implementations that offer unboxed 64bit arithmetic, unboxed 32bit arithmetic and for implementations with efficient fixnum arithmetic,
i.e. requiring fixnums that can represent (unsigned-byte 16)."
☟︎ mod6: will see if
I can clean it up a bit more tomorrow.
trinque:
I admit to having wanted as little irc autism in my head as would make the thing go.
trinque: nickserv is what it is;
I didn't invent it
trinque: anyhow
I wrote it; ben_vulpes added a patch.
phf:
i would've remembered
a111: Logged on 2017-12-29 01:44 esthlos: fwiw
I read McIlroy's paper and would be willing to implement it _transparently_, if there's interest
a111: Logged on 2017-12-29 03:09 phf: but then
i can also understand the whole "back in my day" sentiment. common lisp certainly lets you write ~very sloppy~ code and get away with it :>
a111: Logged on 2017-12-29 03:05 esthlos: even with small C projects
I start to panic when
I realise
I don't know how it works anymore