While that leak was certainly damaging, I doubt GCP is going anywhere in two years.
If Google's strategy to catch up to AWS and Azure fails to gain them meaningful market share, I would expect them to change their behavior to succeed. It's good business.
WebGL is supposedly a first class citizen of the browser and is used in a ton of pages, but it gets left out or deferred in many tooling packages. There are many tools that are nearly useless to us because they don't support WebGL. It's disappointing.
tylko - http://tylko.com - Poland (Warsaw).
tylko is a start-up company on a mission to redefine the furniture industry. We are a team of
designers, developers and managers that combine our knowledge of design and technology
to bring customized furniture effortlessly to everyone.
We are looking for frontend developers with good html5, css, js (vanilla + threejs). Experience in webgl would be helpful.
details: http://tylko.com/uploaded/jobs_pdfs/job_offer_FRONTEND.pdf
Contact: slawek@tylko.com or jobs@tylko.com
Looking at this: https://codereview.chromium.org/1548893004/ and this, is there chance that there will be decent option for headless webgl testing or making screenshots? Phantomjs doesnt want to do that, slimmerjs also (on xvfb), anybody have a working solution?
For http://Clara.io, we explored a bunch of headless gl solutions and none worked. It may have changed by now. But even if you got a headless gl solution working, it likely would have poor extension support, which means the results will suffer anyhow. :(
So did you take any other solution? I was thinking about renting or collocating server with gpu and just automate whole process with ansible/fabric or just vnc.
About exentions - thats true. I was able to run software rending for shaders (llvm, xvfb, ec2), framerate was acceptable (1-5 fps, which is more than fine for screenshots), but issues like having max anisotropy = 1 make it unusable for this use case.
Primarily mochitest-gl, but also others. You can get an idea of what uses it by seeing what is blocking updating our ancient version of Mesa.[1] We anticipate that this update should improve the reliability of our tests.
I don't think there are specific results that are useful to anyone but us, other than that Mesa is viable for these sorts of things. We don't have a centralized tracking list for Mesa issues.
Like usual, if you try running WebGL on Mesa and run into unfixed issues, file a bug and we'll fix it.