Firefox privacy, security and anti-tracking: a comprehensive user.js template for configuration and hardening
You can disable JIT in firefox, which makes it fall back to an interpreter. That should theoretically make it safer as there are less optimizations going on and less generated code being directly executed by the CPU.
Of course, it won't help you since it's not built into a web browser.
Appwrite - The open-source backend cloud platform. The open-source backend cloud platform for developing Web, Mobile, and Flutter applications. You can set up your backend faster with real-time APIs for authentication, databases, file storage, cloud functions, and much more!
The official mirror of the V8 Git repository
Looks like these are the two commits, based on the issue number:
Although there could be others.
OpenSnitch is a GNU/Linux interactive application firewall inspired by Little Snitch.
an interactive firewall for inbound and outbound connections
ECMAScript 5/6/7 compatibility tables
https://bellard.org/quickjs/ would be the easiest effort then
Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.
Media Source Extensions
It depends heavily on the website we're talking about but there's generally a lot going on when streaming video on the web.
On some websites, you might want to play with as low latency as possible between the broadcaster and the user. In those cases, you might want to optimize your JS code, have very small checking intervals, and you might again prefer to run as much code as possible in a worker to avoid rebuffering due to the risk of the main thread being too occupied doing other things to push media segments.
You might also want to apply some processing on the media played, for example transmuxing mpeg-ts segments to MP4 ones so they can be played by more browsers. Those are very frequent operations that can be performance-sensitive and are also often performed in another thread.
Also performance issues and poor memory management from the browser-side can lead to a lot of issues. A recurring issue at my work is bad performance leading through side-effect to a very poor quality being played (due to the high overhead in loading segments, pushing them to the buffer etc.).
All these would suffer without a powerful and featureful JS engine like we generally have today on most browsers.
11 projects | dev.to | 14 Jun 2023
Embeddable Common Lisp 23.9.9
4 projects | news.ycombinator.com | 9 Sep 2023
2 projects | news.ycombinator.com | 8 Sep 2023
Effective use of middleware in express.js: practical approaches
2 projects | dev.to | 3 Sep 2023
The Ascent of Node.js: How a runtime changed the Web
14 projects | dev.to | 30 Aug 2023