Stories
Slash Boxes
Comments

SoylentNews is people

Trinity Desktop Environment R14.0.0 Released!

posted by LaminatorX on Wednesday December 17 2014, @10:21AM   Printer-friendly
from the just-thought...-you-were-a-guy. dept.

SpaceMan writes:

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!

 
This discussion has been archived. No new comments can be posted.
Trinity Desktop Environment R14.0.0 Released! | Log In/Create an Account | Top | 34 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 1, Informative) by Anonymous Coward on Wednesday December 17 2014, @09:38PM

    by Anonymous Coward on Wednesday December 17 2014, @09:38PM (#126998)

    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_

    Starting Score:    0  points
    Moderation   +1  
       Informative=1, Total=1
    Extra 'Informative' Modifier   0  
    Total Score:   1