HNHacker News
TopNewBestAskShowJobs

jasonlaster11

563 karma · joined March 1, 2012

submissionscomments
jasonlaster11··on Firefox Replay
Hmm, join us in http://devtools-html.slack.com/ and we'd be happy to help you debug it.

If the tab crashed, you can get the report in about:crashes

jasonlaster11··on Firefox Replay
Firefox Replay supports MacOS while we're validating the feature. When it comes time to plan for releasing replay we'll work on cross-platform support.

Unfortunately, Replay hooks into low-level OS system calls to do the recording, which makes it non-trivial to support other platforms.

jasonlaster11··on Firefox Replay
Thanks for the feedback!

Our #1 use-case at the moment is bug reports with a recording attached. We think that will really help when it comes to understanding the specifics of a bug when STRs are often not clear.

jasonlaster11··on Firefox Replay
That's right. The only way to have a performant recording is to capture the browser's OS system calls in the recording. This unfortunately makes the feature quite OS specific.

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.

jasonlaster11··on Firefox Replay
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 (https://searchfox.org/mozilla-central/source/toolkit/recordr...).

jasonlaster11··on Firefox Replay
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.

jasonlaster11··on The Firefox UI Is Now Built with Web Components
Hi, Firefox DevTools Debugger engineer here.

We've focused on performance and quality over the past six months and believe it should be much better.

If you're still seeing issues, feel free to record a performance profile and send it to us:

- https://profiler.firefox.com/ - https://bugzilla.mozilla.org/enter_bug.cgi?product=DevTools&...

I'd be happy to fix it!

jasonlaster11··on Faster Smarter JavaScript Debugging in Firefox DevTools
Happy to discuss collaborating on mapping variables. The current approach is based on re-parsing with babel, but we would like to extend source maps to include relevant mapping data.

https://twitter.com/auchenberg/status/1129435519727820800

jasonlaster11··on Ask HN: Why doesn't a time travel debugger exist yet for JavaScript?
That's a great point. Tracing quickly becomes slow and memory intensive.

I think you would enjoy this write-up. WebReplay is explicitly not tracing for that reason.

https://developer.mozilla.org/en-US/docs/Mozilla/Projects/We...

jasonlaster11··on Ask HN: Why doesn't a time travel debugger exist yet for JavaScript?
The problems I see with limiting the scope to single function IO are

1. JS is dynamic and a single function can do a lot, even if you try to stub out the world.

2. from a product perspective it would be hard to communicate what is going on.

3. Perhaps console logs could cover a lot of these cases.

Does that make sense? What are you thinking of?

---

We definitely want to make it easy to visualize function calls (inputs/outputs). For instance,

- see outlier function arguments (the time the first param was null) or the function returned early...

- see outlier call sites (the time when the function was called from a different call site)

- see outlier timings (the time when the function called when some other state was null or a promise was pending) i.e. race detection

On the other side, we would love to help users see the impact of a function call. For instance,

- program slicing: the other code that was run because this function was invoked

- data tainting: the data that was either read or written to because this function was invoked

jasonlaster11··on Ask HN: Why doesn't a time travel debugger exist yet for JavaScript?
Thanks for sharing the link. I'd like to emphasize that webreplay is still R&D :)

It is neat to see how far we've come in a year though!

jasonlaster11··on Ask HN: Why doesn't a time travel debugger exist yet for JavaScript?
We'd love to.

We have a WIP patch. At the moment, we're prioritizing MVP functionality, performance, and stability.

jasonlaster11··on Ask HN: Why doesn't a time travel debugger exist yet for JavaScript?
We're making progress on an experimental version in Firefox DevTools. It's not on the roadmap, but it is easy to try and we'd love feedback.

https://developer.mozilla.org/en-US/docs/Mozilla/Projects/We...

This video highlights some of the existing functionality:

https://www.youtube.com/watch?v=yS5ai04TP5Y&t=4s

1. a realtime recording button 2. a timeline view of events on the top 3. the ability to scan back to a console message 4. the ability to rewind to a breakpoint 5. the ability to add a logPoint in the debugger and see the messages in the console quickly

I'll second other comments on the complexity side. Our architecture works on the Operating System level, which makes it fast and non-invasive, but the difficulty level in terms of pulling something like this off is very high as you have to understand the browser architecture from the system calls it makes, to way processes behave, to graphics, the JS engine, and DevTools architecture.

I think we're in a good place in terms of getting feedback and iterating on the product. There's lot's to do and it is very exciting!

jasonlaster11··on WebReplay – Time Travel Debugging for Firefox
That's amazing!
jasonlaster11··on WebReplay – Time Travel Debugging for Firefox
Yep. It's on the roadmap, but the recording is done at the OS level, so Windows and Linux will require some work to get support.
jasonlaster11··on WebReplay – Time Travel Debugging for Firefox
Here are some docs on how to try it in nightly.

https://gist.github.com/jasonLaster/1e220992c294a571dd9b59ab...

jasonlaster11··on Ask HN: What good open source projects written in React that I can learn from?
yep - at the time we were not sure if we would want to transpile the code.
jasonlaster11··on Ask HN: What good open source projects written in React that I can learn from?
Thanks!

We'd love to have OSS help. We try to be as beginner friendly as possible.

Getting started is as easy as `npm install; npm start`. Here are our contributing docs - https://github.com/devtools-html/debugger.html/blob/master/C...

We have lots of great "up for grabs" issues for first time contributors - https://github.com/devtools-html/debugger.html/issues?q=is%3.... If you're interested, comment on one of the issues and it's yours.

This week we've had lots of first time contributors and there's a lot of low hanging fruit.

jasonlaster11··on Introducing the Firefox debugger.html
I like that idea. I think we can do several things when it comes down to tracking changes:

* make it easier to pause when a reference is set/get * make conditional breakpoints more of an every-day experience * better symbol search so that it is easier to see the different variable references and add the right breakpoints

jasonlaster11··on Introducing the Firefox debugger.html
Thanks for the feedback. (project maintainer)

I agree that "live edit" is an exciting feature. It supports a tighter feedback loop that lets you iterate in the correct context.

There are two challenges

1. transpiling, which would require a tighter integration with the project's build tools. Not impossible, but something that would require the correct UX. Chrome DevTools supports live edit now, but that is only for non source-mapped sources.

2. mapping to project sources. VS Code has done a lot of great work with source maps to map to the on disk sources with source maps. In theory, this should be easy, but there are many build tools and some edge cases with nested source maps, imagine an ember app that pulls in ember libraries which are also mapped.

With that said, this is definitely exciting and with the new front-end we can begin to work on an ambitious projects like this!

jasonlaster11··on Bret Victor, Inventing on Principle (2012) [video]
We're working on a new Firefox debugger wtitten in react-redux, which we hope will be a platform for prototyping interactive/visual features.

https://github.com/jlongster/debugger.html

jasonlaster11··on Peru – A tool for including other people's code in your projects
Thanks! This is a cool concept. It's interesting in that it helps pull in projects in a way that seems similar to package managers like npm, bower, bundler...
jasonlaster11··on MacDown: Open-source Markdown editor for OS X
same!
jasonlaster11··on Table-to-JSON
Would be great as a chrome extension
jasonlaster11··on Bootstrap Designer – Generate Bootstrap Templates
I think the editor is valuable if: 1. is responsive and lets you think visually 2. doesn't break bootstrap's model, so the output is similar to what a human would do. This means that you should have control over ids and classes and generally know the html structure of the components. 3. lets you extend bootstrap's components with CSS,JS,HTML 4. lets you create new components in a similarly modular way 5. plays nicely with server-side/front-end templates (mustache/erb) 6. talks with github so the changes you make can eventually be merged in (feature branch, pull request)
← PreviousPage 2 of 2