Extensions were always going to be added. You have to have a usable browser before you can even use extensions.

That is not true. In February, they were merely "look[ing] at it".

https://github.com/mozilla-mobile/fenix/issues/574#issuecomm...

They actually do sometimes AFAIK

This is the GitHub repository

https://github.com/rust-lang-nursery/

We’re in the process of deprecating the nursery, so they’ll end up in the rust-lang org at some point.

This is still a preview, it's nowhere near a finished product. Extensions come after MVP https://github.com/mozilla-mobile/fenix/issues/662#issuecomm...

There is no minimum viable product here. The MVP was the first usable mobile Firefox. A version of Firefox without extension support is just broken.

(minimum viable product)

Isn't it strange that the big flash announcement comes before MVP?

This release is what they termed MVP. Everything after it is post-MVP. It means minimum viable product. In my personal opinion, a lot more functionality was included than what most would call an MVP.

The big flash announcement is to get early adopters for testing. There's no reason to delay testing until the MVP is ready, as long as testers remain aware that Firefox Preview is a preview that shouldn't be expected to already have all features implemented.

It's just that, for me and a bunch of other people, we would be happy to test a preview if we could compare it against our current browsers. We can't, because

advertising is an abomination that destroys the utility of the internet

and so there's no fair comparison.

Yes, that's what "viable" means. Viable for big flashy announcement.

IMozilla engineers have specifically said Stylo (Quantum Style whatever) would be impossible in C++, because they actually tried it in C++. Presumably it'd be the same with WebRender.

Impossible is a strong word. Architecture makes a very big difference. They can claim it is impossible, but it really doesn't make sense. I'm surprised anyone would just take their word for it.

Trying to use raw threads and ad-hoc futures is going to be difficult, but fundamentally concurrency is about separating data by dependencies.

Dependency graphs that pass data around combined with lock free data structures can be used to isolate parts of the program so that dealing with concurrency is one generic part of the program.

The Rust Evangelism Strikeforce only exists in completely inane comments like yours, maybe instead of posting memes you comment on the actual content of the article not the headline?

Every project with millions of lines of C or C++ is going to be around the same, Firefox is over 50% as well.

>I think the best experience for developing rust right now is in VScode or vim, IMO.

Intellij + Rust Intellij plugin is probably the best, in terms of actual usefulness (code completion etc) and stability.

I really dislike intellij, so I've not spend much time trying their rust plugin. If memory serves according to the rust survey, vim or vscode are the most widely used environments.

>it doesn't leak memory

Fairly sure you can leak memory, just no memory safety issues (in safe Rust).

You can also cause segfaults, the point I think is more that it is hard to do this instead of easy as it is in some languages, like C.

Memory leaks can happen in safe code, segfaults cannot. That’s at least one major difference.

New companies can't benefit from that scheme anymore, since 2014 actually.

"Finance Minister Michael Noonan closed the Double Irish to new schemes in October 2014 (existing schemes to close in 2020), and expanded the Capital Allowances for Intangibles scheme as a replacement"