Hacker Newsnew | past | comments | ask | show | jobs | submit | xigoi's commentslogin

They’re making a prediction, not a value judgement.

I’d rather understand what my computer is doing than hope that fancy autocomplete happens to do the right thing.

Congratulations, you won $1000000! In order to continue, please download and open this HTML file.

Given that APL was punished for using a non-ASCII character set, this would presumably also affect 05AB1E.

I imagine that having to write

  for (int index = 0; index < size; ++index)
instead of

  for index in 0...size
eats up a lot of tokens, especially in C where you also need this construct for iterating over arrays.

The government already knows whether you have a car. What more information would they need?

If the tool that allows you to have a “noticeably better life” is heavily subsidized by venture capital, you have turned yourself into a ticking bomb.

I would certainly not consider package management to be a good part of JavaScript (or Rust, for that matter).

There is no such thing as a common subset of Markdown. Even basic things are rendered inconsistently by different implementations. If browsers decided to add Markdown support, this would lead to another “works only in Internet Explorer” situation.

> There is no such thing as a common subset of Markdown.

That was true before the widespread use of generative AI. LLM-generated markdown could _become_ the most common subset of Markdown, since machines can generate Markdown faster than humans.


“LLM generated Markdown” is not a coherent description of a language. LLMs can generate anything they have seen in their training data, which includes many incompatible dialects of Markdown.

Major LLMs (e.g. ChatGPT) have a copy button for their output, yielding markdown that is already being consistently rendered by other apps, reflecting what was consistently rendered as HTML. Presumably LLM vendors have built a deterministic way of generating spec-compliant HTML and their well-defined dialect of Markdown, otherwise their chat UI output would not render consistently.

I have certainly seen LLMs generate broken Markdown, so it’s presumably a “hope it works” thing.

I like it, but it doesn’t seem to have a specification, making it hard to create a new implementation.


That’s a reference, not a specification. I would expect something like a formal grammar or a description of a parsing algorithm.

Like the original Markdown. :)

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

Search: