shawn

30 ms·

91.
by shawn 8y ago
But then we wouldn't get to call the debugger Numen: https://github.com/gruseom/numen Also https://github.com/sctb/lumen/pull/169
92.
by shawn 8y ago
https://github.com/sctb/lumen/blob/master/compiler.l One of the coolest projects. Lumen is entirely self-hosted, so compiler.js is built from compiler.l which represents an algorithm that defines how to
93.
Abuse: a game written in Lisp in 1995(abuse.zoy.org)
1 points by shawn 8y ago|0 comments
94.
by shawn 8y ago
oh my you just made my week, month, and year. I've been looking for a practical Lisp-based game design since I was a teen! Dude. Thank you. EDIT: THIS IS SO COOL http://abuse.zoy.org/browser/abuse/trunk/d
95.
by shawn 8y ago
Bahaha, 3 of the 30 front page stories are about Lisp. Yessss, rise, Rise! Let the Lisp dominance commence! Take to the streets and take macros into your hearts! Demand a formal holiday to celebrate all conses! Tear off those strongly typed
96.
by shawn 8y ago
Yes! I've been fascinated with GOAL / GOOL for nearly a decade. I ripped a copy of Last of Us and tore through the game data looking for the lisp code, but unfortunately they only ship the compiled output. What I wouldn't giv
97.
by shawn 8y ago
It might take a moment to familiarize oneself with macros or a DSL, but does that not almost precisely define react component definitions? Surprisingly, the answer seems to be no. Experienced react devs rely heavily on metacomponents: com
98.
by shawn 8y ago
Suppose you were forced to use a language with no objects, and no closures. Since you're an effective dev, you'd find ways to cope. But we invented object systems to do better work. Closures were another step up the ladder of abst
99.
by shawn 8y ago
Lots of Lisp interest today! Here are a few resources. On Lisp: https://www.lurklurk.org/onlisp/onlisp.pdf Lumen - a Lisp for JavaScript and Lua: https://github.com/sctb/lumen The Art of the Inter
100.
by shawn 8y ago
There is no security benefit to forbidding pasting. https://www.troyhunt.com/the-cobra-effect-that-is-disabling/ Why do people do it? The same reason people believe /dev/random provides security benefits. It&
101.
by shawn 8y ago
Emacs is a very important ecosystem that effectively uses macros. The danger of macro overcomplication is real, and emacs' conventions are the primary way they avoid introducing problems. For example, macros and functions are nearly th
102.
by shawn 8y ago
Just wanted to say thanks for taking the time to give feedback. Swinging through the jungles of a new ecosystem is always fun, and guideposts like this are quite helpful.
103.
by shawn 8y ago
Thanks! I appreciate pointing that out.
104.
by shawn 8y ago
Hey, I’m in Chi too! Right by North and Clybourn’s redline stop. If you ever want to reverse engineer this together or figure out how to train a drone to fly itself, drop an email / keybase.
105.
by shawn 8y ago
Is executable bloat worth worrying about?
106.
by shawn 8y ago
I... am not sure. On one hand, it's instructive for language designers to know what turns out to be a barrier to entry. They're often unexpected things. And what's worse, users usually run into them and then quietly disappear
107.
by shawn 8y ago
FWIW, those four links are already purple for me. The reason it's difficult is that it simultaneously introduces the concepts of optionals, unwrapping, string processing, variable assignment, and lifetime management. It's not like
108.
by shawn 8y ago
Well yes, if you've written 1000 lines of Rust, it's certainly trivial. Writing the first 20 lines is an <expletive> though.
109.
by shawn 8y ago
Thank you . I spent ... more time than I'm comfortable admitting trying to figure out how to do that. Out of curiosity, did you spot any other antipatterns? I'm sure there are a bunch: https://gist.github.com/shaw
110.
by shawn 8y ago
It is decidedly not a language to get things done. I say this as someone who put himself in the unfortunate position of challenging BurntSushi (author of ripgrep) to a coding duel, bragging that I could get LuaJIT to match his XSV perform
111.
by shawn 8y ago
Sounds good! I'll hopefully have something interesting by the end of the weekend.
112.
by shawn 8y ago
Agreed, though I'm mainly seeing how quickly I can reimplement everything xsv has to offer without sacrificing performance. I don't consider the challenge finished until, as you say, it handles all of the corner cases. EDIT: I&#x2
113.
by shawn 8y ago
It's just counting lines and skipping any whose contents are "\r" or blank. I believe this is correct behavior because: foo,bar,"quux zap",bang `xsv count` returns 0 for this. Is there any situation where c
114.
by shawn 8y ago
Ok, the `count` command is implemented. The code is 27 lines: https://gist.github.com/shawwn/e178e597cbf7f3682153e449f6633... Without indexing, LuaJIT is twice as fast as XSV for 2.6M rows: $ rm data/*.csv.idx
115.
by shawn 8y ago
Initial results: A naive parser in LuaJIT of your xsv-stats example: > (do (set csv (load "reader.l")) (set plays ((get (require 'system) 'read-file) "data/nfl_all_plays_small.csv"))
116.
by shawn 8y ago
Just to raise the visibility of this: lettergram's HNProfile project is awesome . It identified both of my alt accounts: https://news.ycombinator.com/item?id=17944348
117.
by shawn 8y ago
Wow. Cheers for one of the coolest things I've ever seen on HN. (The algorithm identified not one, but both of my former alts.) Edited to tone down the reaction, but that's amazing.
118.
by shawn 8y ago
Till recently, my primary account was a certain prominent account on HN. I was wondering if you'd be willing to email me the name of it. I would be shocked and impressed, and it would serve as a great demo. (I totally believe you. I&#x
119.
by shawn 8y ago
rust-csv compiled and ran flawlessly. xsv had an error: https://github.com/BurntSushi/xsv/issues/139 Also loved this: // OMG I HATE BYTE STRING LITERALS SO MUCH. fn b(s: &str) -> &a
120.
by shawn 8y ago
That’s very cool! Thank you for pointing out the counterexample.

More ›