Is this a rebranded Firefox Focus?
Firefox Replay
271–280 of 297 posts
Re: Firefox Replay
#272Earlier quoted context omitted.
Well if you can only virtualize it on a computer that's already running macos I don't know how that's supposed to help.
You can virtualize on a PC. Whether you may or not, depends whether you believe you own software. 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.
So you mean you gotta tinker/hack?
Re: Firefox Replay
#273Earlier quoted context omitted.
Why not? A huge portion of developers uses Macs and windows support is coming at some point. Better to get an actual feedback from the developers.
People on HN don't seem to like it when some other companies start their product from one platform.
I think we'd just like to have it labelled "for Mac Only right now"
Re: Firefox Replay
#274Mods: the link should perhaps be changed to: https://developer.mozilla.org/en-US/docs/Mozilla/Projects/We... This currently has 1215 points, and the link is no longer valid. It now just shows an image of Firefox's devtools and the sentence "Replay is an early experiment. We'll let you know on @FirefoxDevTools when it's ready for input." That's not useful, interesting, or informative. The MDN docs seem like an appropr…
The initial version of the site gave a good overview of Firefox Replay: https://web.archive.org/web/20191128111509/https://firefox-r...
That gives me “The Wayback Machine has not archived that URL.”
I also get the same for all the other snapshots, maybe Mozilla applied for a takedown?
Edit: I found it on archive.is: http://archive.is/0ei35 Though it seems a bit broken.
Re: Firefox Replay
#275Earlier quoted context omitted.
I think they saw that it got a lot of attention on HN and weren't in a stage with the product where they were ready for the corresponding feedback. For anyone who missed what it was, it allows you to derterministically record and replay your browsing for debugging purposes, and you can export these recordings to others.
I just looked it up on the internet archive and saw the old website. I think they should have kept the old one, since the new website has almost no information at all. https://web.archive.org/web/20191128111509/https://firefox-r...
That gives me “The Wayback Machine has not archived that URL.”
I also get the same for all the other snapshots, maybe Mozilla applied for a takedown?
Edit: I found it on archive.is: http://archive.is/0ei35 Though it seems a bit broken.
Re: Firefox Replay
#276Earlier quoted context omitted.
It's not like you can pay infinite tools at $50 a month. And if you don't care at all it's unlikely you're there to stay
True (to be fair, I did say it was a hot take :) ). But assuming this is a salaried team at a cost of $150k per employee, a $50 per month expense amounts to 0.4% of salary. You're right though, it can add up quickly. Do that 20 times and you're at nearly 10% overhead. It's also a big assumption that the team is salaried. It might be a team of founders, or an open source project. Ultimately you just need to decide whi…
I would say that it’s also about team output. By getting rid of a productivity tool, you will decrease expenses, but simultaneously productivity and therefore revenue will suffer.
Re: Firefox Replay
#277Earlier quoted context omitted.
This blew me away a bit. Is MacOS this popular in the Web frontend crowd? I always felt that the price/quality ratio was way off with MacOS, compared to a good regular laptop. By good I mean top 10% ranked by price/quality. Even if it wasn't, Apple's general hostility towards consumers is infuriating. Right-to-repair is a banal example.
I think it is popular but it is an expensive laptop. I have started using a Chromebook with 8G of memory and like it much more ... but I am probably in the minority. :(
While I agree, a lot of people (including me) don't have a choice; I simply need mac os x for ios apps. I tried everything, like having a remote mac desktop etc; it works ok, but it's really not for long bouts of work. Everything else I can do on a chromebook (or whatever laptop/hardware).
Re: Firefox Replay
#278They should've put this note at the very top of the page: "Mac OS only for now!". What is the point of promoting this to everyone at this stage?
Team member here. Firefox Replay is currently in user research phase while we validate it. 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 ( htt…
What benefits it provides than record and playback using a screen recorder?
Re: Firefox Replay
#279Earlier quoted context omitted.
There are still a lot of QoL features that Firefox DevTools misses. For example autocomplete for CSS classes, a tab for handling Service Workers, commands to perform actions (like disabling JavaScript), etc. I find myself switching between browsers just to take advantage of the different features each one provides which is slighly annoying. I would sincerely love some kind of unified DevTools.
Yeah, and vice versa as well, of course - for example, I don't think the Chrome DevTools tell you why certain CSS declarations do not apply. That said, the Firefox DevTools have been progressing really fast since the rewrite to React was completed, so I'm hopeful that it'll practically be the unified DevTools soon.
One reason that I use Firefox DevTools mostly is because in the inspector it shows you what events are attached to a DOM element. It's really helpful for debugging legacy applications. Sure, Chrome has something similar but it's a bit more hidden.
Re: Firefox Replay
#280I would love to give Firefox a shot, but there's one thing I've had issues with, when working with projects using things like webpack, when there's an error, Chrome links me back to the original file and line, I never seem to be able to do this in Firefox. Makes it so much harder to debug things. Am I doing something wrong, or is there a way to fix this?
Not sure how long ago you tried, but in one of the recent Firefox versions, they greatly improved the source map support - so it might just be that you should give it another try.
I've tried it with the latest versions (as of now), but it doesn't seem to match up with how good Chrome is at it. I've tried both normal Firefox and the developer version.
Why is this something Firefox seems to be struggling with? All the Blink based browsers seem to be much better in this regard.