SoylentNews is people
SoylentNews
from the just-thought...-you-were-a-guy. dept.
https://www.trinitydesktop.org/newsentry.php?entry=2014.12.16
The Trinity Desktop Environment (TDE) development team is pleased to announce the immediate availability of the new TDE R14.0.0 release. The Trinity Desktop Environment is a complete software desktop environment designed for Unix-like operating systems, intended for computer users preferring a traditional desktop model, and is free/libre software.
Unlike previous releases TDE R14.0.0 has been in development for over two years. This extended development period has allowed us to create a better, more stable and more feature-rich product than previous TDE releases. R14 is brimming with new features, such as a new hardware manager based on udev (HAL is no longer required), full network-manager 0.9 support, a brand new compositor (compton), built-in threading support, and much more!
(Score: 2) by Marand on Wednesday December 17 2014, @01:36PM
This is what I like about FOSS - it's being abandoned but people still like it? Fork it and keep it alive, and make it even better. Try *that* with Windows XP. :)
Yeah, about that [reactos.org] . . .
Don't forget that enthusiasts are also keeping the spirit of BeOS alive [haiku-os.org], too.
Or you could spend some time with an AmigaOS reimplementation [sourceforge.net] or clone [syllable.org].
Old OSes don't die, they just get reimplemented, emulated, or copied.
(Score: 2) by WizardFusion on Wednesday December 17 2014, @02:40PM
I liked BeOS when it was first released
(Score: 2) by Marand on Thursday December 18 2014, @03:10AM
BeOS was definitely something special. Boot times were ridiculously fast, it was stable, and compared to Windows 95, Linux of the time, and whatever MacOS version Apple had, the GUI was slick, modern, and really nice to use.
I was lucky enough to have hardware that worked well with BeOS5, so I spent a bit of time with it. I liked the unix-like feel of the command line aspects and I absolutely loved the way the titlebars just automatically worked as tabs. The latter is something I really wish other window managers would pick up on. Kwin can do something close but it's really clunky in comparison, and most WMs don't even have anything remotely similar.
It's shame it died off. Compared to what was available at the time it was like a glimpse of desktop computing's future. I was cheering for it even though I knew it didn't have much chance against Apple and Microsoft.
(Score: 2) by wonkey_monkey on Wednesday December 17 2014, @02:56PM
Your Syllable link didn't work.
http://www.syllable.org/ [syllable.org]
systemd is Roko's Basilisk
(Score: 2) by Marand on Thursday December 18 2014, @02:50AM
Good catch, I didn't notice syllable.org redirected to web.syllable.org when I was copying the domain. I hate when sites do half-broken redirect nonsense like that.
(Score: 2) by HiThere on Wednesday December 17 2014, @08:00PM
I waited a VERY long time for a MSWind95 compatible OS. It never showed up. It still hasn't showed up. About a decade ago I talked to a ReactOS developer, and he told me that if wine didn't support it, ReactOS wasn't likely to. I didn't go into details about why, but the impression I got was that either they used the same code, or the used wine as a template for development.
Wine *STILL* don't run MSWind95 applications...except some of them (i.e., not the ones I was interested in).
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.
(Score: 1, Informative) by Anonymous Coward on Wednesday December 17 2014, @09:38PM
either [ReactOS] used the same code, or [they] used wine as a template
Neither of those was or is completely accurate.
There has been a significant amount of cross-pollination between the 2 for many years.
Some years back, ReactOS had a major refactoring and they threw away a lot of code in favor of what WINE had done.
If neither of those runs your must-have Windoze-only app, ISTM the next choice is one of the Tiny* things you can get via BitTorrent.
(The less M$ code you run, the fewer bugs and exploitable holes you will encounter, so the cut-down stuff seems like an obvious decision if all-FOSS code isn't getting you there.)
Run that in a virtual machine, of course.
Replacing a snapshot of a M$ OS in a VM is about as simple as a recovery from an M$ failure gets.
.
...and the suggestion in the first place by Marand of ReactOS (whose devs have to grope around in the dark because the source code for MSFT stuff isn't available freely) is about as far away from the statement by ticho as anything could be re: forking existing FREE code.
-- gewg_