HNHacker News
TopNewBestAskShowJobs

groovy2shoes

1,904 karma · joined February 3, 2011

https://github.com/baguette

cmburget@gmail.com

my topcolor is 8674a9

submissionscomments
groovy2shoes··on What can we learn from how compilers are designed?
Virtual dispatch in C++ and Java is dynamic dispatch, but it is singly so rather than multiply so as found in CLOS, Dylan, Julia, etc. If you want multiple dispatch in C++ and its kin, you need to jump through hoops with visitor patterns and such.
groovy2shoes··on Icelandic language battles threat of 'digital extinction'
Latin emphatically did not disappear with the fall of the Roman Empire. Classical Latin was preserved not only by the Roman Catholic Church, but also as the lingua franca of all educated discourse in the West into the 18th century (at least!). Initially, this was probably because education was typically provided by the Church, yet its use persisted after the Protestant Reformation and through the Age of Enlightenment before learned folk began to variously adopt French, German, and eventually English.

Classical Latin aside, sermo vulgaris ("the common speech"—"Vulgar Latin") never died so much as it evolved over time into our modern family of Romance languages: French, Spanish, Portuguese, Italian, Occitan, Catalan, Romanian, Dalmatian, Sardinian, …; the list goes on, but I'm sure you get the idea.

I think that, in the context of what I'm seeing throughout this thread, (and to be clear, this isn't directed at you specifically) before we worry that English will establish some sort of linguistic hegemony over the globe, we should first consider the processes by which some language or another comes to dominate international communication in such a way, and likewise the processes by which such an "auxiliary language" comes to be replaced eventually by another. I contend that the main reason English now serves the role once served by Latin is because the Anglosphere currently has much influence on the sociopoliticoeconomicocultural stage, yet it is not currently without rival on this stage. A century from now, it could happen that everyone will be learning Mandarin Chinese or Arabic or something else altogether. Perhaps Esperanto will finally take off.

Returning to Latin for a final thought: throughout medieval Europe this side of Macedonia, all educated people could read, write, and speak Latin, and no doubt they found that these abilities came in handy from time to time. Notwithstanding, it remained in place as a second language, reserved for specific situations and purposes, and they continued to employ their native language in their day-to-day activities—after all, we still have English, Irish, Gaelic, Scots, French, Dutch, German, Polish, Spanish, &c., &c. in the present. These are not the same languages that were spoken in the Middle Ages, nor are they the same languages that were spoken 100 years ago, but, as you pointed out, languages evolve and change.

groovy2shoes··on Icelandic language battles threat of 'digital extinction'
I'll admit that I've had very few opportunities to travel abroad thus far, but, for what it's worth, my experience has been the same. In fact, most people seem to be a bit gladdened to find that a foreigner (perhaps especially an English-speaking tourist) is making an effort to learn their native tongue. And also, likely, a bit amused by my shortcomings—but that's no big deal: it's how you learn.
groovy2shoes··on The More Gender Equality, the Fewer Women in STEM
I think GP means that she felt like engineer and doctor were the only options she could choose from, and therefore she was effectively dragooned into a STEM career. That is, if she'd been dealt a different hand, she would've preferred a career in something other than engineering or medicine.
groovy2shoes··on How to make a game from scratch using Lua and Löve
1. Tables in Lua have keys. Any value other than `nil` may be used as a key, including `0` if you so desire.

2. Lua's usage of `begin`/`end` was borrowed from "Modula" according to the HOPL paper[1]. Probably Modula-2, but the timeframe would not exclude Modula-3 as a possibility, though I suppose it doesn't really matter.

3. I find this to be a poor argument, but I've never felt like I was missing out on a whole lot by not having modification operators in Lua, either. It's not something that comes up often enough that the couple extra keystrokes should be a deal-breaker.

4. Lua added integers alongside flonums in 5.3, along with bitwise operators, but it's been possible to configure Lua's number representation at compile time for as long as I can remember. Prior to 5.3, anyone with a usecase that really necessitated bitwise operations could easily add them with a dozen lines of C code, or they could use LuaJIT which has offered bitops for some time.

