Re: To what extent is sccache's distributed compilation usable?

On Wednesday, October 30, 2019 at 11:59:45 PM UTC+11, Jeff Muizelaar wrote: > On Tue, Oct 29, 2019 at 9:45 PM Marcos Caceres wrote: > sccache supports doing cross compilation so you don't actually need to > buy a fast Mac to get fast Mac builds. A fast cheap Linux desktop will

Re: PSA: You can use UTF8String from WebIDL

On Monday, January 6, 2020 at 12:51:56 PM UTC+11, Emilio Cobos Álvarez wrote: > If you need UTF-8 inputs from WebIDL (for example if you are passing the > input to Rust), chances are you're doing an extra copy from JS. > > In bug 1449861 I've added an UTF8String so that you can convert a > JSStr

Re: Proposed W3C Charter: Web Payments Working Group

On Wednesday, December 4, 2019 at 1:58:54 AM UTC+11, L. David Baron wrote: > Please reply to this thread if you think there's something we should > say as part of this charter review, or if you think we should > support or oppose it. Feedback I send a little while back: https://lists.w3.org/Archiv

Re: To what extent is sccache's distributed compilation usable?

On Wednesday, October 30, 2019 at 4:53:55 AM UTC+11, Steve Fink wrote: > I really ought to put my decade-old desktop into action again. My last > attempt was with icecc, and though it worked pretty well when it worked, > the pain in keeping it alive wasn't worth the benefit. Thanks Steve... so

Re: To what extent is sccache's distributed compilation usable?

On Tuesday, October 29, 2019 at 3:27:52 AM UTC+11, smaug wrote: > Quite often one has just a laptop. Not compiling tons of Rust stuff all the > time would be really nice. > (I haven't figured out when stylo decides to recompile itself - it seems to > be somewhat random.) Probably a gross misunde

Re: To what extent is sccache's distributed compilation usable?

On Saturday, October 26, 2019 at 11:47:51 PM UTC+11, Emilio Cobos Álvarez wrote: > So you have two options, I think: > > * Setup a Linux box as an sccache-dist scheduler and builder. This > should require no SDKs or what not, but requires some setup in your mac > as described here[1]. Then y

Re: To what extent is sccache's distributed compilation usable?

On Friday, October 25, 2019 at 4:14:05 AM UTC+11, Jeff Gilbert wrote: > My home Ryzen 3900x builds windows debug clobbers in under 10 minutes. Whoa, that's awesome! > Beefy desktops are relatively cheap, and I believe we continue to encourage > firefox-builders to request desktop workstations fo

Re: To what extent is sccache's distributed compilation usable?

On Thursday, October 24, 2019 at 6:46:08 AM UTC+11, Christopher Manchester wrote: > As announced in this week's project call, sccache-dist schedulers have been > deployed to mozilla offices, and those with hardware available can enroll > servers based on the documentation here >

Re: Intent to ship: Web Speech API

On Monday, October 7, 2019 at 12:55:23 PM UTC+11, Marcos Caceres wrote: > As of October 11th, the Emerging Technologies Team intend to turn "Web Speech > API" on by default in *Nightly only* on Mac, Windows, and Linux. It has been > developed behind the "media.webs

Re: Intent to ship: Web Speech API

ust helping with our process stuff :)). On Monday, October 7, 2019 at 8:32:18 PM UTC+11, Jonathan Kew wrote: > On 07/10/2019 09:53, Henri Sivonen wrote: > > On Mon, Oct 7, 2019 at 5:00 AM Marcos Caceres wrote: > > >> - speech is processed in our cloud servers, not on device. &g

Re: Intent to prototype: Web Share Target

On Saturday, October 5, 2019 at 12:28:24 AM UTC+10, David Burns wrote: > Is this something that we could be tested with testdriver.js inside wpt? It's complicated because every handles installation differently in their respective UIs (and it can chance from one browser version to another). _

Intent to ship: Web Speech API

As of October 11th, the Emerging Technologies Team intend to turn "Web Speech API" on by default in *Nightly only* on Mac, Windows, and Linux. It has been developed behind the "media.webspeech.recognition.*" and "media.webspeech.synth" preference. Other UAs shipping this or intending to ship i

Re: Proposed W3C Charter: Web Commerce Interest Group

