#Seamonkey browser reporting a virus install#
Even today, for as hard as M$ is trying to move away from the Win32 API and "unmanaged" code Visual Studio still supports it just fine, if you install the right help and Windows still runs it. Oldest FORTRAN programs run the latest FORTRAN compilers (don't laugh - it's still taken very seriously for mathematics number crunching). Old C programs run just fine in the newest C++ (although you may need to use a special operative to turn off C++ processing but often, not). IMHO, a true successor to the Netscape legacy should be like 8088 code, FORTRAN, C++ or Win32: much of the oldest 8088 machine language will still run on the fastest PC CPU's today aside from the OS API. Some plugins STILL aren't possible in FF using WebExtensions - and there's not even a decent session manager for it in WebExtensions.
In the mean time, FF has lost plugin functionality due to becoming ever more a clone of Chrome - a browser FF users are decidedly NOT wishing they were using (Can you say hamburger menu? I knew that you could). Maybe it'll go away when they rewrite the rest in Chrome. It happens even though my CPU threads are not pegged. It happens even though they've invented a new language (Rust) and re-written their rendering engine in it. I also tried it in safe mode (i.e., all plugins disabled). It even happens if NoScript is on, and I bring up a bunch of pages with no JavaScript running. Still, if I open FF, and bring up about 20 tabs with lots of JavaScript and content, and leave it for about three days, FF still brings my system to its knees, and goes super slow (Win7 SP1 32-bit).
This was also the rationale for eliminating Flash and Acrobat Reader as browser plugins. That hasn't happened or if not, not by much.
The rationale for FF adopting WebExtensions, at least as I first assumed, was that it would supposedly make FF more stable. This seems like a God-awful development, to me.
0 kommentar(er)
