The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70
1–10 of 281 posts
Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70
#2Awesome. I love the direction Firefox is heading now that Chrome is a pain to use.
Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70
#3Awesome. I love the direction Firefox is heading now that Chrome is a pain to use.
I was perfectly fine with Chrome's usability until I started getting a `Hold Command + Q` to quit` prompt on my Mac. Before then, I hadn't even considered the possibility that an application could block me from quickly and easily quitting out of it. Now I have to hold the key combo or double tap it to quit Chrome, and it is the only application I have to do that for. It's so annoying.
Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70
#4One thing that wasn't clear to me from this post is why they still need the C++ interpreter at all. I assume there is some non-obvious cost that makes it not worth it for the coldest of code, but I'm having a hard time guessing what it may be.
Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70
#5Awesome. I love the direction Firefox is heading now that Chrome is a pain to use.
I was perfectly fine with Chrome's usability until I started getting a `Hold Command + Q` to quit` prompt on my Mac. Before then, I hadn't even considered the possibility that an application could block me from quickly and easily quitting out of it. Now I have to hold the key combo or double tap it to quit Chrome, and it is the only application I have to do that for. It's so annoying.
This bugs me big time, I wonder what was the decision behind such inconvenient UX.
Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70
#6Awesome. I love the direction Firefox is heading now that Chrome is a pain to use.
I was perfectly fine with Chrome's usability until I started getting a `Hold Command + Q` to quit` prompt on my Mac. Before then, I hadn't even considered the possibility that an application could block me from quickly and easily quitting out of it. Now I have to hold the key combo or double tap it to quit Chrome, and it is the only application I have to do that for. It's so annoying.
I'm surprised that functionality isn't possible to disable, but tbh I really like it. Too many times a finger slip turns Cmd+W into Cmd+Q and suddenly I'm lost a whole pile of tab state, possibly even half-submitted forms. Yuck.
Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70
#7Awesome. I love the direction Firefox is heading now that Chrome is a pain to use.
I was perfectly fine with Chrome's usability until I started getting a `Hold Command + Q` to quit` prompt on my Mac. Before then, I hadn't even considered the possibility that an application could block me from quickly and easily quitting out of it. Now I have to hold the key combo or double tap it to quit Chrome, and it is the only application I have to do that for. It's so annoying.
To Disable: Uncheck "Warn Before Quitting" on the "Chrome" menu - in between the Apple menu and "File" menu.
Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70
#8Awesome. I love the direction Firefox is heading now that Chrome is a pain to use.
I was perfectly fine with Chrome's usability until I started getting a `Hold Command + Q` to quit` prompt on my Mac. Before then, I hadn't even considered the possibility that an application could block me from quickly and easily quitting out of it. Now I have to hold the key combo or double tap it to quit Chrome, and it is the only application I have to do that for. It's so annoying.
This is extra weird because browsers have become really good at preserving state between closing and restarting.
The real answer to potentially destructive moves is not to ask the user twice, but to let the user easily undo.
Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70
#9Awesome. I love the direction Firefox is heading now that Chrome is a pain to use.
I was perfectly fine with Chrome's usability until I started getting a `Hold Command + Q` to quit` prompt on my Mac. Before then, I hadn't even considered the possibility that an application could block me from quickly and easily quitting out of it. Now I have to hold the key combo or double tap it to quit Chrome, and it is the only application I have to do that for. It's so annoying.
I actually love this and was waiting for this feature for a long time. I can't count the times I quit chrome by mistake.
You can disable it though.
Re: The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70
#10Earlier quoted context omitted.
I was perfectly fine with Chrome's usability until I started getting a `Hold Command + Q` to quit` prompt on my Mac. Before then, I hadn't even considered the possibility that an application could block me from quickly and easily quitting out of it. Now I have to hold the key combo or double tap it to quit Chrome, and it is the only application I have to do that for. It's so annoying.
I'm surprised that functionality isn't possible to disable, but tbh I really like it. Too many times a finger slip turns Cmd+W into Cmd+Q and suddenly I'm lost a whole pile of tab state, possibly even half-submitted forms. Yuck.
Surely that can be restored? In firefox, if you accidentally close a window, there’s a “Recently closed windows” thing in the history menu you can use that brings back all the tabs.