What is the point of promoting this to everyone at this stage?
What is the point of promoting this to everyone at this stage?
Cross platform support will absolutely be a priority when Replay is on the official roadmap.
Thanks for the feedback, firefox-replay.com is also a work in progress. We did not plan an official release today.
We'll be sure to make the Mac OS limitation more clear.
Here is some more context on the mac specific functionality (https://searchfox.org/mozilla-central/source/toolkit/recordr...).
A question about how you develop / roll this out. Do you keep the code private, or do you commit it to the open source repo as you're working with a small amount high touch users?
I guess the question is do you want a full working product when you open source it? Do you tie your PR / forum posts with publicly shipping the source code? Or is all development out in the open?
Everything is in firefox and open source
Here are the bugs: https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&na...
Here's the primary directory: https://searchfox.org/mozilla-central/source/toolkit/recordr...
The debugger API is implemented in JS here https://searchfox.org/mozilla-central/source/devtools/server...
https://searchfox.org/mozilla-central/source/toolkit/recordr...
Replay is currently in the user-research validation phase. We care about cross platform support and will prioritize it when we are ready to commit to the feature.
no, downloading sketchy images or hacking your virtualization software does not count.
You can, and it’s licensed to.
Since Lion:
> (iii) to install, use and run up to two (2) additional copies or instances of the Apple Software within virtual operating system environments on each Mac Computer you own or control that is already running the Apple Software.
No hassle support page on VMware site:
https://kb.vmware.com/s/article/1000131
EDIT: Amusingly on topic with gist of thread above, anger about a dev tool launched for MacOS, this fact with citations from license and support page from VMware garnered instant down votes.
And how it helps when you do it on MacOS on Mac hardware is letting you do all the things you virtualize an OS for, from a fine GUI on a decent kernel.
One of the main things I "virtualize an OS for" is to use software that requires Platform A on a system that runs Platform B. Running "legit" (authorized) virtualized MacOS does not help me do that; I am only allowed to run Platform A on Platform A.
Just to clarify, I don't fault Mozilla for having that attitude, but that doesn't mean I prefer it. I would prefer that they prioritize FOSS platforms like Linux and \*BSD, as well as getting Firefox on platforms like Plasma Mobile, PostmarketOS, and other GNU/Linux-based mobile operating systems. Developer adoption is a necessary (but probably not sufficient) precondition for general adoption, which is why developing for these platforms is important even though they are new/unpopular.
On Linux, Firefox has a bigger percentage (>30%), but (desktop) Linux is much less popular than macOS so in absolute terms they have the fewest users there.
51% Windows 10
27% Windows 7
6% Windows 8
6% macOS
11% Other (Linux, BSDs, etc)
https://data.firefox.com/dashboard/hardwareI think the Firefox Nightly, Developer Edition, and Beta channels have a slightly higher share of macOS and Linux users, but not much. There are a lot of Windows users out there; you just don't see them at JS conferences. :)
Replay requires a ton of difficult platform-level investment to get right and we're still actively finding bugs in the real world.
After it is validated, it will be easier to add the appropriate platform level bindings in other OSs.
Edit: to clarify, I refer to operating systems that have a considerable amount of potential and existing development, not systems with like 2 users .
One of my favorite books starting out was the Stevens book about Unix. It only covers the differences in system call availability and behavior across Unix OSes. It doesn’t even touch graphics. It’s a big fat book just covering file, network, processes, and memory operations. No Mac, no Microsoft, just Unix.
https://en.m.wikipedia.org/wiki/Advanced_Programming_in_the_...
"Almost all implementation work so far has been on macOS. Windows port work is underway, but is not yet working. The difficulties are in figuring out the set of system library APIs to intercept, in getting the memory management and dirty memory parts of the rewind infrastructure to work, and in handling the different graphics and IPC pathways on different platforms."
[0]: https://developer.mozilla.org/en-US/docs/Mozilla/Projects/We...
This makes me think that it's not a feature on the roadmap of firefox sponsored by Mozilla, but an experimentation/side project.