I agree completely with points 5 and 6; nothing to add there :)

[1]: https://www.lua.org/doc/hopl.pdf

groovy2shoes··on Learning to program is getting harder
Really? I remember it being rather easy circa 2003. On Windows, you could download an installer for Dev-C++ or the Borland compiler, install it like any other program, and you were done. On virtually every other platform, you didn't have to do anything at all: the system came with a C++ toolchain ready to go.

I'd say it's still just as easy to get going with those sorts of tools now, and the same goes for many other languages, like Java and C# for example.

That said, I think the question of whether it was easier to start programming then versus now has a more nuanced answer. The kinds of programs people are likely going to want to write—like mobile apps, web apps, and games—are a lot more complex these days than their equivalents were back then. On the other hand, there are boatloads of free tooling and information readily-available to help people through it. On the third hand, there could perhaps be issues of information overload if you go looking without a guide.

So, getting started is one thing, and I can't say for sure whether it's harder now versus then. Of course, that's a slightly different question than whether it was easier to learn programming then versus now. This question is easy for me to answer: of course not, learning it now is just as easy[1] as it's ever been!

[1]: Or hard, if you're of the glass-half-empty persuasion ;)

groovy2shoes··on ‘Hypatia’ Stone Contains Compounds Not Found in the Solar System
I have a feeling TeMPOraL knows this, since their post is rife with Lovecraftian cosmicism :)
groovy2shoes··on Computer Science I [pdf]
There's no way this is true. I cut my teeth on Microsoft QuickBasic, and I promise you that QuickBasic has been far from my mind for many years. At this point, I've written programs in about 50 different languages (not all of them professionally): procedural, object-oriented, applicative, concatenative, relational; different paradigms require different "modes of reasoning" to properly wield.

To extend your translation analogy, it's rather like learning a natural language in that at first you might think in your native tongue and translate on-the-fly, but to become fluent you must really internalize the new language and learn to "switch" your thoughts into it. I feel like the linguistic concepts of "registers" and "code switching" apply well to formal languages as well as natural ones.

groovy2shoes··on Computer Science I [pdf]
Kinkos is called "FedEx Office" these days (last I checked), but indeed they can do this. So can Staples, Office Depot, OfficeMax, etc.
groovy2shoes··on How the Å came to be
Usage of <y> (and <th> for that matter) in place of <þ> predates Caxton's press. An example of a scribe substituting <y> for <þ> in manuscript can be seen at [1], a legal document in an English chancery hand from c. 1445. The use of <th> was already very common in the Middle English period, with <þ> (or later <y>) retaining use only in sigla (common scribal abbreviations). See [2], a page of Chaucer's Canterbury Tales from the Ellesmere manuscript (c. 1410) for example.

In fact, many (most?) of the works printed by Caxton himself actually do feature a distinct <þ> glyph, though it is limited in use to sigla (it never appears without a superscript <e> for <þe>, <t> for <þat>, …). His first printed English work [3], printed c. 1473 while he was still stationed at Bruges in what is now Belgium, has a distinct <þ>; his later works printed at his own press in London do also, such as [4] (which is printed c. 1480 in the typeface characteristic of his press).

For some related discussion, see [5].

That said, I share your dismay that we no longer have a <þ> (or, honestly, an <ð> or a <ȝ>, though [ð] and [θ] are allophones and the <gh> once represented by <ȝ> is now often silent). I just wouldn't be so quick to blame Caxton.

———

[1]: http://medievalwriting.50megs.com/scripts/examples/chancery6...

[2]: https://upload.wikimedia.org/wikipedia/commons/e/e0/Ellesmer...

[3]: http://lcweb2.loc.gov/cgi-bin/displayPhoto.pl?path=/service/...

[4]: https://upload.wikimedia.org/wikipedia/commons/b/bc/Brut_Chr...

[5]: https://news.ycombinator.com/item?id=15678583

groovy2shoes··on Maintaining an Independent Browser Is Expensive
> What has become quite obvious to me within the past few years is that the whole "move the Web forward" thing seems to be really about coming up with and implementing as many complex features as possible (and advocating for their use in new sites), making it harder over time for smaller efforts at creating independent browsers to produce anything useful.

