CPCemu vs uBlock Origin Lite

The Amstrad CPC is a semi-professional 8-bit computer with a 4 MHz microprocessor, introduced in 1984. If you owned one back in the 1980's or would have loved to do so, CPCemu is for you. If you would like to use special CPC software today or learn how to program a Z80 microprocessor, CPCemu is for you. You can also use it to watch the demos bringing the CPC to its limits, due to CPCemu's very high graphics and sound emulation accuracy, down to single microseconds. The type of graphics chip ("CRTC") can be selected in the user interface. Of course you can also play one or two of the amazing games still available using the touchscreen joystick emulation. CPCemu was the first emulator that provided emulation of an M4 Board (http://www.spinpoint.org) which provides an SD-card drive C:, configurable ROM slots and even TCP internet connections and HTTP downloads to the CPC. This emulation is compatible to the operating system SymbOS. CPCemu is the first CPC emulator that provides (basic) emulation of an external graphics card with a V9990 graphics processor, in particular for SymbOS. At any time, snapshots of the current state of the emulation can be saved and reloaded later. CPCemu provides real-time emulation and unlimited-speed emulation. Besides, the CPU speed can be switched between normal and 3x or 24x turbo mode. A simple monitor program (debugger) is integrated. It allows CRTC single-stepping (even if a CPU instruction takes more time than one CRTC step).

uBO Lite (uBOL) is a reliable and efficient content blocker. The default ruleset corresponds to uBlock Origin's default filterset: - uBlock Origin's built-in filter lists - EasyList - EasyPrivacy - Peter Lowe’s Ad and tracking server list You can enable more rulesets by visiting the options page -- click the _Cogs_ icon in the popup panel. uBOL is entirely declarative, meaning there is no need for a permanent uBOL process for the filtering to occur, and CSS/JS injection-based content filtering is performed reliably by the browser itself rather than by the extension. This means that uBOL itself does not consume CPU/memory resources while content blocking is ongoing -- uBOL's service worker process is required _only_ when you interact with the popup panel or the option pages.