How are those namespaces getting on?

Why? Microsoft gives them a ton of money for CI and infrastructure. Unless they are having serious technical issues I don't see why they would move to a more expensive and probably less well integrated CI provider.

I wouldn't recommend the Gang of Four book. Many of the design patterns they espouse are way over complicated from the days of peak OOP. You know, FactoryFactoryVisitor stuff. Usually best avoided.

I don't. You can't even copy to the clipboard in an insecure context.

Except... You can! You just have to use the old deprecated and ridiculously awkward execCommand method.

If that's so insecure why do all browser's still support it?

The article said it pretty well:

if your answer to any perceived failing in a person is “just try harder”, you are either woefully inexperienced or a just a dick

That applies to writing impossibly comprehensive unit tests too.

Though really for a filesystem they should really do silicon-style verification (which we're calling Deterministic System Testing now).

The thing is that "learning C" means "I can write C code that compiles and might be full of bugs", whereas "learning Rust" means "I can write Rust code that compiles and has a small number of bugs". It's not apples-to-apples.

It's like saying "I found it easier to learn primary school maths than I did to learn a physics degree".

That's cool, but in my experience if you get to the OOM killer then 80% of the time it's too late and your system is basically dead. My laptop hard reboots most of the time when this happens.

Hopefully it works with the early-OOM hacks.

Looks nice. Well as far as I can tell anyway. Maybe next time you're showing off a GUI don't make the screenshots 320x240?

Anyone know what toolkit they are using? As far as I know none of the Rust GUI toolkits are close to mature.

Edit: it's iced.

If you are expecting stuff to never go wrong and software to never be updated in a way you disagree with on Linux then you're in for disappointment.

Remember the KDE kidney bean? What about Gnome's idiotic hamburger menus?

• Pijul: patch-based like Darcs but apparently solves its performance issues. In theory this improves conflict resolution.
• Jujutsu: kind of an alternative front-end to a git repo (but not a front-end to git). Has some different ideas, like no staging area (draft commit), and some other stuff I can't remember.
• Sapling: from Facebook. Unfortunately only part of it is available. The server is not public yet (I guess it's tired up in Facebook infrastructure too much).

And it's definitely not a solved problem. Aside from the obvious UX disaster, Git has some big issues:

• Monorepo support is relatively poor, especially on Mac and Linux.
• Submodule support is extremely buggy and has particularly bad UX even for Git.
• Support for large files via LFS is tacked on and half-arsed.
• Conflict resolution is very very dumb. I think there are third party efforts to improve this.

I think the biggest issue is dealing with very large code bases, like the code for a mid-large size company. You either go with a monorepo and deal with slowness, Windows-only optimisations and bare minimum partial checkout support.

Or you go with submodules and then you have even bigger problems. Honestly I'm not sure there's really an answer for this with Git currently.

It's not hard to imagine how this might work better. For instance if Git repos were relocatable, so trees were relative to some directory, then submodules could be added to a repo natively just by adding the commits and specifying the relative location. (Git subtree almost does this but again it's a tacked on third party solution which doesn't integrate well, like LFS.)

Someone find the commit where they accidentally removed this critical component 😄

These long confusing errors are near universal in languages / libraries that have complex types. You get the same thing in C++ code that uses template metaprogramming e.g. Eigen.

It is quite annoying but I don't really know of a solution other than using a library that doesn't express full expressions as types.

Chumsky does something similar but it also has a .boxed() modifier you can use to type erase the types at strategic points to keep them a manageable size. I believe Xylem is going to do the same with its statically typed widget tree. Maybe Diesel offers something like that?