Yeah, it's enough to be infuriating. I've recently been thinking about what it would take to implement a lynx-like browser that had a better understanding of layout and could deal with the modern web.

Hurdle number one is that there's no "Web standard", but rather a great many interrelated standards. At a bare minimum, you need HTTP K₁, SSL/TLS K₂, HTML K₃, XHTML, DOM N, CSS K₄, and ECMAScript K₅. Several of those standards are actually multiple standards, so you'll have to do some digging. That's the easiest hurdle to overcome. Number two is that a few of the standards (including some really fundamental ones like the DOM) are maintained as "living documents", making them moving targets; even the—uh—"dead" documents are subject to speedy revisions (for example, there have been 3 new ECMAScript revisions in the last 3 years). Number three is all the up-and-coming experimental stuff that isn't standardized yet, but if at least one browser supports something, some website somewhere is already using it. Between two and three, you'll need to keep a finger on the rapid pulse of the Web. And on top of all that, you have to support legacy bullshit, deal with malformed documents, and be ever hyper-aware of security threats.

Allowing for off-the-shelf components like libcurl and duktape, I'm sure it's still doable by a single person, but it's a lot of work (much of it frustrating).

groovy2shoes··on Reviving the 1973 Unix Programmer's Manual
There is a bit of a difference, though: if your shell has line-editing facilities (readline, libedit, and the like), they're available within the heredoc, but almost certainly not available on cat's stdin.

I suppose it's possible to have a version of cat that offers line-editing, but I'm not aware of one (nor do I think it's a particularly good idea to make one, "unix philosophy" and all that). Slap it into an rlwrap, maybe ;)

groovy2shoes··on Show HN: Forsh – A Unix shell embedded in Forth
As did various offerings from Apple, IBM, and several others, once upon a time: https://en.wikipedia.org/wiki/Open_Firmware
groovy2shoes··on Cursive Handwriting and Other Education Myths (2016)
Here's some handwriting sample for you:

https://i.imgur.com/0Pdq8Ci.jpg

Sorry for the poor photo quality, but it's the best I could manage to do at the moment.

On the left is some writing that I did just now, just for you! On the right is a page of notes that I wrote a few weeks ago. It didn't occur to me to get anything in there for scale until just now, but the larger notebook (the one on the right) is roughly 13 cm across by 21 cm high. The smaller one 12.7 cm by 19.6 cm according to the cover.

You can see on the right that I've written some elaborate headings... I'd imagine I'm one of very few people, if not the only person, who writes headings in such a script. Below that, you can see that I employ cursive and block for different purposes: most writing is in cursive, but "foreign" language (Old English in this case) words are written in block. I do similar things in other sorts of notes; for example, I might write source code or command names in block to keep them visually distinct from the commentary.

In the US, it seems that most people these days "learn" cursive at some point, but abandon it the first chance they get. This wasn't always the case (my mom and my grandma write exclusively in cursive, for example). Personally, I tend to only write with block letters if the scribbles are intended for a recipient (or, as mentioned above, as a semantic device).

groovy2shoes··on Cursive Handwriting and Other Education Myths (2016)
I had a buddy who would always "sign" receipts by drawing little doodles on the line. A different doodle each time, ranging from simple to elaborate, from decent to obscene, but always comical.
groovy2shoes··on The cargo cult of versioning
I definitely agree that printing was the main cause of the usage of <y> becoming commonplace, and it's likely because printing substantially lowered the cost of written material—both producing and purchasing. It enabled widespread dissemination of written documents for the first time, so any conventions printers happened to adopt then coincidentally became widespread. The arrival of the press is similarly credited with the development of a standard written form of English, though that would take some time to complete.

I spent some time poring over facsimiles of early printed English books. Caxton is credited with printing the first book in English, actually a couple years before he returned to England, while he was still in Flanders. In that book, it looks to me like there's two glyphs, one which resembles <þ> and one which resembles <y>, but they're used completely interchangeably as if they're the same character. However, pages printed on an actual press usually wound up smudging a bit when the page was peeled off of the block, so the differences I perceived could very well just be artifacts of the printing process rather than intentionally distinct glyphs.

That said, early books that were printed in England do have a noticeably distinct <þ> character, but it's use is limited to the common scribal abbreviations, which themselves are quite rare in this material. I couldn't pinpoint any precise date for <þ> -> <y>, but after around 1560, those old scribal abbreviations seem to disappear almost entirely (I only found one document after that which had any such abbreviations—from around 1680(!)—and this document unmistakably uses <y>). It's always apparent whether <y> is intended in its modern sense or as a substitute for <þ> because the abbreviations are always indicated with a superscript.

I wonder if abbreviations in certain types of work were viewed as un-ideal. They certainly seem less common (but still present) in longer works and in works which seem to be a bit more formal. In short works, especially where space was at a premium (broadsides, chapbooks, newsletters, etc.), they are more common, which is understandable. This also seems to be a continuation of a trend that started in manuscripts, where fancier and more elaborately-illuminated texts started employing abbreviations less often. But at the moment I haven't the foggiest why they appeared at all in longer works—especially when print comes into play—since their usage is rare and doesn't follow any obvious pattern—perhaps the typesetter was just running out of <t>'s!

The picture is pretty muddy, and further complicated by the timing of the press's appearance because we can't really know if the development of <þ> -> <y> would've happened anyway, or if it would've simply remained a quirk of certain scribes.

Anyway, when I woke up this morning I had no idea that this was how I was going to spend my day, and it was fun to dig through all this stuff :)

