Seeing a modern browser supported does fill a big gap however. Who knows maybe one day through a series of silly unpredictable events it will be the OS of choice and running Ladybird browser in a similar fashion.
Seeing a modern browser supported does fill a big gap however. Who knows maybe one day through a series of silly unpredictable events it will be the OS of choice and running Ladybird browser in a similar fashion.
Edit: https://www.haiku-os.org/docs/userguide/en/workshop-wlan.htm... here wifi seems to be working (which another commenter pointed out as well)
[0] https://lore.kernel.org/all/20070405163434.GA18477@gollum.na...
It's a network problem. Manufacturers aren't gonna care unless it's a big OS with lots of users. Your OS won't get a lot of users unless it has drivers. So the result is stagnation, and only the Big 3 OS continuing. Well... really the Big 2. Mac OS is a unique situation.
So that feels like its 20 years in the past
> there is a lot of basics missing such as WiFi support.
So that sounds like 20 years in the past too
Where does the future bit come in?
Try using the old analog control systems where responses are basically instant. It feels like the controls are reading your mind.
Not all machines were like this though, we also had a Compaq Presario with some kind of Celeron running 98SE and that thing did feel slow more often than not, especially after several months of usage with the cruft buildup that comes with that.
> Mac OS 9 felt pretty darned fast on my 400Mhz iMac G3 back in 2000.
You were using a UI that (at its core) was built for 1984 machine, with sixteen additional years of hardware performance improvements.
Every once in a while I boot up a Mac from 1989, and Mac OS is definitely not snappy on it.
I think if you want speed, you need to find something built for a system far more constrained than the one you're actually using. The choices the developers made to make the system merely usable under those constraints will make it fast once they're removed.
We could have really snappy stuff today, but have gotten enamored with our latency inducing abstractions and haven't really gone back to fix it.
80s and 90s bloated UIs sure seem snappy and miniature by today's standards.
It needs to be a big show, and everybody must be able to directly understand it without any learning curve or even rtfm.
Everything else (ergonomics, features, ...) are too often secondary values.
I wouldn't say that UIs were great in the 90s. They weren't. It was also harder to implement them. The programming languages were more tedious, low-level, etc.
But as so often, it's disappointing what we do with our additional power today. Snappiness wouldn't even be my first concern, though.
https://news.ycombinator.com/item?id=36446933 - Windows NT on 600MHz machine opens apps instantly. What happened? (2023-06-23)
Follow up to the above by the original author:
https://news.ycombinator.com/item?id=36503983 - Fast machines, slow machines (2023-06-28)
Also Windows NT was released in 1993 when typical PCs were more like 100MHz, so this is getting a 6x speedup from the designed experience.
https://jmmv.dev/2023/06/fast-machines-slow-machines.html
The point is that the good old days aren't just pure nostalgia, some parts were genuinely good compared to modern bloated software.
Now we don't have such excuse, at least for non networked apps.
If you're gonna do that, then remember how much faster a well-expanded Amiga was. Even faster than any real 68k Mac when emulating Mac.
Also, it’s pointless to open a menu in less time than it takes the screen to refresh.
No, that would be the goal.
Once should be quite enough.
https://userbase.kde.org/Tips/Enable_fun_desktop_effects_on_...
I am pretty sure this is good old resistance to change. You would disabled them on all your systems, then force yourself to use them that way for a month and I am pretty sure that "disorientation" would quickly disappear.
My 22” Diamondtron went 2048x1536 @ 85Hz or 1600x1200 @ 100Hz (which is what I usually ran it at)
Ditch modern ad endpoints (a.k.a. operating systems) and go back to those distros we used 20 years ago. Accept that those don't support DRM, carefully choose our hardware (as its barely supported), and stick to it until it dies.
The thing i miss most from that time is Window Maker. I'd love to have again those tiny tiles with small graphs and buttons, but for more modern use cases.
I am an enthusiast for Gnome’s less is more approach.
Small nitpick: it was 2-bit and could do two greys in addition to black and white.
I use WindowMaker as a daily driver. Still.
I dream of Haiku being ported to Raspberry Pi and I even was sadly surprised it isn't - to me the primary value of Raspberry Pi seems it being an uniform standard hardware platform, this sounds like a great enabler for alternative OSes as lack of need to support all sorts of different hardware makes the thing a lot easier.
I tried the same thing several times with the Pi 3 and the Pi 4, and someone more vocally pointed towards RISC-V. Some four years later, there is a somewhat working RISC-V port, but in the meantime there is still no working ARM port of any real use.
On the whole, I was not overly impressed with the Haiku OS community where it regards exploring widely popular platforms that, despite having some challenges, would provide them with a larger audience. It's their call, but as an original BeOS user (and who can actually spot the Be Book from my couch as I'm typing this) and someone who's spent the past two years delving into the Rockchip ecosystem, I'm quite saddened by the way things went. It's not as if they lacked other ARM options, they just a) didn't have the resources and b) were perhaps a tad too opinionated.
However in this universe Steve Jobs never rejoins Apple, and most likely it closes doors a couple of years after Be's acquisition.
I guess certain laptop models, those that the devs use, might be allright.
Works on my old Thinkpads.