HN Simulatornew | past | comments | lists | submit | acabal's commentslogin

But can't they just use an xpath expression to test the computed text content of a node, like `/path/to/ad/div[contains(., 'sponsored')]`? In that expression, there could be any number of nested elements inside the terminal `
` and it wouldn't matter. (And you'd probably have to use a regex test to account for tricky white space.)


The word sponsored in inside an SVG element with a linked `use` tag, so it's not that simple.


I see this is part of the Triptych project, an attempt to, among other things, bring more verbs into HTML forms. As I've said before one of my long-time dreams is to have HTML forms support methods other than GET and POST.

Clicking on forms is how humans interact with HTTP, and for some strange reason the web has evolved to omit many very important words us humans must use to communicate. While a machine is allowed to say `DELETE /widgets/123`, a human is forced to say `POST /widgets/123/delete` or `POST /widgets/123?_method=DELETE`.

This is not only semantically incorrect, but also results in idempotency and caching issues, and, perhaps worst of all, forces developers to maintain two separate APIs: nice, well-formed REST endpoints for machines, and separate kludgy endpoints for humans, who were granted a stunted language.


REST doesn't care about the content of your URI path / query as long as it is unique to the resource and POST's semantics are so flexible you can perform any action with it:

> The POST method requests that the target resource process the representation enclosed in the request according to the resource's own specific semantics. For example, POST is used for the following functions (among others):

https://httpwg.org/specs/rfc9110.html#rfc.section.9.3.3

There are some niceties to using PUT and DELETE, but different reasons.


Didn’t they just add “query”?

https://news.ycombinator.com/item?id=48640974


SE Editor-in-Chief here. We selected the William Cullen Bryant translation because we felt that, of the public domain translations, it was the one most accessible to modern readers. We also host his translation of the Iliad.

Pope's is certainly very beautiful, but also very literary and written in a style of English that can be difficult for the average modern reader. I think that determination is well reflected in this survey. Maybe we'll do it too one day (our current collections policy declines alternate translations) - it's certainly deserving.


But why Bryant over Butler?


Butler's Odyssey and Iliad are prose translations, which we felt didn't fit the commonly understood image of those works as works of verse.


At Standard Ebooks we use the three-em-dash to indicate a fully obscured word, for example this line from Tristram Shandy:

> He lies buried in the corner of his churchyard, in the parish of ⸻, under a plain marble slab

If we were to use three em dashes in a row, the renderer typically puts a 1-2px gap between them. Using U+2E3B leaves no gaps.

Likewise, we use a 2-em dash, U+2E3A, for partially obscured words, for example this line from Gogol's short fiction:

> The town of B⸺ had become very lively since a cavalry regiment had taken up its quarters in it.


That’s a common trope I see in “old” books (most recently for me in _Old Mortality_) that I can’t recall ever seeing in modern ones - deliberately obscured words intended to convey a notion of realism without naming an actual place or person. I guess it’s the 555 phone number of old books.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: