1 |
On 28/01/2014 14:28, Neil Bothwick wrote: |
2 |
>> Really?, Try that approach at a carrier network support center, where |
3 |
>> > new stuff is rolled out to cutomers without first explaing, warning |
4 |
>> > and offering up options..... It's shows a blatant disrespect for |
5 |
>> > the existing customer base. Nobody in business, treats existing |
6 |
>> > customers that way, imho. In industry, punks with that mentality get |
7 |
>> > *FIRED*.... |
8 |
> Yes, really. People boot a distro's live CD, maybe install it, and make |
9 |
> quick decisions about whether they like it or not. |
10 |
> |
11 |
|
12 |
|
13 |
James isn't talking about whatever the latest flavour of the month |
14 |
happens to be that you like. He's talking about the firmware running on |
15 |
carrier core, or on the black box installed at the customer's edge. Or |
16 |
the company portal that lets our customers drill deep down into their |
17 |
traffic stats or do monitoring or investigate billing. |
18 |
|
19 |
I work in carrier and that shit is sacrosanct so change it at your |
20 |
peril. I really couldn't care what desktop the user runs today as I |
21 |
don't support any of them, just the API we present to the world. |
22 |
|
23 |
I think you are looking at this from the POV of a desktop end user, |
24 |
while James and I are talking about infrastructure that the end user |
25 |
only gets to use, never change. |
26 |
|
27 |
James's point is valid though - corporates like to claim they will never |
28 |
unleash shit like kdepim on an unsuspecting world and fire anyone who |
29 |
lets it slip through. That's what they say, in reality it happens all |
30 |
the time anyway. Which doesn't change that very few of the kdepim-4 |
31 |
releases should never have seen the light of day with a release tag |
32 |
|
33 |
|
34 |
-- |
35 |
Alan McKinnon |
36 |
alan.mckinnon@×××××.com |