Slightly off-topic: while I was busy skimming facsimiles for abbreviations, I came across this gem, which I find both interesting and... "irrationally amusing" (I don't know how else to describe it, but if I weren't so robotic I might've been giggling like a child): http://hdl.huntington.org/cdm/singleitem/collection/p15150co...

groovy2shoes··on The cargo cult of versioning
I've been studying paleography for about a year now, and I really don't find this to be true. This seems to be a common story, one that I've heard before and one which makes plenty of sense, but also one which seems to be false. Certainly, the use of <y> in place of <þ> for certain common abbreviations would've become most common in the early days of the printing press—not because presses couldn't have a thorn character, but because it didn't make sense to spend resources making one if it wasn't necessary. However, the substitution of <y> for <þ> in scribal abbreviations started happening in English manuscripts even before the introduction of the printing press in England.

In the most common scripts at the time (cursiva anglicana and later bastarda anglicana), <y> and <þ> were already very similar (the only difference being which of the two strokes had the descender—both letters have a closed bowl in these scripts), so similar that it was common in bookhands to write a small dot above <y> to aid the reader even when <þ> was still visually distinct. You can see this clearly in [1], written c. 1399. Use of either character to represent <th> was already becoming quite rare in the late Middle English period, and remained in use almost exclusively as a scribal shorthand; it's not uncommon to encounter manuscripts in which <þ> and <th> are mixed freely.

I can't say for certain why it is that <y> started to be substituted for <þ> in manuscripts. Obviously in the common hands of the time they're visually very similar, yet I'd imagine anyone who'd been educated as a scribe would be able to spot and write the difference. Perhaps it was a stylistic choice. But it did happen: you can see an example at [2]. This document was written c. 1445. Gutenberg's printing press is thought to have been invented at this time, but it wouldn't arrive in England until Caxton set one up c. 1476. It seems very unlikely to me that the printing press had anything to do with the initial substitution, though I'd imagine that the press was a major nail in thorn's coffin.

[1]: https://en.wikipedia.org/wiki/Confessio_Amantis#/media/File:...

[2]: http://medievalwriting.50megs.com/scripts/examples/chancery6...

(both of these documents are written in a bastarda anglicana)

groovy2shoes··on 10 years of love for Emacs undone by a week of VSCode
cscope may be irrelevant, but ctags/etags has support for JS (and other languages that would be relevant for web developers, like HTML, PHP, Python, Ruby, SQL, ...).
groovy2shoes··on Standalone Signal Desktop
Electron lowers the knowledge barrier for people who are already knowledgeable in web development. For others, learning Electron can be far more complicated than learning, say, Vala or PyQt or Tk or even one of the plethora of Java toolkits, just as examples.
groovy2shoes··on Where Did the Fear of Poisoned Halloween Candy Come From? (2013)
The real travesty here is that anyone would consider it acceptable to give trick-or-treaters an apple. :)
groovy2shoes··on Superheroes a 'cultural catastrophe', says comics guru Alan Moore [2014]
> The media of today is often created by the very people who were dissatisfied with what was available to us back in the 80's. It'll be interesting to see what people dissatisfied with the media of today come up with in another 30 years.

