3 ms·
I see what you're saying, however they don't seem to be "strangling" Gecko in the Strangler-pattern sense of the word. Rather it seems they're borrowing smaller
by quincunx 10y ago
I see what you're saying, however they don't seem to be "strangling" Gecko in the Strangler-pattern sense of the word. Rather it seems they're borrowing smaller pieces (Stylo) written in a foreign language and integrating them with Gecko as the main engine.
To me that sounds like the end-state is a Chimera and not a Lion, without any incremental end-user benefits along the way.
- stymaar 10y ago> To me that sounds like the end-state is a Chimera and not a Lion This is an aesthetic judgment. There is no such things as «a Lion» in the real world. Engineering is the work of building chimeras that solve your problems. > without any incremental end-user benefits along the way. The expected benefits are : - speed (thanks to the massive parallelization permitted by Rust «fearless concurrency») - reliability (thanks to Rust's memory safety to avoid crashes and better type system that helps reducing the number of bugs) - security (thanks to Rust's memory safety to avoid exploits) Component from Servo will be included in Gecko one by one, the user will gain on these three fronts each time a new component is included.
- Ericson2314 10y agoServo will still exist, so they'll always have the lion and the chimera. Creating a new langauges to incrementally change and clean-slate rewrite is an orders-of-magnitude bigger investment than what either what Joel's criticizing or advocating. I don't think that article is very relevant here one way or the other.
- Ygg2 10y agoNothing about that pattern says you need to replace everything... After all, not all vines completely replace the host. There can be legacy system that can just be maintained without modifying. Like for example JavaScript engine.