Quote:
Originally Posted by troyb
Favicons should be working better.
The exploding history.plist problem should be fixed.
Are people still seeing regular delays?
The one issue that isn't fixed is the history ox database problem but I'm curious if the two fixes above are helping most people.
|
Some developers/companies concentrate on fixing bugs and they don't cleanup debug etc code on alphas, they don't "optimise" the code before all major problems are fixed.
Is it true for Omniweb alphas too?
I am asking since your own Omni tool, Object Sweeper does these all and I have seen it how great it is thanks to Path Finder, its memory usage essentially went half after author used it.
Of course I maybe an advanced user only, not a developer, just speaking as guess.
In my prediction, on beta or release candidate stage, Omni will start taking care of speed and memory issues. Is it true assumption?