Web Browser
- Thread starter ps3lover
- Start date
, 
, 
, 
, 
, 
, 
, 
, 
, 
, 
-
Spielt gerade: GT7 | 60fps FTW
Endlich nach Ewigkeiten ein neues Release: SeaMonkey 2.46
https://blog.seamonkey-project.org/2016/12/22/tears-of-joy/
Leider sind immer noch nicht alle Probleme gelöste und daher fehlen einige normal mitgelieferte Extensions in diesem Release:
http://www.seamonkey-project.org/releases/seamonkey2.46/
Update:
Windows 2.40 -> 2.46 updates and SSE
2.46 and OSX64
https://blog.seamonkey-project.org/2016/12/22/tears-of-joy/
Leider sind immer noch nicht alle Probleme gelöste und daher fehlen einige normal mitgelieferte Extensions in diesem Release:
http://www.seamonkey-project.org/releases/seamonkey2.46/
Update:
Windows 2.40 -> 2.46 updates and SSE
2.46 and OSX64
Zuletzt editiert:
, , , , , , , , , ,
-
Spielt gerade: GT7 | 60fps FTW
Warum ist die Wiedergabe von Videos mit Opera (und Chrome(ium)?) so furchbar schlecht optimiert? (Windows)
In der Standardeinstellung liefert Youtube leider VP9 Videos aus. Hardwaresupport dazu ist lange nicht so verbreitet wie h.264.
Ein 1080p60 Video läuft damit auf einer Haswell 3GHz CPU (integ. GPU) mit sehr hoher CPU Last und hat teils Probleme überhaupt flüssug zu laufen
Also mit Extension h.264 erzwungen. Etwas besser, aber nicht wirklich gut. Dann per opera://flags Platformdecoding eingeschaltet. Ist am Ende aber auch nicht wirklich gut. Immer noch viel zu hohe CPU Last.
Zum Vergleich: In Edge (
) läuft das gleiche Video mit ein paar % CPU Last, die CPU taktet sehr weit runter.
Auf einer anderen, älteren Intelhardware habe ich ähnliches erlebt. In Opera CPU am Limit, läuft nicht flüssig. Im Internet Explorer läuft's und braucht auch nur einen Bruchteil CPU Last.
In der Standardeinstellung liefert Youtube leider VP9 Videos aus. Hardwaresupport dazu ist lange nicht so verbreitet wie h.264.
Ein 1080p60 Video läuft damit auf einer Haswell 3GHz CPU (integ. GPU) mit sehr hoher CPU Last und hat teils Probleme überhaupt flüssug zu laufen
Also mit Extension h.264 erzwungen. Etwas besser, aber nicht wirklich gut. Dann per opera://flags Platformdecoding eingeschaltet. Ist am Ende aber auch nicht wirklich gut. Immer noch viel zu hohe CPU Last.
Zum Vergleich: In Edge (
) läuft das gleiche Video mit ein paar % CPU Last, die CPU taktet sehr weit runter.Auf einer anderen, älteren Intelhardware habe ich ähnliches erlebt. In Opera CPU am Limit, läuft nicht flüssig. Im Internet Explorer läuft's und braucht auch nur einen Bruchteil CPU Last.
, , , , , , , , , ,
-
Spielt gerade: GT7 | 60fps FTW
Ein weiterer Mozilla-Add-On-Entwickler verabschiedet sich:
http://fasezero.com/lastnotice.html
http://fasezero.com/lastnotice.html
, 
, 
, 
, , , , , , , , , ,
-
Spielt gerade: GT7 | 60fps FTW
Enable MP4 (H.264 + AAC) HTML5 video in Firefox on Windows XP without Flash
Geht auch mit dem aktuellen ESR Release - die letzte Version von FF mit XP Support
Geht auch mit dem aktuellen ESR Release - die letzte Version von FF mit XP Support
, 
, , 
, , 
Der Firefox zeigt mittlerweile an, wenn Passwortfelder die Inhalte unverschlüsselt weiterleiten.
https://www.heise.de/newsticker/mel...t-sich-bei-Firefox-ueber-Warnung-3660544.html
Tja, ein Admin einer Website findet das gar nicht lustig, denn sie hätten ihr eigenes Sicherheitssystem und das wäre seit 15 Jahren sicher
, , , , , , , , , ,
-
Spielt gerade: GT7 | 60fps FTW
WTF? Firefox unterstützt jetzt nur noch PulseAudio (Linux/Unix).
https://news.slashdot.org/story/17/...lseaudio-only-leaves-alsa-users-with-no-sound
https://news.slashdot.org/story/17/...lseaudio-only-leaves-alsa-users-with-no-sound
, , , , , , , , , ,
-
Spielt gerade: GT7 | 60fps FTW
The State of the SeaMonkey Union!
Man versucht Mozilla zu folgen, Resourcen für einen eigenen Gecko-Fork sind nicht da, und es gibt auch keinen von Dritten der zukunftsträchtig scheint. Wenn Mozilla etwas entfernt oder unbrauchbar macht, wird das auch in Seamonkey so sein (NPAPI, klass. Themes u.ä.).
Greetings,
I am just relaying the following message for the SeaMonkey Council. It is not on the web page but it is official. If you have any questions you can either ask here or use the provided web address.
Have fun
FRG
+++ snip +++
Hello fellow users and supporters of the SeaMonkey suite.
The important part first: SeaMonkey is alive and we do not plan to discontinue it. But in continuing to deliver the best and only suite based on the Mozilla Gecko web engine, we need your help.
Lets first start where we are.
SeaMonkey 2.46 was released in late December after struggling for months with infrastructure and build issues. While still using the Mozilla infrastructure, we are mostly on our own here. We plan to release a final 2.48 based on the level of Firefox 51 soon. Again this is late due to infrastructure and build issues, but not so much as 2.46. Being based on Firefox 51 means that security patches are again not up to par with current Firefox. Believe us, we dislike this as much as you do.
The SeaMonkey project is entirely driven by volunteers working on it in their free time. The current members of the core team (count up to 7) are committed but, with all the changes, are getting slowly overwhelmed.
This means bugs do not get fixed as fast as we would like. With an aging infrastructure becoming more and more abandoned by Mozilla, due to switching Firefox building to the cloud, releasing builds does not become easier. It also means that if even one of the current key people quits, the project is in danger of becoming un-maintainable which is even worse.
Also keeping up with Firefox is becoming difficult at best. Mozilla plans to discontinue classic extensions and themes with Firefox 57 which is right around the corner. XUL, one of the key technologies of SeaMonkey, is also on the chopping block and will be discontinued in the near future. The replacement technologies, based on modern web standards, are immature and still under constant development. In the end, an almost complete rewrite of the current program will probably be needed. If it weren't for our friends from the Thunderbird project, we would now have even bigger problems.
The good news is that financially we are a little better off than last year. DuckDuckGo is now the default search engine of SeaMonkey. Every time you use it for searches in SeaMonkey we get paid. For the conspiracy seeking people out there
Not being able to easily set the search engine in 2.46 to another provider was a genuine bug with a workaround documented in the release notes from day 1. It has now been fixed.
What we plan:
After releasing SeaMonkey 2.48 we will switch to the Firefox 52 ESR source code for 2.49.x releases. This means that the code base is more or less frozen for a few release cycles and only security updates and bug fixes will be in the releases.
The infrastructure issue has been discussed. While critical, there are no final plans yet (also thanks to lack of manpower). Thunderbird is in the same boat and we hope to work out something together. If worst comes to worst, we could ask our team member Adrian Kalla to produce our regular builds. This had been discussed earlier. It was dismissed, for now, as no crash symbols for builds would be available on the Mozilla servers.
Switching to ESR means we can work on bugs in the current tree for a while longer without having to fear that they are carried over into a release. They need to be fixed for the next ESR of course.
The most critical issue is to support web extensions in one of the next releases. It is unclear how long we will be able to support classic extensions.
There are a number of Gecko Forks in the wild. We do not plan to switch over to one of them as the basis for SeaMonkey. We think that they currently do not have enough developers themselves to cope with the changes Mozilla plans. Web technologies are also evolving all the time and we fear that they are not able to keep up.
Also, we are not planning to support any abandoned stuff like classic extensions and NPAPI plugins on our own. We will try as long as possible. But when they are gone, they are gone. The current developer base is much too small to do our own fork.
Based on how successful Mozilla is, or if one of the forks gain ground, this might change in the future.
What we need:
Setting up our own infrastructure, potentially in conjunction with Thunderbird, will cost. If you feel you can contribute towards future releases in this way, please consider donating:
https://www.seamonkey-project.org/donate/
But what we need even more is people to help out. Even if you are not a developer, you can help. For example, writing a document such as this takes time. Also, maintaining a website is not done by staring at it all day.
So if you want to help, these project areas are looking for a few good contributors:
- Development. Most code is either JavaScript or XML/CSS mixed with C++ and Mozilla technologies based on XUL and friends. In SeaMonkey not so much HTML right now, but this might need to change. The build environment makes heavy use of Python.
- Graphics: Icons and symbols need a face lift for HiDPI screens. There are plans to switch everything over to svg files in the backend which would mean a massive effort to convert existing files. With a sometimes extremely conservative user base when it comes to changes in the interface, not an easy job
- Website: Some areas are severely outdated and things like release notes need to be written too.
- Bug hunting and triaging: We could use a few more people to check out bugs and try to reproduce and categorize them in Bugzilla. We are especially short on people doing this on macOS. While we are on it. Writing lengthy threads in the news and support groups is fine but if no one actually reports them as a bug in the end they usually won't get fixed.
- Everything else not covered above. If we forgot something you can fill this slot too. Just think about it.
As a final statement, we do not think that SeaMonkey will take over the browser world any time soon. SeaMonkey is a niche product and will stay that way. Too many people are not interested in a classic suite anymore and most users are happy to use what is hip. That is OK with us. It's all about choice.
We would like to continue supporting the power users like ourselves and those who are looking for something different and flexible without reinventing the wheel with every release. We try to listen to you, our user base, for advice/orders/demands/suggestions. Of course, we won't be able to implement everything under the sun. But we would still like to implement something and stay current. It's your call now.
If you would like to support us, either send a mail to us, the SeaMonkey Council (seamonkey-council at mozilla dot org), ask for guidance in the official support groups or just pick your favorite unassigned bug from Bugzilla and start.
We are looking forward to hearing from you.
The SeaMonkey Council
I am just relaying the following message for the SeaMonkey Council. It is not on the web page but it is official. If you have any questions you can either ask here or use the provided web address.
Have fun
FRG
+++ snip +++
Hello fellow users and supporters of the SeaMonkey suite.
The important part first: SeaMonkey is alive and we do not plan to discontinue it. But in continuing to deliver the best and only suite based on the Mozilla Gecko web engine, we need your help.
Lets first start where we are.
SeaMonkey 2.46 was released in late December after struggling for months with infrastructure and build issues. While still using the Mozilla infrastructure, we are mostly on our own here. We plan to release a final 2.48 based on the level of Firefox 51 soon. Again this is late due to infrastructure and build issues, but not so much as 2.46. Being based on Firefox 51 means that security patches are again not up to par with current Firefox. Believe us, we dislike this as much as you do.
The SeaMonkey project is entirely driven by volunteers working on it in their free time. The current members of the core team (count up to 7) are committed but, with all the changes, are getting slowly overwhelmed.
This means bugs do not get fixed as fast as we would like. With an aging infrastructure becoming more and more abandoned by Mozilla, due to switching Firefox building to the cloud, releasing builds does not become easier. It also means that if even one of the current key people quits, the project is in danger of becoming un-maintainable which is even worse.
Also keeping up with Firefox is becoming difficult at best. Mozilla plans to discontinue classic extensions and themes with Firefox 57 which is right around the corner. XUL, one of the key technologies of SeaMonkey, is also on the chopping block and will be discontinued in the near future. The replacement technologies, based on modern web standards, are immature and still under constant development. In the end, an almost complete rewrite of the current program will probably be needed. If it weren't for our friends from the Thunderbird project, we would now have even bigger problems.
The good news is that financially we are a little better off than last year. DuckDuckGo is now the default search engine of SeaMonkey. Every time you use it for searches in SeaMonkey we get paid. For the conspiracy seeking people out there
Not being able to easily set the search engine in 2.46 to another provider was a genuine bug with a workaround documented in the release notes from day 1. It has now been fixed.What we plan:
After releasing SeaMonkey 2.48 we will switch to the Firefox 52 ESR source code for 2.49.x releases. This means that the code base is more or less frozen for a few release cycles and only security updates and bug fixes will be in the releases.
The infrastructure issue has been discussed. While critical, there are no final plans yet (also thanks to lack of manpower). Thunderbird is in the same boat and we hope to work out something together. If worst comes to worst, we could ask our team member Adrian Kalla to produce our regular builds. This had been discussed earlier. It was dismissed, for now, as no crash symbols for builds would be available on the Mozilla servers.
Switching to ESR means we can work on bugs in the current tree for a while longer without having to fear that they are carried over into a release. They need to be fixed for the next ESR of course.
The most critical issue is to support web extensions in one of the next releases. It is unclear how long we will be able to support classic extensions.
There are a number of Gecko Forks in the wild. We do not plan to switch over to one of them as the basis for SeaMonkey. We think that they currently do not have enough developers themselves to cope with the changes Mozilla plans. Web technologies are also evolving all the time and we fear that they are not able to keep up.
Also, we are not planning to support any abandoned stuff like classic extensions and NPAPI plugins on our own. We will try as long as possible. But when they are gone, they are gone. The current developer base is much too small to do our own fork.
Based on how successful Mozilla is, or if one of the forks gain ground, this might change in the future.
What we need:
Setting up our own infrastructure, potentially in conjunction with Thunderbird, will cost. If you feel you can contribute towards future releases in this way, please consider donating:
https://www.seamonkey-project.org/donate/
But what we need even more is people to help out. Even if you are not a developer, you can help. For example, writing a document such as this takes time. Also, maintaining a website is not done by staring at it all day.
So if you want to help, these project areas are looking for a few good contributors:
- Development. Most code is either JavaScript or XML/CSS mixed with C++ and Mozilla technologies based on XUL and friends. In SeaMonkey not so much HTML right now, but this might need to change. The build environment makes heavy use of Python.
- Graphics: Icons and symbols need a face lift for HiDPI screens. There are plans to switch everything over to svg files in the backend which would mean a massive effort to convert existing files. With a sometimes extremely conservative user base when it comes to changes in the interface, not an easy job
- Website: Some areas are severely outdated and things like release notes need to be written too.
- Bug hunting and triaging: We could use a few more people to check out bugs and try to reproduce and categorize them in Bugzilla. We are especially short on people doing this on macOS. While we are on it. Writing lengthy threads in the news and support groups is fine but if no one actually reports them as a bug in the end they usually won't get fixed.
- Everything else not covered above. If we forgot something you can fill this slot too. Just think about it.
As a final statement, we do not think that SeaMonkey will take over the browser world any time soon. SeaMonkey is a niche product and will stay that way. Too many people are not interested in a classic suite anymore and most users are happy to use what is hip. That is OK with us. It's all about choice.
We would like to continue supporting the power users like ourselves and those who are looking for something different and flexible without reinventing the wheel with every release. We try to listen to you, our user base, for advice/orders/demands/suggestions. Of course, we won't be able to implement everything under the sun. But we would still like to implement something and stay current. It's your call now.
If you would like to support us, either send a mail to us, the SeaMonkey Council (seamonkey-council at mozilla dot org), ask for guidance in the official support groups or just pick your favorite unassigned bug from Bugzilla and start.
We are looking forward to hearing from you.
The SeaMonkey Council
Man versucht Mozilla zu folgen, Resourcen für einen eigenen Gecko-Fork sind nicht da, und es gibt auch keinen von Dritten der zukunftsträchtig scheint. Wenn Mozilla etwas entfernt oder unbrauchbar macht, wird das auch in Seamonkey so sein (NPAPI, klass. Themes u.ä.).
, , , , , , , , , ,
-
Spielt gerade: GT7 | 60fps FTW
Nun hat sich auch das andere bekannte Mozilla-Projekt zu seiner Zukunft geäußert.
Die langfristige techn. Entwicklung bleibt hier ebenfalls offen. Webtechniken bla bla - das waren die Mozillaprodukte im Grunde schon immer, nur eben in ihren eigenen Stil. Organisatorisch bleibt TB bei Mozilla.
Thunderbird’s Future Home
Proposal to start a new implementation of Thunderbird based on web technologies
https://groups.google.com/forum/#!topic/tb-planning/SPs8gzO5Wy0[1-25]
Die langfristige techn. Entwicklung bleibt hier ebenfalls offen. Webtechniken bla bla - das waren die Mozillaprodukte im Grunde schon immer, nur eben in ihren eigenen Stil. Organisatorisch bleibt TB bei Mozilla.
Thunderbird’s Future Home
Proposal to start a new implementation of Thunderbird based on web technologies
https://groups.google.com/forum/#!topic/tb-planning/SPs8gzO5Wy0[1-25]
Zuletzt editiert:
, , , , , , , , , ,
-
Spielt gerade: GT7 | 60fps FTW
Electron is flash for the desktop
2017 braucht man wohl für einen simplen Textchat 160MB Disk, 1GB RAM und 5% CPU Load. 
What is slack doing?
The process was in the background when this happened. I wasn't even interacting with it - I was in a meeting. I only noticed because my laptop fans were whurring when I got back. Restarting slack seemed to fix it for now.
But that's not abnormal for slack. In fact, slack often idles at 5% CPU usage. Whats it doing? I have no idea.
And I bet the slack team doesn't know either. How many lines of code do you think the slack team wrote to make their client work? I'd guess around 50k. Maybe 100k. But slack isn't a native app. At least - not a normal native app. Its built on top of electron, so when you download slack you're actually downloading a complete copy of Google Chrome. Chrome, at the time of writing is 15 million non-comment lines. When you download slack, 99% of the code is 'below the water'.
You can think of slack as a small javascript program running inside another operating system VM (chrome), that you have to run in order to essentially chat on IRC. Even if you've got the real chrome open, each electron app runs its own, extra copy of the whole VM.
And its not a stretch to call chrome an OS. By lines of code, chrome is about the same size as the linux kernel. Like the linux kernel it has APIs for all sorts of hardware, including opengl, VR, MIDI. It has an embedded copy of SQLite, memory management and its own task manager. On MacOS it even contains a userland USB driver for xbox360 controllers. (I know its there because I wrote it. Sorry.)
Does slack contain my code to use xbox controllers? Does the slack team know? Does anyone know? I mean, the slack app is 160 megs on disk.
...
Sure! You say. Disk size is cheap you say! Sure but ram sure isn't. The brand-spanking-new macbook pros only ship with 8 GB ram by default. Because of battery concerns you can't configure them past 16 gigs. And right now slack is sitting on somewhere between 300 megs to 1 gig of my laptop's ram:
I mean come on. Its a text chat program.
The process was in the background when this happened. I wasn't even interacting with it - I was in a meeting. I only noticed because my laptop fans were whurring when I got back. Restarting slack seemed to fix it for now.
But that's not abnormal for slack. In fact, slack often idles at 5% CPU usage. Whats it doing? I have no idea.
And I bet the slack team doesn't know either. How many lines of code do you think the slack team wrote to make their client work? I'd guess around 50k. Maybe 100k. But slack isn't a native app. At least - not a normal native app. Its built on top of electron, so when you download slack you're actually downloading a complete copy of Google Chrome. Chrome, at the time of writing is 15 million non-comment lines. When you download slack, 99% of the code is 'below the water'.
You can think of slack as a small javascript program running inside another operating system VM (chrome), that you have to run in order to essentially chat on IRC. Even if you've got the real chrome open, each electron app runs its own, extra copy of the whole VM.
And its not a stretch to call chrome an OS. By lines of code, chrome is about the same size as the linux kernel. Like the linux kernel it has APIs for all sorts of hardware, including opengl, VR, MIDI. It has an embedded copy of SQLite, memory management and its own task manager. On MacOS it even contains a userland USB driver for xbox360 controllers. (I know its there because I wrote it. Sorry.)
Does slack contain my code to use xbox controllers? Does the slack team know? Does anyone know? I mean, the slack app is 160 megs on disk.
...
Sure! You say. Disk size is cheap you say! Sure but ram sure isn't. The brand-spanking-new macbook pros only ship with 8 GB ram by default. Because of battery concerns you can't configure them past 16 gigs. And right now slack is sitting on somewhere between 300 megs to 1 gig of my laptop's ram:
I mean come on. Its a text chat program.
-
Spielt gerade: mit´m RKKV Prototyp
Mir geht Firefox nach mit unter fast 10 Jahen nurnoch auf die Nerven.
Keine Silverlight Unterstützung mehr, die braucht man für Amazon Prime Video anscheinend unbedingt und die Youtube Performance ist seit dem letzten Update unter aller Sau.
Edge macht keine Murren bei noch so vielen Tabs, Videos die gleichzeitig ablaufen.
Bei Firefox hab ich manchmal CPU Auslastung von 65-100% mit einem Tab (Video bzw Nur auf Youtube) kombiniert mit miserabler Framerate.
Schließe ich FF und guck mir das gleiche Video nochmal an, nichts, 3-7% Auslastung..
Keine Silverlight Unterstützung mehr, die braucht man für Amazon Prime Video anscheinend unbedingt und die Youtube Performance ist seit dem letzten Update unter aller Sau.
Edge macht keine Murren bei noch so vielen Tabs, Videos die gleichzeitig ablaufen.
Bei Firefox hab ich manchmal CPU Auslastung von 65-100% mit einem Tab (Video bzw Nur auf Youtube) kombiniert mit miserabler Framerate.
Schließe ich FF und guck mir das gleiche Video nochmal an, nichts, 3-7% Auslastung..
Electron is flash for the desktop
2017 braucht man wohl für einen simplen Textchat 160MB Disk, 1GB RAM und 5% CPU Load.
2017 braucht man wohl für einen simplen Textchat 160MB Disk, 1GB RAM und 5% CPU Load.
ich verstehe ehrlich gesagt denn Sinn der Desktop App nicht.
Die tut genau das selbe und sieht exakt so aus wie wenn ich mit nem browser auf slack gehe. Sie ist weder schneller noch komfortabler.
Die hat überhaupt keinen mehrwehrt. Einfach nur unnötig.