HN user

jean-

245 karma
Posts5
Comments32
View on HN

Great article. One of the papers it cites is https://arxiv.org/abs/2403.07183, which is also great and looks at the issue of LLM usage to write peer reviews.

It’s an issue I’ve noticed personally, as I’m seeing an increasing number of reviews that lack substance and are almost entirely made of filler content. Here’s an excerpt from a particularly egregious recent example I ran into, which had this to say on the subject of meaningful comparison to recent work:

Additionally, while the bibliography appears to be comprehensive, there could be some minor improvements, such as including more recent or relevant references if applicable.

The whole review was written like this, with no specific suggestions for improvement, just vague “if applicable” filler. Infuriating.

So happy to see tarot games mentioned on HN, I'm a big fan of their strategic depth and centuries-old cultural background.

Something a lot of people don't realise is that when tarot cards were invented, their intended purpose was to be a game. The whole divination/cartomancy aspect was made up much more recently, mostly to amuse French aristocrats.

An excellent resource for people interested in learning more about this very old tradition is the following YouTube channel: https://www.youtube.com/watch?v=DiCFfp_ZY4g

Mozilla VPN 6 years ago

I'm a Fastmail and Google Suite paying customer. I would SO transition to a "Firefox Suite" email+calendar service if Mozilla provided one.

> left and right.

I've never had it be necessary to use these words. Often "on my/your side" if I'm walking with someone, or "beside/towards X" if there's a feature there.

(it has deficiencies, and can be cumbersome, but these aren't them)

Surely the lack of words for left/right would make it pretty cumbersome to describe, say, the vehicle code, or to give driving directions, no?

Bilingual speakers tend to have a smaller vocabularies in each individual language than monolingual speakers

Do you have any citations to support this? From the research I have read (and my own anecdotal experience) this is not necessarily the case, especially when taking into account the bilingual speakers' dominant language.

See e.g.

Pearson et al. (1993). Lexical Development in Bilingual Infants and Toddlers: Comparison to Monolingual Norms.

Allman (2005). Vocabulary Size and Accuracy of Monolingual and Bilingual Preschool Children. – although note the difference in English vs Spanish vocabulary scores for monolingual vs bilingual speakers.

Absolutely. If your only input is the subject line, then you're dealing with a single-sentence classification task. You'd need to take the "class label" vector from the top layer of BERT (labelled "C" in Fig 2b of the paper) and then feed that to your own classifier.

For the experiments in paper they actually fine-tuned BERT on the downstream task, but I reckon you'd get acceptable performance by just keeping it fixed and using its outputs as features for a shallow classifier.

We always could do that with extensions

You couldn't, until Firefox 59. Before that, protocol handlers were not allowed to handle links to Dat/IPFS resources [0].

And while I agree with your comment regarding the chicken and egg problem, there are still some technical issues. As the shadowbanned sibling comment says, extensions don't have access to UDP/TCP sockets, meaning that you will need to run a gateway on your machine. See e.g. what dat-fox [1] does.

[0] https://developer.mozilla.org/en-US/Add-ons/WebExtensions/ma...

[1] https://github.com/sammacbeth/dat-fox

Vim 8.1 8 years ago

It's much more powerful than that, though. Among other things, it integrates very well with Kakoune's excellent support for multiple cursors.

You can get an idea of the kind of things that are possible from this demo: https://vimeo.com/82711574

Vim 8.1 8 years ago

There's a WIP Kakoune mode plugin for VSCode, [0] which is unfortunately unusable and unmaintained. I keep checking every couple of months, hoping the developer will pick it up again, but so far no luck.

[0] https://github.com/glennsl/kakode

It's a neat idea, but I'm not entirely sold.

How would you implement, amongst others: vectors and matrices, matched auto-sizing delimiters (\left and \right) \operatorname, \limits, \displaystyle, \textstyle? In my line of work, every other line of maths I write requires at least one of these LaTeX features.

Also: \underset / \overset, \underbracket / \overbracket

Good stuff. Would be even nicer if it showed information about optionally self-closing tags, which is one of the main reasons I occasionally need to look at the spec. For instance:

A p element's end tag may be omitted if the p element is immediately followed by an address, article, aside, blockquote, div, dl, fieldset, footer, form, h1, h2, h3, h4, h5, h6, header, hgroup, hr, main, nav, ol, p, pre, section, table, or ul, element, or if there is no more content in the parent element and the parent element is not an a element.

Links to the relevant parts of the official spec would be nice too, e.g. https://www.w3.org/TR/html5/grouping-content.html#the-p-elem...

Whoa, I have been working with Rust for a little over a year, and had no idea about the [-] button.

I would echo the suggestions to make that button much more visible. Or perhaps even have the top-level description expanded by default but method/trait descriptions hidden. I can't think of a case where you'd simultaneously want to see every method description.