Announcement

Collapse
No announcement yet.

The DDE 2.0 Desktop Is Looking Nice

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • phoronix
    started a topic The DDE 2.0 Desktop Is Looking Nice

    The DDE 2.0 Desktop Is Looking Nice

    Phoronix: The DDE 2.0 Desktop Is Looking Nice

    This weekend marked the release of Deepin Linux 2014 along with the Deepin Desktop Environment 2.0 release that's powered using HTML5. In my testing of the release today, it's been working fairly well and is proving to be quite interesting...

    http://www.phoronix.com/vr.php?view=MTczNTg

  • curaga
    replied
    Originally posted by widardd View Post
    Sorry, but i got a serious problem with attitudes like this.
    Forcing users to buy new products every 5 years is wasting ressources.
    And wasting ressources just because they're cheap (Memory for google/MS/KDE/GNOME) is the worst.

    Anything not "close to metal" is wasting ressources, if you ask me. How can concentrating everything on unefficient high level languages be a good idea regarding this?

    As long as i see JS locking up my 5-6 year old machines, or an ARMv6 with Maemo surpassing modern day Snapdragons with Googles funny VM, i don't think i can be convinced.
    This. Doesn't matter that "what you can buy" would run JS acceptably. Installed base is what matters.

    Leave a comment:


  • caligula
    replied
    Originally posted by widardd View Post
    CPU scaling doesn't work that way, you cannot simply abstract performance from 1 to X cores.
    How about running some task X on both hardware? X could be 1) cpu intensive command line app 2) launching a big desktop app 3) some normal long term operation like indexing all movies in XBMC database? Surely there is some way to measure the systems? In all these cases my calculations pretty much hold water. Of course the network can be also a bottleneck in 3).

    Leave a comment:


  • widardd
    replied
    Originally posted by caligula View Post
    RPI is 50% slower clock per clock. That means 8 times slower.
    CPU scaling doesn't work that way, you cannot simply abstract performance from 1 to X cores.

    Leave a comment:


  • caligula
    replied
    Originally posted by doom_Oo7 View Post
    My raspberry says "fuck you"
    It's a toy. Back when RPI was published dual or quad-core Cortex-A9 1.2 GHz ARM was pretty normal for dev boards. RPI is 50% slower clock per clock. That means 8 times slower.

    Leave a comment:


  • doom_Oo7
    replied
    Originally posted by caligula View Post
    Only 2.0 GHz ARM, Core i3 x86 at minimum, no slower machines.
    My raspberry says "fuck you"

    Leave a comment:


  • efikkan
    replied
    This is why web developers are not suited to write software. Any decent programmer knows HTML and JS can never achieve the required level of responsiveness. It's not a matter of optimizing, but rather the fundamental implementation. In order to achieve responsiveness you need complete control of threading, timing, callbacks and execution time, JS will never be able to do this.

    JS is not only slower, it's also way harder to debug. Compiled code will always retain the advantage of predictable execution.

    Leave a comment:


  • johnc
    replied
    Originally posted by caligula View Post
    It will take some time but if you look at academic conferenses about programming languages and the hype in general, most effort goes into dynamic languages and especially JS. No doubt JS is now a bit slower still, but in the future it will have fastest VM, fastest FFI and interface with GPU, asm.js like accelerations. It will quickly replace all other scripting languages by an order of magnitude better performance. It's also possible to write slow C/C++ if you're a novice. So.. for a casual user the JS will turn out to be faster way to do things. It also encourages more voluntary workers since the language is easier to approach. Computers will also become faster so it doesn't matter if JS won't become lightning fast. You can't buy the slow computers soon anymore. Only 2.0 GHz ARM, Core i3 x86 at minimum, no slower machines.
    JavaScript is about 10x harder to program than C, is an awful, completely crippled language and is slow as shyt.

    It doesn't surprise me that everyone thinks it's the wave of the future.

    Leave a comment:


  • JS987
    replied
    Originally posted by caligula View Post
    You can't buy the slow computers soon anymore. Only 2.0 GHz ARM, Core i3 x86 at minimum, no slower machines.
    You can buy computer with small memory since 16 GB RAM became expensive. ARM is much slower than Core i3.

    Leave a comment:


  • widardd
    replied
    Originally posted by caligula View Post
    You can't buy the slow computers soon anymore.
    Sorry, but i got a serious problem with attitudes like this.
    Forcing users to buy new products every 5 years is wasting ressources.
    And wasting ressources just because they're cheap (Memory for google/MS/KDE/GNOME) is the worst.

    Anything not "close to metal" is wasting ressources, if you ask me. How can concentrating everything on unefficient high level languages be a good idea regarding this?

    As long as i see JS locking up my 5-6 year old machines, or an ARMv6 with Maemo surpassing modern day Snapdragons with Googles funny VM, i don't think i can be convinced.

    Leave a comment:

Working...
X