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

71–80 of 297 posts

Re: Firefox Replay

#71

Post by scarface74 »

bad_user wrote: post #55
paulintrognon wrote: post #16

Earlier quoted context omitted.

Do you really think the web developpers that use advanced dev tools can make a real difference in their market share? (real question)

Developers in general are very influential. Not only among our family and friends, but also because our choices create a lock-in effect due to the nature of our work. When you use Chrome day in and out, your work is going to be optimized for Chrome and will work best on Chrome. This led to a Chrome-optimized web and while Google isn't necessarily to blame, we're back to the days of " works best in IExplorer 6 ". Comp…

Developers and computer geeks have been overestimating their influence for over a decade. If geeks were influential, the “year of the Linux desktop” would have been years ago, no one would be on Facebook, and people wouldn’t buy into Apple’s wall garden and people would care about “freedom”. Definitely no one would have bought the iPod since it “had less space than the Nomad and no wireless”. (https://slashdot.org/story/01/10/23/1816257/apple-releases-i...)

The consumerization of technology happened a long time ago.

Re: Firefox Replay

#72

Post by aedron »

I am not primarily a web developer, but I guess I don't really see it.

I suppose 'rewind' would mostly be useful for Javascript applications? But in Javascript you can already debug pretty well. It's been a while, but I suppose Javascript debuggers can drop frames, like debugging other languages, so you already have a kind of rewind?

Does anyone have a good example use case for this?

Re: Firefox Replay

#73

Post by aphroz »

Aeolun wrote: post #44
aphroz wrote: post #42

While Microsoft is making great effort towards opening, it is sad to see Firefox develop a feature working on Mac OS only. This is terrible because you might argue that this is the same as a feature working on Windows only, but Windows can run on different hardware manufacturer. This is like a double closing. I am on Linux and I will uninstall Firefox as a repercussion hoping it will have an impact. Too bad for the l…

Don’t you think that’s a bit of an overreaction? Maybe it cannot work on anything but OSX?

Yes it is an overreaction. Whenever I see something working on Mac OS only I can't help myself but think that something went wrong in IT since 2000.

Re: Firefox Replay

#74

Post by Vinnl »

aspaviento wrote: post #10
strombofulous wrote: post #2

Ooooh wow. This might be enough to get me to use Firefox to develop with. This could be huge for its market share, a big part of the reason chrome was able to become so popular was because of how good its devtools were (compared to the competition at the time). Firefox definitely managed to catch up but not before lots of devs switched to chrome and stopped checking for compatibility with Firefox.

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.

Re: Firefox Replay

#75

Post by bflesch »

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.

How about linux users?

Re: Firefox Replay

#76

Post by paulintrognon »

dmos62 wrote: post #65
devit wrote: post #3

Why "Download Firefox Nightly for macOS"? Is it not supported on Linux and Windows? Why?

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.

Yes it is indeed very popular. All of my friends in IT switched to MacOS over the last few years, and I see more and more devs using Apple devices in web agencies. Because it looks good, it looks more pro.

Re: Firefox Replay

#77

Post by Vinnl »

aedron wrote: post #72

I am not primarily a web developer, but I guess I don't really see it. I suppose 'rewind' would mostly be useful for Javascript applications? But in Javascript you can already debug pretty well. It's been a while, but I suppose Javascript debuggers can drop frames, like debugging other languages, so you already have a kind of rewind? Does anyone have a good example use case for this?

I'm not quite sure what "drop frames" means in this context, but a use case would be stepping through the debugger, realising that the problem might be in a piece of code that has already executed, and wanting to inspect the value of a variable at that point in time.

Or even more mundane: accidentally hitting "Step over" twice in a row.

Re: Firefox Replay

#78

Post by saimiam »

tinus_hn wrote: post #67
saimiam wrote: post #21

This didn't work for me. 1. I installed the nightly build as told. 2. Open nightly build 3. Went to the "Save Recording" option 4. The first two times, I got a [javascript error] saying I could not record. 5. The remaining couple of times - after I open a "New Recording Tab", whatever that is - I didn't see the javascript error but the website whose clickthru I wanted to record using this tool didn't even load in tha…

If you’re on Windows, try the built-in Steps Recorder (formerly known as Problem Steps Recorder)

Mac.

Re: Firefox Replay

#79

Post by Vinnl »

sdan wrote: post #51

How is this different from recording in Chrome Web Dev tools? To be clear, I use both Chrome and Firefox for development but just to the surface level, so I'm probably missing the point here.

I'm not too familiar with "recording in the Chrome devtools", but this allows you to actually step back as well as forward in the debugger, e.g. for inspecting the value a variable had when code executed before.

Re: Firefox Replay

#80

Post by martius »

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?

This project is advertised on its own domain (not a mozilla.org subdomain) and there's no header/footer/link to mozilla.org.

This makes me think that it's not a feature on the roadmap of firefox sponsored by Mozilla, but an experimentation/side project.

Post reply on HN