Nokia would have to fall on really hard times before selling out to Microsoft
and they don't need to. The E7 phone can work with Microsoft Office documents better than Word does, and you can even create powerpoints on the thing (no doubt to send to your PA with instructions to 'just tidy up the edges', but if you're targeting sales account managers and the like, this is the kind of thing that makes them sit up).
So why would they 'downgrade' themselves to sell out to MS. In the mobile world, they *are* the Microsoft (in market share, not in bullying uselessness). Microsoft would do well to sell out to Nokia and licence Meego or Symbian.:)
Dalvik on the other hand started (and has remained so) with support to a subset of Java. Why? Because it caters to the masses of J2ME developers already in existence; another strategic move, and a better response to iPhone's reliance on Objective-C.
This confuses me, see if they wanted a strategic language for Android that gained a absolute heap of developers, J2ME wasn't it. It was C/C++ as used by Symbian. Add some symbian->Android conversion tools, libraries or frameworks and you'd have had a massive amount of development loveliness. To point this out, on many Android forums one cry I used to read a lot was "how can I port my existing C++ code to Android, why did they make it all Java".
I think Google went Java because it was their 2nd (or is it 1st) choice language, and the guys doing the phone API happened to want to make it Java, probably no other reason than that. Now they should start improving the Qt abilities and getting a richer software ecosystem going instead of trying to lock it all down to Dalvik-code only. (ie make it easier and more supported, to write in C/C++ and maybe Python too)
The thing about Symbian is it really doesn't seem to be going anywhere; in the other sense
You could say the same thing about Windows. Saying it still won't change the world for quite a few years, don't be fooled into thinking the entire world now wants Android phones (good though they are). Incremental updates and a vast target market will keep them relevant for a long time.
Where I work we use a lot of Apple Java and now we have absolutely 0 idea on whether we should invest any more in Apple at all
Its interesting that you didn't say "whether we should invest any more in Java".
Apple has plans that I'm sure involve them making lots of money and world domination. Just like Oracle, only Oracle wants you to pay licence fees for using Java, and Apple wants you to pay licence fees to write apps. Hmm, perhaps you should port it all to.NET?:)
So why would the eclipse maintainers switch to a version of Java that stops people running on the Mac?
because one day, maybe 5 years in the future, they will want the 'new cool' features the updated Java offers. Oracle doesn't have to give a shit about Mac, they make money selling horrible Java apps to enterprise customers who buy thousands of seats worth to run on their horrible windows desktops. Mac, really doesn't feature in 0.1% of Larry's sales.
I do agree there - IPv6 should have retained the IPv4 addressing we're used to. Migration would have been simply putting in a new router, no hosts/servers/apps would have needed to be modified. And eventually all those old IPv4 addresses would have gone away as v6 DHCP servers were rolled out. (except to those old servers that needed a bit of backward-compatibility until replacement in 20 years).
really? what happens when a packet goes past a NAT router, into a network that's behind another NAT router? I guess you can store every packet that zips past the router in its own memory, but you couldn't store it in the packet itself. Not unless you had 2 optional fields. And then what happens when.. you get the idea.
If we're going to roll out updates to every NAT device and host, we might as well roll out IPv6, its already partially rolled-out. Job done!
VMware Workstation was the first to support 3D graphics in virtualized environments and is now the first to support Windows Aero in Windows Vista and Windows 7 virtual machines. Run even more 3D applications with support for DirectX 9.0c Shader Model 3 and OpenGL 2.13D graphics in Windows virtual machines.
A) You're not familiar with this technology. This is probably not the best way to get indoctrinated with VM's.
Quite the opposite. its how I always learned the ins, outs and plain 'don't do this again-ness' of various computer systems. The alternative is to read the documentation and find out what the manufacturer wanted you to learn.
Still, IO and Gfx performance is not something a VM is good at. Did I mention I also learn a lot by reading slashdot?:)
true, but if an Android app is written in Java, porting it to "Apple java" isn't nearly as difficult as porting it to Obj-C. As a result, devs will write Android code then port it over as quickly (and cheaply) as possible resulting in lesser quality apps for Apple.
At least, that's how Apple sees it (I guess). The answer is to write your apps in as neutral a language as possible (C/C++ with Qt?) and try to reuse as much as possible. Here's the chance for Android to give such languages first-class support so the android app will become the one written first, and then mangled^H^H^H ported to Macs.
Oracle will no doubt release a JVM for Mac, but it might take a while to get it out. Even then, it'll be geared to run Java apps without all the Mac-specific bits, so I can't see it gaining much traction beyond being available to run the atrocious 'enterprise' line-of-business apps.
Faced with this problem, typical core developers usually come up with overkill rules, such as very detailed naming conventions and flowerbox documentation requirements, and quickly you end up with reams of paper wasted and no improvement. Then someone brings up an idea of using a common library, and from there it's a sure path to Yet Another Framework.
kinda disagree, as the above description is a Dev manager rols at my current place. Perhaps its terminology and experience we're talkign about here. I know some good architects, but I also know others who love to create over-engineered 'astronautic' schemes that have no place in reality (like above). One architecture group at my current place has come up with a scheme that, last time I looked, required 6 dlls for each web service (yes, it had to be SoA, or is that SaaS they're doing? Oh yes, its the PoS system).
I think it doesn't matter what you call them, some 'senior' chaps don't do real-world code anymore, these are the people we're talking about. They often have titles like 'architect', sometimes with 'chief' in there too. People who look to microsoft's patterns and practices group and think the crud they come up with is good.
CR/LF is the proper way (unfortunately), LF moves down a line, CR returns the carriage back to the start. It makes sense if you model your computerised stuff on electromechanical devices. it also makes sense when you realise the ctrl-l is 'move down' control key (like ctrl-h is move left).
The fact that 1 line-end character is easier to manipulate obviously didn't factor in the design though, progress sometimes means breaking with the past:)
ah you miss the point slightly - the time it took to gain the experience on Windows needs to be factored in just as much as the time taken to learn the Linux stuff, otherwise you're not being fair in comparing the two.
Anyone who is experienced in using Windows took time to get that, it wasn't free.
However the time and effort that I have spent installing Samba 4 would have cost this organisation a fair bit more than the cost of a Windows Server 2008 Standard license
Does trhat count the time it took you to get trained in Windows Server 2008, Active Directory and all the other gubbins? IIRC there was a fair learning curve going from domains to AD. (and we'll ignore the cost of the CALs)
This annoys me a little about Linux migrations, people say how much more it costs based on the fact that they already know Windows, then compare that to the time taken to not only implement but also learn the Linux equivalent. Now you've done it once, you should be able to put in another Samba4 system without any fuss, surely?
and you can, of course, supply your config experience to the community - or to your own, ad-laden, blog. Might as well earn a little from getting people to come read what you did.
Good post. I do the same, but I figured that was just me not havign enough experience of using the ribbon. Fortunately, I managed to just figure out where the stuff I use often was before the company upgraded me to Office 2010.
One thing of note in 2010, the orb 'menu button' is now a.... coloured 'File' tab. It appears the adage "nothing sensible ever goes out of fashion" is still true.
I'm not especially keen on that Java-alike stuff even though I work with it, but either way, I'd rather code like its 2012. That won't involve Silverlight, now will it.
and yes, Sharepoint v Drupal - seriously. There's a lot of good software out there if you care to take a look, it can be difficult to get past the 'less mature' stuff, but the good OSS stuff is really good, better than the commercial stuff.
Strangely, considering we're a Microsoft shop where MIS people choose Microsoft becuase it stops them having to make decisions or think (something they're not too good at anyway), we have a Drupal site for our user community.
Its quite good, basically its another CMS, so pretty much everything sharepoint does, but less oriented on being a web-based network fileshare, without folders. Its used by a couple of high-profile websites, the Economist and the White House for example.
Apparently you can connect a Drupal site to Sharepoint "back end" using its CMIS module, and there are several file management modules in addition to the basic functionality. Collaboration doesn't even need to be discussed as its what the thing was designed to do:)
The site itself has fairly good documentation, and if you wantg really good example - check out Apache or Subversion, both very comprehensively documented.
are you saying Apple's flying too near the sun and is ready to fall, or that Microsoft has enjoyed the fat years for so long their bubble's burst and they're heading downwards?
true, but that doesn't mean its good - eg we have sharepoint, can't find one of the documents on there because the indexing/search/layout is poor, and we have word documents embedded into infopath documents stuck onto sharepoint.
I've seen other departments sharepoint sites and they're not much better than ours. Sharepoint needs to be killed by society for our own good.
I think you want a Nokia E7. They say you can create powerpoints on it. Not sure about comfortably, but you can plug it into a TV via HDMI and bluetooth keyboard, so I guess that counts.
The final device that was introduced during the keynote was the E7, a smartphone with a four-inch touchscreen and a slide-out qwerty keyboard. Vanjoki describes it as a spiritual successor of the original Nokia communicator and the best business smartphone that the company has ever produced. The E7 looks a lot like a keyboard-enhanced version of the N8, but there are some key software differences that also differentiate it from its media-centric cousin. For example, the E7 will ship with full support for reading, creating, and editing Microsoft Office documents. Vanjoki says that it's even possible to create PowerPoint presentations on the phone itself
they've also seen their share price wibble along going nowhere while Apple's streaks upwards. You may not think that matters but it does, a lot. If this doesn't show some promise for future MS growth, you can expect a little shareholder revolt, Ballmer being kicked out and maybe a ton of layoffs and re-organisation in the name of shareholder value. You will probably also see some divisions spun off to stand on their own feet (yep, online and entertainment divisions.... you'll get your crutch made of cash kicked away) and then we'll see if MS is still the powerhouse, or if other companies suddenly find themselve with a lot of attention from ex-Microsoft shops.
Let me put it this way - would you implement a Silverlight app today, when tomorrow it could be a dead technology replaced by Flash.Net? Its the same with businesses looking to implement their next set of apps, would they buy MS products if it looked like they were stumbling, or would they at least look at alternatives?
Sharepoint? You've never used it - Drupal is a lot better from almost every viewpoint.
Silverlight? So good its only got a 60% market share (accrding to Microsoft) and they're looking at partnering/buying Adobe for Flash.
Expression suite isn't so bad, but its a bit like FrontPage for the hackery it puts in your designs. Take a look at all the expression dlls the generated code references.
C# 4.0 - dynamic types (and crap like extension methods) is weakening the language. Now, you can slap code together like a scripting language, and most code will have just the same amount of quality to it as a lot of script has.
Slashdot Mirror
Nokia would have to fall on really hard times before selling out to Microsoft
and they don't need to. The E7 phone can work with Microsoft Office documents better than Word does, and you can even create powerpoints on the thing (no doubt to send to your PA with instructions to 'just tidy up the edges', but if you're targeting sales account managers and the like, this is the kind of thing that makes them sit up).
So why would they 'downgrade' themselves to sell out to MS. In the mobile world, they *are* the Microsoft (in market share, not in bullying uselessness). Microsoft would do well to sell out to Nokia and licence Meego or Symbian. :)
Dalvik on the other hand started (and has remained so) with support to a subset of Java. Why? Because it caters to the masses of J2ME developers already in existence; another strategic move, and a better response to iPhone's reliance on Objective-C.
This confuses me, see if they wanted a strategic language for Android that gained a absolute heap of developers, J2ME wasn't it. It was C/C++ as used by Symbian. Add some symbian->Android conversion tools, libraries or frameworks and you'd have had a massive amount of development loveliness. To point this out, on many Android forums one cry I used to read a lot was "how can I port my existing C++ code to Android, why did they make it all Java".
I think Google went Java because it was their 2nd (or is it 1st) choice language, and the guys doing the phone API happened to want to make it Java, probably no other reason than that. Now they should start improving the Qt abilities and getting a richer software ecosystem going instead of trying to lock it all down to Dalvik-code only. (ie make it easier and more supported, to write in C/C++ and maybe Python too)
The thing about Symbian is it really doesn't seem to be going anywhere; in the other sense
You could say the same thing about Windows. Saying it still won't change the world for quite a few years, don't be fooled into thinking the entire world now wants Android phones (good though they are). Incremental updates and a vast target market will keep them relevant for a long time.
Where I work we use a lot of Apple Java and now we have absolutely 0 idea on whether we should invest any more in Apple at all
Its interesting that you didn't say "whether we should invest any more in Java".
Apple has plans that I'm sure involve them making lots of money and world domination. Just like Oracle, only Oracle wants you to pay licence fees for using Java, and Apple wants you to pay licence fees to write apps. Hmm, perhaps you should port it all to .NET? :)
So why would the eclipse maintainers switch to a version of Java that stops people running on the Mac?
because one day, maybe 5 years in the future, they will want the 'new cool' features the updated Java offers. Oracle doesn't have to give a shit about Mac, they make money selling horrible Java apps to enterprise customers who buy thousands of seats worth to run on their horrible windows desktops. Mac, really doesn't feature in 0.1% of Larry's sales.
I do agree there - IPv6 should have retained the IPv4 addressing we're used to. Migration would have been simply putting in a new router, no hosts/servers/apps would have needed to be modified. And eventually all those old IPv4 addresses would have gone away as v6 DHCP servers were rolled out. (except to those old servers that needed a bit of backward-compatibility until replacement in 20 years).
Ho hum, maybe we need IPv7 instead.
really? what happens when a packet goes past a NAT router, into a network that's behind another NAT router? I guess you can store every packet that zips past the router in its own memory, but you couldn't store it in the packet itself. Not unless you had 2 optional fields. And then what happens when.. you get the idea.
If we're going to roll out updates to every NAT device and host, we might as well roll out IPv6, its already partially rolled-out. Job done!
no... 'cos then I wouldn't see any of my own posts. ;)
Its true, but only with the latest VMWare Workstation (7.1), which is not one of their freebie offerings. Its not too expensive though.
http://www.vmware.com/products/workstation/new.html
VMware Workstation was the first to support 3D graphics in virtualized environments and is now the first to support Windows Aero in Windows Vista and Windows 7 virtual machines. Run even more 3D applications with support for DirectX 9.0c Shader Model 3 and OpenGL 2.13D graphics in Windows virtual machines.
A) You're not familiar with this technology. This is probably not the best way to get indoctrinated with VM's.
Quite the opposite. its how I always learned the ins, outs and plain 'don't do this again-ness' of various computer systems. The alternative is to read the documentation and find out what the manufacturer wanted you to learn.
Still, IO and Gfx performance is not something a VM is good at. Did I mention I also learn a lot by reading slashdot? :)
or just copying features that have been around since Windows 2000?
Best watchit doesn't vioate some patent :)
true, but if an Android app is written in Java, porting it to "Apple java" isn't nearly as difficult as porting it to Obj-C. As a result, devs will write Android code then port it over as quickly (and cheaply) as possible resulting in lesser quality apps for Apple.
At least, that's how Apple sees it (I guess). The answer is to write your apps in as neutral a language as possible (C/C++ with Qt?) and try to reuse as much as possible. Here's the chance for Android to give such languages first-class support so the android app will become the one written first, and then mangled^H^H^H ported to Macs.
Oracle will no doubt release a JVM for Mac, but it might take a while to get it out. Even then, it'll be geared to run Java apps without all the Mac-specific bits, so I can't see it gaining much traction beyond being available to run the atrocious 'enterprise' line-of-business apps.
Faced with this problem, typical core developers usually come up with overkill rules, such as very detailed naming conventions and flowerbox documentation requirements, and quickly you end up with reams of paper wasted and no improvement. Then someone brings up an idea of using a common library, and from there it's a sure path to Yet Another Framework.
kinda disagree, as the above description is a Dev manager rols at my current place. Perhaps its terminology and experience we're talkign about here. I know some good architects, but I also know others who love to create over-engineered 'astronautic' schemes that have no place in reality (like above). One architecture group at my current place has come up with a scheme that, last time I looked, required 6 dlls for each web service (yes, it had to be SoA, or is that SaaS they're doing? Oh yes, its the PoS system).
I think it doesn't matter what you call them, some 'senior' chaps don't do real-world code anymore, these are the people we're talking about. They often have titles like 'architect', sometimes with 'chief' in there too. People who look to microsoft's patterns and practices group and think the crud they come up with is good.
CR/LF is the proper way (unfortunately), LF moves down a line, CR returns the carriage back to the start. It makes sense if you model your computerised stuff on electromechanical devices. it also makes sense when you realise the ctrl-l is 'move down' control key (like ctrl-h is move left).
The fact that 1 line-end character is easier to manipulate obviously didn't factor in the design though, progress sometimes means breaking with the past :)
ah you miss the point slightly - the time it took to gain the experience on Windows needs to be factored in just as much as the time taken to learn the Linux stuff, otherwise you're not being fair in comparing the two.
Anyone who is experienced in using Windows took time to get that, it wasn't free.
However the time and effort that I have spent installing Samba 4 would have cost this organisation a fair bit more than the cost of a Windows Server 2008 Standard license
Does trhat count the time it took you to get trained in Windows Server 2008, Active Directory and all the other gubbins? IIRC there was a fair learning curve going from domains to AD. (and we'll ignore the cost of the CALs)
This annoys me a little about Linux migrations, people say how much more it costs based on the fact that they already know Windows, then compare that to the time taken to not only implement but also learn the Linux equivalent. Now you've done it once, you should be able to put in another Samba4 system without any fuss, surely?
and you can, of course, supply your config experience to the community - or to your own, ad-laden, blog. Might as well earn a little from getting people to come read what you did.
There is some awareness going on. For example, the Avon and Somerset Constabulary website has 'inappropriate' 999 calls.
Check out the man who wants the cops to do something about his wife who has gone out without making his sandwiches.
Good post. I do the same, but I figured that was just me not havign enough experience of using the ribbon. Fortunately, I managed to just figure out where the stuff I use often was before the company upgraded me to Office 2010.
One thing of note in 2010, the orb 'menu button' is now a .... coloured 'File' tab. It appears the adage "nothing sensible ever goes out of fashion" is still true.
lolz? yes, quite....
I'm not especially keen on that Java-alike stuff even though I work with it, but either way, I'd rather code like its 2012. That won't involve Silverlight, now will it.
and yes, Sharepoint v Drupal - seriously. There's a lot of good software out there if you care to take a look, it can be difficult to get past the 'less mature' stuff, but the good OSS stuff is really good, better than the commercial stuff.
Strangely, considering we're a Microsoft shop where MIS people choose Microsoft becuase it stops them having to make decisions or think (something they're not too good at anyway), we have a Drupal site for our user community.
http://drupal.org/
Its quite good, basically its another CMS, so pretty much everything sharepoint does, but less oriented on being a web-based network fileshare, without folders. Its used by a couple of high-profile websites, the Economist and the White House for example.
Apparently you can connect a Drupal site to Sharepoint "back end" using its CMIS module, and there are several file management modules in addition to the basic functionality. Collaboration doesn't even need to be discussed as its what the thing was designed to do :)
The site itself has fairly good documentation, and if you wantg really good example - check out Apache or Subversion, both very comprehensively documented.
are you saying Apple's flying too near the sun and is ready to fall, or that Microsoft has enjoyed the fat years for so long their bubble's burst and they're heading downwards?
true, but that doesn't mean its good - eg we have sharepoint, can't find one of the documents on there because the indexing/search/layout is poor, and we have word documents embedded into infopath documents stuck onto sharepoint.
I've seen other departments sharepoint sites and they're not much better than ours. Sharepoint needs to be killed by society for our own good.
I think you want a Nokia E7. They say you can create powerpoints on it. Not sure about comfortably, but you can plug it into a TV via HDMI and bluetooth keyboard, so I guess that counts.
The final device that was introduced during the keynote was the E7, a smartphone with a four-inch touchscreen and a slide-out qwerty keyboard. Vanjoki describes it as a spiritual successor of the original Nokia communicator and the best business smartphone that the company has ever produced. The E7 looks a lot like a keyboard-enhanced version of the N8, but there are some key software differences that also differentiate it from its media-centric cousin. For example, the E7 will ship with full support for reading, creating, and editing Microsoft Office documents. Vanjoki says that it's even possible to create PowerPoint presentations on the phone itself
they've also seen their share price wibble along going nowhere while Apple's streaks upwards. You may not think that matters but it does, a lot. If this doesn't show some promise for future MS growth, you can expect a little shareholder revolt, Ballmer being kicked out and maybe a ton of layoffs and re-organisation in the name of shareholder value. You will probably also see some divisions spun off to stand on their own feet (yep, online and entertainment divisions.... you'll get your crutch made of cash kicked away) and then we'll see if MS is still the powerhouse, or if other companies suddenly find themselve with a lot of attention from ex-Microsoft shops.
Let me put it this way - would you implement a Silverlight app today, when tomorrow it could be a dead technology replaced by Flash.Net? Its the same with businesses looking to implement their next set of apps, would they buy MS products if it looked like they were stumbling, or would they at least look at alternatives?
Sharepoint? You've never used it - Drupal is a lot better from almost every viewpoint.
Silverlight? So good its only got a 60% market share (accrding to Microsoft) and they're looking at partnering/buying Adobe for Flash.
Expression suite isn't so bad, but its a bit like FrontPage for the hackery it puts in your designs. Take a look at all the expression dlls the generated code references.
C# 4.0 - dynamic types (and crap like extension methods) is weakening the language. Now, you can slap code together like a scripting language, and most code will have just the same amount of quality to it as a lot of script has.