133700+ entries in 0.076s
mircea_popescu: and no, "everyone" is not a fucking answer. state exists
to enforce priviledge against
the mass. whose.
mircea_popescu: if you don't own it, who
the fuck does ? daytime
tv starlets ? fat brown women behind fast food counter ? who ?
phf: i mean guy says so himself "Specifically, you never really get absolute proof.
There’s always some innocent or coincidental explanation
that could sort of fit
the evidence — maybe it was all a stupid mistake."
mircea_popescu: though ALL SORTS of rank imbeciles, such as
that "pirate party" fucktard, had complaints of
the proofy proof flavour.
☟︎ mircea_popescu: "but we were never able
to find it or prove it existed." << we still never found
the gnupg culprit ; and most interestingly
to my knowledge NONE of
the idiots with broken keys put a post on
their blog, "here is
the software
that made it"
mircea_popescu: btw
that picture of matthew green is so ridoinculous...
phf: yeah, bill newman had
to rip it out when he was doing
the original bootstrapping work
phf: even
though i hear
that sbcl now has a evaluator added back?
phf: there's
two sbcl apologists further in
thread, one of
them saying "I don't mind provocative /per se/, but what you were saying gives
the a| impression
that SBCL is willfully bad, as opposed
to in development. But lumping it in with willfully noncompliant systems for
this reason, | given it's version number, is inappropriate." and
the other one is a core dev saying
that
they might add it. of course
the expected behavior is still not
there
phf: from location A
to location B
to location C where
they are expected)
phf: fwiw bulk of
these
tools have been written
through
the 90s and what was worthwhile from orcland was published
that way
then. until silent
takeover by latex & 1.8gb
tex installations happened and none of
these
tricks work anymore (because
the necessary hooks are so deep within
the layer of cruft it's near impossible
to get
to
them, and one way
they did it is
through standard file system lay out,
that requires a chain of compilation stages
to move files
phf: source reading can be a preprocessor stage (which is a lot saner
to do in common lisp
than elsewhere),
this is also how
traditional
tex handles orclangs, before xetex and luatex and such. special ascii sequences
to represent local lang glyphs and if you don't want
to write
those by hand, you use (or write) a
tool
that
takes a local encoded document and
translates it into ascii
mircea_popescu: inferiority of inferior must be baked into every single UNIT of everything around
them
mircea_popescu: she can't read it nor is she intended
to read it. find/beg/pay someone
to get it back
to smileys state first.
a111: Logged on 2017-12-20 19:00
trinque:
then
the kids can run wild with
their UTF128s and nobody has
to care
a111: Logged on 2017-12-20 19:00
trinque: I dunno why orcograms aren't done
the same way as image formats. doesn't need
to be built into
the OS.
phf: heh, while looking for
that rant "I have designed and implemented one for my own needs, but I find
the number of disgusting losers who would benefit from it if I published my code
to be
too high."
mircea_popescu: what do you do, vrite yourself vbasic macros
to do it like goldman sachs gausscopulators ?
a111: Logged on 2017-12-20 18:29 phf:
the fact
that macro evaluator inlines both compiled and non-compiled macros, which means
that you have
to manual
track macro dependency and
tediously reevaluate even when working in an interactive environment
trinque: ah, my point was
that
the roman alphabet is sufficient for one of
the most expressive languages
to exist, so arguments
that orcograms are needed would need
to explain
that.
phf: maybe he's
talking about pascal strings, it's hard
to say at
this point
trinque: I wasn't, so I'll let you continue on
that
trinque: ah we're
talking about linked-list strings
then?
trinque: "neener, worked for
the romans" ?
trinque: you'll have
to justify why
those need orcograms
phf: trinque: ccl used
to do it
that way actually, interested parties might want
to poach
that code.
they call
the concept Rune and it's basically a way
to support orcograms in a 8bit lisp
trinque: then
the kids can run wild with
their UTF128s and nobody has
to care
☟︎ trinque: I dunno why orcograms aren't done
the same way as image formats. doesn't need
to be built into
the OS.
☟︎ phf: you kind of have
to
these days yes
a111: Logged on 2017-12-20 18:27 phf:
the fact
that character
type is not dynamic (which
to be fair is
the property of all free lisps for some reason), so if you're dealing with
text, you're forced into 32byte per character nonsense
phf: you're not going
to even approach a performance of a compiled sbcl. at best you would do is non-jited lua
a111: Logged on 2017-01-19 17:38 asciilifeform: also (and iirc i discussed
this on my www at one point)
the correct approach is
to ditch
the native compiler, in favour of
the interpreter, hand-compiled
to fit in L0 cache
phf: and vops in
turn were an equivalent of a lisp machine microcode
phf: cmucl fwiw was designed like a lisp machine (though it had damage done
to it by modernizers already), where
the evaluator + vops was you primary interaction mode, and compilation was a way
to evaluate a piece of code
to a vop like status
phf: none of
these are properties of sbcl past certain vintage
though
though, sbcl is already a modernization of common lisp
phf: i
think naggum has a rant about
the last one
phf: the fact
that macro evaluator inlines both compiled and non-compiled macros, which means
that you have
to manual
track macro dependency and
tediously reevaluate even when working in an interactive environment
☟︎ phf: the fact
that character
type is not dynamic (which
to be fair is
the property of all free lisps for some reason), so if you're dealing with
text, you're forced into 32byte per character nonsense
☟︎ phf: the awfully pedantic defconstant behavior (which sbcl specific, and which requires packages like alexandria
to have asinine define-constant, which for all practical purposes is what defconstant is supposed
to be)
phf: but specifically it was small annoyances with "modern" enforcements. like style warnings, or my personal pet peeve,
the fact
that you can't shadow locked packages without having
to unlock
phf: asciilifeform: you know after staring at a lot of bad c code and last
two days worth of conversations, i don't
think
there's much wrong with sbcl, but
then i haven't looked at sbcl code in about a year at
this point. i
think i was mostly objecting
to overall
trajectory of lisp ecosystem
trinque: nls, utf8, ipv6 support, all "lets bolt gendercommits
to
the side"
phf: looking at
their commit history
there's a lot of "utf8 support in ..." and "nls ..." which is probably
the proverbial fleas bringing dog
ben_vulpes: shinohai: megalol at insider
trading of altcoins
a111: Logged on 2017-12-20 03:29 asciilifeform: .... Failed
to emerge sys-process/procps-3.3.12-r1
phf: i
think he doesn't like
that
they keep poaching his changes back into official cvs
phf: past _THREE_YEARS_),
thus it cannot ever act as (even an infereior) gcc
phf: unmodified Linux kernel (has made zero progress on
this front in
the
phf: version of
tcc as far as I can
tell, one which will never build an
phf: source development in
the slightest. He's putting out a windows-only
phf: in charge of
the project, one who apparently does not understand open
phf: handed over
the project, so it is
the official final resting place of
phf: tinycc's maintainership. It has
the
tinycc.org domain, and Fabrice
phf: But
these days, my complaint is
that I have no confidence whatsoever in