Slashdot Mirror


Gartner Reveals Top 10 Technologies For Next 4 Years

Dr. Jim writes "The good folks over at the Gartner Group have revealed the top 10 technologies that they believe will change the world over the next four years. The usual suspects including multi-core chips, virtualization, and cloud computing are on the list. Multicore servers and virtualization will mean that firms will need fewer boxes, and apps can be easily moved from box to box (and right out the door to an outsourced data center). Workplace social networks and cloud computing means that the need for a centralized IT department will go away. Firms will no longer need to own/maintain the boxes that they use to run their firm's apps. With no need to touch a box, there will be no need to have the IT staff co-located with the boxes."

8 of 163 comments (clear)

  1. Misleading summary; lean blog post by bbasgen · · Score: 5, Informative


      The article summary quotes a blog posting, *NOT* the Gartner study. Further, the blog posting only quotes the top ten items from Gartner, and provides no further data.

      The blogger is passing around FUD, without supporting those statements with any information from Gartner. This is a non-article with so little data.

    1. Re:Misleading summary; lean blog post by antifoidulus · · Score: 3, Informative

      The blogger is passing around FUD, without supporting those statements with any information from Gartner.

      And this is different from stuff actually by Gartner how? This is Gartner we are talking about, so if they did publish such a study, a more accurate title might be, "Top 10 technologies we have a vested financial interest in promoting"

  2. From TFA by Anonymous Coward · · Score: 2, Informative

    1. Multicore and hybrid processors
    2. Virtualization and fabric computing
    3. Social networks and social software
    4. Cloud computing and cloud/Web platforms
    5. Web mashups
    6. User Interface
    7. Ubiquitous computing
    8. Contextual computing
    9. Augmented reality
    10. Semantics

  3. Re:Forgetting one thing by Maint_Pgmr_3 · · Score: 5, Informative
  4. He left off a word!!!! by Maint_Pgmr_3 · · Score: 5, Informative

    http://www.gartner.com/it/page.jsp?id=681107 "Gartner Identifies Top Ten Disruptive Technologies for 2008 to 2012"

  5. Re:Let me be the first to say by Red+Flayer · · Score: 2, Informative

    Anyone who's been watching computers for the past year could have compiled that list.
    Duh. Gartner's target readers are not people who've been watching computers for the past year. Gartner's targets are the people who pay other people to watch computers, so that those people can pretend to know what they are talking about when they discuss new technologies with their minions.

    That's for generic articles like this one; Gartner does some targeted research and analysis that's better, particularly if you pay a lot of cash.
    --
    "Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
  6. Re:Let me be the first to say by afabbro · · Score: 5, Informative

    'Duh'

    Gartner is mainly known for two things:

    • "Duh"
    • Being wrong.
    Oh, and charging a lot. cf. Cringley's fine column on Gartner.
    --
    Advice: on VPS providers
  7. Re:Let me be the first to say by chthon · · Score: 2, Informative

    It looks to me a solution with the same problems as microprogramming : looks good in theory, but too many strings attached in practice.

    One of the biggest obstacles I see is the fact that this FPGA does not run on its own : you need several interfaces (hard and soft) to the chip.

    • A programming interface
    • A data exchange interface (byte or block oriented ? or maybe both)
    • A driver of course, based upon the above byte or block oriented interface
    • An application library, containing the code to reprogram the FPGA. Can you standardise on just one type of FPGA for your host architecture ?
    • Also part of the application library, the code to interface with the programmed functionality.

    I won't say wide deployment is not possible, but before that happens a whole lot of standardisation needs to be done first.