This is a good observation, and seems to be true to me throughout literary/artistic history. You can look back through time, and many eras are obviously predominated by a particular creative movement, and each movement can be seen as a reaction of the previous dominant movement: postmodernism as a reaction of creators who were dissatisfied with modernism, modernism as a reaction of those who were dissatisfied with realism, itself a reaction to romanticism, etc. Hegelian dialectics come to mind.

Of course, the avant-garde of any era didn't necessarily dislike the former movement (or otherwise be entirely unappreciative of it) to be dissatisfied with it; the only needed to recognize the shortcomings therein. The ebb-and-flow of these movements makes me wonder if the arts are inherently unable to characterize and embody the human experience. I don't see any reason why that must be true, but the notion that people have been identifying and responding to the shortcomings of their broader artistic environments since the dawn of art itself makes me contemplative. Perhaps it's simply that the human experience itself is in a constant state of flux.

groovy2shoes··on Crystal in Production: Diploid
> Fran Allen is the opinion that the adoption of C delayed the field of compiler optimizations research back to pre-history (Coders at Work).

Yes! The entire book is wonderful, but as a compiler writer myself, Fran's interview really stuck with me.

The relevant passage, for the curious:

———

Seibel: When do you think was the last time that you programmed?

Allen: Oh, it was quite a while ago. I kind of stopped when C came out. That was a big blow. We were making so much good progress on optimizations and transformations. We were getting rid of just one nice problem after another. When C came out, at one of the SIGPLAN compiler conferences, there was a debate between Steve Johnson from Bell Labs, who was supporting C, and one of our people, Bill Harrison, who was working on a project that I had at that time supporting automatic optimization.

The nubbin of the debate was Steve's defense of not having to build optimizers anymore because the programmer would take care of it. That it was really a programmer's issue. The motivation for the design of C was three problems they couldn't solve in the high-level languages: One of them was interrupt handling. Another was scheduling resources, taking over the machine and scheduling a process that was in the queue. And a third one was allocating memory. And you couldn't do that from a high-level language. So that was the excuse for C.

Seibel: Do you think C is a reasonable language if they had restricted its use to operating-system kernels?

Allen: Oh, yeah. That would have been fine. And, in fact, you need to have something like that, something where experts can really fine-tune without big bottlenecks because those are key problems to solve.

By 1960, we had a long list of amazing languages: Lisp, APL, Fortran, COBOL, Algol 60. These are higher-level than C. We have seriously regressed, since C developed. C has destroyed our ability to advance the state of the art in automatic optimization, automatic parallelization, automatic mapping of a high-level language to the machine. This is one of the reasons compilers are …[sic] basically not taught much anymore in the colleges and universities.

Seibel: Surely there are still courses on building a compiler?

Allen: Not in lots of schools. It's shocking. There are still conferences going on, and people doing good algorithms, good work, but the payoff for that is, in my opinion, quite minimal. Because languages like C totally overspecify the solution of problems. Those kinds of languages are what is destroying computer science as a study.

———

(pp. 501-502)

I recommend that any programmer who hasn't read this book give it a read. In fact, I think I might give it another read this week :)

groovy2shoes··on The Uncanny Resurrection of Dungeons and Dragons
Perhaps it's due to my own personal shortcomings, but I found FAE really difficult to wrap my head around until I'd read through Fate Core. I do like its brevity and simplicity, especially now that I have a good understanding of it, but I felt like some parts of it were unclear to me as a fledgling.

