There is a couple of good rules to follow when browsing on the internet. 1. Don't believe everything you read on the internet. 2. Check who your sending your emails too incase they maybe know more then you. On Friday, 23 February 2018 00:18:11 ACDT, Liam Proven wrote:
On Thu, 22 Feb 2018 08:15:26 +1030 Simon Lees
wrote: Then I read this:
https://what.thedailywtf.com/topic/15001/enlightened
(Warning: sweary.)
It's become quite famous and attracted many angry responses, including from Rasterman himself -- but as it was at the time, it appears to be almost entirely true and accurate.
As someone who has been involved in the enlightenment project for over 7 years (including when this article came about, and frankly its pretty much all over exaggeration's or plain wrong. As a starting point it looks like the author was trying to use completely the wrong library for what he was trying to do, enlightenment's libraries (efl) have been designed to be very modular there is a low level library (evas) thats not that useful in most cases and a higher level toolkit (elementary) which is and it seemed like he was possibly using the wrong one to start with. Yes the documentation isn't as good as Qt there is no big team of core devs that can sit down and spend all there life writing doco which Qt has had at some point. The API's are very much C like and if you get the way of doing things in C with functions and pointers it all makes sense and you don't have issues. Some of the complaints very much just seemed like he wanted a C++ api which is also what I'd prefer. Having spent 5 years as a professional Qt application developer i've spent time with both, personally I like the C++ way (efl will soon have C++ bindings anyway), but there are good reasons why they chose C stuff like abi compatibility is much easier for low level libraries with C rather then C++, reading Qt's source code will show you the extra effort involved with picking C++. I have written stuff in both, they use completely different styles but both work etc. Raster is a great friendly guy I chat to him every second or 3rd day on irc he had plenty of right to angrily defend a bunch of lies someone posted on the internet.
There were some very hasty edits to the code and the docs to conceal some of the things the article criticises, but there's history to show that.
The only hasty change I remember was removing the second error message because frankly it shouldn't have been there, know one knew it was there because they had never seen it, from memory I believe it was added by an early contributor who had long left the project.As soon as people were made aware of it, it was replaced and from memory someone took the time to scan the code base for other possibly offensive messages.
Later, even Bodhi itself got annoyed with the development cycle and forked E17 to create its own desktop.
This again is inaccurate and untrue, From Enlightenment e18 and onward Enlightenment required the compositor to be enabled (this was mostly for wayland but also greatly helped clean up parts of the code base). When this was done a bunch of 3rd party modules of varying quality that depended on the compositor not running stopped working. Bodhi was the only distro shipping these modules (on openSUSE we didn't because from my testing they didn't seem stable enough and they weren't part of the core e17). This combined with people presuming that compsiting would be slow on old hardware (its not e has an awesome highly optimized software renderer) was the main reason for bodhi staying with e17 (for a while they offered 2 versions). It wasn't really anything to do with the development cycle (I believe they are still using the latest enlightenment foundation libraries)
So, yes, long may it continue and so on -- I gather Tizen uses it, for instance -- but I don't foresee it escaping its niche in the foreseeable future.
Well for me its the only desktop that does workspaces / virtual desktops properly with multiple screens out of the box, I can have screen 1 on workspace 4 and screen to on workspace 2 then change screen 1 to workspace 3 then sometime later change screen 2 to workspace 2, this is great for having certain apps on one screen and flicking between multiple on the other. It also has the most extensive theme engine (As a down side themes take forever to write) oneday i'll get a bunch of themes done and be really happy. Anyway we are rather offtopic, but I thought it was worth correcting some misconceptions, if you want to discuss this further feel free to contact me off list via mail or on irc Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B