Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox Replay

firefox-replay.com

Post reply on HN
Print view View original

231–240 of 297 posts

Re: Firefox Replay

#231

Post by gnufx »

jasonlaster11 wrote: post #189
BoppreH wrote: post #90

Earlier quoted context omitted.

Sounds like Mozilla is applying the concepts they developed for their C/C++ debugger, rr ( https://rr-project.org ).

That's exactly right Brian Hackett collaborated early on with ROC. Here are the basic principles of Replay ( https://developer.mozilla.org/en-US/docs/Mozilla/Projects/We... ). In a nutshell, replay records Firefox's OS system calls, so that that Firefox can read from the recording when replaying.

For what it's worth, the DMTCP [1] user-space checkpoint/restore system does that (and more). C/R is a way of doing coarse batch-based reversible debugging, typically of distributed HPC programs, and FReD [2] is a(n unfortunately dead) reversible debugger using DMTCP record/replay. 1. http://dmtcp.sourceforge.net/ 2. https://arxiv.org/abs/1212.5204

Re: Firefox Replay

#232

Post by rckclmbr »

jasonlaster11 wrote: post #194
Roark66 wrote: post #60

They 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…

> Firefox Replay is currently in user research phase while we validate it

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?

Re: Firefox Replay

#233

Post by anoncake »

asutekku wrote: post #64
Roark66 wrote: post #60

They 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?

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.

One would expect an organization dedicated to freedom to prioritize Linux support.

Re: Firefox Replay

#234

Post by bsamuels »

floatingatoll wrote: post #218
fireattack wrote: post #113

Earlier quoted context omitted.

People on HN don't seem to like it when some other companies start their product from one platform.

When that platform is Mac, certainly. For some mysterious reason you don't see complaints about Linux-only utilities :)

you can virtualize linux, you cannot virtualize macos.

no, downloading sketchy images or hacking your virtualization software does not count.

Re: Firefox Replay

#236

Post by wizzwizz4 »

laumars wrote: post #117
albertgoeswoof wrote: post #18

Earlier quoted context omitted.

It happens because applications will stop working on chrome if developers never test on it. The recommendation when a user hits a bug will be to check it in Firefox and slowly Firefox will become the reliable/advanced/working option. It’s happened with IE, Chrome before and will swing back away from Chrome eventually.

IE was stagnant and shit, Chrome isn't. I may not like the Chrome monoculture happening at the moment but that doesn't mean Chrome is the same dumpster fire that was IE. And Google are hardly going to let Chrome stagnate when Chrome is the perfect vehicle to local users into Google's non-free ecosystem (I say "non-free" because you pay with your privacy)

You don't just pay with your privacy. It's not a one-way street. Google's knowledge about you feeds back to you, as they attempt to manipulate you in the way that best increases the money they receive from their advertisers.

But if we want people to stop being locked into Chrome, the best way is to cease to support it. If stuff works in Chrome, that'll be because Chrome supports web standards properly, and not because there's some proprietary random Google standard-they-just-came-up-with that it relies on. (I'm looking at you, .)

Don't contribute code to Chromium; instead, contribute it to a popular fork (like ungoogled-chromium), or a different browser altogether. Until Chromium is a less-centralised project, you're pretty much just giving a competitive edge to Chrome, and hence Google's near-monopoly on the web, without Google having to put in the resources to do it themselves. You're working for Google for nothing.

Re: Firefox Replay

#237

Post by sm4rk0 »

glassounds wrote: post #219
kevsim wrote: post #6

The biggest benefit for me (I think) would be if the product/design people I work with could find issues and send their recordings to me. Don't think I'll be able to convince them to switch to FF though.

https://birdeatsbug.com is great for that kind of thing

Important part:

$0; Essential features; Up to 3 users

$50 / month; All features; Unlimited reports; Up to 10 users

...

Re: Firefox Replay

#238

Post by darshan »

Mods: 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 appropriate replacement.

Re: Firefox Replay

#239

Post by dessant »

darshan wrote: post #238

Mods: 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...

Re: Firefox Replay

#240

Post by makarov »

glassounds wrote: post #219
kevsim wrote: post #6

The biggest benefit for me (I think) would be if the product/design people I work with could find issues and send their recordings to me. Don't think I'll be able to convince them to switch to FF though.

https://birdeatsbug.com is great for that kind of thing

Co-founder of Bird Eats Bug here. It's so great to hear!
Post reply on HN