From that point of view, they've made a major mistake. Since they've suspended you for a reason which they've explained to you (do get it in writing if you can) this means that they'll have to investigate.
(N.B. I long ago gave up on putting INAL in posts; first of all, if you are too dumb to work out INYL (Y==Your) then you deserver what you get from following my advice. Secondly, where I live any random idiots of the street or even turtles are allowed to give legal advise to Americans. On the internet nobody can tell you are a turtle lawyer!)
Something like: "I am a systems administrator for an Indiana-based....... What is my best course of action? How did you resolve this issue? How can I prove it's not me?"; Just cut and paste the question above; substitute real names and feed it to the lawyer.
Being serious; they need to prove it was you. Once you've identified a good lawyer to handle it, enjoy a free holiday as long as you possibly can; simply deny any connection but try to avoid helping them in any way.
The type of lawyer you want to see, incidentally, is "effective and brutal libel".
It's a bit late, now you've posted it on slashdot, I hope you lied about the details, but if you had any sense you would have started acting terribly emotionally damaged. Fake a suicide attempt. Find a friendly doctor to certify you depressed. Disappear into the wilderness on camping expeditions (so that you can have fun in an environment where it will be difficult to trace you) etc. etc.
Now that you have posted this on slashdot, probably your lawyer will advise you to prostrate yourself before the HR department; apoloigise for screwing up an internal investigation and offer to pay the company for the damage you've done. If he does that then just do what he says. He clearly knows beter than you do.
Don't lump yourself together. Your position (which I don't fully agree with, I must say) is that of a thinking intelligent person. By labelling yourself as either a "Conserveral" or a "Libertive" you put us into a black and white world which makes us all stupider.
On both the 6330 and N70 the different locking modes would overlap making it almost impossible to unlock the phone sometimes.
Care to explain? Never had this problem with my N70 and N73.
From memory (thank god; I've not been using those phones for several years): Turn on autolocking because you hate making automatic calls; turn on numerical security because a) you don't want your stolen phone to be used and b) it provides better protection than the normal locking. Now wait; sometimes (but not always) you'll find the two lock modes get confused. The numeric lock comes on top of the normal lock and then you almost can't get back into the phone. However sometimes you can. If you have fexplore installed 90% of the time it will let you kill the autolock process once you've unlocked the other one
The web browsers always failed and locked up (just yesterday I tested this against a friends E72 loading a standard AJAX site - he wanted to prove it was just as good as the N900 - his phone crashed).
S60 browser does suck, but there are alternatives. Symbian^1+ browser is much better and does support flash.
This is supposed to be a defence of Nokia? Or an accusation that they are hobbling Symbian as well as Maemo?
the excel replacement locks out and demands a license;
And the phones that, in comparison, come out of the box with a fully-free excel replacement are...
God knows; but I'm sure that if apple developed the same feature and it was as broken as it is on S60 phones, they would never ever ship it under their own brand or anywhere that it might be associated with their brand. They would probably not even allow it in their app store.
the PC software screws up your Windows desktop;
Nokia's PC suite sucks, except that other manufacturers'ones suck more. I've tried HTC sync, Motorola mobile phone tools, Samsung Studio. Besides having much less features, they're all unstable, ugly and reek of Visual Basic.
I believe the relevant competition in this case is iTunes. I will never use it 'cos it's a big pile of DRM suck, but I never heard that the user interface was terrible.
the systems aren't compatible with Linux ; etc. etc. etc.
Nokia uses open protocols for just about everything. They probably sell the only phones whose full features are accessibile on Linux.
at it's heart; you should understand that that this is not the complaint of a person who hates Nokia; rather a loyal user who feels he's being betrayed. I do agree with you up to a point. However, sometimes this seems more like Microsoft's use of open protocols than anything else. They use the "standard" interfaces but keep changing them so that it often takes months for a new model to start working (like when the data connection on phones started hopping about bluetooth channels and they didn't document it anywhere I could find).
Oh... not enough extras. Okay; the file system access is inconsistent,
Whereas the iPhone does not have a filesystem at all, and Android does not ship with a filesystem explorer out of the box, so you can save files but then only wonder where in the FS they did end up.
You are probably right that Nokia should have committed to Android at the beginning, however they've spent too long being Microsoft's on off boyfriend to get in as a serious Google partner. Their work on OVI makes it pretty clear that to everyone that they are exactly who Google shouldn't work with (unless they sell what little of OVI is worth having and prostrate themselves totally to Google; at that stage though they become just another commodity phone maker with a good logistics system but without even the Android experience of HTC)
Possibly they should port all the good open source stuff from Android into Meego, get the right licenses from Oracle make it fully integrated into the normal Linux environment so that Android Meego app ports are trivial and automatically give even more power and then come back to Google in a year or two to integrate the two together from a position of strength.
otherwise, their bridges to Android are already burned and at least "????" is better than nothing:-) No risk no fun.
No we didn't know that. Thanks though; I'll benefit. He never will 'cos he already bought an Android 'cos he didn't know that when he went to the shop. Perhaps Nokia marketing should concentrate on explaing that instead of hiring tacky porno girls to promote their new phones. In fact perhaps they should concentrate on marketing a phone OS instead of investing so much of their money into Symbian.
What's wrong with the N900 is the same as the E52. It's a rush job which didn't get finished. In both cases; bug reports have almost certainly been sitting in the bug database, a list of functions is known to be missing, but the phone gets released anyway because the CEO has promised a series of new releases and needs it out fast to keep his job. In the case of Symbian, I believe this is long term unfixable, but for the N900 it should be possible. Nokia seems to have forgotten that most phone purchases now are repeat purchases and that even those that aren't are recommendations by the user. Nokia needs to start worrying about the customers who already have their phones.
Furthermore, in each case; Nokia could be fixing these problems (the E52 is even worse than the average Symbian phone and the N900 lacked lots of basic Nokia features in the default config) with over the air updates. Instead they choose to concentrate on releasing yet more hundreds of new and mostly irrelevant X series phones.
Bullshit; or rather "I assume you are extrapolating from your experience on a Nokia symbian phone and have never actually tried using OVI maps on an N900".
Nokia was so determined to make the N900 fail that they didn't port the whole OVI map experience; despite the fact that this is a separate application so there could be no possible way that dumping programmers into it could slow down the main Maemo development. The Symbian version of OVI maps does all you say. The N900 version a) can't talk; b) doesn't even do real graphical turn by turn c) can't mark waypoints d) doesn't remember recent routes you did e) is a complete fail if you lose network connection during your travel.
Having said that; I suggest you try the following on a Symbian OVI maps. a) go abroad b) find a wifi point; load a map and plan a route d) disconnect from the internet 'cos you can't afford to pay for the cost of roaming internet. You will soon find that OVI maps is nothing like as good as Google maps. Even Google maps running on an N900 which is pretty much fine apart from the lack of live location.
From Colin's comments it seems that there's a person out there who hasn't realised that Nokia Symbian phones are shit. I really worry that some of these people work for Nokia and might think that it's worth trying to continue Symbian instead of killing it dead with a death target time of about two years and a move to the bottom end in one.
I've had in my life, for reasons of company policy, three Symbian phones.
Nokia 6330
Nokia N70
Nokia E63
The number of bugs which recur from phone to phone is astounding; Every phone completely messes up out of memory conditions with applications breaking. On both the 6330 and N70 the different locking modes would overlap making it almost impossible to unlock the phone sometimes. The web browsers always failed and locked up (just yesterday I tested this against a friends E72 loading a standard AJAX site - he wanted to prove it was just as good as the N900 - his phone crashed).
Beyond that; the mail clients regularly overload; the excel replacement doesn't deal with pretty basic XLS files let alone advanced ones; the excel replacement locks out and demands a license; the PC software screws up your Windows desktop; the systems aren't compatible with Linux ; etc. etc. etc.
Oh... not enough extras. Okay; the file system access is inconsistent, I had to use FExplorer to even survive on it (and without FExplorer's process killing I would have given up completely on Symbian long ago). Enough?
If you release with bugs that is bad, but may be down to a lazy tester and a CEO who doesn't now how to put testing people onto software. If you can't fix major bugs in your software in five years, then that is a strong hint that your software is designed wrong.
KILL SYMBIAN NOW. Nokia, for your own sake. We are begging. Symbian programmers who can deal with Linux should go to Meego. Those that can't should go to putting a Symbian compatibility layer in Meego. Those that can't cope with that need to go. Take this as a chance to prove to your customers that you will never repeat the story of the N700 to N800 where you abandoned them or the N800 to N900 where you did the same or the S2 to S3, etc. etc.
Every phone designer at Nokia should be forced to have an iphone and use it for at least a week. Until they and their managers realise that a) they have to finish phones before releasing and b) phones nowadays need a real proper operating system and Symbian is not it.
Ah yes; because you have special privileged prior access to the full Dubai file? I mean, I admit that I don't have enough evidence to prove it's Israel. I'll even believe you don't have enough evidence. I'm just not sure that that's really relevant to the question of whether Dubai has enough evidence..
Unfortunately, that's not exactly the way it works. He lost a year of work, for which he'll get nothing. He had 200,000 pounds costs of which it seems that he'll only get 70% back. He's definitely a hero and if someone has a few thousand of pounds spare, there would be worse ways to spend it than donating it to him.
No; it's true. During the third world thousands of the surviving Texans and Arizonans (mostly those who had been in Mexico at the time) escaped south through Argentina. Most of those from Arizona were killed in reprisals for their treatment of their own Hispanic immigrants, but the Texans were just dumped on ships bound for Oz where they set up Ghettos north of Melbourne (just goes to show how forgiving South Americans are, given that the Texans had hardly done much for them).
Then of course there was the great Meteor strike which wiped out many of the original inhabitants of western Australia and means that nowadays most Ozzie wine is actually produced by resettled Texans.
I'm not going to argue against your comment overall. I agree with the general gist that using a higher level language is often going to be a good strategy. However:
If object oriented languages introduce more complexity into an application, then why would anyone use them?
There are so many good and obvious answers to this that it just isn't an argument
because the people deciding are often managers who don't have a clue
because they don't know any better. They only know.Net/Java.
because, by the time they realise they made a mistake it's too late
etc.
The fact is that most software is probably written in Java/.Net nowadays, but most successful software is not. I'm not sure that's because Java is bad, but I guess that it's a sign that someone who thinks to use something different is normally someone who's thinking about the problem properly.
Any software engineer or programmer worth their salt will tell you that you always use the appropriate tool for the job at hand.
again; I agree with your sentiment. However, the "job at hand" for most programmers is normally maintaining something that's already written. That means that "the appropriate tool for the job" is normally the language that the system is already written in.
er.. design your application so it gives debugging feedback you can use? Put in assert statements so that you spot when something is wrong? Make the debugging facilities and instructions for using them so that the support people can give you useful bug reports?
Ahh. Well then I don't advise you to visit any medical colleges or hospitals. 'cos, whilst the doctors that will be treating you aren't going to be exactly trained monkeys, they definitely won't be the ones that developed the procedure. In fact, most of the time you will find that they are pretty much following the documentation.
And the inhabitants of "Gitmo" had the "constitutional right" to a proper trial. Lot of good it did them. I guess "constitutional rights" are for those who have the lawyers to wield them. In this case Monsanto.
Yup; it's great. It has almost as much intelligent comment about what's wrong with the movie as the grandparent's comment. However, it manages to stretch that out over enough words to actually fill a review space in a magazine. Astounding.
You might want to see the film Food inc. which will give some background about Monsato and the rest of the "modern" food industry. The funniest thing is that in their response to the film Monsato even directly admits they require farmers saving seed to provide "samples for testing". That's right; if you have nothing to do with Monsato, you still have a duty to provide them with samples of your seeds so that they can be sure you haven't "infringed their intellectual property rights".
Unfortunately you are not right. There is a lower end of cameras where you can only choose between different modes (e.g. sport vs portrait) and even if you read the manual it's never entirely clear what these mean. Normally there's a similar model which does have a munual mode bur you have to be careful.
because he had never heard of snort before and his sourcefire sales person came wondering buy and told him how good it was. Except they probably rather concentrated on the IPS features and he never even realised that snort was under there.
There are lots of commercial software sites which give the link to their community edition directly on their main web page. If they were "serious" they would do that too.
Well actually, that's not 100% true. Snort is an "open core" project. Sourcefire make most of it's money on the IDSs and other add ons on top, which they don't release under open source licenses. This means that sourcefire doesn't want to put features into snort because they want to profit from them on their upper layers. Also other developers don't want to contribute to snort because they don't think they will get their value back; their features will be taken but sourcefire will not continue their development except where there is benefit for their own solution.
Worst of all; the existence of open source snort makes it difficult for other competing projects to get off the ground; just look at all the snort forks and how little they change it.
The death of snort may be a chance for a better challenger to come up with no open core vendor sucking the life from it.
Having said that, snort has been really valuable; this may also be the thing which motivates Sourcefire to get back into the open source game properly. Let's see if they try to compete or run off into proprietary locked off systems.
It's easier for everyone to deputize the security force and let them deal with things on campus.
I'm surprised they don't do the same thing in your country.
In theory it could make people's life easier if the security force can deal with problems. However, we can see here that it clearly isn't making people's life easier in practice. If the guy was dealing with a larger, properly trained, properly structured police force then they would have a group of people who at least know what an IP address is and how to phone an ISP to ask for the subscriber information behind it.
Probably the reason the Australians don't do it like in the USA is that they like things which work in real life and not just in theory.
Slashdot Mirror
From that point of view, they've made a major mistake. Since they've suspended you for a reason which they've explained to you (do get it in writing if you can) this means that they'll have to investigate. (N.B. I long ago gave up on putting INAL in posts; first of all, if you are too dumb to work out INYL (Y==Your) then you deserver what you get from following my advice. Secondly, where I live any random idiots of the street or even turtles are allowed to give legal advise to Americans. On the internet nobody can tell you are a turtle lawyer!)
Something like: "I am a systems administrator for an Indiana-based....... What is my best course of action? How did you resolve this issue? How can I prove it's not me?"; Just cut and paste the question above; substitute real names and feed it to the lawyer.
Being serious; they need to prove it was you. Once you've identified a good lawyer to handle it, enjoy a free holiday as long as you possibly can; simply deny any connection but try to avoid helping them in any way.
The type of lawyer you want to see, incidentally, is "effective and brutal libel".
It's a bit late, now you've posted it on slashdot, I hope you lied about the details, but if you had any sense you would have started acting terribly emotionally damaged. Fake a suicide attempt. Find a friendly doctor to certify you depressed. Disappear into the wilderness on camping expeditions (so that you can have fun in an environment where it will be difficult to trace you) etc. etc.
Now that you have posted this on slashdot, probably your lawyer will advise you to prostrate yourself before the HR department; apoloigise for screwing up an internal investigation and offer to pay the company for the damage you've done. If he does that then just do what he says. He clearly knows beter than you do.
It's more like buying a Mac to run Ubuntu. People do it because the hardware is good.
Because you're thinking of Polio?
Don't lump yourself together. Your position (which I don't fully agree with, I must say) is that of a thinking intelligent person. By labelling yourself as either a "Conserveral" or a "Libertive" you put us into a black and white world which makes us all stupider.
From memory (thank god; I've not been using those phones for several years): Turn on autolocking because you hate making automatic calls; turn on numerical security because a) you don't want your stolen phone to be used and b) it provides better protection than the normal locking. Now wait; sometimes (but not always) you'll find the two lock modes get confused. The numeric lock comes on top of the normal lock and then you almost can't get back into the phone. However sometimes you can. If you have fexplore installed 90% of the time it will let you kill the autolock process once you've unlocked the other one
This is supposed to be a defence of Nokia? Or an accusation that they are hobbling Symbian as well as Maemo?
God knows; but I'm sure that if apple developed the same feature and it was as broken as it is on S60 phones, they would never ever ship it under their own brand or anywhere that it might be associated with their brand. They would probably not even allow it in their app store.
I believe the relevant competition in this case is iTunes. I will never use it 'cos it's a big pile of DRM suck, but I never heard that the user interface was terrible.
at it's heart; you should understand that that this is not the complaint of a person who hates Nokia; rather a loyal user who feels he's being betrayed. I do agree with you up to a point. However, sometimes this seems more like Microsoft's use of open protocols than anything else. They use the "standard" interfaces but keep changing them so that it often takes months for a new model to start working (like when the data connection on phones started hopping about bluetooth channels and they didn't document it anywhere I could find).
the iPhone browser seems to say otherwise however, it seems that the filesystem is hidden unless you jailbreak, so point taken.
You are probably right that Nokia should have committed to Android at the beginning, however they've spent too long being Microsoft's on off boyfriend to get in as a serious Google partner. Their work on OVI makes it pretty clear that to everyone that they are exactly who Google shouldn't work with (unless they sell what little of OVI is worth having and prostrate themselves totally to Google; at that stage though they become just another commodity phone maker with a good logistics system but without even the Android experience of HTC)
Possibly they should port all the good open source stuff from Android into Meego, get the right licenses from Oracle make it fully integrated into the normal Linux environment so that Android Meego app ports are trivial and automatically give even more power and then come back to Google in a year or two to integrate the two together from a position of strength.
otherwise, their bridges to Android are already burned and at least "????" is better than nothing :-) No risk no fun.
No we didn't know that. Thanks though; I'll benefit. He never will 'cos he already bought an Android 'cos he didn't know that when he went to the shop. Perhaps Nokia marketing should concentrate on explaing that instead of hiring tacky porno girls to promote their new phones. In fact perhaps they should concentrate on marketing a phone OS instead of investing so much of their money into Symbian.
What's wrong with the N900 is the same as the E52. It's a rush job which didn't get finished. In both cases; bug reports have almost certainly been sitting in the bug database, a list of functions is known to be missing, but the phone gets released anyway because the CEO has promised a series of new releases and needs it out fast to keep his job. In the case of Symbian, I believe this is long term unfixable, but for the N900 it should be possible. Nokia seems to have forgotten that most phone purchases now are repeat purchases and that even those that aren't are recommendations by the user. Nokia needs to start worrying about the customers who already have their phones.
Furthermore, in each case; Nokia could be fixing these problems (the E52 is even worse than the average Symbian phone and the N900 lacked lots of basic Nokia features in the default config) with over the air updates. Instead they choose to concentrate on releasing yet more hundreds of new and mostly irrelevant X series phones.
Bullshit; or rather "I assume you are extrapolating from your experience on a Nokia symbian phone and have never actually tried using OVI maps on an N900".
Nokia was so determined to make the N900 fail that they didn't port the whole OVI map experience; despite the fact that this is a separate application so there could be no possible way that dumping programmers into it could slow down the main Maemo development. The Symbian version of OVI maps does all you say. The N900 version a) can't talk; b) doesn't even do real graphical turn by turn c) can't mark waypoints d) doesn't remember recent routes you did e) is a complete fail if you lose network connection during your travel.
Having said that; I suggest you try the following on a Symbian OVI maps. a) go abroad b) find a wifi point; load a map and plan a route d) disconnect from the internet 'cos you can't afford to pay for the cost of roaming internet. You will soon find that OVI maps is nothing like as good as Google maps. Even Google maps running on an N900 which is pretty much fine apart from the lack of live location.
From Colin's comments it seems that there's a person out there who hasn't realised that Nokia Symbian phones are shit. I really worry that some of these people work for Nokia and might think that it's worth trying to continue Symbian instead of killing it dead with a death target time of about two years and a move to the bottom end in one.
I've had in my life, for reasons of company policy, three Symbian phones.
The number of bugs which recur from phone to phone is astounding; Every phone completely messes up out of memory conditions with applications breaking. On both the 6330 and N70 the different locking modes would overlap making it almost impossible to unlock the phone sometimes. The web browsers always failed and locked up (just yesterday I tested this against a friends E72 loading a standard AJAX site - he wanted to prove it was just as good as the N900 - his phone crashed).
Beyond that; the mail clients regularly overload; the excel replacement doesn't deal with pretty basic XLS files let alone advanced ones; the excel replacement locks out and demands a license; the PC software screws up your Windows desktop; the systems aren't compatible with Linux ; etc. etc. etc.
Oh... not enough extras. Okay; the file system access is inconsistent, I had to use FExplorer to even survive on it (and without FExplorer's process killing I would have given up completely on Symbian long ago). Enough?
If you release with bugs that is bad, but may be down to a lazy tester and a CEO who doesn't now how to put testing people onto software. If you can't fix major bugs in your software in five years, then that is a strong hint that your software is designed wrong.
KILL SYMBIAN NOW. Nokia, for your own sake. We are begging. Symbian programmers who can deal with Linux should go to Meego. Those that can't should go to putting a Symbian compatibility layer in Meego. Those that can't cope with that need to go. Take this as a chance to prove to your customers that you will never repeat the story of the N700 to N800 where you abandoned them or the N800 to N900 where you did the same or the S2 to S3, etc. etc.
Every phone designer at Nokia should be forced to have an iphone and use it for at least a week. Until they and their managers realise that a) they have to finish phones before releasing and b) phones nowadays need a real proper operating system and Symbian is not it.
Ah yes; because you have special privileged prior access to the full Dubai file? I mean, I admit that I don't have enough evidence to prove it's Israel. I'll even believe you don't have enough evidence. I'm just not sure that that's really relevant to the question of whether Dubai has enough evidence..
Unfortunately, that's not exactly the way it works. He lost a year of work, for which he'll get nothing. He had 200,000 pounds costs of which it seems that he'll only get 70% back. He's definitely a hero and if someone has a few thousand of pounds spare, there would be worse ways to spend it than donating it to him.
No; it's true. During the third world thousands of the surviving Texans and Arizonans (mostly those who had been in Mexico at the time) escaped south through Argentina. Most of those from Arizona were killed in reprisals for their treatment of their own Hispanic immigrants, but the Texans were just dumped on ships bound for Oz where they set up Ghettos north of Melbourne (just goes to show how forgiving South Americans are, given that the Texans had hardly done much for them).
Then of course there was the great Meteor strike which wiped out many of the original inhabitants of western Australia and means that nowadays most Ozzie wine is actually produced by resettled Texans.
Where have you been?
If object oriented languages introduce more complexity into an application, then why would anyone use them?
There are so many good and obvious answers to this that it just isn't an argument
The fact is that most software is probably written in Java/.Net nowadays, but most successful software is not. I'm not sure that's because Java is bad, but I guess that it's a sign that someone who thinks to use something different is normally someone who's thinking about the problem properly.
Any software engineer or programmer worth their salt will tell you that you always use the appropriate tool for the job at hand.
again; I agree with your sentiment. However, the "job at hand" for most programmers is normally maintaining something that's already written. That means that "the appropriate tool for the job" is normally the language that the system is already written in.
Sorry, was it a trick question?
Ahh. Well then I don't advise you to visit any medical colleges or hospitals. 'cos, whilst the doctors that will be treating you aren't going to be exactly trained monkeys, they definitely won't be the ones that developed the procedure. In fact, most of the time you will find that they are pretty much following the documentation.
And the inhabitants of "Gitmo" had the "constitutional right" to a proper trial. Lot of good it did them. I guess "constitutional rights" are for those who have the lawyers to wield them. In this case Monsanto.
Yup; it's great. It has almost as much intelligent comment about what's wrong with the movie as the grandparent's comment. However, it manages to stretch that out over enough words to actually fill a review space in a magazine. Astounding.
You might want to see the film Food inc. which will give some background about Monsato and the rest of the "modern" food industry. The funniest thing is that in their response to the film Monsato even directly admits they require farmers saving seed to provide "samples for testing". That's right; if you have nothing to do with Monsato, you still have a duty to provide them with samples of your seeds so that they can be sure you haven't "infringed their intellectual property rights".
Unfortunately you are not right. There is a lower end of cameras where you can only choose between different modes (e.g. sport vs portrait) and even if you read the manual it's never entirely clear what these mean. Normally there's a similar model which does have a munual mode bur you have to be careful.
because he had never heard of snort before and his sourcefire sales person came wondering buy and told him how good it was. Except they probably rather concentrated on the IPS features and he never even realised that snort was under there.
There are lots of commercial software sites which give the link to their community edition directly on their main web page. If they were "serious" they would do that too.
This is not a good thing for anyone concerned !!
Open source project dead? How can that be now?
Well actually, that's not 100% true. Snort is an "open core" project. Sourcefire make most of it's money on the IDSs and other add ons on top, which they don't release under open source licenses. This means that sourcefire doesn't want to put features into snort because they want to profit from them on their upper layers. Also other developers don't want to contribute to snort because they don't think they will get their value back; their features will be taken but sourcefire will not continue their development except where there is benefit for their own solution.
Worst of all; the existence of open source snort makes it difficult for other competing projects to get off the ground; just look at all the snort forks and how little they change it.
The death of snort may be a chance for a better challenger to come up with no open core vendor sucking the life from it.
Having said that, snort has been really valuable; this may also be the thing which motivates Sourcefire to get back into the open source game properly. Let's see if they try to compete or run off into proprietary locked off systems.
It's easier for everyone to deputize the security force and let them deal with things on campus. I'm surprised they don't do the same thing in your country.
In theory it could make people's life easier if the security force can deal with problems. However, we can see here that it clearly isn't making people's life easier in practice. If the guy was dealing with a larger, properly trained, properly structured police force then they would have a group of people who at least know what an IP address is and how to phone an ISP to ask for the subscriber information behind it.
Probably the reason the Australians don't do it like in the USA is that they like things which work in real life and not just in theory.