304500+ entries in 0.194s
ben_vulpes: > allows programmers
to work directly with objects as if
they were in memory while in fact
the object data is always stored persistently << stinks of ORM shit-dippery
ben_vulpes: were i not desperately
trying
to eke my own living out i would most likely be camping outside of
the cognitect offices until
they
took pity upon me and let me sweep
the floor.
phf: Don't worry you can hire
them
to consult :)
ben_vulpes: it is
the classic "db
that looks good but needs
tender loving care from its authors
to work well" software
trap.
phf: And
those proverbial millions of records require really beefy machines. 8gb of ram, fast flash drives, etc
☟︎ phf: Basically
the game becomes "how does query
translate into PostgreSQL so I can index all
the
things"
ben_vulpes: yeah, i only run on postgres for
that precise reason.
phf: Needless
to say it's nowhere near
there. Be prepared
to grok both datomic and
the underlying store.
phf: Sorry I'm on phone and just needed
to pipe in. But I picked up datomic on a project as "clojure
take on allegro cache" and I was expecting similar performance (tens of millions of records on a reasonable machine)
ben_vulpes: (and also as previously discussed in logs,
the scraps on my
table are rarely of "web scale" magnitude)
ben_vulpes: phf: i would like
to hear about what kinds of misery you've found in datomic. not
to doubt! never
to doubt
the misery of
technology. but out of curiosity, and limits-finding by proxy.
☟︎ ben_vulpes: mostly, i find rocks of various sharpness and heaviness and use
them
to beat my local reality into shape.
ben_vulpes: i wish i had
the historical perspective
to even know.
phf: Datomic is piece of shit for non-trivial datasets. I don't understand how
they could steal so much old lisp
tech and still manage
to fuck it up
ben_vulpes: whatever it is
that returns
the JSON
that sends mircea_popescu scrambling and screaming for
the "programmer's view"
ben_vulpes: asciilifeform: yes,
that. or your actual logic layer of choice.
trinque: tbh I'm willing
to consider
that if you wrote
too many layers of joins and views, you chose
the wrong data structure in
the beginning
☟︎ ben_vulpes: mostly, except as
trinque discovered when one goes
to do joins.
ben_vulpes: but i don't know enough about elephant
to say.
ben_vulpes: simple an EAVT data store with a single
threaded writer. caches recent images of
the db in peer memory (yes, 'immutable' db).
ben_vulpes: the answer
to 'ever play with symbolics *' is always 'no', dude.
ben_vulpes: effectively a distributed prolog-alike db,
to
the extent
that i can be
trusted
to call something 'prolog-alike'
ben_vulpes: proprietary proggy
that sits atop your $db of choice
ben_vulpes: look at
the upside!
think of all
the
tacks you don't have
to chew!
ben_vulpes: you could be fielding questions from clients past about why you billed
them nine hundred grand for misc. support over
the month.
phf: the-phuctoring is second
top ref from
trilema, losing out by a large margin
to
top ref ill-pay-for-your-tits
phf: (the last
three values are
totals)
phf: since
today is a looking at stats day, btcbase is at modest 3500 hits right now, which has been
the average since about april 6th, but note
that
the day is not over and system has been down for almost 8 hours.
the number of hits brought by referer has spiked
though
to ~~500, and looking at graph roughly correlates
to
trilema posts. not surprisingly
the
top referer is
trilema at ~~1000, followed by qntra at ~~600 and phuctor at ~~80.
mircea_popescu: but yes, pretty nifty as you can use it
to send a [sorta] encrypted message entirely via web
mircea_popescu: i put it on my pgp page on
trilema,. forgot all abpout it, now stumbled on it all over again
mircea_popescu: so isn't
this pretty much 99% of bignum->rsa in pgp format ?
mircea_popescu: PGencode.js particularily interesting i
thought as it really
takes base64 pubkey and puts it
through rsa.js
mircea_popescu: you're asking me who you
talked
to ? what am i,
the omniphone ?
fromphuctor___: will
the submit page
tell me my key is malformed if i made a mistake?
fromphuctor___: i need
to figure out how
to convert plain key
to
that base64/der stuff
mircea_popescu: helps build your identity, and you'll be able
to self-voice.
fromphuctor___: thanks... would
the phuctor checker work with non PGP keys, if i correctly converted an RSA key
to
the required format?
jurov: ssh-keyscan and
the github
trove are completely independent
things (former scans for server keys, latter are users' keys)
mircea_popescu: if you have a conversion script anywhere plox feel free
to publish.
mircea_popescu: fromphuctor__ yes but phuctor currently eats rfc 4880 format, owing
to its history as a pgp key checker.
mircea_popescu: the rub
there is, currently,
the conversion not
the acquisition