Originally posted by Danielsan
View Post
Announcement
Collapse
No announcement yet.
Firefox 68 Integrates BigInt Support
Collapse
X
-
Originally posted by Vistaus View Post
Yes, and there's nothing wrong with that, but it still differs from my initial point/question.
Leave a comment:
-
Originally posted by Vistaus View PostExcept that the Eolie dev is not part of the GNOME Team, just like the Midori devs aren't part oi the Xfce Team. They just use the infrastructure provided by resp. GNOME and Xfce.
Leave a comment:
-
Originally posted by dremon_nl View PostNot in a standard library, but I am pretty sure there are 3rd-party solutions with better performance. There is also unique_ptr for move semantics but I wouldn't use it as it's quite easy to produce undefined behavior with it. Rust, on the other hand, has two reference-counted types: Rc for single-threaded use and Arc for multithreading, ARc being naturally slower due to atomicity. That's the inherent difference between the classical languages which were not designed for concurrent and asynchronous programming and the language which was built for that from ground up.- T* (or T&) can be used in single-threaded scenarios as long as the top-level function caller refers to the object via a single shared_ptr<T> to prevent its deallocation and as long as the object does not escape to the heap or elsewhere. If it escapes to heap or to upper scope or to another thread (that is: the object outlives the scope in which is has been created), it needs to be encapsulated in a shared_ptr<T>.
- shared_ptr<T> is suitable in multi-threaded scenarios for passing objects between threads
- shared_ptr_st: for use in single-threaded code
- shared_ptr_mt: for use in multi-threaded code
- shared_ptr_mt cannot be directly assigned nor converted to-or-from shared_ptr_st, which should help the programmer to reason about concurrency
- The C++ compiler is unable to enforce the rule that everything reachable through a shared_ptr_mt must be shared_ptr_mt as well (struct fields), so it is up to the programmer to ensure this rule holds
Leave a comment:
-
Originally posted by Danielsan View Post
Actually they did, Midori is under the Xfce4 umbrella...
https://goodies.xfce.org/projects/applications/midori
Leave a comment:
-
Originally posted by Vistaus View Post
Why doesn't the Xfce team create a browser?
https://goodies.xfce.org/projects/applications/midori
- 1 like
Leave a comment:
-
Originally posted by Steffo View PostOnly a small part of Firefox is written in Rust. They wouldn't exchanged parts of it, if it wouldn't gain on performance. You should do your recherche, before you post...- Rust is just as fast as C/C++ at the language level. The differences are minimal, there are benchmark wins on both sides, usually not much bigger than background noise.
- Rust makes complicated code much easyer. Firefox tried and failed multiple times to parallelize their render and css using C++, but succeeded with Rust. Often, naive/idiomatic rust code will be much closer to theoretical max performance than naive/idiomatic C++ code.
- Firefox is still overall slower than Chrome mainly due to javascript performance, which is still written in C++. Page layout and css parsing, which Firefox has rewritten in Rust, are faster in Firefox.
- 4 likes
Leave a comment:
Leave a comment: