February 10, 2011
Citrix's Labana: Enterprise tablet apps a jump ball between Apple, Android (and yes Microsoft)
Citrix tech guy gives his take on directions in mobile and odds on Apple, Android, and yes, Microsoft....
Citrix’s Harry Labana has a notable view of mobile enterprise computing. Labana has been a Wall Street technology executive, is responsible for supporting multiple devices with the Citrix Receiver and has a ground-level view of mobile development and what it means to the enterprise.
We caught up with Labana, chief technology officer of desktop and application virtualization at Citrix, to talk strategy, managing mobile devices in the enterprise, Microsoft’s tablet prospects and cloud computing.
Here’s the recap from our conversation earlier this week.
On bring your own IT, Labana said the trend isn’t going away, but also noted that Citrix isn’t only promoting consumerization. “BYO isn’t a religion and we’re not only promoting it,” said Labana. “The devices can be enterprise or consumer owned, but there will more of them.”
What about the impact of consumerization on managing technology? The reality here is that there are costs to managing distributed devices, said Labana. “If it costs X to manage the PC and phone fleet it’s going to cost even more to manage tablets,” said Labana. “The greater number of devices there are the greater the risks.” Before joining Citrix, Labana was a technology executive at Goldman Sachs and other Wall Street firms so he knows the perils of data leakage and risks to a company’s reputation. The Holy Grail for IT is to manage a smaller, simpler device footprint, but with enough flexibility to keep users happy.
Are so-called thin clients the answer? Labana played down the role of the thin client. The reality is that some things will need to run locally. Labana prefers the idea of a slim client that can run some things locally, but is simple. In the enterprise, these slim clients are really lightweight PCs. “Companies aren’t buying workstations and several hundred dollar PCs,” he said. Some verticals like healthcare can use zero touch thin clients, but most will prefer slimmed down PCs.
How’s Microsoft’s tablet strategy looking? Citrix is a long-time partner of Microsoft so Labana couldn’t complain too much, but did acknowledge that the software giant has catching up to do. However, Labana noted that it isn’t too late for Microsoft to be a tablet player. “The sweet spot for Microsoft is still the enterprise customer, who is broadly Windows based. That’s not going to change,” said Labana.
What are the most mature platforms today? Given Citrix’s move to put its Receiver software on multiple devices, Labana has a good view of the mobile platform landscape. “We have focused the Citrix Receiver to run on all devices, but it requires a lot of spending to make it run on every platform,” he said. Labana breaks down the mobile platforms this way:
Apple’s iOS is the most mature to develop for. Android is second and Citrix’s Receiver was easy to port since it was built on Linux. The problem with Android is that it runs differently on each type of device—Dell Streak, Samsung’s Tablet, Motorola, HTC etc.
Who wins in the enterprise? Labana says the customers and technology managers he talks to are split on Apple vs. Android. “To some of them, open and fragmented (Android) is a good thing. The IT buyer won’t feel locked in,” said Labana. “But all the users are buying iPads.” He did note that enterprises are concerned about lock-in with Apple.
Where will the enterprise app focus go—smartphones or tablets? Labana said “the IT guys are not writing apps for smartphones. If they are going to invest in something they are going to write apps for tablets.” Why? Form factor. The tablet is simply more useful for work tasks.
Posted by Staff at 02:01 PM | Comments (0)
December 31, 2010
2011 Predictions & Guesses
Every year new predictions come around and this year we thought we would compile a few of them to try and give them their own context for the whole so to speak. This year we learn about "fabric-based computing". Where people come up with this stuff who knows.
feature article
Every year new predictions come around and this year we thought we would compile a few of them to try and give them their own context for the whole so to speak. This year we learn about "fabric-based computing". Where people come up with this stuff who knows.
feature article
Posted by Staff at 06:17 PM | Comments (0)
December 04, 2010
Google Chrome: Meet the Contender
 Woody Leonard/Infoworld commentary on upcoming Google Chrome OS and what it means. And what it means to Microsoft. |
