81200+ entries in 0.656s

mircea_popescu: we are, intellectually speaking, in the bizarre situation of st. petersburg,
a small town on the mississppi where for some bizarro enchantment reason all the boys decided the thing to do is dig up the river. and drowned there.
mircea_popescu: nevertheless, the problem here isn't
a discrete technological product, be it
a font or
a bridge ; nor the dysfunctional process that produced it, be it
a broken cnc mill or lucent ; but altogether something more fundamental, where young man looking to "go west" decides the west is at the bottom of the lake and proceeds to dig.
mircea_popescu: this is not so different from the problem of, eg, emacs. or plan9. or any software. or any fucking shop in
a town, or
a mall. why the fuck are there FIFTY fast food offering the same crap in the food court ?
mircea_popescu: instead, those rapidly diminishing returns drive
a diminishing of quality.
mircea_popescu: there is absoloutely no reason there should be more than maybe
a dozen or so fonts. but there are, because "easy to make", and in spite of the rapidly diminishing returns of "making".
mircea_popescu: so you are essentially looking at
a collection of ink spots, until you fall over.
mircea_popescu:
a) you can not meaningfully say if you've found
a "good" font, seeing how you can't say what portion of fonts youv'e actually seen ; b) the very notion of good font is impossible because in principle all possible fonts were made already in triplicate.
mircea_popescu: consider
a simpler problem - you wish for whatever reason to "pick
a good font". suppose your "good" is specified. you proceed to... look at fonts, selected by some criteria. eventually you are tired to the point your eyes blur, and haven't seen 5% of the available offerigs in "gothic medieval" from one place. there's more places. when are you done ?
phf: now the question of whether or not designing
a font language that simulates movement of calligraphic brushstrokes is
a good idea..
mircea_popescu: phf even limiting the matter to ttfs (seriously, postcript is
a whole extra layer of crazy) one quickly discovers some very serious conceptual problems. i don't even mean from
a technological pov.
trinque: in reading the source, the bsd folks crapped
a bunch of things that should be in
a sed-like into cat.
phf: i think that's
a separate set for their own postscript implementation
trinque: they got it
a .io for the better to hackernews you with
phf: (it also has
a nifty set of astro tools, that i use to chart the skys from time to time, because it's really easy to use and i don't know any better)
phf: well, it's
a 93 whitepaper :)
phf: i don't know. it has
a whitepaper though
trinque: and something quite stupid and forth-y could handle parsing
a rudimentary set of possible statements to
a db which eats from one serial port, shits to another
trinque: I've thought having
a hardware parser/filter on
a serial line where only certain bits can possibly flow over, and only in certain order, would compliment it.
trinque: his serial diode concept being
a good example
trinque: though
a topic I've been thinking upon
a lot is, trigger warnings to asciilifeform, mitigations
shinohai is still trying to source
a nice 2005 thinkpad
trinque: seems this runs the risk of continuously being
a refugee. "they broke my emacs, so I left for hemlock/climacs/etc, then they broke my X, then they broke my ..."
trinque: I'll be clinging to
a frozen emacs version and frozen pile of elisp til valhalla.
phf: breaks my heart all that's been done to emacs. it used to have
a strong culture of backwards compatibility. large packages would have compat files compat-19.el, compat-20.el, etc. where's now only latest and greatest work. used to be very non-dwim, now every single package insist on some "smart input" dwimy interaction mode. but all this complexity is broken, things clash and interact with each other in all kinds of funny ways
trinque: at any rate, if I were to invest time in climacs, that is time stolen from learning osdev to put
a lisp interpreter on iron, which is time stolen from learning to fab silicon in
a garage, which is time stolen from ...
☟︎ trinque: there was
a "10 cans of soda" thread
trinque: I keep hoping for
a g_l writeup on the subj, but do not see
a blog anywhere
a111: Logged on 2016-11-30 21:12 asciilifeform: re elisp, imho the 'apocalyptic' scale of the problem is overblown, if every d00d were to rewrite the few 100 of elisp that he actually ~uses~, in climacs, or whereever, job would be done in
a week.
mircea_popescu: in principle this should be automatable tro
a huge degree
mircea_popescu: "The number of people aboard who can matter-of-factly hack the Emacs internals on the C level is consistently going down, and is already so small they can be counted on one hand. We must make Emacs depend less on people from this small and diminishing group, if we want the development pace increased or even kept at its current level." << this is
a very solid point.
mircea_popescu: it also makes 0 sense for it to be
a c piece of code, but that's
a discussion for another time
mircea_popescu: well, from
a system design perspective. it makes 0 sense for emacs to actually save c machine state.
yalehasaquestion: hey, I'd like to know, I've been running
a listening node, and I added 46.166.165.30 as
a peer -- but I don't look like I'm connected to it
mircea_popescu: meanwhile according to reddit, theguardian.com is
a respectable source and qntra.net is the spamsite. because totally.
mircea_popescu: meanwhile the idiots at the guardian made
a begging banner which has an X that is not connected to anything, just drawn on the banner itself.
jurov: i have read that tobacco must be dried slowly (like,
a month) otherwise it retains more sugar which burns nastily
BingoBoingo: jurov: the linked eclipse thing is cigarette shaped fiberglass reinforced paper tube tipped with charcoal. Is
a lulzy thing best not stuck in mouth.
jurov: nope, e-cigs are
a thing here
mircea_popescu: whatever his plans, desires, choices whatever, it seems absolutely certain trump will have
a major depression on his hands ; to the tune of "70% of this country's wealth evaporated overnight ; wut do ?!?!"
mircea_popescu: srsly, the world is now
a us-iran partnership trying to stand up to
a russian-turkey alliance while
a very horny europe is drooling cunt juice on one side and
a rather geeky china is holding its distance on the other side.
mircea_popescu: <BingoBoingo> Seriously not
a single attempt to read any of the linked content to develop context on the venue << i dunno dood, "the serene republic of somalia" etc. they be trynna.
BingoBoingo: Seriously not
a single attempt to read any of the linked content to develop context on the venue
trinque: I have
a hard time seeing how
a single DNS record within the set could accidentally be missing.
mod6: shouldn't be
a problem... so weird
trinque: makes me think this is
a jihadi decimation strategy, if you can call it that.
mats: half
a dozen chix go public with 'hersh raped me when i was 9'
trinque grunting out
a few things of his own
diana_coman: danielpbarron, automating storage retrieval/mixing would be great and it's sorely needed; for starters maybe have
a look at the code in botstorage.cpp as that one deals with storage (it was used by an earlier version of the bot to get the ingredients directly from storage)
danielpbarron: which btw i'm gonna figure out
a way to automate storage procedures like withdrawing in bulk and mixing
diana_coman: like all stops, it was but
a break I suppose; even if
a ...hmmmm, 10 years break sort of thing
diana_coman programmed (briefly) long time ago for
a French open-source company; with azerty keyboard + unicode support because "clients" mostly French public sector entities -> after that initial experience (in fairness the unicode part was but
a very small part of it - the bulk was the overall nonsense of the "endeavours") I just stopped programming all together (I got back into it years later mainly because ...eulora)
mod6: <+mircea_popescu> speaking of above article, can i get
a commitment to never signing any V material which includes any non-ascii characters ? BingoBoingo diana_coman hanbot trinque mod6 danielpbarron mircea_popescu mike_c asciilifeform davout ben_vulpes phf jurov << I commit to never signing any V material with non-ascii characters.
mircea_popescu: in principle there is
a strong argument to say "alphabet size = machine word size" even if this didn't hold on pre-8 bit machines. and consequently you ~could~ have
a type string that always takes 4 bytes and represents whatever the fuck. the problem is that this gives you
a 400% memory allocation bloat for that type of string.
a111: Logged on 2016-11-29 14:43 phf: we had
a thread when diff was first discussed as
a way to do patches (i think maybe before even v), where i was erring on the side of no unicode support on the grounds that if we decide to support unicode we have to, to borrow asciilifeforms, drink the whole spittoon