PS all those panicking about credits can just buy an A600GS and type "about :" in the browser url bar

Last edited by broadblues on 09-Aug-2025 at 05:07 PM.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

Once we saw this can we get a refund?
Pretty easy to do a propre press release no? Well maybe not for Matthew L.

Something worth celebrating, yet purists still want to see some kind of 68k miracle.

It would be like an x86 purist complaining how it's not really a proper Windows app because there's a bunch of CUDA code executed on dedicated hardware.

_________________
All the way, with 68k

Wow. Brilliant. I have just purchased an A600GS and have to say it is a brilliant system - very capable. Looking forward to using Amibrowser.

_________________
Sam

I'm also interested in the support they provide

_________________

This is great news.

So many complains about how it is made and works, I don't get all those complaints, does it matter? Haters gonna hate..

_________________

To me it seems a genius way of getting Chrome onto an Amiga with a native Amiga shell around it. It's a little like MS is doing with Edge. I know this is not literally the same thing. Great job AmigaKit and co.

_________________
Sam

agami Quote:

Something worth celebrating, yet purists still want to see some kind of 68k miracle.

If wanting to see 68k Amiga hardware rather than ARM non-Amiga hardware, then I guess that makes me a purist.

agami Quote:

It would be like an x86 purist complaining how it's not really a proper Windows app because there's a bunch of CUDA code executed on dedicated hardware.

A programmable computer has a native CPU which requires native code. In contrast, a computer can boot up and function without a GPU. Modern GPUs use drivers which are written in native CPU code while GPU processors are dedicated device processors. Many devices have used processors for many years and I have never seen a purist complain. The 68k Amiga has blitter and copper co-processors so where are the complaints?

Yssing Quote:

So many complains about how it is made and works, I don't get all those complaints, does it matter? Haters gonna hate.

This is a proprietary hybrid CPU code browser that would require multiple CPUs even if it was not proprietary. This does not move the Amiga forward at all. I can run a fully featured and supported browser in Windows with a WinUAE window open but it is EOL support for the Amiga and is not an advancement of the Amiga at all. This browser support is less advanced because there is a desire to not show another OS but it is there and replacing the 68k CPU and AmigaOS all the same. It is more bait and switch deception to replace the 68k Amiga.

Damn, every post you / news you jump on.

Going by your crazy logic. AROS have been baiting and switch deception since it started.
So I guess you hate AROS.

_________________

Damn, every post / news you jump on.

Going by your crazy logic. AROS have been baiting and switch deception since it started.
So I guess you hate AROS.

_________________

@F0L
I have allowed my code to be used in AROS which shows how much I hate it. Even though the A600GS and A1200NG ARM non-Amiga hardware uses AROS, this hybrid 68k/ARM browser kludge would be unlikely to make it back to the AROS code base even if it was not proprietary. I have nothing against AROS (or any other so called NG AmigaOS) which has been useful because it has been more open than the AmigaOS. However, the existence of AROS, and the fact that AmigaKit is using it, demonstrates the failure of the AmigaOS to adequately improve and proliferate. AmigaOS development and control is a disaster which began when control of it fell into the hands of con men through a coerced contract of the owner in financial duress. One of the biggest advantages of the 68k Amiga today is the tiny footprint standard system with a large library of software. Much of that is lost here (and with most NG AmigaOS recreations) and kludges are introduced. Inefficient function stubs are back which swizzle (endian convert) and extend/truncate registers as needed for 32-bit and 64-bit address conversions. Optimized ARM libraries were added to avoid emulation overhead and load-to-use stalls the 68k does not have and requires RISC code bloat to remove. This cheap ARM non-Amiga hardware and kludge software is far from an elegant 68k Amiga system. Here lies the "deceptive bait and switch" along with deceptive marketing and not with AROS specifically. The proper way to support such ARM hardware would be with little endian 64-bit ARM64/AArch64 AROS but then much of the advantage of the 68k Amiga tiny footprint standard system with large 68k Amiga software library is lost.

Blame Hyperion for OS mess. Thats the reason for Enhancer, as they refused to do any changes / fixes. So replacement commands had to be written to get around this problem.

In regards to AROS, any bug fixes are passed back to AROS team. Just like the recent AROS rom bug fix.

_________________

@Matthey

No.
Just no.
They made a product, theyre supporting their product. Its as simple as that.
Whether or not you, or anyone lese likes it is moot.
Also, dont be facetious. There's no "bait and switch" going on here. How did you not cringe at yourself for even thinking that, let alone sharing the thought?
Theyve been pretty open to the fact its partially ARM native. Heck theyre promoting the fact.

It runs the software its purported to run. How it goes about this is also moot *unless* disingenuous or dishonest. Theyre not.

Believe it or not, but no-one is obligated to continue the Amiga/Amiga-related hobby in the ways you deem best.
You like 68k? Great, so do many of us.
Those who have less narcissistic outlooks on the world however just continue to enjoy what we enjoy without feeling there's an injustice based on what strangers decide to do.

Im not an Amigakit fan for multiple reasons, but sheesh bloke get a freaking grip.

@fishy_fis
Read comments #15-#18 if you do not think there has been deception. Matthew makes his browser solution sound better and different than similar hybrid browser solutions. The title says "AmiBrowser: new modern web browser" but there is no real 68k Amiga browser here. There is only a 68k Amiga GUI with kludge interface to an ARM64 Linux browser.

@agami

Maybe this is the right time to change your signature then?

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@matthey

Quote:

There is only a 68k Amiga GUI with kludge interface to an ARM64 Linux browser.

Yes, thankfully, as an actual modern browser on AmigaOS is a nightmare both to implement and maintain, not to mention the security aspect. What do you think the British authorities would say it they were to find out that a UK company is selling products to consumers, knowing well that it doesn't even provide a bare minimum of security to its users? With this solution, the bare minimum of security is at least possible.

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@kolla

Quote:

@agami Maybe this is the right time to change your signature then?

Me thinks you are right.

_________________
All the way, with 68k

The A600GS is my dreamer thank you @amigakit very really good job

Salvatore Abbate

_________________

The Register published a news article about AmiBrowser.

https://www.theregister.com/2025/08/28/amiga_web_browser_amibrowser/

Last edited by Rob on 29-Aug-2025 at 07:45 PM.

Quote:

The Register publiced a news article about AmiBrowser.

Hm, quite a misleading title though - "AmiBrowser brings 21st century web to 20th century Amigas" - AmiBrowser is not for 20th century Amigas.

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC