Slashdot Mirror


User: Desler

Desler's activity in the archive.

Stories
0
Comments
5,621
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 5,621

  1. Re:GIMP vs. Ps (If PS is free!) on The Book of GIMP · · Score: 3, Informative

    If you had to actually pay $700 for it would it be worth your value then for its features?

    No, that's why they made Photoshop Elements that you can get for around $70 on Amazon for version 11.

  2. Re:MS Office mewlers and shills, queue here! on LibreOffice 4 Released · · Score: 1

    Yes, I read that. And? How does that change the fact that OO.org used ancient and crappily-written C++?

  3. Re:But what if Java is the next WAIS? on LibreOffice 4 Released · · Score: 0

    I don't confuse the two. Your misunderstanding seems to purely be an issue on your end.

  4. Re:MS Office mewlers and shills, queue here! on LibreOffice 4 Released · · Score: 2

    It didn't use it much before that point either. It's always been predominately a C++ codebase. It was just mostly ancient and crappily-written C++. Java was only needed for the HSQLDB, accessibility/assistive features and some of the wizards. The vast majority of its users can get away without those features.

  5. Re:But what if Java is the next WAIS? on LibreOffice 4 Released · · Score: 0, Troll

    Yep, malware authors are loving it. It's become quite the easy way to exploit 10s of millions of computers.

  6. Re:But what if Java is the next WAIS? on LibreOffice 4 Released · · Score: 5, Informative

    OpenOffice/LibreOffice is like 90+% C++. The Java bits are mostly irrelevant.

  7. Only because its develoment costs are subsidized by Oracle's other revenue and before that Sun's. It makes no actual revenue on its own.

  8. Re:blanket statement: evidence please on Researchers Opt To Limit Uses of Open-access Publications · · Score: 0

    Only if you go to a larger or more expensive college do you get access to major journals.

    Wrong. I've gone to small community colleges during summers when I was in college that had the access. If a University's library doesn't have such access as well then it's either being cheap or it's a shit school.

  9. Re:looks fanatastic on Experience the New Slashdot Mobile Site · · Score: 1

    I have a couple of Joomla based websites that use a plugin that automatically detects if you're on a mobile device and just sends you to the mobile optimized site. Not sure why you don't just do that.

    Because that's extraordinarily annoying when websites do that.

  10. Re:Why can't I turn off the ads? Otherwise...OK on Experience the New Slashdot Mobile Site · · Score: 1

    Normal Slashdot has a "disable ads" button if you have good karma. I believe that is what they are rederring to.

  11. Re:Classic on Experience the New Slashdot Mobile Site · · Score: 1

    The sad thing is I really wish I had been joking.

  12. Re:Tried it on Experience the New Slashdot Mobile Site · · Score: 1

    The look is not the issue. It's the rampant bugs and usability problems.

  13. Re:I'm sorry, but on Ubuntu Smartphone Shipping In October · · Score: 1

    You're joking with this post, right? How will an Ubuntu Phone run x86/x86_64 binaries?

  14. Re:Tried it on Experience the New Slashdot Mobile Site · · Score: 1

    I see it on my Galaxy S 2 with stock and FF browsers and in Mobile Safari on my iPhone.

  15. Re:Tried it on Experience the New Slashdot Mobile Site · · Score: 1

    I am too. iOS 6.1. There are other navigation issues beyond those that manifest.

  16. Re:No thanks on Experience the New Slashdot Mobile Site · · Score: 1

    More bugs I've noticed to alert the devs.

    Hit the "plus" submission button then hit back. More than half the time it doesn't go back and instead moves the cursor to the title field. The. There is no way to get back to the main page without refreshing because the back button is not enabled because the browser still thinks it's on the same page.

    Click a story then hit the "stories" button to back to the main page. Again the button disappears and does nothing. The url is still "m.slashdot.com" for some reason still. When hitting the back button in the browser (which is enabled now) it does not go to the main screen but to a poll page. So I have to hit forward then refresh to get the main page.

    This was about all I could stand before quitting it out of frustration. Mobile Safari is what I saw these happen under.

  17. Re:scrolling still broken on Experience the New Slashdot Mobile Site · · Score: 1

    The same laggy scrolling and scrolling being seen as a click issues as others are reporting.

  18. Re:Threshold slider on Experience the New Slashdot Mobile Site · · Score: 1

    It often doesn't work even on a desktop browser I've noticed.

  19. Re:No thanks on Experience the New Slashdot Mobile Site · · Score: 1

    We built this app using the latest technologies and frameworks such as Backbone, Zepto, Underscore, Hamstache, Jasmine, and Sass.

    Apparently in all their zest they forgot about the concept of progressive enhancement.

  20. Re:Fire your product manager on Experience the New Slashdot Mobile Site · · Score: 1

    +5 funny.

  21. Re:Abbreviated posts on Experience the New Slashdot Mobile Site · · Score: 1

    Their*

  22. Re:Classic on Experience the New Slashdot Mobile Site · · Score: 1

    Then they should hire someone competent for the job. Oh and get IPv6 support. With all the editorial whinging over the lack of people supporting IPv6 and the not supporting it yourself rings of pot calling the kettle black.

  23. Re:Abbreviated posts on Experience the New Slashdot Mobile Site · · Score: 1

    Dice has to get there money back somehow. Plunging the toilet they flushed it down didn't work apparently.

  24. Re:Too funny on Experience the New Slashdot Mobile Site · · Score: 1

    Incompetents leading the incompetent since Taco left, apparently. Not that he was the greatest leader, but it's been even shittier since his departure.

  25. Re:scrolling still broken on Experience the New Slashdot Mobile Site · · Score: 1

    It's just as bad on Firefox, too. Firefox doesn't magically fix broken code.