It might be well known in Amiga circles, but it would be hard to call a web browser for Amigas that last had a release nearly two decades ago "well known".

Name clashes happen all the time, it doesn't seem like a big deal.

here's what I did instead, I went to https://duck.ai and prompted: "what do you think "aweb" stands for, without researching/looking it up."

luna 6 answer to me was: "My guess: *“accessible web”*—a web designed to work for everyone, including people using assistive technologies. Could also just be a stylized spelling of “a web.”"

I then clicked "2nd opinion" and the result from Gemma 4 was: "Depending on the context, I think it most likely stands for one of these three things:

First, the most literal interpretation would be *Advanced Web* or *Accessible Web*, likely referring to a specific set of technical standards or a high-performance version of a website.

Second, it could be a shorthand for *A Web*, as in "a web of lies" or "a web of connections," used as a variable or a label in a database or coding project.

Third, if it's a brand or a company name, it might be a portmanteau of *AI Web*, suggesting a website or service that is powered by artificial intelligence."

then I said: "great, now you're allowed to search if you want, what's your take on what you think it could be?"

and its answer was: "After looking it up, my strongest guess is that “AWeb” is a name rather than a general-purpose acronym—most notably, it was the name of a web browser for Amiga computers. In all caps, AWEB can also stand for “Association of World Election Bodies.” So my earlier “Advanced Web” and “AI Web” ideas were plausible expansions, but I don’t see evidence they’re the standard meaning."

just sharing, thought it was fun to run this N=1 experiment since you shared yours

For the fun of it: I asked Google Gemini and ChatGPT (OpenAI) "What is AWeb?" and they both gave me the amiga browser as answer. No idea if they just know, or did a similar lookup as I did? :)

Fascinating! And here I am thinking that it would be obvious that it stands for "agentic web" :-)

They allow port scans?

I did use nmap on a Linux VM going over the free ProtonVPN for this purpose, but at some point Proton broke something (it may be related to their VPN accelerator feature) and checking any port always reports "Open" (even if it's not), so sadly that made this cool use case entirely useless for me. It definitely was nice to know you had no open ports other than the ones you purposefully opened. :)

Occasionally drag'n'drop failures —where it just stops working— I experienced already with Yosemite, so it may be a VERY old bug. :) Usually you would see "CoreDragError" codes popping up in the system.log

Rather than rebooting, I just kill "pboard" in Activity Monitor, and afterwards restart a few GUI programs that were directly affected (including Finder and Dock.)

My wild theory is that Firefox is the culprit. At least the issues happened more frequently once I had to switch to Firefox for proper content blocking extensions. Anyway… I have no idea how to prove that, so it's just a guess, not a blame.

If you leave that in it's actually worse, since the platform was discontinued. I had to fix all my client's projects to remove this stuff. One of those stillborn ideas of the EU.

In my own ranking of favourite programming languages C is at the first place. C++ comes in last. I personally hate it when people write C/C++ as if it's the very same thing. I'm quite sure there's more like me out there. :)

Interestingly Perl comes in second, even I use it rarely (aka not at all) these days. But that's a slightly off-topic side note. :)

Perl is just C with less type safety.

And yes, for the most part. C++ as simple shorthand for struct-attached functions and automatic memory management (no, not smart pointers; RAAI) is good. Every single thing added after that is misery and should push a modern developer to Rust, Go, or Zig (roughly in that order) where such things are implemented sanely or not at all.

Funny I think of Perl as Bash with slightly saner syntax plus robust regexp. (said with love)

This is also fair.

The only thing Perl and C have in common is the curly-brace.

And direct access to system calls. And the uncanny ability to look like it's going to do what I want and then five minutes into a run wind up in a small town in Arkansas blind drunk and crying vaguely about fluffy red squirrels taking its sandwich.

But it adds to the charm.

For me, C++ is always in first place. It allows me to do high-level abstractions to low-level hijinks all with total control (i.e. zero-cost abstractions, Templates for compile time programming etc.) across all levels of the software stack and the full spectrum of available hardware.