> I love Fate Core, but it's very wordy because it functions as a toolkit to adapt the game to any sort of setting imaginable.

I can see why so many people love it! I like it, though I must admit it isn't my favorite (I don't play a lot of pulpy games, and I've found Fate works really well for pulp, as designed to do, but not particularly well for other tones (though not particularly poorly, either)). I just finished up another reply to GP, wherein I mention that toolkit-esque quality. I don't think I truly understood Fate as a system until I internalized that it's not a game so much as a foundation and scaffold for creating games. Fate's immediate ancestor, Fudge by Steffan O'Sullivan, is very much in the same vein, but, I think, more obviously so (the Fudge book itself reads more like a list of possibilities than a list of rules!).

> I'm working on a space opera variant (in the 27th century genetically engineered cosplayers, makers, scientists and pop culture enthusiasts set out to reconnect the lost civilizations of humanity) …

That sounds fun! Is it available on the web somewhere for perusal?

I myself am working on a game, as well, though I opted to try my hand at designing a system "from scratch" (more of an amalgam of lots of ideas and mechanics that I like and that seem to work well together; exceedingly few of them are my original creations, but I have a ludography documenting and acknowledging my inspirations). Unfortunately, it's been on the backburner for a little over a year now, and the partially-written playtest document is out of date wrt my notes.

Perhaps we could talk nerdy game-design sometime :)

groovy2shoes··on The Uncanny Resurrection of Dungeons and Dragons
> Oh, really? That's too bad, accelerated seems to be a way to get up to speed with Fate in a very short time without knowing anything about the game, shame that that's not so much the case.

You might be able to get by with just FAE and watching enough actual play to get a good grasp on how it works. For me, it felt like the FAE book sorta glossed over a lot of stuff that's more thoroughly explained in the Core book. That's just my experience, though; yours might well be different, of course!

> I browsed through that a bit and it seems to have the exact same text as the guide, so I'm a bit confused. Is it just the guide in HTML format?

Yup! It's exactly the same text, but some people prefer the organization and function to that of a book, so I figured I'd mention it :)

> That's a fantastic suggestion, thank you! I'll definitely check that out.

No problem! Fate—like its ancestor, Fudge—is so flexible and malleable that I've found it better to think of it as a framework/starting-point for creating a game rather than as a game in-and-of itself. Actually, it wasn't until I started thinking of it that way that I really felt like I understood the game. I think that if you take a look through some of those "Worlds of Adventure", you'll see it reflected therein: in tailoring the system to fit the setting, certain parts of the system are removed or restricted nearly as often as new parts are added.

> I've been playing D&D for a while, I just haven't DMed, so I'm not completely new to RPGs. I'll have a look at Dungeon World too, though, as it may fit our group better, thank you.

I wasn't sure how experienced your group is. Even if you decide not to play Dungeon World, I highly recommend reading over the GM chapters (The GM, First Session, Fronts, The World, Monsters, Equipment) and perhaps the appendices of the Dungeon World book (or "SRD" site as I linked before; it's the same text). The vast majority of the "rules", guidelines, and advice written there is generally applicable to GMing any sort of game. I've applied much of that stuff to D&D 5e and even GURPS games, and players have reacted positively. As an added bonus, I now spend far less time preparing for sessions (because I encourage and guide the players' own collaborative creativity so that we're largely creating the world and the plot on-the-fly, together as a group; they have more fun, sessions are railroad-free, and I have more freetime ;) ).

> Good call, I'm going to watch a few to get a feel for how the game is played, thanks again.

That group (modulo the guest player each season) has played a lot of different games, so if you're interested in checking out some new systems, I recommend looking through their videos :)

groovy2shoes··on The Uncanny Resurrection of Dungeons and Dragons
In my experience, the contents of the Accelerated Edition are nigh incomprehensible without a prior understanding of Core. I'd recommend that if you choose to play Accelerated, the GM be familiar with Core. It'll also be a lot easier to understand if you watch some "actual play" on YouTube beforehand.

Note that the text of both editions (as well the Fate Toolkit and some other goodies) is dual-licensed under CC-BY or OGL: http://www.faterpg.com/licensing/licensing-fate-cc-by/

