Munksgaard

I'm also having trouble with getting it to read PDFs from URLs. I got this error:

web https://example.com/file.pdf Error: page.goto: net::ERR_ABORTED at https://example.com/file.pdf Call log: - navigating to "https://example.com/file.odf", waiting until "load" at main (/usr/local/lib/web2md/web2md.js:313:18) { name: 'Error' }

/workspace#

Just tried it out, but it's unclear what the different buttons at the bottom of the chat history does. The rightmost one (cloud with an upwards arrow) seems to do the same as the first?

I agree that the terminology is not ideal, but think there's a huge difference between JS' "weak types", i.e. abundant implicit conversions, and e.g. Elixirs "strong types", where `1 + "foo"` is a runtime error. I don't care if we call the latter something else though. Any good suggestions?

That said, I prefer having both strong and static typing, but that's another argument.

As someone who has used both SML, Haskell, Rust and Elixir professionally: No, not really.

Access to the BEAM is nice, but unless you're targeting the BEAM in your compiler I don't see any benefit. Even if you're targeting the BEAM, you might decide to use another language, cf. Gleam: https://github.com/gleam-lang/gleam/

Edit: Actually, one thing I will mention is the superior support in Elixir/Erlang for pattern matching bitstrings[0]. Not usually helpful in compilers, but an evolution of pattern matching that other languages should take up, in my opinion.

0: https://hexdocs.pm/elixir/Kernel.SpecialForms.html#%3C%3C%3E...

Erlang/Elixir are certainly strongly typed[0] but they are not statically typed[1].

0: https://en.wikipedia.org/wiki/Strong_and_weak_typing

1: https://en.wikipedia.org/wiki/Type_system#Static_type_checki...

Elixir has this, which is close:

    &foo(&1, bar)

Graphite.dev does this, and it works great.

Not quite. Note that the Elixir pipe puts the left hand of the pipe as the first argument in the right-hand function. E.g.

    x |> f(y) = f(x, y)

As a result, the Elixir variant cannot be defined as a well-typed function, but must be a macro.

There isn't actually any close() function in the std::fs::File: https://doc.rust-lang.org/std/fs/struct.File.html

The same way Rust prevents calling close() two times on a file.

Also, you don't actually have $5 in either box, but you once sold a 1% ownership stake in each box for 5 cents. There's only 10 cents in the in the merged box, but you value it at $10.

> - there is no way to browse navigation outside this broken ExDocs which outputs only HTML and LSP

ExDoc support outputting EPUB as well as HTML.

Meta is a couple of times larger than the entire entertainment industry combined...

I'm still not sure why I should switch away from alacritty...

You'll never guess what happened next!

Or `man ascii`

You're one of today's lucky 10,000: https://xkcd.com/1053/

I had the same reaction. But now I'm wondering, what is the intended way to close the minibuffer in these cases?

I use typst to generate PDFs on the fly in my sass-platform. The only other reliable ways I could find to do that was by using LaTeX (slow) or various WebKit-based tools (also slow, and in carious states of unmaintained/deprecated). It works like a charm.

Here's a direct link for anyone who, like me, would be interested in reading the original article: https://people.csail.mit.edu/rivest/pubs/BFPRT73.pdf

That's an impressive list of authors, for sure.

Maybe I'm missing something, but isn't Lisp the original version of this?

Your coffee machine uses AI to continually enhance your coffee experience based on the mineral contents of the water, the specific beans being used, your personal tastes and various other dynamic factors.

Have you looked at Futhark?

I've definitely heard variants of "the market will decide what is fraud" from people that I know in real life.

Reminds me of https://motherfrunker.ca/fsd/

Out of curiosity, what is the margin on their service income vs. their hardware income?

That's a bold claim, do you have any evidence to back that up with?

To be clear, I agree that it could be a reason, along with a multitude of others. I think that discerning which is the most substantial reason (if any such exist) is hard if not impossible.

> Single exit, though, means no "break", or "continue" for loops, and no early returns from functions.

Sounds like pretty standard functional programming a la Standard ML or Haskell, or am I missing something?

Perhaps I am unfamiliar with this usage of the word horde, but is it possible that you mean hoard?

I don't like curly braces, but I don't let that decide which programming languages I use.