jdub

Richard says he's not autistic. People who try to conflate his bad behaviour and autism are excusing his behaviour and unfairly generalising about autistic people.

Richard is argumentative about his bad behaviour. He's not oblivious. Plenty of people have spoken to him about it. You'd think he might take a hint after being removed from his own organisation and all the surrounding commentary. He doesn't care.

(Separately, "techrights" is run by an obsessive troll who harasses people in the FLOSS community.)

It's not an email client.

I think this is a massive win for Mozilla, which may end up having a longer and larger impact on the world than Firefox.

Having "control" over Rust didn't ever seem like Mozilla's goal (nor in its interests), so the trajectory of the language since 1.0, its healthy and energetic community, and the founding members of the independent Rust Foundation is a huge achievement.

Thanks to Mozilla for incubating a long shot project.

Not really. They share some dependencies, and there's quite a bit of desire to work on those dependencies together (via the rust-vmm project).

It's more like a persistent 60/40 (or optimistically 70/30) split, but it's understandable that some people are simply wrong.

And the rest of the developed world applauds their attempts to catch up.

It's Python. So it's Monty Python.

It doesn't go both ways, and that's precisely the point the original poster was trying to make. US parties do not behave the same way. One has been festering extremism for 60 years.

Ah, I wondered why that tweet was going around again! :-)

A little tribute to Phil Karlton's classic. And DNS.

Parler was set up by spivs and cranks to encourage fools and fascists to gather and destroy civil society. Now that same civil society has rejected them. Don't feel too bad.

The change from GNOME 1 to 2 was much greater than the change from 2 to 3, and there were people who complained (and attributed malice to GNOME contributors) on both occasions.

The project has a point of view: that software freedom should be accessible and usable for everyone.

If that doesn't excite you, cool. But it has improved the entire FLOSS / Linux stack over the last couple of decades, whether you use GNOME or not.

It's not virtualisation.

Check out SolidRun's Honeycomb LX2K. All very normal: Mini ITX, PCIe x8, DDR4 SODIMMs, USB 3.0, M.2 for NVMe. Bonus: 4 10GbE SFP+ ports.

Mine is a delight.

https://www.solid-run.com/nxp-lx2160a-family/honeycomb-works...

Rockchip, Mediatek, and Qualcomm are not in the same ballpark as Apple Silicon. They're barely in the same sport.

Very little will change for most developers.

I suspect you're deploying on Linux, right? You're already building and deploying on different operating systems, how much can a different architecture complicate things? Well...

What if you're using interpreted or VM languages (Python, Java, PHP)? Unless you have native dependencies, very little changes.

If you build native code (C/C++, Go, Rust), then you might need to cross-compile. That might range from super-easy if you're 100% Rust or Go, to challenging if you have C/C++ dependencies.

But you use CI, right? In that case, the problem almost disappears. Test locally (ARM) without cross-compiling, build and deploy on CI (x86) without cross-compiling.

Who builds deployment artefacts locally these days? Hopefully very few. :-)

There are some macOS-on-M1-specific issues you might face if you're using Docker (native ARM or virtualised x86) containers, but those will clear up soon enough.

I'd take the improved CPU and memory performance of the M1, but I don't need a laptop refresh, and the Mac Mini can't drive two DisplayPort displays yet.

I didn't see it in the post, but a huge amount of this is due to Andy Grove's work on Rust implementations of Apache Arrow and DataFusion.

I imagine he's happy where he is, but I hope there's some opportunity for InfluxDB to give credit and support for his great work.

That's a very, very old "manifesto" that was pasted verbatim into almost every FLOSS news site and mailing list at the time (relevant or not), written by a well known troll and harasser who was removed from multiple FLOSS communities.

Yeah! The amount of toil and burden AWS removes or reduces for me across the board (security, managed services, running multiple datacentres and everything necessary to do so…) means I can work on vastly more valuable things. Which more than makes up for the price.

The cost of 1 server is not a sufficient metric of value.

Every company I've worked for in the last ten years has needed all of the above, and I like to work for small companies (fewer than 100 people). Only in the last couple of years have I had any interest or need to branch out to the other clouds, largely because they're doing specific things really well.

Are there tens of regions around the world? Are there multiple AZs within a region that are single-digit milliseconds apart? Can I autoscale? Is there a managed load balancer? Do I have to manage my own database instances and availability? Do I have access to hundreds of other services for things that I don't want to spend time managing myself?

Aren't we years beyond the 1:1 cost comparison for a single server argument?

That's a different concept of abandonment to what's happening with the Xorg server code today.

If you're talking about forks, they're pretty much the complete opposite of abandonment. Forks exist because people want to work on the code.

There's been some interest among the Samba hackers, including some discussion with Microsoft. They seem quite excited about SMB-on-QUIC as an Internet-capable network filesystem protocol.

Oh, I was describing the nature of build.rs files as script-y, rather than Rust itself. :-)

Here's a very simple one: https://github.com/alexcrichton/brotli2-rs/blob/master/brotl...

Here's one with much more complicated requirements: https://github.com/sfackler/rust-openssl/blob/master/openssl...

Unless you're writing libraries, Rust feels a lot like Python.

One thing that sticks out in a scripting mindset is the various string types, but I mostly accept that as a small price to pay for doing things correctly (OS strings vs. UTF-8 vs. C strings).

Because of the kinds of things I build with Rust, I've had to write quite a few cargo build scripts (build.rs files), which are very bash/Python script-y in nature. Not once have I wished for a different language!

> Technological advancement is good in its own right.

Holy shit, it's 2020. Look around.

But then, Go is the lurching zombie of Plan 9. :-)

This is very far away from the Rust I know, both language and contributors.

Since 1.0 Rust has improved a lot while maintaining compatibility, even through a big deprecation step like the 2018 edition.

A good chunk of those improvements are about making Rust more usable and more forgiving. Some were things I didn't initially recognise as usability problems, but what came out the other side was absolutely better – the modules changes are a good example.

Rust's lead contributors have been welcoming and humble – while also being human. It can be very frustrating running an open source project, and Rust is trying very hard to be open and inclusive, which increases the challenge.

When writing Rust, there are definitely paths of least resistance. You often read about the moment people realise they're going "against the grain", and discovering why it's safar and/or faster to do it "the Rust way". But that's not subjugation. It's about understanding your tools, how they work, and what they're for.

Design and build? Yes, very much so. It'll be simple, but it's doable. How useful it becomes is a function of how much time you spend on it, and how many others you get interested in it.

That's awesome – better update the README. :-)