This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-08
Channels
- # bangalore-clj (5)
- # beginners (6)
- # boot (66)
- # cider (48)
- # cljsrn (14)
- # clojure (699)
- # clojure-austin (2)
- # clojure-berlin (1)
- # clojure-boston (5)
- # clojure-dev (3)
- # clojure-india (7)
- # clojure-italy (24)
- # clojure-nl (5)
- # clojure-russia (33)
- # clojure-spec (30)
- # clojure-uk (64)
- # clojure-ukraine (22)
- # clojurescript (123)
- # clojurewest (1)
- # cursive (18)
- # datascript (44)
- # datomic (12)
- # dirac (46)
- # figwheel (1)
- # gsoc (5)
- # hoplon (6)
- # immutant (29)
- # instaparse (1)
- # juxt (26)
- # lein-figwheel (5)
- # leiningen (4)
- # luminus (8)
- # mount (56)
- # off-topic (60)
- # om (67)
- # om-next (1)
- # onyx (8)
- # proton (28)
- # re-frame (125)
- # ring (3)
- # ring-swagger (3)
- # specter (22)
- # testing (2)
- # unrepl (1)
- # untangled (91)
Morning
I learned to code on a ZX-81 - that had an awesome keyboard, far better than all this modern rubbish
Even nostalgia isn’t what it used to be...
I made a joke about usenet newsgroup splits on a work slack, and no-one reacted - kids these days don't know the joys of rec.games.computer.ultima.dragons
rubber keys, @korny ? my zxspectrum had them too. but then i had a spectrum+ with plastic keys...
the keyboard was a plastic sheet that was "touch sensitive" with almost no feedback at all
well, it wasn't touch sensitive like a modern screen - you still had to push down on the "buttons"
It had a massive 1K of memory and (unlike the ZX81) it couldn't display on the TV and run calculations at the same time. So the screen went to 'snowstorm' when you ran something.
It came in two versions, kit form (build it yourself) and prebuilt! I think kit form was about £10 cheaper - so it cost £89.99 or £99.99 (from memory). I remember saving up Christmas and Birthday money plus pocket money for months to get one.
I saved up from my paper run - from memory my parents matched me dollar-for-dollar. I think I was aiming for a ZX-80 but by the time I had the money the ZX-81 was out\
I could never get games to load on my ZX81, had to manually enter the code each time
have to admit i never had a z81. i had a spectrum and spectrum+ and could load stuff from a casette player
my friend had the spectrum, so I have fond memories of the Horace games and Harrier Attack
Elite was fun
I work with the guy that wrote the spectrum game Gladiator - he's no longer a programmer and works in UX
elite & thrust
(tho on acorns rather than sinclair)
good morning
wow i remember how excited i was about that game. being a big tolkien fun. never really played much with it at the end tho
I probably spent more time entering the code than playing the game, but it was a good introduction to BASIC, although I didn't learn another language until a couple of years ago when otfrom made me learn Clojure 🙂
I couldn't possibly comment 😃
it's not bullying if you eventually like it, is it @thomas ?
very true @mccraigmccraig
it's part of the same group of behaviours as 'voluntelling' i think... there should be some better words
@minimal have you done cljs/sentry integration (i saw some relevant gists) ? not just the exception capture, i also want to create releases and upload source and source-maps - have you seen any boot tasks to do same ?
@mccraigmccraig yes, hold on
@mccraigmccraig I have a few tasks, one sec
@mccraigmccraig would be awesome to have that as a package on clojars wink
@martinklepsch nice, a lot more comprehensive. I’ve just been using a date based one and the implicit release creation on first error
thanks @minimal - i'll look at packaging @martinklepsch - since it looks like you've just saved me a bunch of time, i have some time to spend on it 😄
@minimal I think using a date is a great idea, probably better than git-sha or similarly “information-less"
The source map stuff with Sentry is really it’s killer feature and why I wrote the above. You need the releases stuff to upload source maps so it was more of a side-effect of wanting source maps 🙂
it also means that you can provide source maps for code deployed to mobile devices on file:///
urls
yeah, i've had the public source-map stuff working for a while on the web, but i'm getting some very unhelpful errors from android devices which could do with source-map magic
So I meant to ask earlier, how was the integrant talk last night?
good @yogidevbear - i got some ideas i can steal, inasmuch as one can steal open-sourced ideas
Real pity I missed it. Looked like it was going to be a good one