reycharles

To be fair, the bug report is against a type of software that is famously stochastic and unreproducible.

Would you mind sharing the name of that plugin? Thanks!

> Why wouldn't these tools be available suddenly?

Take a look at how ridiculously much money is invested in these tools and the companies behind them. Those investments expect a return somehow.

It's a type of rock

Not directly, but it sets a course where this might change.

One reason why they're not the same is because the memory representation is different (sort of). This will break FFIs if you allow reordering the tuple arbitrarily.

> 200 years ago the average life expectancy was 30

If you take out infant mortality the life expectancy wasn't all that different from what it is today. https://pmc.ncbi.nlm.nih.gov/articles/PMC2625386/

to be fair they said "test for everything"

I would say they would worry if they were even remotely in touch with nature.

I wrote a small thing for adding a `#doc List.find` directive. However, I don't maintain it anymore since I think it doesn't see much use and it's work to keep up on OCaml compiler internals changes (and it's my impression it never picked up much adoption). https://github.com/reynir/ocp-index-top

dbuenzli's down also has a similar feature.

In an electric car? Really? I don't know too much about electric cars, but it's my impression that gears and transmissions are completely unnecessary in an electric car. Please correct me if I am wrong.

The README has this text:

> For example, if you are using a recent version of OpenSSH, you may wish to explore using the ServerAliveInterval and ServerAliveCountMax options to have the SSH client exit if it finds itself no longer connected to the server. In many ways this may be a better solution than the monitoring port.

Are you the author? I found a few bugs. For example, using domain/ as the path makes it think there is no path.

ETA: example https://url-parts.glitch.me/?url=https://news.ycombinator.co...

I helped build a tar-backed filesystem for MirageOS[0]. It is definitely easiest to make it append-only. I did add in-place renaming, updates (of file content), pre-allocating a file and removing the last file.

We also scan the filesystem on boot and keep a mapping in-memory of file names to file metadata and block offsets, and update this memory representation when modifying the on-disk tar filesystem. If you have a lot of small files this is maybe not a great idea as you will be storing most in memory, though.

For the purpose we had in mind it worked fine: A content addressable mirror of package archives. The archives exist somewhere on the web and the package file has a link to the archive and a checksum. We can then download the package and store it by the checksum. This gives integrity that the tar filesystem does not offer. Removing the last file works great if you only have one download job. Otherwise if a download fails and it is not the latest file you can rename it to `failed/<hash>-<random>` and do garbage collection in the filesystem at a later point.

[0]: https://github.com/mirage/ocaml-tar/blob/main/mirage/tar_mir...

Update: interestingly, this was motivated after trying to use a (mostly) LittleFS-compatible filesystem which unfortunately didn't work very well for us at the time (bugs, poor performance).

It is possible to run Mirage in ARM under for example KVM or using the seccomp target.

There is as well an experimental bare-metal target for raspberry pi 4 called gilbraltar https://github.com/dinosaure/gilbraltar. A big obstacle there is the device drivers. It is very cool to run bare metal on an rpi4, but it would be cool to be able use the network interface too.

A big difference in my opinion is that projects like Mirage does not try to reimplement the same hardware drivers as the host system and instead implements much simpler drivers for virtual hardware.

For example, how do you write to a block device? You make a hypercall with a "handle", offset into the block device, the number of blocks to write and a pointer to memory to be written. There's no pretending it's a spinny disk with sectors and heads or what have you.

https://github.com/Solo5/solo5/blob/bf29b8af11feec9dbc2e74cc...

Indeed, and I believe it predates all the other ones by quite a bit.

> Woke Finns add American Pronouns to their twitter pages.

Could it be these Finns interact with English speaking tweeps?

Why did you make this comment?

> Facebook is not a monopoly.

Are we not living on the same planet?

No, Reason's actual name is Reason. The Reason ML name is similar to Go's "golang" name -- to work around the SEO nightmare the choice of the name really is. Your comment is otherwise correct in that Reason is an alternative syntax for good 'ole OCaml.

They mentioned that in the article and link to another article about this.

> Also I think the name 'sum type' is bad.

The intuition is that for each types A and B with number of elemnts |A| and |B| the sum type A+B has number of elements |A|+|B|.

> If I'm going somewhere for a coffee, it's good to be able to charge my phone too.

Here it's more common you leave the phone at the bar to be recharged if charging your phone is what you want.

Their headquarters were in Sweden less than a year ago. Nordea is a merger of a lot of Scandinavian and Finnish banks. I don't think it's fair to call it a Finn bank.

Why do you soak the lentils?

I find that the problem with the ternary operator isn't the operator itself per se, but the concrete syntax. If you could write it

    result = if boolean_flag
        then do_this()
        else do_that();

then I'm sure no one would find it as bad as they do now. The way you formatted the ternary with line-breaks helps a lot, too, I think!

I get hit with a login page. Can anyone describe what is linked to?

It's my understanding that the counter measures being completely broken (or not) doesn't matter.