Munksgaard

In Clojure, `[1 2 3]` is a vector, which is a distinct data type from a list, which looks like `(1 2 3)`. A vector in Common Lisp is written using `#(1 2 3)`.

Using vectors for function arguments is unique to Clojure, and I'm not entirely sure why they chose to do it that way.

Algebraic datatypes, which naturally begets Option and Either, predate OCaml.

Why is this (almost) at the top of HN? Nothing really stood out for me after a quick skim of the wiki page. Is there some additional context that I'm not aware of, or is this just a case of "huh, cool"?

This is great! Forth is such an interesting language.

Does anyone know of uses in industry?

Most of what you mention is filed automatically for me, here in Denmark. I think the only thing normal employees regularly file manually here is kms driven to and from work, which gives a tax deduction (kørselsgodtgørelse).

What's your take on the issues listed by formerly_proven[0]?

0: https://news.ycombinator.com/item?id=25844338

As far as I've understood, judges can (perhaps are even expected to) throw out cases that have no real evidence behind them. I could accuse you of stealing my car and sue you, but unless I have some basic proof, the judge doesn't have to take my case seriously.

People happily pay $20 to go to the movies. Why are nude photos, which might have same ratio of $/hour of entertainment or better, so much worse?

Is this really true? I know that, at least here in Denmark, the relevant authority has sent out a note saying, explicitly, that dying of eg. a heart attack, while infected with COVID-19, does not count as a COVID-19 death. It also explicitly says the same thing about motor-cycle accidents, which I know has been a rumor that has made the rounds.

Source: https://sundhedsdatastyrelsen.dk/-/media/sds/filer/rammer-og...

You're right, that was a a mischaracterization from my side. Thank you for the correction.

I must admit that I don't know anything about screenreading or accessibility in general, but I think you raise a valid concern: Certainly, the "next-generation good internet" should be accessible to all.

However, I would think that being much simpler (also, mind you, content-wise) would be a positive thing for gemini, in this context? Would you care to elaborate on what kinds of things are made harder by the choices gemini made? And what do you think could be done to alleviate those problems?

I think gemini[0] is an interesting alternative to the regular internet. It's deliberately designed to avoid many of the things making the web terrible[1].

0: https://gemini.circumlunar.space/

1: https://gemini.circumlunar.space/docs/faq.html

On the one hand, I agree. It is not good practice to blindly download and install through curlbash. On the other hand, that particular method of installation is ubiquitous nowadays. Hell even Rust presents it as the suggested method of installation[0]. Would you suggest Rust is a low-quality project? I don't think you can completely disregard something based on whether it suggests bashcurl for downloading and installing it.

Of course, in the ideal world, that's not the way it should be, but such is the reality we live in.

0: https://rustup.rs/

I'm guessing the code of conduct primarily concerns the software development process?

What am I looking at here?

Does someone have an ELI5 on what AMD has done since ~2015 to turn their whole operation around like this, and why these new processors are so good? What's the catch?

Obligatory xkcd: https://xkcd.com/882/

Out of curiosity, what printer would they be using for something like this? I've been considering getting a 3D-printer for a while, but I don't know enough to decide which one to get.

A portfolio management website (frontend and backend) and a portfolio performance calculation engine. You're welcome to contact me on my personal email, if you want to hear more.

I have worked professionally with Standard ML for a few years, but my friends and I used to joke that I was probably the only professional Standard ML developer in existence.

Worth noting: A colleague of mine recently released an implementation-agnostic package manager for Standard ML https://github.com/diku-dk/smlpkg

MLKit is a (quite performant) SML implementation written in Standard ML, including the parser.

> 1. Both Vim and Emacs are horribly annoying with their automatic indentation for SML. There is a lot of fighting against the editor in this department. In Emacs e.g. you have to delete whitespace all the time, because otherwise you'd have top-level function definitions shifted 80 characters to the right.

I've used sml-mode in Emacs for years, and I've never had the problem you're describing. On the contrary, I find sml-mode to be quite adequate for my needs. Can you elaborate a bit on what's causing you problems?

Edit: Ah, I see what you're saying. After finishing a function definition and starting a new, the cursor is wildly indented, that's true. But if you just type `fun` and press tab, sml-mode automatically indents the definition correctly.

> 2. I've used Poly/ML and SML/NJ so far. Both of them are purely interactive, meaning I can't just compile a program into ELF and ship it somewhere else without the compiler. That makes it a no-go for me for real-world use.

I can recommend MoSML for interactive development. It can also produce compiled binaries. When I want to produce efficient compiled code, I usually use MLton.

> 3. The interactive modes of Poly/ML and SML/NJ don't support readline shortcuts. They are the most cumbersome REPLs I've ever used.

Use the REPL in emacs, it's excellent.

> 4. Inline type declarations (as opposed to Haskell-style type declarations on a separate line) are very noisy - they make reading the code harder. Omitting them (which is the rule in SML in practice) leads to hard-to-decipher compilation errors when you write a new piece of code and you made an error somewhere which confused the type-inference about your intentions. Suddenly forgetting about a word or a set of parentheses in one function results in errors in another perfectly-good function. It's the horror of C++ templates all over again.

I agree, this is a pain point. I usually leave type declarations in comments before the definitions, but that of course has obvious drawbacks.

I don't know of any developed country where the police can reasonably expect to face better equipped adversaries than they can in the US. This is interesting for two reasons: You may have a point that it is necessary in the US for the police to have automatic weapons, but the US is also the only western country that has put itself in such a situation. Take from that what you will...

What's the caveat? I just read it and thoroughly enjoyed it.

Didn't a human being write the glibc implementation?

I'm not sure exactly what you're saying here, but if you're saying that the proposed algorithm will work for all mazes in RCT2, I think you're wrong: https://github.com/OpenRCT2/OpenRCT2/pull/12546#issuecomment...

Do you have any examples of such cases?

I'm asking because I'm part of the team that's working on the Futhark language[0], which is exactly what you're describing: a high-level array language in a functional style, targeting the GPU. We're always on the lookout for interesting applications or benchmarks. In particular, we're interested in knowing exactly where our shortcomings are, compared to hand-written GPU code, so that we may work on improving them. For the curious, we think we're doing reasonably well compared to benchmark suites such as Rodinia[1], though there are still cases where we cannot keep up.

[0]: https://futhark-lang.org/ [1]: https://futhark-lang.org/performance.html

Interesting that Haskell is so slow, I thought it was supposed to produce pretty performant code. Anyone have any idea why?

Interestingly, this package manager is based off of the Futhark package manager (https://futhark-lang.org/blog/2018-08-03-the-present-futhark...), which has a very simple, yet powerful design. It's basically language agnostic, which means the technique could easily be used for other languages as well.

Edit: It's also about time that SML got a proper package manager. Smackage never really worked well.