If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Glad it is dead, this made me ban Safari as a web browser in an all Mac environment because of how badly it behaved with WYSIWYG. Back then Safari also had a tendency to crash when undoing or just randomly.
Even worse, when you copied formatted strings to external programs.
- It was like a fingerprint.
My first thought is that hopefully they can get rid of the absolutely TERRIBLE performance problems, but then I realized that other khtml browsers are actually fast, so its not the rendering engine at fault.
In other words... who the hell cares? Chrome is going to remain a complete turd.
When Opera switched to WebKit I was bummed (monoculture, Chrome+skin, abandoned Presto, etc) but thinking that at least they got WebKit and this might be a good this in the end felt right. But now... daaam