Stories
Slash Boxes
Comments

SoylentNews is people

posted by CoolHand on Wednesday December 02 2015, @04:33AM   Printer-friendly
from the desktop-nirvana dept.

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?


Original Submission

 
This discussion has been archived. No new comments can be posted.
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: 2) by Post-Nihilist on Wednesday December 02 2015, @05:12AM

    by Post-Nihilist (5672) on Wednesday December 02 2015, @05:12AM (#270505)

    Also there is some posts on thedalywtf about rasterman being an asshole, but I experience otherwise. I made a patch, he suggested real improvement to it and merge it into the mainline. Also I did find the source quite easy to understand, and I mostly program in java. 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....

    --
    Be like us, be different, be a nihilist!!!
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by Gravis on Wednesday December 02 2015, @05:58AM

    by Gravis (4596) on Wednesday December 02 2015, @05:58AM (#270514)

    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

      by Post-Nihilist (5672) on Friday December 04 2015, @01:35AM (#271654)

      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

        by Gravis (4596) on Friday December 04 2015, @01:44AM (#271656)

        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.

  • (Score: 3, Insightful) by Runaway1956 on Wednesday December 02 2015, @02:49PM

    by Runaway1956 (2926) Subscriber Badge on Wednesday December 02 2015, @02:49PM (#270680) Journal

    You know, there's nothing inherently "wrong" with assholes. Mostly, I don't give a damn if someone is an asshole. Maybe it depends on what kind of an asshole he is. I think Bill Gates is an asshole, but I also think he's an a unethical SOB, so I don't use his software. There are people who think Linus Torvalds is an asshole. Ehhh - if so, he's a very useful and endearing kind of asshole. I use his software all the time. Being an asshole is alright - and it has almost nothing to do with the quality of a person's work.

    Is rasterman an asshole? I don't care if he is - he does useful work, and he's never said or done anything that bothers me. Being an asshole is pretty much irrelevant.

    • (Score: 0) by Anonymous Coward on Wednesday December 02 2015, @08:25PM

      by Anonymous Coward on Wednesday December 02 2015, @08:25PM (#270881)

      In Jeff Hoogland's page that introduces his E17 fork, he indicates that the Enlightenment development team creates, loses interest in what they created, and moves on to The Next Big Thing.

      I have heard similar complaints about rasterman previously.
      It seems that he gets bored easily and quickly stops supporting previous efforts.

      What is lacking is someone on the core team who revels in responding to users and polishing the "old" (current) version as the rest of the team moves on to the alpha|beta|RC builds of the successor.
      My take on this:
      Not being a glamorous job, it's difficult to find someone who is interested.

      -- gewg_

  • (Score: 2) by TheRaven on Wednesday December 02 2015, @03:46PM

    by TheRaven (270) on Wednesday December 02 2015, @03:46PM (#270739) Journal

    The supposedly experienced C programmer criticizing the api must have looked only at the headers

    Why is that a surprise? Headers are where C APIs live. If you have to look at the implementation to understand the interface, then you have a poor API.

    --
    sudo mod me up