It would be nice if enough stones get thrown that everyone's glass houses are broken. Apple has the cash to survive it, and we need real reform with patents to move forward. Let Apple be one of those who start this process of breaking down the current system.
I thought at first that the Apple Maps would be a big deal. I mean, I'd heard about it *everywhere*, so surely it would be a huge step backward.
But you know what? I'm sure it affects somebody, but it works fine for me. Until it becomes a problem for me I don't really care. And Google? I don't trust them as much as I trust Apple, so there you go. Apple just doesn't have that level of personal info on me and Google does. I don't want *any* single company to have so much it's dangerous.
tl;dr? Apple Maps works for me, sorry you're upset but not so sorry I will lose any sleep over it.
Whether it's successful or not is immaterial. The "free" in FOSS has nothing to do with revenue. As otherwise stated, there are successful companies in this market, but it remains to be seen what impact this will have on others. I'm happy to have more choice.
The Ribbon compared to a traditional menu system is much like comparing a McDonald's register to a regular cash register: A significantly simplified interface with pictures / icons instead of textual menus.
Read into that what you will. For some of us, it's a tear-your-hair-out, dumbed-down experience. For someone else it's nirvana because they are clickers, not typers and reading that many words hurts their brain. As someone who's been using office software since it was created -- think GEM desktop and others -- and who has used many many systems, this change is unwelcome and feels wrong. It's slow to use and takes up too much room.
If you want to have the same skills as everyone else, go clickie at the pictures. And now it's much harder for you to use any other system because your "hamburger" button isn't there.
Yes, this is a point I don't see a lot of people making. The help features in OS X apps are pretty nice. I especially like search-as-you-type in help, showing menu items in a separate group; hovering over them results in an animated arrow showing you exactly where that particular menu option is located. Very user-friendly and quick.
My father was a Mason but was very secretive about it. He wanted a Masonic funeral when he died. The Masons showed up and basically unnerved everyone with their weird chanting, hand gestures, and phrasing. I almost left in the middle of the service. Creepy and religious was what I got out of it. The addition of the almost-shame and secrecy was enough to tell me I don't want to be a part of that group.
You still need people to program, to come up with new ideas, to push the technology forward. Or it will eventually collapse on itself as the ones who know retire and die out, leaving the shiny to people who don't understand how it works or how to even repair it.
Anecdotal evidence is anecdotal. You can get infected using Windows simply by visiting Google, seeing ads on mainstream sites etc. It's happened to us during setting up new installs. It's not too hard to do. We no longer search for drivers until the AV is installed; previously drivers came first.
There's an upside and downside to marshalling objects. Some of us have been around since DCOM and COM were prevalent, and the additional security and overhead isn't always worth it. "More powerful" is an oversimplification; it all depends on what you're doing and whether that's the most efficient way of doing it. With objects there's a minimum overhead that you can't code around. Text streams, pointers to objects / inodes / etc all have their uses.
In the Windows world, until recently, text stream support was extremely weak so they pushed some of these other methods instead. It's still catching up, and a large part of that is because Windows developers were encouraged by Microsoft to throw objects around in memory even when other more simple and scalable approaches existed. The API -- the "objects" -- are part of the lock-in of developers to the Windows model, so Microsoft can't totally be blamed for that.
You are right at least in part. The reasons people didn't like it were (in no particular order): Internet capabilities / pages not showing properly; Intranet pages not showing properly or functions not working; SharePoint pages not showing properly or not working or too slow; Can't navigate with the little roller ball; Fingers too big for the little keys; Can't connect to our VPN; No terminal emulation; Lack of business-related apps for monitoring servers, troubleshooting wifi, checking MySQL servers for data etc; Can't print emails to network printers (very handy in meetings); No voice control (hands-free dialing is recommended); Email attachments often can't be opened / viewed; Smaller screen; Lack of accessories; not as easy to keep clean so they can look pretty grungy after a short while (and the symbols on the keys wear off)...
Those are just the ones off the top of my head that I remember. The only thing it did better was sending replies for meeting invites, and I think that's largely resolved with the Exchange upgrade.
As for the email capability of at least iPhones -- I rotate the screen sideways and type away. I don't have any problems with the touch screen, but I guess it's a big deal for some people. If it was a big deal I'd buy a Bluetooth keyboard such as this: http://www.hdaccessory.com/servlet/the-9956/iphone-4s-naztech-sliding/Detail . I'm sure there are cheaper ones too.
Doesn't work that way in our environment. There are very few of us (5 not including our dept head who is a VP) and no room for playing games like that. Because there are only a few of us, the "escalation team" is already on the phone or can be found nearby. Like I said, it's quick and efficient in our environment.
RIM is a zombie company. The vultures are just deciding which pieces they'll devour first.
Stock-wise, they're at 6.61 right now with a 52-week range of 6.56 to 32.48. They're scraping the bottom of their 52-week range, and are 20% of the value from their 52-week high. Trend is flat to downwards. It seems the market doesn't like them.
Technology-wise, they have old, tired products and their biggest asset is the corporate customers who haven't already migrated away.
Marketshare is dropping steadily.
Apps: They don't participate in the apps trend that both Android and iPhone enjoy. Not the best decision, but with such a tiny marketshare they won't get the mindshare from developers who need to target the big guys. So that's a big negative too.
So... what bright future do you see for RIMM? I see none.
Our department works under the premise that if more than a couple of emails go back and forth over a topic, we get on the phone. Especially if it's sensitive or urgent. We've found this to be very efficient. Of course, not all positions or environments are conducive to this.
My fingers tend to be too large for physical phone keyboards. The iPhone keyboard works very well. But 50 emails a day? I think that's more the sales or marketing department, not applications / DB development where I reside.
Anecdotal remark... All members of our department were given or offered BlackBerry Bold 9000-series phones... 3 of us tried to use them but gave them back, 1 didn't accept it to begin with, 1 was the dept head and he's sick of it and waiting for the iPhone 5. Only one person kept their BlackBerry, and that person is the BES admin... and he's consistently frustrated with it.
So, in our world you have:
1 with a BlackBerry Bold 9000 (or newer): Not very happy but can hardly switch since he recommended the BES setup.
1 with a BlackBerry Bold 9000 (or newer), hates it, waiting for the iPhone 5
1 with an iPhone 3GS, waiting for the iPhone 5
1 with an iPhone 3GS, not sure if / when he will upgrade
2 with different Android models
In addition, we have more than 50 salespeople and managers which were offered BlackBerries, and many have chosen either to turn it in or decline the offer with a BYOD instead. We are seeing lots of Androids and iPhones, so far I don't think any of the BYOD's are Blackberries.
What made all the difference for us was upgrading from Exchange 2000 to Exchange 2010. The iPhones and Androids no longer have to use IMAP; the calendaring functions are available now and the sync is very fast. There are fewer and fewer reasons to want to use the BlackBerry anymore for us. Remote wipe is one of them, although that does get murky with BYOD's and our relatively generous policies. With more critical mass on iPhone we will probably implement policies; I've tested adding VPN setup and alpha passcodes along with some other options and although it was a little cumbersome, the end result was easy to implement. Of course Android requires a different setup...
You'd think this would be obvious... but it's good to see someone stand up and take notice. Of course having the source is extremely beneficial, especially if you have the inclination and skills to interact with it (or can pay someone who does possess these qualities). I hope this gets lots of coverage. Maybe with more eyes and more review, people can spend more of their time creating and trying new things and less time recreating the wheel. Open source is an excellent way to help achieve that goal.
Very insightful. Give them the means to help themselves, and assist them along the way. Make the process reward achievement and effort.
The alternative is to destroy hope, drop benefits quickly, punish initiative and keep them chained to the system. With no hope, crime soars and lives are wasted in a socioeconomic limbo.
One method continues the cycle of dependency, and one method gives the person the opportunity to overcome the limitation long-term. Now, there are some people who won't be trained, and there are circumstances where they need the help immediately vs having time to learn and increase knowledge gradually, but giving someone hope and ability is an important part of helping them make a positive contribution to society. I think if we had guided programs whose purpose was to get people back on their feet instead of waiting for the next handout we'd have happier, more productive people who can see a real future.
And of course none of this applies if you truly can't be trained or can't do something because of a true disability or handicap. There will always be a certain percentage who need help because they just can't help themselves. The hard part is sometimes determining which type of person you're dealing with -- judging their ability and intent vs their potentially very applicable limitations.
I'd like to first start by saying that I did not write the AC post that is swearing at you etc.
Thank you.
Even a Windows install is not suitable for many consumers. But your point has merit. Realize this is software for enthusiasts, and you understand the target audience more. An enthusiast will obtain the necessary skills and persevere. Even when your Linux distro is setup correctly, if you lack the skills to maintain it, or the skills to work around issues including interoperability issues caused for various reasons (proprietary software lock-in, licensing, knowledge, lack of functionality or different implementation etc), your OS will be less useful to you in the long run.
Now it's important to understand that many of these reasons are true even for Mac systems, or when you choose to use a tool that is less known than the "standard", whatever that means. An OS X user has to deal with workarounds for some things, and has easier ways to do other things, than a Windows user. The toolsets are not 100% the same. That doesn't mean Macs are bad, or Linux is bad, it means that some OSs are more for enthusiasts and those who enjoy tweaking or who prefer finer grained control than other systems. Some OSs are more for those who enjoy a wider range of COTS software. It's all for different folks.
You're doing the equivalent of replacing the engine or transmission in your car (yes I know that's a HW viewpoint for a SW problem, but it's a system so there you go), which unfortunately does require some expertise. The equivalent of driving the car is using it with the OS that came pre-installed and setup for you.
It's very possible you're right, in my case I found some things were available on MacPorts, some on Fink, and some were absent from both. Also as you report sometimes it was available on both, but my experience was that it was sometimes a different version which made the whole process more complicated. Installing from source was as often a fail as a success. Of course YMMV and all that.
Wow. Anecdotal experience is anecdotal, so please understand I'm not negating your experience or telling you you're doing it wrong. I've not run into these hardware problems so I'm little help there. Every piece of hardware -- from a DL320 to BL460CG6 to a little bitty HP 2510p sitting on a corner of my desk. They all work fine. Now that may be because HP generally has excellent support for Linux, or maybe my luck is very good. The worst I've encountered is needing to install a Linux driver for RHEL3 with an add-on FC card; RHEL 5.3 and up has support built-in. So in this particular case, it seems the make/model you're using has some major compatibility issues. Which make/model is it? I doubt I can help but I am curious.
SMB, as in SAMBA issues: Are you talking Samba3? That's pretty new and IMHO primarily intended for 2008+ domains; the rest of us are still using the older Samba 2 lineage. Depends on your needs which you need to use, and no they both can't be installed and running. You have to choose. It's not ideal but it is a major change. Unfortunately SAMBA is a rather large subject because of all the components and the particular issue you're experiencing will need possibly a great level of detail to be resolved. Personally, I have a checklist and I use that, although once you understand the settings and their many locations it makes it much easier to troubleshoot. No insult to Jeremy and the team, but simple is not the word I'd use to describe SAMBA.
It wasn't only XCode that was giving me crashes and problems, the system had become unstable. Uninstalling XCode at that point was the least of my problems. Sorry your butt hurts so much.
Slashdot Mirror
It would be nice if enough stones get thrown that everyone's glass houses are broken. Apple has the cash to survive it, and we need real reform with patents to move forward. Let Apple be one of those who start this process of breaking down the current system.
I thought at first that the Apple Maps would be a big deal. I mean, I'd heard about it *everywhere*, so surely it would be a huge step backward.
But you know what? I'm sure it affects somebody, but it works fine for me. Until it becomes a problem for me I don't really care. And Google? I don't trust them as much as I trust Apple, so there you go. Apple just doesn't have that level of personal info on me and Google does. I don't want *any* single company to have so much it's dangerous.
tl;dr? Apple Maps works for me, sorry you're upset but not so sorry I will lose any sleep over it.
Whether it's successful or not is immaterial. The "free" in FOSS has nothing to do with revenue. As otherwise stated, there are successful companies in this market, but it remains to be seen what impact this will have on others. I'm happy to have more choice.
The "free" to which you refer has nothing to do with price. Think of "free" as in "freedom".
The Ribbon compared to a traditional menu system is much like comparing a McDonald's register to a regular cash register: A significantly simplified interface with pictures / icons instead of textual menus.
Read into that what you will. For some of us, it's a tear-your-hair-out, dumbed-down experience. For someone else it's nirvana because they are clickers, not typers and reading that many words hurts their brain. As someone who's been using office software since it was created -- think GEM desktop and others -- and who has used many many systems, this change is unwelcome and feels wrong. It's slow to use and takes up too much room.
If you want to have the same skills as everyone else, go clickie at the pictures. And now it's much harder for you to use any other system because your "hamburger" button isn't there.
Yes, this is a point I don't see a lot of people making. The help features in OS X apps are pretty nice. I especially like search-as-you-type in help, showing menu items in a separate group; hovering over them results in an animated arrow showing you exactly where that particular menu option is located. Very user-friendly and quick.
My father was a Mason but was very secretive about it. He wanted a Masonic funeral when he died. The Masons showed up and basically unnerved everyone with their weird chanting, hand gestures, and phrasing. I almost left in the middle of the service. Creepy and religious was what I got out of it. The addition of the almost-shame and secrecy was enough to tell me I don't want to be a part of that group.
You still need people to program, to come up with new ideas, to push the technology forward. Or it will eventually collapse on itself as the ones who know retire and die out, leaving the shiny to people who don't understand how it works or how to even repair it.
Anecdotal evidence is anecdotal. You can get infected using Windows simply by visiting Google, seeing ads on mainstream sites etc. It's happened to us during setting up new installs. It's not too hard to do. We no longer search for drivers until the AV is installed; previously drivers came first.
There's an upside and downside to marshalling objects. Some of us have been around since DCOM and COM were prevalent, and the additional security and overhead isn't always worth it. "More powerful" is an oversimplification; it all depends on what you're doing and whether that's the most efficient way of doing it. With objects there's a minimum overhead that you can't code around. Text streams, pointers to objects / inodes / etc all have their uses.
In the Windows world, until recently, text stream support was extremely weak so they pushed some of these other methods instead. It's still catching up, and a large part of that is because Windows developers were encouraged by Microsoft to throw objects around in memory even when other more simple and scalable approaches existed. The API -- the "objects" -- are part of the lock-in of developers to the Windows model, so Microsoft can't totally be blamed for that.
You are right at least in part. The reasons people didn't like it were (in no particular order): Internet capabilities / pages not showing properly; Intranet pages not showing properly or functions not working; SharePoint pages not showing properly or not working or too slow; Can't navigate with the little roller ball; Fingers too big for the little keys; Can't connect to our VPN; No terminal emulation; Lack of business-related apps for monitoring servers, troubleshooting wifi, checking MySQL servers for data etc; Can't print emails to network printers (very handy in meetings); No voice control (hands-free dialing is recommended); Email attachments often can't be opened / viewed; Smaller screen; Lack of accessories; not as easy to keep clean so they can look pretty grungy after a short while (and the symbols on the keys wear off)...
Those are just the ones off the top of my head that I remember. The only thing it did better was sending replies for meeting invites, and I think that's largely resolved with the Exchange upgrade.
As for the email capability of at least iPhones -- I rotate the screen sideways and type away. I don't have any problems with the touch screen, but I guess it's a big deal for some people. If it was a big deal I'd buy a Bluetooth keyboard such as this: http://www.hdaccessory.com/servlet/the-9956/iphone-4s-naztech-sliding/Detail . I'm sure there are cheaper ones too.
Doesn't work that way in our environment. There are very few of us (5 not including our dept head who is a VP) and no room for playing games like that. Because there are only a few of us, the "escalation team" is already on the phone or can be found nearby. Like I said, it's quick and efficient in our environment.
So... what bright future do you see for RIMM? I see none.
Our department works under the premise that if more than a couple of emails go back and forth over a topic, we get on the phone. Especially if it's sensitive or urgent. We've found this to be very efficient. Of course, not all positions or environments are conducive to this.
My fingers tend to be too large for physical phone keyboards. The iPhone keyboard works very well. But 50 emails a day? I think that's more the sales or marketing department, not applications / DB development where I reside.
All members of our department were given or offered BlackBerry Bold 9000-series phones... 3 of us tried to use them but gave them back, 1 didn't accept it to begin with, 1 was the dept head and he's sick of it and waiting for the iPhone 5. Only one person kept their BlackBerry, and that person is the BES admin... and he's consistently frustrated with it.
So, in our world you have:
In addition, we have more than 50 salespeople and managers which were offered BlackBerries, and many have chosen either to turn it in or decline the offer with a BYOD instead. We are seeing lots of Androids and iPhones, so far I don't think any of the BYOD's are Blackberries.
What made all the difference for us was upgrading from Exchange 2000 to Exchange 2010. The iPhones and Androids no longer have to use IMAP; the calendaring functions are available now and the sync is very fast. There are fewer and fewer reasons to want to use the BlackBerry anymore for us. Remote wipe is one of them, although that does get murky with BYOD's and our relatively generous policies. With more critical mass on iPhone we will probably implement policies; I've tested adding VPN setup and alpha passcodes along with some other options and although it was a little cumbersome, the end result was easy to implement. Of course Android requires a different setup...
You'd think this would be obvious... but it's good to see someone stand up and take notice. Of course having the source is extremely beneficial, especially if you have the inclination and skills to interact with it (or can pay someone who does possess these qualities). I hope this gets lots of coverage. Maybe with more eyes and more review, people can spend more of their time creating and trying new things and less time recreating the wheel. Open source is an excellent way to help achieve that goal.
Very insightful. Give them the means to help themselves, and assist them along the way. Make the process reward achievement and effort.
The alternative is to destroy hope, drop benefits quickly, punish initiative and keep them chained to the system. With no hope, crime soars and lives are wasted in a socioeconomic limbo.
One method continues the cycle of dependency, and one method gives the person the opportunity to overcome the limitation long-term. Now, there are some people who won't be trained, and there are circumstances where they need the help immediately vs having time to learn and increase knowledge gradually, but giving someone hope and ability is an important part of helping them make a positive contribution to society. I think if we had guided programs whose purpose was to get people back on their feet instead of waiting for the next handout we'd have happier, more productive people who can see a real future.
And of course none of this applies if you truly can't be trained or can't do something because of a true disability or handicap. There will always be a certain percentage who need help because they just can't help themselves. The hard part is sometimes determining which type of person you're dealing with -- judging their ability and intent vs their potentially very applicable limitations.
I'd like to first start by saying that I did not write the AC post that is swearing at you etc.
Thank you.
Even a Windows install is not suitable for many consumers. But your point has merit. Realize this is software for enthusiasts, and you understand the target audience more. An enthusiast will obtain the necessary skills and persevere. Even when your Linux distro is setup correctly, if you lack the skills to maintain it, or the skills to work around issues including interoperability issues caused for various reasons (proprietary software lock-in, licensing, knowledge, lack of functionality or different implementation etc), your OS will be less useful to you in the long run.
Now it's important to understand that many of these reasons are true even for Mac systems, or when you choose to use a tool that is less known than the "standard", whatever that means. An OS X user has to deal with workarounds for some things, and has easier ways to do other things, than a Windows user. The toolsets are not 100% the same. That doesn't mean Macs are bad, or Linux is bad, it means that some OSs are more for enthusiasts and those who enjoy tweaking or who prefer finer grained control than other systems. Some OSs are more for those who enjoy a wider range of COTS software. It's all for different folks.
You're doing the equivalent of replacing the engine or transmission in your car (yes I know that's a HW viewpoint for a SW problem, but it's a system so there you go), which unfortunately does require some expertise. The equivalent of driving the car is using it with the OS that came pre-installed and setup for you.
It's very possible you're right, in my case I found some things were available on MacPorts, some on Fink, and some were absent from both. Also as you report sometimes it was available on both, but my experience was that it was sometimes a different version which made the whole process more complicated. Installing from source was as often a fail as a success. Of course YMMV and all that.
Wow. Anecdotal experience is anecdotal, so please understand I'm not negating your experience or telling you you're doing it wrong. I've not run into these hardware problems so I'm little help there. Every piece of hardware -- from a DL320 to BL460CG6 to a little bitty HP 2510p sitting on a corner of my desk. They all work fine. Now that may be because HP generally has excellent support for Linux, or maybe my luck is very good. The worst I've encountered is needing to install a Linux driver for RHEL3 with an add-on FC card; RHEL 5.3 and up has support built-in. So in this particular case, it seems the make/model you're using has some major compatibility issues. Which make/model is it? I doubt I can help but I am curious.
SMB, as in SAMBA issues: Are you talking Samba3? That's pretty new and IMHO primarily intended for 2008+ domains; the rest of us are still using the older Samba 2 lineage. Depends on your needs which you need to use, and no they both can't be installed and running. You have to choose. It's not ideal but it is a major change. Unfortunately SAMBA is a rather large subject because of all the components and the particular issue you're experiencing will need possibly a great level of detail to be resolved. Personally, I have a checklist and I use that, although once you understand the settings and their many locations it makes it much easier to troubleshoot. No insult to Jeremy and the team, but simple is not the word I'd use to describe SAMBA.
It wasn't only XCode that was giving me crashes and problems, the system had become unstable. Uninstalling XCode at that point was the least of my problems. Sorry your butt hurts so much.
Perhaps you should look up the word yourself; it's quite obvious you have much learning to do and the experience might prove beneficial.