RX14

Have you considered the syntax crystal uses i.e. 42_i32 and 42_u8?

Personally I've had 0 issues with the bcachefs dkms packages from distro repos. Unlike zfs it keeps up with upstream kernel releases so it's far less hassle than running zfs dkms.

It's had consistent contributions for 5 years now, with the latest being about a month ago.

Hunting in modern rail vehicles is largely a solved problem using axle yaw dampers and other systems. I struggle to see why BART doesnt use a standard wheel profile and buy from a rolling stock supplier with experience of designing for good ride quality.

There are some trains which use independent wheels, but they need complicated mechanical centering mechanisms to replace the self-centering effect, and these are more expensive to maintain.

Long-distance trains in the UK manage about the same, with 200km/h max, but for more of the track (and higher accel/decel)

The -ls flag to find prints the same as ls

I would greatly greatly appreciate an effort to benchmark builds without optimizations too. We've seen some LLVM-related slowdowns in Crystal, and --release compile times are far less important than non-release builds to us.

DBMSes always keep their database in the file system in a consistent state to be able to recover from system crashes. Taking a file system snapshot is equivalent to pulling the power on the database server in terms of data recovery, but databases are designed to support this.

It seems a lot of people have these stories, and then people like me and OP who have had btrfs survive the most fucked up situations (I've had a btrfs nas built on "random drives I've had lying around" and abused it for 5 years and had 0 bugs at all).

I'm not sure what causes it, but there seems to be an effect where btrfs loves you or hates you and few people with mixed experiences regarding data loss. One possible cause is distro choice tends to be per person and how up to date said distro keeps it's kernel. But, I'm not sure.

My secondary motive is that I'm a girl :)

I certainly wasn't much more than sleepy and wanting to break the stereotypes on that particular expression when I wrote it.

First class? About a girl-year or two I'd guess. Fully usable? About half that.

If you reach out to manas directly, I'm sure they will be happy to have a sponsor for a particular feature.

Yes, you can do the same optimizations in Crystal, and Nim. Someone should write these and post the code for comparison.

Hopefully wasm's gc proposals will be implemented and get LLVM support, allowing languages like Crystal to sanely support wasm.

Yes, we do so for more complex formats like YAML and XML. However, for JSON, reimplementing is worth it for binary portability.

The basic foundations of a Windows port are already in place for Crystal, merged into master. In fact you can can already cross-compile a "Hello World" on Windows.

This means the port is in a place where the community can pitch in and help port little bits of the standard library, and help bring it into a release-ready condition.

Unfortunately there's no concrete timeline, it's being worked on on-and-off by the community.

If you have free time, or free money, it'd be a great help to the effort.

JSON is actually implemented entirely in Crystal for Crystal, I'm pretty sure it's the same for Nim too.

For a language which claims to be fast, having to use a C-based JSON parser would be a bit of a cop-out :)

The JSON code is written in a way which forces the whole object to be loaded into memory - both in Nim and Crystal. It would be interesting to compare code clarity and benchmarks for a streaming JSON implementation though.

Agree that performance comparisons between Nim and Crystal are going to be largely moot. They're both "fast enough" for their target audiences.

> We’ve been waiting for years.

I know, and it's unfortunate that there's not been time to work on this. I don't think people understand how small a language like Crystal is though. There's just one person working full-time on it currently!

If you'd like Windows support, one thing you could do to help is donate time or money to the Crystal project [1].

[1] https://salt.bountysource.com/teams/crystal-lang and https://opencollective.com/crystal-lang

Nice article!

There's one small error, where the article says "With Nim, we were also able to link both the Nim and C files into the same executable, which Crystal sadly cannot do." However, this is not true! You've passed the object file you created directly to the linker, so it is in fact included directly in the executable.

I'm a core team member of Crystal, feel free to ask away.

We used to be a pretty nice purple, and I kinda miss that.

It's unique selling point is union types as a part of the type system, with whole-program type inference and flow typing. This has never been done before (as far as I am aware), and it is incredibly powerful and interesting. It's compile-time duck typing.

It's certainly decentralized, just federated instead of distributed.

And yeah, it sucks as a protocol (but not that badly, the standard is just weak like everything else the w3c produces) but it's better than reinventing the wheel. Or letting twitter unilaterally dictate a standard.

And please stop spamming the same message down the page.

Matrix is a fundamentally broken protocol held up by the prowess of it's UI design team.

A long poll connection (i.e., a TCP connection not sending packets) uses exactly 0 joules of battery until something is sent.

Someone who has been doing this for years before serverless existed can set up and manage this infrastructure trivially, using almost no time compared to developing the application and the business. It also provides you with security: you know the pitfalls and the problems with hosting these, serverless is another new technology which can go wrong.

I suspect it's because he's so successful at spawning developer communities around the software he writes. Just look at sway: between 1.0 and 1.1 he was nowhere near the largest contributor. I'd guess that means a lot of time to work on other projects.

It's not a feature and you can't disable it, previously it'd just crash. I think it's to do with the content workers being `exec`d from disk each time instead of forking from a master.