pdubroy

9 ms·

31.
Make It Happen(dubroy.com)
2 points by pdubroy 2y ago|0 comments
32.
Towards a unified theory of reactive UI (2019)(raphlinus.github.io)
1 points by pdubroy 2y ago|0 comments
33.
by pdubroy 2y ago
I found some benchmarks in the ANTLR project: https://github.com/antlr/grammars-v4/blob/master/java/java/B... Project Parsing/Lexing Ratio ----------------------------------
34.
by pdubroy 2y ago
Yes, you're right that PEG parsing is usually not the fastest option. As with many things, the operative question is: is it fast _enough_? > Note that this includes the time for tokenization, which is generally the bulk of the time
35.
by pdubroy 2y ago
It's worth noting that Python 3 uses a PEG-based parser and its performance (when it was introduced at least) was within 10% of the old parser: https://peps.python.org/pep-0617/
36.
by pdubroy 2y ago
Oh, that sounds cool! Are you on the Ohm Discord? I'd love to hear a bit more about this project :)
37.
by pdubroy 2y ago
Maintainer of Ohm here :) The main difference in Ohm grammars vs "standard" PEGs is support for left recursion. It's the same approach that was used in OMeta, which is described in the paper "Packrat parsers can support
38.
by pdubroy 2y ago
Very close! Alex Warth created OMeta ( https://en.wikipedia.org/wiki/OMeta ) as part of the STEPS project. Ohm was designed as a kind of successor to OMeta, but was created after STEPS.
39.
by pdubroy 2y ago
Thanks for the kind words :) I also wrote a blog post about some of the decisions that went into the visualizer: https://dubroy.com/blog/visualizing-packrat-parsing/
40.
by pdubroy 2y ago
Hey, author here! Yes, that's how I see it as well.
41.
Five coding hats(dubroy.com)
93 points by pdubroy 2y ago|39 comments
42.
by pdubroy 2y ago
Glad to hear! If you haven't looked at it in a while — we just published a draft of the final technical chapter, and are planning an official launch on March 4. So, might be a good time to dig back in :-)
43.
by pdubroy 2y ago
You should check out the book :-) We have a chapter called "What Makes WebAssembly Safe?" which covers the details. You can get a sneak peek here: https://bsky.app/profile/wasmgroundup.com/post/3lh2e
44.
by pdubroy 2y ago
This is great! The WebAssembly Core Specification is actually quite readable, although some of the language can be a bit intimidating if you're not used to reading programming language papers. If anyone is looking for a slightly more a
45.
by pdubroy 2y ago
Co-author of the post here — we had 280 characters in mind. :-)
46.
by pdubroy 2y ago
Cool — didn't know about that one! Thanks, I added it as an addendum to the OP.
47.
by pdubroy 2y ago
I think most people associate bytecode VMs / interpreters with general-purpose programming languages, but it's a surprisingly useful concept in other contexts. Sometimes bytecode VMs appear in unexpected places! A few that I'
48.
The Full Spectrum of Collaboration(zed.dev)
2 points by pdubroy 3y ago|0 comments
49.
by pdubroy 3y ago
Ohm and Chevrotain solve a similar problem, but chose quite different spots in the solution space. Ohm is focused on being easy to use. Grammars are generally very readable, and people love our online editor ( https://ohmjs.org&#x
50.
by pdubroy 3y ago
Ohm is based on parsing expression grammars: https://bford.info/pub/lang/peg/ The current implementation does use a tree-walk interpreter, but I'm considering creating a version that compiles to WebAssem
51.
by pdubroy 3y ago
Hi HN, I'm one of the authors of Ohm. Happy to answer any questions you have. We've been on here a few times before: • Ohm – A library and language for building parsers, interpreters, compilers, etc.: https://news.ycomb
52.
Great Works in Programming Languages(cis.upenn.edu)
3 points by pdubroy 4y ago|0 comments
53.
by pdubroy 4y ago
Acme was inspired by Oberon, and Oberon was inspired by a system called Cedar[1] which was created at Xerox PARC. From "Acme, A User Interface for Programmers"[2] by Rob Pike: > Cedar was, however, the major inspiration for Ob
54.
by pdubroy 4y ago
The rumor at the time was that they actually printed them out and went through them with a black marker. But now that I think of it, it couldn't have been true. With Courier 10pt you can fit about 4KB per page. So a 1GB core dump would
55.
by pdubroy 4y ago
Author here. Unfortunately, I don't actually know what happened to Ray...and it was long enough ago that I've forgotten his name!
56.
Core dumps, feedback loops, and a game of telephone(dubroy.com)
81 points by pdubroy 4y ago|12 comments
57.
Visualizing Packrat Parsing(dubroy.com)
2 points by pdubroy 5y ago|0 comments
58.
Visualizing Packrat Parsing(dubroy.com)
10 points by pdubroy 6y ago|0 comments
59.
Downs–Thomson Paradox(en.wikipedia.org)
1 points by pdubroy 6y ago|0 comments
60.
Incremental Packrat Parsing [pdf](ohmlang.github.io)
4 points by pdubroy 6y ago|0 comments

More ›