[dev-servo] seanmonstar and hyper are really great!
I’d like to take a moment to publicly acknowledge the effort that Sean McArthur has put into hyper and the quality of support that he provides on an ongoing basis. He receives the brunt of our “something is wrong in the network stack, what do I need to do to fix it?” requests, and he’s been really good about helping us figure out what needs to change and how. I would also like to acknowledge the incredible amount of thinking and design that has gone into hyper over the years. This struck me recently when I finally figured out the solution our SSL test automation problems, which was made possible by the loose coupling of the HTTP connector system that hyper provides. This is a part of the library that I’ve never looked closely at before, and the reasons for the complexity of the various small, generic components were never clear to me. Upon sitting down and thinking through my problem, I realized that the loose coupling provided me with exactly the tools that I needed in order to solve a longstanding issue in a straightforward and self-contained manner. I would hardly say that hyper is unappreciated by the Servo team - I’m sure I speak for others when I state that it’s wonderful to make use of existing high-level APIs taken for making HTTP requests in a browser. However, I think it’s worth taking a moment to thank seanmonstar for the excellent work that he and others have put into the library on which we rely so heavily. Thanks Sean! Both you and hyper are a pleasure to work with on a regular basis. Cheers, Josh ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] seanmonstar and hyper are really great!
> Thanks Sean! Both you and hyper are a pleasure to work with on a regular > basis. I second this whole-heartedly. Hyper provides a large amount of value to us, but also to the whole Rust ecosystem. Thank you! jack. ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] seanmonstar and hyper are really great!
Agreed. Sean has done great things for rust. Thanks Sean. On Apr 6, 2017 3:07 AM, "Josh Matthews" wrote: > I’d like to take a moment to publicly acknowledge the effort that Sean > McArthur has put into hyper and the quality of support that he provides on > an ongoing basis. He receives the brunt of our “something is wrong in the > network stack, what do I need to do to fix it?” requests, and he’s been > really good about helping us figure out what needs to change and how. > > I would also like to acknowledge the incredible amount of thinking and > design that has gone into hyper over the years. This struck me recently > when I finally figured out the solution our SSL test automation problems, > which was made possible by the loose coupling of the HTTP connector system > that hyper provides. This is a part of the library that I’ve never looked > closely at before, and the reasons for the complexity of the various small, > generic components were never clear to me. Upon sitting down and thinking > through my problem, I realized that the loose coupling provided me with > exactly the tools that I needed in order to solve a longstanding issue in a > straightforward and self-contained manner. > > I would hardly say that hyper is unappreciated by the Servo team - I’m > sure I speak for others when I state that it’s wonderful to make use of > existing high-level APIs taken for making HTTP requests in a browser. > However, I think it’s worth taking a moment to thank seanmonstar for the > excellent work that he and others have put into the library on which we > rely so heavily. > > Thanks Sean! Both you and hyper are a pleasure to work with on a regular > basis. > > Cheers, > Josh > ___ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo > ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
[dev-servo] Plans for Google Docs-related work
Our Google Docs efforts have stalled for a number of reasons. Besides cross-origin wrappers, there aren’t any big missing pieces that we can point at as being a clear problem in our current Servo builds. Efforts like the Chromium UseCounter data and Manish’s feature-detector user script show us a list of features that we don’t implement yet that Google Docs may care about, but it’s very difficult to tell whether we’re receiving fallback behaviour that works around them. I propose a new focus for our efforts rather than guessing which DOM features we should implement: 1) Prioritize fixing assertions and crashes that are triggered by Google Docs so we can actually experiment with it. 2) Un-minify JS/CSS/HTML that Servo encounters before evaluating it, and store local copies for later investigation. [0] 3) Build more tools and features that expose Google Docs’ behaviour. For example, if retrieving JS backtraces from Rust code would be useful, that’s something we can enable without much effort [1]. One specific piece of investigation is the missing text editing. If you’re lucky enough to reach a blank document, a text cursor appears but pressing keys does not do anything. We need to figure out why that’s the case, and we also need to figure out how to do that investigation efficiently. I would love to compile a wiki page with a list of strategies for investigating web compatibility problems. Cheers, Josh [0] https://github.com/servo/servo/issues/14824 (unminify all JS for more readable exceptions, and store local copies for later investigation) [1] https://github.com/servo/servo/issues/14987 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