Furthermore, any C++ programmer who says they do not know C, knows neither C nor C++ (hence my preference in using C/C++ as a shorthand to encompass both and highlight the dependency of the latter on the former). I often see this in novice C++ programmers who started with "Modern C++" and identify it as something like Java/C# because of the now huge set of standard libraries and copious syntactic sugar which only compounds their confusion further.

> Furthermore, any C++ programmer who says they do not know C, knows neither C nor C++ (hence my preference in using C/C++ as a shorthand to encompass both and highlight the dependency of the latter on the former).

Right, but this dependency is one-way. There is an entire legion of C programmers who reject C++ (most notably Linus), so claiming that almost all C programmers are also C++ programmers is a bit off.

What i meant was that almost all C programmers are aware of and know C++ to varying degrees. But they choose to not use it for their application based on needs/expertise/etc.

Linus Torvalds objection to using C++ is perfectly logical for his use-case. I know many embedded programmers who refuse to use C++ even though they understand and agree with the benefits that it can bring to the table. Their C expertise is so good that when they program, cognitively the language just disappears and they "flow" through the problem solution implementation. This is the crux of problem-solving.

I'm always surprised on here when I see others admin to liking C and Perl. It makes me feel less alone.

Many of us were there when yada yada white wizard. Hell, my first paid job was writing Perl CGI scripts. Well, script. Monolithic MFing thing spread across 100 files and running a whole company on text files with zero format documentation and RCS as version control. No need for CVS because the systems were incrementally archived with tar every hour...

Until they weren't. (I'm glad you saw that coming, because they didn't.)

If they don't have to re-code half the app (new UI kit, not required features, etc.) then what does it matter if they are 10k unrelated commits behind?

I like it's there as a choice for us who prefer the old-timey Audacity for some quick sample editing.

I do not have one (and it's actually true.) And it's not easy. :-(

The proper way to cheat is to not leave a trace on the tracker where a tracker staff may or may not make correct judgement. It's called "ghost leeching." Basically you directly connect to known peers' IPs (e.g. from some heavy seedbox users) and never even report anything back to the tracker.

Of course, those peers where you ghost leech of then would correctly report the upload they generate (making THEM look suspicious of cheating by "over-reporting" upload.) It's impossible for any tracker staff to properly detect and attribute proper cheating in such cases, unless they can detect a pattern. The tracker staff objectively can only catch people that do really stupid things.

That's just the way BitTorrent and private tracker economics work. A "private" tracker is more like a social contract between its users to do the honourable thing, but you'll always have some idiots that do not get that, of course.

The limitation with ghost leeching is that it won't help raise your ratio. It's a way to avoid decreasing it (by never reporting download). If your ratio is bad and for reasons you want to increase it, you will have to generate upload one way or another. You can ghost leech and then seed the torrent you downloaded, but it can also look weird that you are now seeding a torrent that you never downloaded. But due to the nature of torrent, it is also possible.

But that's what I find fascinating. BitTorrent is a very cool tech, and not that hard to understand. It uses a lot of simple idea that works very well together. It's really fun to hack on it. And I add an obsession with findings 'cheating' methods a few years back. Overall, as you said, it's more of a social contract. None cared unless it was stupidly obvious.

You mean that if I experience a call of nature with AROS I have to stop, dismount, and go behind a tree? :)

(BTW, I had uptimes of many hundred days with a regularly used Amiga machine. So crashes were possible, but if you run only quality software eventually (you'll eventually get to the point after a few years) it could be really, really stable. Eventually memory fragmentation would hit you though.)

"cross-platform" and Rust, as advertised in the current title/link label, is incompatible for sure. Can't get that to run on my older OS X machine nor my Amiga. :)

Yup, I have private forks where I've had Claude/Codex rip out Rust for that reason.

feel free to fork MartyPC to build it for your Amiga