This is really cool. Was going to donate but I spent all my money on a shitty narc-computer that probably can't run it so I'll wait.
Oh yeah there's always QEMU but then I'm in Windows so...
No but it's supercool and I'm really looking forward to this. I remember reading "this will happen" and it was a lot quicker than I thought it would be. Huge respect for you guys.
What's the current status for the updated Odyssey? Our old Odyssey can't handle websites like GitHub any more (for a while already), and that's where we need to download things like the SDK addon and our CMake port...
i'm working on it. However also actual branch even if show github better doesn't works perfectly. I think the very latest branch from webkit maybe will fix it. I plan to release an alpha version soon but keep in mind that there are a lot of issues
Waiting for this new version, have you seen the thread regarding Browservice?
I can now surf on GitHub and go on any existing website thanks to it (and it's fast). If you've got a server already running (or a spare Rpi4 for example), juste give it a try, it changes everything.
I have downloaded new version APT on GitHub without any problem (and really fast).
As much as I would like to have a browser that can display all modern websites under AmigaOS 4.1, I agree that Browservice is currently the best solution for all our problems.
Facebook, Discord, Gmail, Github/GitLab, etc., including download/upload, it works really well. I'm glad there is a solution like Browservice.
We should be a little realistic. @afxgroup is doing a really great job, but it will certainly be a long time before we get a fully functional browser that works similarly to Wayfarer.
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
And even if Wayfarer is excellent (I'm using it with MorphOS on a PowerMac G5 2,7 Ghz), it struggles with sites like Discord or facebook, which is not the case with Browservice.
It's a market issue for AmigaOS and similar platforms, see G5 for MorphOS.
I used Morphos for a while, But I don't like the graphical interface.
Because they sell the hardware, not the software, that's the reality.
Imagine building an X64 PC or buying a recent MacOS without a browser, without recent games, without graphics applications, without video editors, etc. It's like buying a PS5 and then playing PlayStation 1 games.
And everyone knows this. The dream of having a modern AmigaOS never took off.
Plus, even if someone wants to buy it out of nostalgia, the prices are stratospheric
It's like buying a Pentium 4 + GeForce NVIDIA 256 for 2.000 euros
----------------------------------------------------------------- Want to sell something similar with Virtio GPU drivers ? Build a PC box for no more than €400. Because it's essentially a toy, maybe the price is right.
Just as a day well spent brings a happy sleep, so a life well used brings a happy death.
Web Browsers are huge task to accomplish even for big teams so it wouldn't surprise me if this will never happen on amiga os4.. But I am honest with you.. I still have faith in IBrowse!
Talking about os4 I think that the best solution would be a complete switch to X64 or newer technology than remain stuck on PPC..
I completely agree, because it's the reality. It's a shame Morphos can't find someone to finance the X64 switch. But this would be the same for AmigaOS.
It's just a question of supply = performance and software adequate for 2025.
My point is just related to the high cost for the current machine.
HARDWARE supply = ZERO performance (0)
It's not a bad argument, it's the reality.
Just as a day well spent brings a happy sleep, so a life well used brings a happy death.
i'm working on it. However also actual branch even if show github better doesn't works perfectly. I think the very latest branch from webkit maybe will fix it. I plan to release an alpha version soon but keep in mind that there are a lot of issues
Great to hear.
Quote:
I've seen wayfarer in use and honestly I was expecting more. Browsers on ppc are dead. We need to be realistic..
Why do you think that is? Is it because there's no up-to-date Javascript JIT compiler for PowerPC? Or are there more problems in the way.
If it's mostly the JIT compiler, then that reinforces the need to migrate to a more supported CPU (something I cover in the "Saving AmigaOS" series in the Kea Campus). Other problems could also be overcome during such a migration.
In the meantime, I'm still looking forward to your updated Odyssey.
Web Browsers are huge task to accomplish even for big teams so it wouldn't surprise me if this will never happen on amiga os4.. But I am honest with you.. I still have faith in IBrowse!
Start a movement called "The Simpler Web Project," where we dump a lot of bloat from the browser specifications to create a much simpler standard. I think that most if not all websites could work well with a fraction of what is currently part of the modern web platform standard.
No point, in having a good webbrowser without a secure OS.
We learned a lot from OS4, now its time to think about OS5, a more secure OS, stack should be private, not shared, we need to learn more from UNIX based systems. Also I think intuition virtualization is good idea, a bitmap lock or intuition lock should not freeze the user interface.
(think WinNT 3.0/4.0, something new that will take over in time)
This can solve the SMP issue, and add 64bit support, a legacy can be done suing compatibility layer.
Edited by LiveForIt on 2025/8/26 8:21:59
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
@Hans Our systems (ALL OF THEM OS4 or MOS) have 1 core that have to do EVERYTHING. From transport data from Stack with no DMA and no Hardware accelerated functions to render. Sites that uses a lot of javascript are a great problem and they born every day. Modern CPU and OS has multicore support, hardware accelerated instrctions for weight tasks, JIT, hardware accelerated renderer and so on.. We can continue to stay on ppc. But in the end we'll die.. that's for sure
So it's not PowerPC per-se, but a lot of missing software functionality. Switching CPU architectures would get us Javascript JIT, but wouldn't magically solve things like disk and networking performance, or hardware accelerated rendering (which is available, but nobody has written the code for webkit to use it).
@LiveForIt
If you keep moving the goalposts on what "we need to have first," then we'll never get there...
I cover OS modernisation in the Kea Campus "Saving AmigaOS" series that I mentioned earlier.
What's the connection you're drawing between the CPU and JavaScript? I'm confused. CPU's/SOC's fold in new features periodically (cryptography, AI ?) but I didn't think anything JavaScript-related was among them.