Secondly, all more or less recent versions of IBM i OS,i5/OS,OS/400 (V4, V5, V6) can talk to a vt100 telnet client. The default Windows telnet client works just fine - but the F keys don't work, so the use is pretty limited on an i.
IBM still ships their IBM i systems insecure as hell, leaving most customer setups in the same shape.
Example: Telnet is enabled by default, but telnet/ssl is not. Everyone uses SSL. I've seen many people directly exposing Port 23 to the Net, cause the i is secure.
All our POS products are based on touchscreen technology. And they work very well.
Of course, on modern POS you don't type in numbers as you used to do in yesteryear - that's why we have barcodes and more recently RFID.
Touchscreens allow you to offer a fully dynamic user interface that adopts to the current situation. It work wells, as long as you do not need to do any sort of more-than-occasional data entry.
I don't buy this argument, neither from Mozilla nor Microsoft.
Corporations will use some sort of managed upgrade procedure anyway, as users do not have permissions to install updates.
On the IE7 side, this can be managed using WSUS, SCE, SCCM. On the Firefox side, i guess it would have to done by using a software deployment solution like SCE or SCCM.
I have no idea - never looked into Firefox deployment options.
We have multiple customers - of these, only one or two have unexpected downtimes per year. That means that there is an awful lot of customers without any downtime.
But what about annoying behaviour, bugs, changes, etc.?
If you're self hosted, you'll have people looking into solving the problem and actually trying to do so. In the end, it might not happen because the cost may to high or because of something else.
When you call Google you'll reach some guy in india that doesn't give a shit about your problem.
What about your planned downtime? If you're running Windows, you're rebooting to install patches on a regular basis or you're running unpatched systems. What about software installs?
A non-issue for these customers, as they do not run 24/7 businesses. Larger stuff can be done over the weekends, smaller stuff after everyone left.
For a 24/7 enterprise with distributed locations etc. things might be different.
But then again: This is "just" e-mail. While becoming more and more critical even in the smallest of businesses, there are worse things that could crash. For instance, your production control application that controls machines (if you are a producing company), or your ERP software if you're mainly selling oriented.
There also might be some companies that depend on E-Mail as their main business application, but these should then invest into providing highly reliable internal E-Mail. That costs more than 50$ / year / account, though.
You can win the lottery too, if you are lucky. How many people win the lottery though?
The chance of having a single server run through a year is much, much higher than winning the lottery.
Depending on the size of your company, you can have 0 unexpected downtime with a single server, if you are lucky.
Statistics don't matter for the individual case.
We have many customers with SBS Server or smaller Windows environments with just redundant Domain Controllers, and out of our entire customer base, we only have one or two unexpected downtimes per year.
Of course this doesn't invalidate your point it all - it just may explain where the execs delusional ideas come from.
How do you make money with hosting applications? Simple - the more customers you have, the more money you make. It scales with the size of the customer base.
That means you, as a single customer, are insignificant. And that shows daily when dealing with any large service provider.
On the other hand, with internal infrastructure, you either have a infrastructure service provider (most likely a local company, not to small and not to big), which cares about each of its customers.
Or, if you're a bit bigger, you have your own employees. These depend on doing their job because they need to eat - or pay that new LCD TV they bought;)
Of course, hosted apps are cheaper as long as everything works. Which it won't, sooner or later.
If you kill a random person at a random location, with the only value that influences your choice of victim being the chance of getting away with it, the chances of getting away with it, if properly executed, are almost 100%.
But that's not how it works in the real world - most murders happen for a reason, even those be insane or sane serial killers.
Add to the fact that this sort of business software is usually extremely boring to write and develop, and requires much more process knowledge than programming knowledge.
Slashdot Mirror
1% margin on car? Any sources?
Can't believe this.
Local security does not exist. If someone has access to your hardware, consider it compromised.
Impractical? Hell yes. But that doesn't reality.
Actually, no.
First of, the IBM i uses 5250, not 3270.
Secondly, all more or less recent versions of IBM i OS,i5/OS,OS/400 (V4, V5, V6) can talk to a vt100 telnet client. The default Windows telnet client works just fine - but the F keys don't work, so the use is pretty limited on an i.
IBM still ships their IBM i systems insecure as hell, leaving most customer setups in the same shape.
Example:
Telnet is enabled by default, but telnet/ssl is not. Everyone uses SSL. I've seen many people directly exposing Port 23 to the Net, cause the i is secure.
Oh, and don't talk about SNA and DDM Files.
All our POS products are based on touchscreen technology. And they work very well.
Of course, on modern POS you don't type in numbers as you used to do in yesteryear - that's why we have barcodes and more recently RFID.
Touchscreens allow you to offer a fully dynamic user interface that adopts to the current situation. It work wells, as long as you do not need to do any sort of more-than-occasional data entry.
Like spreading vegemite on bread?
TPMs are nice. Allows me to run full disk encryption for our work laptops without interfering with the user.
TPMs are just technology. Like a gun. Or a knife.
They can be used for whatever you to. You can use a knife to spread butter on a bread. Or stick it into your wife's heart.
The users still don't have permission to do that.
Some may enforce it technically (Software Restriction Policies), almost all enforce it legally.
I don't buy this argument, neither from Mozilla nor Microsoft.
Corporations will use some sort of managed upgrade procedure anyway, as users do not have permissions to install updates.
On the IE7 side, this can be managed using WSUS, SCE, SCCM. On the Firefox side, i guess it would have to done by using a software deployment solution like SCE or SCCM.
I have no idea - never looked into Firefox deployment options.
Had this issue after restoring a backup. Try redownloading a free app. Enter itunes/apple id credentials. Then, all apps worked again.
Your parents must have hated you.
It isn't.
No matter how good the admin is, running it on an old gaming machine provided by the CEOs Son won't give you five nines. You can be happy to get 80%.
I don't think you can even get a SLA from the power company.
Well, here you can. Of course, it won't be cheap.
That mostly happens because decision makers never can make up their mind with what they want.
Erm, no.
We have multiple customers - of these, only one or two have unexpected downtimes per year. That means that there is an awful lot of customers without any downtime.
The system being completely down is one point.
But what about annoying behaviour, bugs, changes, etc.?
If you're self hosted, you'll have people looking into solving the problem and actually trying to do so. In the end, it might not happen because the cost may to high or because of something else.
When you call Google you'll reach some guy in india that doesn't give a shit about your problem.
What about your planned downtime? If you're running Windows, you're rebooting to install patches on a regular basis or you're running unpatched systems. What about software installs?
A non-issue for these customers, as they do not run 24/7 businesses. Larger stuff can be done over the weekends, smaller stuff after everyone left.
For a 24/7 enterprise with distributed locations etc. things might be different.
But then again: This is "just" e-mail. While becoming more and more critical even in the smallest of businesses, there are worse things that could crash. For instance, your production control application that controls machines (if you are a producing company), or your ERP software if you're mainly selling oriented.
There also might be some companies that depend on E-Mail as their main business application, but these should then invest into providing highly reliable internal E-Mail. That costs more than 50$ / year / account, though.
You can win the lottery too, if you are lucky. How many people win the lottery though?
The chance of having a single server run through a year is much, much higher than winning the lottery.
Google Apps Premier is not free - it's 50$ per year per account.
I'm using it for my private mail. I like it. But i don't expect 100% uptime - especially for just 50Ã per year per account.
Depending on the size of your company, you can have 0 unexpected downtime with a single server, if you are lucky.
Statistics don't matter for the individual case.
We have many customers with SBS Server or smaller Windows environments with just redundant Domain Controllers, and out of our entire customer base, we only have one or two unexpected downtimes per year.
Of course this doesn't invalidate your point it all - it just may explain where the execs delusional ideas come from.
The issue is simple:
How do you make money with hosting applications? Simple - the more customers you have, the more money you make. It scales with the size of the customer base.
That means you, as a single customer, are insignificant. And that shows daily when dealing with any large service provider.
On the other hand, with internal infrastructure, you either have a infrastructure service provider (most likely a local company, not to small and not to big), which cares about each of its customers.
Or, if you're a bit bigger, you have your own employees. These depend on doing their job because they need to eat - or pay that new LCD TV they bought ;)
Of course, hosted apps are cheaper as long as everything works. Which it won't, sooner or later.
Yes, of course.
If you kill a random person at a random location, with the only value that influences your choice of victim being the chance of getting away with it, the chances of getting away with it, if properly executed, are almost 100%.
But that's not how it works in the real world - most murders happen for a reason, even those be insane or sane serial killers.
Yeah, paying for people for their work seems like such a superfluos concept.
Maybe you should move to somewhere where communism rules.
Doesn't change the fact that hey probably paid big money for the certification.
Add to the fact that this sort of business software is usually extremely boring to write and develop, and requires much more process knowledge than programming knowledge.