Hi Tantek, bcc: Ian Jacobs, who is the W3C Team contact and activity lead. On July 18, 2017 at 9:58:40 AM, Tantek Çelik (tan...@cs.stanford.edu) wrote: > I'd like to hear feedback from Marcos (cc'd) on how/why this group > will complement or help our work in the Web Payments WG (does not seem > t

Re: W3C Charter Advance Notice: Web Platform (recharter) & Service Workers WGs

On July 6, 2017 at 1:40:13 PM, L. David Baron (dba...@dbaron.org) wrote: > I've taken what you (Tantek) wrote and made minor changes to yield > the following Formal Objection to the Web Platform WG charter. I support the updated formal objection. Thanks Tantek for drafting it. I've raised these i

Re: Intent to put Permission API's .revoke() method behind a pref

On August 17, 2016 at 5:02:07 PM, Anne van Kesteren (ann...@annevk.nl) wrote: > On Wed, Aug 17, 2016 at 6:48 AM, wrote: > > There is consensus that .query() is beneficial, so that one can remain. > > Is there really? Well, the use case at least: that a developer should not need to actually invoke

Re: Linked Data must die. (was: Linked Data and a new Browser API event)

On June 29, 2015 at 7:07:33 AM, Michael Henretty (mhenre...@mozilla.com) wrote: > We will definitely start with the simple open graph stuff that Ted > mentioned ("og:title", "og:type", "og:url", "og:image", "og:description") > since they are so widely used. And yes, even these simple ones are >

Re: Linked Data must die. (was: Linked Data and a new Browser API event)

On Saturday, June 27, 2015, Benjamin Francis wrote: > On 26 June 2015 at 19:25, Marcos Caceres > wrote: > >> Could we see some examples of the cards you are generating already with >> existing data from the Web (from your prototype)? The value is really in >> seei

Re: Linked Data must die. (was: Linked Data and a new Browser API event)

On June 27, 2015 at 10:02:47 AM, Anne van Kesteren (ann...@annevk.nl) wrote: > > > The data I have does not back this up, Microdata is shown to be growing > fast whereas Microformats usage has remained relatively stable. > Also, we didn't find Microformats usage on any of the example > high p

Intent to implement W3C Manifest for web application

Summary:   JSON-based manifest, which provides developers with a centralized place to put metadata associated with a web application. This includes, but is not limited to, the web application's name, links to icons, as well as the preferred URL to open when the user launches the web application

Intent to implement: HTML `picture` element

Sending this on behalf of John Schoenick, who is doing the actual implementation. #Summary  The picture element finally brings responsive images to the Web! It allows developers to list multiple and have the browser intelligently select one that is best suited for users (based on device capabi

Re: W3C Proposed Recommendations: XQuery, XPath, XSLT, EXI, API for Media Resources

On October 29, 2013 at 10:02:14 AM, Henri Sivonen (hsivo...@hsivonen.fi) wrote: > >On Tue, Oct 29, 2013 at 1:39 AM, Ralph Giles wrote: >> On 2013-10-28 2:11 PM, L. David Baron wrote: >>> API for Media Resources 1.0 >>> http://www.w3.org/TR/mediaont-api-1.0/ >... >> Thus I think we can be positive

Re: Studying Lossy Image Compression Efficiency

that it was not part of the study. > If this is researched I'd love to see how it compares to lossy PNG from > pngquant2 http://pngquant.org and "blurizer" tool > https://github.com/pornel/mediancut-posterizer/tree/blurizer That would be great. -- Marcos Caceres _

Re: Suggested API exposure guidelines redux

meeting and moving them out of User:Overholt. > In the Special Cases section, it should be made clear that these exceptions only apply to packaged and hosted apps - and not the browser that ships with Firefox OS. It would be bad if the regular browser in F

Re: New Promise Constructor

On 11/09/2013, at 8:18 PM, Boris Zbarsky wrote: > On 9/11/13 2:13 PM, Marcos Caceres wrote: >>> callback PromiseInit = void (object resolve, object reject); >>> [Constructor(PromiseInit init)] >>> interface Promise {...} >> >> What members does Promis

Re: New Promise Constructor

On 11/09/2013, at 6:11 PM, Andrea Marchesini wrote: > Hi all, > > I just want to inform that I'm landing a patch that changes the DOM Promise > constructor. > DOM Promise is disabled by pref but I know that there are a few existing > pieces of code that already use them. > > The old constru

Re: Detection of unlabeled UTF-8

On Friday, September 6, 2013 at 5:36 PM, Neil Harris wrote: > On 06/09/13 16:34, Gervase Markham wrote: > > > > Data! Sounds like a plan. > > > > Or we could ask our friends at Google or some other search engine to run > > a version of our detector over their index and see how often it says >

Re: Intent to Ship: Web Audio

On Tuesday, July 30, 2013 at 6:54 PM, Ehsan Akhgari wrote: > On 2013-07-30 1:44 PM, Marcos Caceres wrote: > > I have previously indicated our intent to ship to the working group for > Firefox 24, but that slipped. I need to update the working group on the > new plans. &g

Re: Intent to Ship: Web Audio

a spec from which interoperable implementations can be created). My personal opinion about the spec is that it could be improved (lots of stuff seemed underspecified, etc. when I tried to read it a few months ago - but maybe it's better now) - if it

Re: AppCache usage on Alexa top ~50,000 sites

On Thursday, 11 July 2013 at 18:02, Ian Hickson wrote: > On Thu, 11 Jul 2013, Marcos Caceres wrote: > > > > As a result of a discussion a few of us had today at the Toronto work > > week about the use of appcache on the web (and if we should "fix it"), I &g

AppCache usage on Alexa top ~50,000 sites

ub.fr leovegas.com netzkino.de shopfato.com.br giorgiotave.it jsonlint.com dragonbound.net nordea.se ex.fm amardeshonline.com -- Marcos Caceres ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Making proposal for API exposure official

Hi Andrew, Below is a review of the document. I've included the text and responded inline… On Sunday, 7 July 2013 at 15:24, Marcos Caceres wrote: > Guidelines > > Mozilla aims to advance the state of the open web with new APIs. Toward this > end, > > Mozilla w

Re: Web MIDI API, was Re: Making proposal for API exposure official

On Wednesday, July 3, 2013 at 12:16 PM, Robert O'Callahan wrote: > On Wed, Jul 3, 2013 at 11:06 PM, Marcos Caceres (mailto:mcace...@mozilla.com)> wrote: > > On Wednesday, June 26, 2013 at 11:33 PM, Robert O'Callahan wrote: > > > I'd like someone with exp

Web MIDI API, was Re: Making proposal for API exposure official

pplications (judging by the amazing range of MIDI applications on iOS). Is there anything in particular you would like to see from a review? What would you expect to see to feel confident that it would make sense to implement it? [1] https://gith

Re: SpiderMonkey Regrets

ff that's non-standard instead of putting energy into the ES.next? Won't fixing non-standards things just encourage people to use it more and lead to more confusion/content (thus making it harder to do away with the non-standard stuf