SoylentNews is people
SoylentNews
E20 is out. Straight from the horse's mouth:
The E20 development cycle has come to a close, with 1890 patches submitted by over 50 developers in the course of 441 days.
25+ reported Coverity analyzer issues and 165 tickets were addressed during this time (based on commit message tagging).
I'd like to personally thank everyone who contributed, whether by submitting patches, writing documentation, reporting bugs, or simply providing feedback on IRC.
The bug reporting MVP for this cycle was @ApB with 231 submitted tickets: an impressive echievement, though I regret that only about 70% of these tickets were able to be solved.Release Highlights
- Full Wayland support
- New screen management infrastructure and dialog
- New audio mixer infrastructure and gadget
- Many internal widgets replaced with Elementary
- Improved FreeBSD support
- Geolocation module
The complete log can be seen here.
Every time they release a new major version I feel compelled to try it, then I remember why I don't dig Enlightenment. It's just too hardcore a desktop environment for me. Any of you lot use it regularly or do I have company in my ass-pansy-ness?
(Score: 2) by Gravis on Wednesday December 02 2015, @05:58AM
Also there is some posts on thedalywtf about rasterman being an asshole, but I experience otherwise.
unless thedalywtf has several people reporting the same, both are anecdotal and thus should not be considered when judging his character.
The supposedly experienced C programmer criticizing the api must have looked only at the headers, it is open sources for God's sakes read the fucking sources....
with good code, you shouldn't have to look at the source if you have the headers. this is called encapsulation and it reduces the amount of knowledge required to make use of code. if it's poorly documenting, that's one thing, if he refuses to explain anything about it and demands that anyone using it should read the entire source, well, then he's an asshole programmer.
(Score: 2) by Post-Nihilist on Friday December 04 2015, @01:35AM
I agree that an API should stand on it's own . However, I find it usually faster to become proefficient with an API by looking at how a functionality is used by the library implementing it or the project that spawn it than reading the documentation, particularly when an implicit protocol is present ( C-based object orientation, in the case of EFL )
Be like us, be different, be a nihilist!!!
(Score: 2) by Gravis on Friday December 04 2015, @01:44AM
I find it usually faster to become proefficient with an API by looking at how a functionality is used by the library implementing it or the project that spawn it than reading the documentation
that's fine but not everyone is like you.