Whether you are developing at the enterprise level or for the smallest venues, IT is all about automation, finding ways to allow these infernal machines to do things better, faster, or in many cases, “at all” than the human alternatives.
New Automation Opportunities in .NET
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Yeah, and I guess writing some spaghetti mess of Perl/Bash some how make you more intelligent.
Why are these people so afraid of modern systems. They are so blinded by some idiology that they can’t look at a piece of technology just for the sake of its value.
ut this is replacing perl/bash scripts
Is it? Does the fact that .NET exists mean that we can’t run perl scripts anymore?
with a spaghetti mess of .NET code compiled into executables!
I will say this much – I actually like both C# and perl and have some (but not a lot) of experience with both, and I gotta say that C# code to me is easier to read than any piece of perl code I’ve ever seen.
Windows has been a joke on the server for years, and it’s getting funnier every day as Microsoft attempts to take the things that UNIX does well
You could also say “Linux/Unix has been a joke on the desktop for years, and it’s getting funnier every day as they attempt to take the things that Microsoft does well ..”
It seems to me that both *nix and Windows are trying to become like each other, when maybe both should just stay with what they’re good at.
Hi
Perl has a glue language and tell me something which has better library and regex support.
if you want a clean language take a look at python.
.net is not cross platform and despite c# its just a lock in strategy
ram
.net is not cross platform and despite c# its just a lock in strategy
I would imagine that everything is a ‘lock-in strategy’ to MS and their ilk – I think it’s called trying to run a business. I guess they could make a Linux version of .NET if they so desired, but that doesn’t exactly help their bottom line, does it? Hell, maybe they should make a version of MS Office for Linux and release the source code? And why don’t they just give it away while they’re at it?
Services have been a part of windows about as long as NT has been in existence. Writing and debugging NT services in languages other than VS.NET is simple enough. Anyone with a debugger can do it.
Bash is a highly useful automation environment, which also gives the human control over the instructions in his/her scripts.
Perl is being actively developed and it is a sucessful technology. I wouldn’t dismiss an open and accessible technology like Perl if it is capable of doing the job. It might be just what someone needs. It appears to be more healthy than ever. It’s worth investigating. I would think that Bash or at least one of the shells, is a necessity. Perl is more optional. Perl is also connected to protocols that serve the interest of the platform, the tools that are already available, rather than expensive non portable tools.
Yeah, and I guess writing some spaghetti mess of Perl/Bash some how make you more intelligent.
Why are these people so afraid of modern systems. They are so blinded by some idiology that they can’t look at a piece of technology just for the sake of its value.
Sorry, but is this article some kind of joke – “New Automation Opportunities in .NET” ? Is this meant to be an example of how powerful .NET development is ?
For all of you that are saying .Net is spaghetti code, then you must also admit on the same token that Java is also spaghetti code, since C# follows the same paradigm as Java.
I though this article was going to be some _actual_ feature, as I’ve heard a lot of good things about C#, vb.net and the whole .net architechture.
But how long has Unix had deamons? Decades? The windows world is just discovering this now? Good god, if any windows developer found this a revolutionary feature, well… let’s just say I’m feeling more secure about my Unix programming job.
I think it’s called trying to run a business.
Really? I think its called trying to run a monopoly. But maybe that’s just me.
I like .NET. I don’t know anything about it, but it sounds like they’re trying to make Longhorn something I might consider trying out. At least for the new CLI functionality if nothing else.
So will Longhorn come with an ssh server or any remote CLI stuff? And will .NET let me use my generic Perl objects? If not, why not? Perl is a completely OSS language. I prefer to reuse my code, over and over and over again. Not reorganize, relearn, rewrite a bunch of stuff I already have debugged. Besides, my objects are already cross-platform. The ONLY platform they might have a problem with is Microsoft’s. Currently I have them automating all forms of Linux, *nix, and OSX through any protocols available.
What exactly are the new automation opportunities of .NET? Or are these opportunities only available for Windows?
When I think of automation I think of automating a network of computers running whatever OSs they may be running. All OSs being equal this is not an impossible or even difficult task as long as the vendors at least try to play nice. To date Microsoft has been the only major vendor ignoring common standards like a CLI and ssh. Which is probably why I usually leave that OS in the capable hands of the resident MCSEs and recommend against its use on my networks. Maybe that will all change with Longhorn. Maybe not.
“But how long has Unix had deamons? Decades? The windows world is just discovering this now?”
It sounds like *you* might just be discovering this feature now, but the rest of us have been quite familiar with it for some time. Windows has had services for a while now.
.NET + Windows Services: That’s a little different. Even if Windows has had its services for some time, .NET is still relatively new.
One problem with .NET is that it does so much that many developers just flat out miss many of its cooler features, which is why someone might only be getting excited about this now, long after .NET’s debut.