I've said it before, which is, it seems as though there's a glut of AOS internet web browsers.
I've been using AWeb forever, well only since I've gotten my AmigaOne and it's the first Amiga browser experince I've ever had.
I've used the limited IBrowse that came with AOS4. I like it quite a bit too. I tried to buy a key for it, but they couldn't provide me with one. I prefer genuine AOS constructed browsers, and software as well. It responds quicker and is usually MUCH smaller. Aweb starts so quick it's almost instant.
I'm quite happy with it, but it isn't upto date, as far as what's needed for the full web experience.
It has crashed almost not at all, compared to my FireFox 1 and 2 installs. Seriously, AOS4 crashes before AWeb does. I've had it run 27 days, then AOS4 locks up. The keyboard and mouse are no longer acknowleged, but dnetc, and the clock keep working. A script in the background with even the window it runs in turned off, also kept the time current. One time when I could see the dnetc OGR25 being calculated and the network connection was shut down (seems to happen when the keyboard and mouse cease to work), I waited for the last packet I had left to be loaded and waited to see if when it was done if an internet connection could be opened for updating, but it could not as the connection was severed.
I wonder if there's a script that could be written that would run in the background to reconnect to the internet if the connection is severed. This just to see if when the keyboard and mouse are no longer usable, if the ethernet socket is also disabled when the AOS lockup happens. I wonder if there's a counter and when it overflows, then the KB and mouse are inactive, it would be like the Y2K bug of windos.
My longest uptime was 32 days 19 hours.
These are my 4 longest uptimes.
System has been up since 16-Oct-07 20:38:22 (total uptime 26 days, 16:14:10) System has been up since 27-Mar-08 06:41:00 (total uptime 27 days, 23:26:21) System has been up since 29-Apr-08 09:38:48 (total uptime 29 days, 15:22:18) System has been up since 15-Jun-08 03:06:43 (total uptime 32 days, 19:15:54)
Support Amiga Fantasy cases!!! How to program: 1. Start with lots and lots of 0's. 10. Add 1's, liberally. "Details for OS 5 will be made public in the fourth quarter of 2007, ..." - Bill McEwen Whoah!!! He spoke, a bit late.
No, it's a WebKit browser. No idea what, if anything (WebKit itself includes parts from various sources incl. Mozilla), they took from FireFox, but nothing major related to the web engine.
Quote:
Half way there then? ;)
The only major difference to all other WebKit browsers is that they replaced the WebKit JavaScriptCore by the V8 VM, which only supports x86 and ARM CPUs. The rest is basically the same as in the other WebKit browsers (implementing the platform specific parts, in Chrome currently Windows-only), or even similar to OWB (abstraction layer between WebKit and the own parts, but unlike in OWB not with the goal to make it more portable). Additionally there are some parts which are impossible and/or don't make any sense on AmigaOS like the sandbox (AmigaOS has no different security levels) or using processes instead of threads (both are the same on AmigaOS). It includes next to nothing which could be ported to AmigaOS, for example the GUI would have to be rewritten from scratch.
The only part which helps for AmigaOS as well is that now 2 big companies are working on WebKit, like the Apple changes the Google ones will improve all WebKit browsers, incl. OWB. Additionally, if it's successful, more sites which currently only work with IE and/or FireFox will be fixed to work with WebKit browsers as well.
Elwood wrote: Chrome is the Firefox killer. FF3 is so slooow compared to Chrome. Wow, in 6 months for now, we won't hear FF mentioned anymore....
You should really think twice, or at least read more, before writing such cristal-ball sentence. I suggest you begin with this link for example, and then go to this other one.
Then rethink.
Bye, TMTisFree
"Never ascribe to malice that which is adequately explained by incompetence." (Napol?on Bonaparte) "I would love to change the world, but they won?t give me the source code." (Unknown)
11.1 You retain copyright and any other rights you already hold in Content which you submit, post or display on or through, the Services. By submitting, posting or displaying the content you give Google a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content which you submit, post or display on or through, the Services. This license is for the sole purpose of enabling Google to display, distribute and promote the Services and may be revoked for certain Services as defined in the Additional Terms of those Services.
Google has responded with haste to the huge outcry about a section in Chrome's EULA that gives Google "a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license" to do all kinds of dirty stuff?in public no less?to content you post through Chrome. Rebecca Ward, Senior Product Counsel for Google Chrome, told Ars that it's actually an oopsie from basically copying and pasting the same EULA it uses in other products, and that they're updating it as fast as they can to remove the ridiculous terms. Quote:
She says that Google is
"working quickly to remove language from Section 11 of the current Google Chrome terms of service. This change will apply retroactively to all users who have downloaded Google Chrome."
I hope this realy was just an oopsie and not a sign of worse things to come.