Google Chrome: Meet the Contender - PCWorld
By Woody Leonhard, Infoworld Dec 4, 2010 7:35 am
It's been a tumultuous year for IT shops, with paradigms shifting like tectonic plates in San Andreas. You might think the IT world would begin to stabilize a bit, at least conceptually, as we launch into the year-end consumer feeding frenzy.
Alas, it's not to be.
Depending on whom you follow, Google's long-anticipated Chrome OS could make its debut in the next couple of weeks, or the next couple of months. In mid-November, at the Web 2.0 Summit, Google CEO Eric Schmidt said Chrome OS would hit "in the next few months." A week later, Chrome OS head honcho Sundar Pichai was quoted in the New York Times, saying Google would launch a lightweight netbook with Chrome OS by the end of the year.
Although few heads will turn at the sight of a Chrome OS netbook -- we're not talking iPad 2 here -- the technology involved represents a radical departure from anything IT shops have seen in many years.
If you were around the computer industry 10 or 15 years ago, you may recall Larry Ellison's infatuation with the concept of a thin client: a minimalist chunk of hardware that sits on a desk, inextricably tethered to a server. The server provides all of the brains and most of the storage; the thin client only exists to interact with the server.
I tend to think of Chrome OS as implementing a gaunt client -- thin to the point of cadaverous -- tethered to the Web. No desktop applications. No backup programs. No UI tweaks. No tuning. No utilities. Just the Web, the browser, and the Web, and the browser.
More than a year ago, Google posted a YouTube video that explains Chrome OS's charm: Your netbook runs the browser, and that's it -- simple, fast, no layers of overhead, no dark corners for malware, just the browser on metal. More than that, Chrome OS doesn't store any of your data or settings on the computer -- it's all in the cloud. You can flit from one netbook to another and absolutely everything travels with you. If your netbook breaks down, pick up another one. Somebody steals it, who cares? If you're interrupted in the middle of doing something, you can pick right up where you left off by using any other Chrome OS device.
Google's given a lot of thought to the interface, as well. More than a year ago, Sundar Pichai posted another YouTube video with all sorts of details -- application tabs, dockable pop-up panels -- which may or may not end up in the product we'll see in a few weeks.
At the same time, Google released Chrome OS's source code, called the Chromium OS Project. Developers have been hacking away at it for a year. Chrome OS is from Google, and it's focused on hardware specifically built to Google's specifications. Chromium OS may run on many different boxes.
That was a year ago. Since then, we've heard very little from the Chrome OS team -- remarkable because it appears as if Dell, HP, Lenovo, Acer, Asus, Toshiba, and other hardware manufacturers are actively bulding machines using Chrome OS. Since then the world's changed, leading to much speculation about how Chrome OS may (or may not!) have adapted to the meteoric rise of the iPad and Google's own Android. By many accounts, netbook sales are hurting, with the iPad rushing in where Windows-based PCs feared to tread.
So how, you may ask, is Chrome OS different from Android? They were developed by two entirely different teams, working from diametrically opposed starting points. As Eric Schmidt said during his Web 2.0 presentation, Android is designed for touch devices and Chrome OS is designed for keyboard devices. Of course, that immediately begs the question of which operating system is intended for use on phones with keypads or slates with touchscreens -- a distinction that will certainly fade in the next year or two.
I wonder if Schmidt ever dreamed he would face a situation where two of his open source products will fight each other for market share. It seems inevitable, at this point.
Posted by Staff at 04:48 PM | Comments (0)
July 19, 2010
Dell Comes Out on Ubuntu
Unusual but Dell has new webpage on the merits of Ubuntu versus Windows. Seeing Linux bleeding over into consumer area is remarkable and Dell does a nice job of positioning. WINDOWS OR UBUNTU ? | Dell UK
Posted by Staff at 08:12 PM | Comments (0)
July 04, 2010
Mad Dog 21/21: Microclients: Thin Enough? Rich Enough?
Blog covering Hyperspace and Splashtop clients. Definition of a microclient - It is a mix of hardware and software that turns any computer into a tightly managed Web appliance with a small collection of applications.
Published: June 28, 2010
by Hesh Wiener
Is corporate computing better off when end users have powerful Windows machines or relatively powerless thin clients? The answer is Yes. For the past couple years, computer makers have offered technology that lets users choose what kind of client they see when they boot up, but the vendors did a terrible job of selling this versatile concept. Now, however, things are starting to change. Microclient technology, which turns wide-open PCs into locked-down terminals, works well. One more thing: It is nearly free.
So just what is a microclient? It is a mix of hardware and software that turns any computer into a tightly managed Web appliance with a small collection of applications. So it is pretty secure. It is also quick. On a typical computer (whether laptop or desktop), a microclient can boot up in something like 15 seconds and it runs as lightning fast. The applications built into microclients provide Web browsing, cloud email, instant messaging, Internet telephony, and virtual desktop computing (as defined by Citrix Systems, Microsoft, or VMware). To keep the environment stable, predictable, and secure, the microclients don't let users change applications. Any changes in microclients come from their creators, their computer vendor resellers, and, in the future, very possibly software and services providers who want to add special features that tie microclients to, for instance, ERP applications suites.
Microclients are still new, evolving, and changing shape. For now, as a first approximation, you might want to think of a microclient as an iPad without the Apple Apps Store . . . but with a keyboard and a mouse and a Skype phone.
Currently, computer makers (and at least one supplier of motherboards sold via retail as well as industry channels, Asus) favor microclients based on the Splashtop family of products from DeviceVM. But there is also an alternative called Hyperspace.
Hyperspace was developed by Phoenix Technologies. In June, Hewlett-Packard bought Hyperspace for $12 million, but if has not integrated Hyperspace into its product line. HP still offers Splashtop derivatives on its various products.
Both microclient systems are built on Linux and both are aimed at users of machines that run Windows when they are not in the microclient environment.
Splashtop has setup and configuration software that requires Windows (XP or later). Users make adjustments to their Splashtop setup while it is dormant. There are some configuration options available within Splashtop, but some tasks, such as password management, are done from outside, as if Splashtop is an application, not a complete operating environment. So even though users are running Linux when they boot to Splashtop, the package isn't yet available for Ubuntu or any of the other client-oriented Linux distros. (Once set up via Windows, Splashtop can be run on a machine that multi-boots into Windows, MacOS, Linux and Solaris.)
Hyperspace is also tied to Windows, perhaps even more closely than Splashtop. During installation, Hyperspace depends on Microsoft's partition management software to rope off part of the target computer's boot drive for its use. Like Splashtop, even though it also is written to share a system with Windows, it can probably be set up to work on a multi-boot system.
One distinction between Hyperspace and Splashtop is the use of virtualization in Hyperspace to allow a computer with hardware virtualization support to boot Windows at the same time Hyperspace starts up. The two operating systems can be alive simultaneously and uses can flip back and forth between them. By contrast, a user running Splashtop must shut down that environment to go to Windows. However, by using Windows hibernation along with Splashtop the transition can be accomplished without having to close Windows applications. It is not clear whether this distinction will make much different to ordinary business users, who might well see no point in bouncing between big Windows and small Linux.
For IT managers who just want their end users' machines to come to their servers using secure, consistent thin clients, Splashtop technology is a pretty good place to start. This is particularly true for companies whose end users are mobile. Microclient technology is very widely available for portable computers ranging in power from the lightest 10-inch netbooks up to portable workstations with the heft to run CAD applications, financial simulations or video editing packages. Any current or recent desktop machine can be equipped with microclient technology, with versions of Hyperspace being built from scratch for aftermarket installation. Splashtop, by contrast, really needs some hardware support and it's not clear whether it can run in machines that were built without it in mind; it seems as if it would need some BIOS support that has to be baked in to a computer right from the start.
Rest of Article -- The Four Hundred--Mad Dog 21/21: Microclients: Thin Enough? Rich Enough?
Posted by Staff at 05:31 PM | Comments (0)
January 06, 2010
Self-service trends in 2010
The people at Selfserviceworld.com asked us to write a trends article for 2010 and what will be hot. Here is a roundup of 2010's potential suspects, from my point of view, divided into three market groups — maturing, growth and new drivers. Mentions of PC over IP, POE, green devices, clouds and thin client (imagine that...). Full article on Selfserviceworld.com
Posted by Staff at 06:58 PM | Comments (0)
October 29, 2009
Perspective - The fundamental flaws of thin clients
Very nice piece looking advantages and disadvantages of thin clients and the current best mode to implement them. From Brianmadden.com is Jeroen van de Kamp
by Jeroen van de Kamp
Sorry, I have to get this of my chest. As you might suspect after reading the not-so-subtle title, there is something fundamentally wrong with thin clients.
Let me be specific here: I am NOT talking about good old trusty SBC (Terminal Server/XenApp) or the hot and sexy VDI as a concept. I'm talking about the actual "desktop appliance" or "access point" or "thin client" itself.
This discussion is not new, but now that VDI has made hosted desktops an attractive option again, there's a sort of revival of thin clients in our market space.
Thin clients can be discussed from two angles:
First, there is the typical Citrix user who's been doing SBC for years already and has been pretty successful with it.
Second, there are the organizations venturing into the VDI space who are interested in the power, manageability, and cost advantages of thin clients.
From either perspective (both SBC and VDI), that the only logical choice for the thin clients is not to use typical thin client solutions, whether Linux, Windows CE or Windows XP embedded.
To understand that logic, let's look at the constants we need to deal with in the context of thin-clients:
1. Organizations are required to build a mature and fully automated management infrastructure for PCs and laptops, even when 90% of the clients are “thin.”
The majority of distributed organizations with 1000 desktops or more are often required to support conventional PCs (for rich media editing, 2D/3D design, etc...) and laptops (mobility). This is today’s reality of Enterprise IT. Deploying 100% thin clients is still not feasible in the typical heterogeneous IT environment, even if you're considering all innovations we currently see in remoting protocols from all major vendors.
The problem is that it's not economic to neglect the management aspect of the remaining 10% (or whatever) of devices that are laptops or PCs. You can't ignore patching them just because they're the minority. And manual configuration of PCs and laptops is just too costly in distributed environments, even if you perform only one change every year. So this means that unless you can go 100% thin clients (which I don't think you can), then you have to build a management system for your non-thin clients.
The good news is PC management has matured considerably over the past few years. Building an effective management solution for laptops and PCs is not rocket science anymore.
And by the way, BYOL (Bring your own laptop) doesn't this fix this problem. BYOL is a cool concept, but the majority of organizations still require full management of the desktop/laptop for practical, legal, or security reasons. In most cases BYOL is not an option.
2. When it comes to the support of innovation and new features within remoting protocols such as RDP and ICA (HDX), traditional Windows (XP+) is, by a big margin, the best platform to choose.
All the cool features, especially those which require client-side rendering, are first developed for Windows. Quite often such innovations demand the availability of CODECs, the .NET framework, WPF, the Windows USB or printer driver architecture, and more.
The fact is that Linux or Windows CE as a thin client OS seriously lacks the rich media and user experience optimization support we see being developed first for the Windows client. This is relevant because any user experience- and performance-related innovations are very important to our end users and ultimately, the acceptance of any SBC and VDI solution.
3. A thin client is not a “fire and forget” solution. Thin clients require a mature deployment and management infrastructure.
Don’t believe me? Talk to all the IT admins who've been supporting thin client for years. They'll tell you from experience that a management infrastructure is required to deploy security fixes, client/application upgrades, root certificates, firmware updates, and configuration changes. Those who don’t probably have a very static IT environment.
In comparison to conventional fat clients, the rate of changes and updates on thin clients is considerably lower. However, one single update already justifies the investment in a management infrastructure, as manual configuration of all your thin-clients is extremely expensive.
The reality of thin devices, regardless of protocol, and even hardware embedded solutions (e.g. “PC-over-IP” devices), is that you need to be able to centrally manage and update them. The minute a bug is discovered, a security fix is required or a configuration change is needed--you need a management infrastructure where you can automate such changes.
Posted by Staff at 03:26 PM | Comments (0)
October 02, 2009
Perspective - Larry Ellison on Cloud Computer
Ellison gets it for taking the phrase cloud computing a little too seriously. I can sympathize. Titled -- Another One of These Cloud Computing Rants and You’ve Got Yourself a Stand-Up Routine, Larry. From Digital Daily and John Paczkowski (link below)
by John Paczkowski
Posted on October 2, 2009 at 11:38 AM PT
Print Share
The passing of a year hasn’t much changed Oracle (ORCL) CEO Larry Ellison’s opinion of cloud computing. Remarking on the industry’s sudden fascination with the concept at Oracle OpenWorld last September, Ellison reduced it to a thin sheen of windshield condensation.
“The interesting thing about cloud computing is that we’ve redefined cloud computing to include everything that we already do,” Ellison said. “I can’t think of anything that isn’t cloud computing with all of these announcements….These people who are writing this crap are out there. They are insane. I mean it is the stupidest. Is it ‘Oh, I am going to access data on a server on the Internet.’ That is cloud computing?…Maybe I’m an idiot, but I have no idea what anyone is talking about. What is it? It’s complete gibberish. It’s insane. When is this idiocy going to stop?”
In conversation with former Sun (JAVA) CEO Ed Zander at a Churchill Club event a little over a year later, Ellison expanded on those remarks, suggesting that if the cloud is anything, it’s a cloud of BS.
Cloud’s water vapor….Cloud computing is not only the future of computing, it is the present and the entire past of computing.
…Salesforce.com has been around for a decade. And so has NetSuite…and people are saying, “Well, that’s cloud computing.” Google is cloud computing. Everyone is cloud computing….Everything is in the cloud now….It’s this nonsense.
…But it’s not water vapor. All it is is a computer attached to a network. What are you talking about? I mean, what do you think Google runs on?…Water vapor? It’s databases and operating systems and memory and microprocessors and the Internet!
…And the VCs, I love the VCs. [They ask their start-ups] “Oh…is that cloud?” [And the start-ups go] “Oh! Oh! Microsoft Word! Change ‘Internet’ to ‘cloud’! Mass change. Give it back to these nitwits on Sand Hill Road.”
…What do you mean by “cloud computing”?…All the cloud is is computers on a network.
Our industry is so bizarre. They just change a term and they think they’ve invented technology….You can’t just come up with a [slogan] like “Let’s call that ‘cloud.” [But] it sure beats innovation.”
Posted by Staff at 10:18 PM | Comments (0)
July 16, 2009
Google and Microsoft Announcements Suggest a Thin Client Future
Opinion piece on thin client and latest Google and MS announcements. The major MS announcement being that somehow they are going to make Office available for free via the web. Somehow I think that won't include Exchange but then who knows.
by Chris Howard Jul 15, 2009
On June 14, 2005, I wrote an article proposing over a future filled with thin client technology. Reader response was negative, generally suggesting thin-client would come to nothing and that people wouldn't trust their personal files to the internet. But recent announcements by Google and Microsoft have renewed my expectation of a thin-client future, a future where you won't need a powerful computer, as the applications will be delivered over the web to your browser (like Google Docs) and all the processing is done on the host server.
Also, recently I had an interview with a manufacturing come and was pleasantly surprised to find it ran thin-client technology. And a few weeks before that I eavesdropped a conversation in my local cafe of three executive types, and one of them pulled out a thin-client terminal and told his peers it was the way of the future.
In the enterprise, thin client is still alive and kicking, and still growing.
Google Chrome OS will kick off the push to get thin-client into the home and Microsoft wasted no time announcing it was getting on that train too.
I am still a netbook skeptic but Google's approach undermines my resolve a little. The big problem with netbook marketing of the last 12 months has been its portrayal as a desktop (and/or laptop) computer. This is why demand has grown for larger and larger screens on netbooks. Initially netbooks were 7", now they are as large as 12", which is defeating the whole philosophy of netbooks.
Conversely, the iPhone has seen massive success as an internet device - despite its tiny screen - which suggests people would be quit happy with small screens on their internet device. So a 7" netbook screen was a good size. They just needed a different interface.
Google's entry into netbooks reclaims the netbook as an internet device. Being essentially a thin-client device, it by its nature defines expectations. There can't be any confusion about what it can and can't run. Salesmen won't be able to mislead you into thinking it can replace your laptop or desktop needs.
I still wouldn't get one because I'm exceptionally happy with my iPhone. It does for me most of what I would use a netbook for. And for those tasks the iPhone can't perform, I have the MacBook.
But iPhones are only 20% of the smartphone market, and therefore a small part of the entire mobile phone market. Therefore, many of the non-smartphoners could well take to the Google netbook when looking for an internet device.
And this would be the beginning of the move of the thin-client concept into the consumer market.
It's only been four years since my article but things have changed so much. Online storage has boomed (eg DropBox), Google has entered the web-app space (which again store your docs online), social networking has taken off, and people are trusting the internet more than ever.
That article makes interesting reading now. Mostly I think I was getting it right. However, I did predict Microsoft would be the greatest beneficiary of thin-client. But it seems Google is trying to overtake it. Which might explain Microsoft's announcement "that Office Web applications will be available ... through Windows Live, where more than 400 million consumers will have access to Office Web applications at no cost". Not that I'm suggesting it was an announcement in reaction to Google's Chrome OS.
Apple has also dabbled a bit in a future of thin clients delivering web based apps. It has iWork.com that currently only allows you to share your iWork files online and have others annotate them. It's not hard to imagine Apple working on online version of iWork that allows editing.
It also stuck its toe in the water with the first iPhone, which ran web-based apps. But without any serious apps from Apple itself to support the concept, web-based apps on the iPhone floundered and sunk. Thereafter Apple brought out the iPhone SDK and the app store and things went a little nuts.
Thin-client won't be for everyone immediately. Netbooks will be the beginning as they are ideally suited, being firstly web devices. But as the internet evolves, you'll see more and more desktop functionality migrated to web based apps, until one day you'll realise it's the way you mostly work.
Google and Microsoft's announcements serve to confirm thin-client is coming to a consumer near you.
Posted by Staff at 02:24 PM | Comments (0)
May 13, 2009
Opinion - Linux does have a future on netbooks
Netbooks like the Asus and HP are big sellers right now. These units start around $350 and can end up over $500 and they live off the net. Interesting commentary on Lenova (who is difficult to figure out anyway) and Dell and Linux in general.
Steven J. Vaughan-Nichols
Cyber Cynic
May 12, 2009 - 7:33 P.M.
Linux does have a future on netbooks
I'm puzzled. Desktop Linux, for the first time ever, has at least 1% of the desktop market. Linux probably has considerably more than that. So, why is Lenovo's Worldwide Competitive Analyst Matt Kohut claiming that Linux has no future on netbooks?
Could it be because, as Kohut said, "there were a lot of returns because people didn't know what to do with it." Really? That's odd. Most of the time, you have to ask for Linux by name. Of the big name computer companies only Dell makes it easy to choose Linux and even at Dell, you really should head straight to Dell's Ubuntu Linux site or you can spend a lot of time looking for it.
That reminds me. Dell is now offering the newer Ubuntu 8.10 on its Inspiron 15n laptop. In the past, they were only offering the LTS (Long Term Service) Ubuntu 7.04. Check it out. You see, Dell is taking desktop Linux seriously.
All the other big vendors, including Lenovo, make it almost impossible to find their desktop Linux offerings. You'd almost think they want desktop Linux to fail, and they're only offering it because those darn, pesky customers keep asking for it.
As a matter of fact, Lenovo, even though their flagship ThinkPad laptop line works great with Linux, has been blowing hot and cold about desktop Linux for years. And, last fall, they finally made it impossible for individual users to buy a ThinkPad with Linux.
Kohut also claims that desktop Linux is also harder than Windows to use. Come on. Ever try to get Vista to talk to a NAS (Network Attached Storage) device? You know, the ones that are almost certainly running Linux and Samba under the hood? OK, how about getting Vista to transfer files at faster than a snail's pace? Or, my latest favorite, getting Windows 7 to create a new partition for itself in a fresh installation?
Guess what, in all those cases, and many, many more, you need to get just as down and dirty with Windows registry and the like as you might ever have to do with Linux. Oh, except for that last one. I had to resort to Linux to create a partition that Windows 7 could live with.
On the flip side, I can go weeks, months, without end on both Windows and Linux and never touch the Windows registry or a Linux configuration file. This is 2009. Any modern, pre-installed Linux is just as easy to use as Windows for day-in and day-out jobs.
You know what really ticks me off the most about Lenovo's attitude towards desktop Linux? I know there's a demand for ThinkPads with Linux. Go to any Linux tradeshow. You'll see more ThinkPads than any other kind of Linux-powered PC. Lenovo could have been the poster-child for desktop Linux. But, instead, the real reason why Lenovo is making its ridiculous claims against desktop Linux is that the company wants to be Microsoft's stooge.
Good luck standing out from the crowd with that approach. It's only what 99% of all PC vendors do. Desktop Linux will continue to grow with, or without, Lenovo.
Oh, one last thing, Lenovo? About Linux and netbooks? Keep an eye on those ARM-powered netbooks running Linux and Google making its netbook Android move later this year. I see unpleasant surprises ahead for any PC vendor that's actively campaigned against Linux.
Posted by Staff at 07:16 PM | Comments (0)