The Fate SRD site is a third-party creation that presents the texts in a more convenient/organized way: https://fate-srd.com/

There's really no need to buy any books, but they're very reasonably-priced; the Core and Toolkit books are also very well-constructed and can withstand a good deal of usage. Though you can technically play with standard d6's, I'd recommend picking up some Fate (or Fudge) dice; I got a couple sets on Amazon, each set having enough dice for 3 players.

For stories/settings, there are loads of freely-available "Worlds of Adventure" on DriveThruRPG: http://www.drivethrurpg.com/browse/pub/2152/Evil-Hat-Product...

--

You might also like to check out Dungeon World if you haven't already: http://www.dungeon-world.com/

It similarly is CC-BY and has an "SRD" site: http://book.dwgazetteer.com/

IMO it's considerably easier to grok than Fate, especially for people new to RPGs, but YMMV. It also has a pretty expansive section of "rules" for the GM, which leaves room for little doubt about what the GM should be doing (and is, in large part, applicable to other games as well). It also uses standard d6's, so there's no need to invest in special dice (though the Fate dice sets aren't terribly expensive anyway).

I'll also plug Open Legend (I'm unaffiliated other than being a KS backer): http://www.openlegendrpg.com/

--

No matter what you decide to play, I highly recommend spending some time watching some "actual play" videos beforehand. I've found the Rollplay R&D series enjoyable: https://youtu.be/ooa-apRt2wk

groovy2shoes··on Show HN: Gutenberg – A static site engine as a single executable
I figured that's what you meant :)

I apologize if I came off as dismissive or disdainful; I was in a sort-of playful mood when I wrote that, but moods don't usually survive internet transmission!

It's a neat project. I myself don't have much use for a site generator of any sort, but I am interested in Rust (though I haven't had much opportunity to use it in the last year or so). I wonder: how are you liking Rust as a language? as an ecosystem? For a project like this, what advantages has Rust afforded? what disadvantages?

groovy2shoes··on Show HN: Gutenberg – A static site engine as a single executable
No dependencies? Then what's all this?

    [dependencies]
    clap = "2"
    chrono = "0.4"
    toml = "0.4"
    term-painter = "0.2"
    # Used in init to ensure the url given as base_url is a valid one
    url = "1.5"
    # Below is for the serve cmd
    staticfile = "0.4"
    iron = "0.5"
    mount = "0.3"
    notify = "4"
    ws = "0.7"
Not to mention the Rust toolchain!

You and I must have different ideas of what constitutes a dependency ;)

groovy2shoes··on Ohm: Parsing Made Easy
While PEGs necessarily impose a notion of "precedence" due to their construction, LL parsers don't necessarily impose any such notion. Any precedence that an LL parser might have is a consequence of its implementation. It's also possible to check an LL(1) grammar for ambiguities by computing an LL(1) parsing table and checking that any given (state, input) pair has at most one entry in the table. The process for other sorts of LL parsers is similar.
groovy2shoes··on Reflections of a Lifelong Metalhead
I would also pull in:

Dark Tranquility - The Gallery

At the Gates - Slaughter of the Soul

Edge of Sanity - Crimson

groovy2shoes··on SmallerC – Small, Simple, Self-Compiling, Single Pass C Compiler
That's likely because most C compilers (in my experience) use top-down parsers (LL) rather than bottom-up ones (LR).

In contrast to LR parsers, LL parsers are quite easy to write and maintain by hand (recursive descent, parser combinators, etc.), and the nature of such hand-written parsers makes it comparatively easy to step outside theoretical bounds and implement context-sensitive portions of the grammar. Such parsers have some other benefits, too, like being easier to debug and making it easier to provide useful error messages (but see Menhir for OCaml, for example, which offers some improvements in these areas over traditional LR parser generators).

What Appel has said is true—it's rare to encounter hand-written LR(1) or LALR(1) parsers in practice. However, many practical languages are easy enough to parse with hand-written top-down parsers that it's quite common to encounter hand-written LL(1)-ish parsers in practice.

← PreviousPage 4 of 34Next →