And for no -trivial automation tasks? At some point, if you're go to administer any system, you're going to have to learn how it works, and not just throw some poorly-fitting compatibility layer on top of it so system administrators of one system don't have to put the effort into learning another.
That's not really the point. The underlying APIs are very dissimilar and to replicate the kinds of calls PowerShell uses for automation is going to require some sort of translation layer to convert Linux system calls and the configurable settings in/proc and/etc. It's the inverse of Cygwin. I don't care if the whole thing gets compiled to binaries, there's going to be a hit on performance (and it's not like powershell is any speed demon even in a Windows environment). Those wrapper libraries are going to be pretty complex and I imagine you'll never get 100% portability, so you'll be left with all sorts of idiosyncrasies that still means a maintenance nightmare.
I stopped using Cygwin for precisely that reason. Slow, kludgy and some things just don't work. When I'm in a Windows environment, I'll use PowerShell, because despite being a horribly verbose scripting language, it does work. But in *nix I'll use the GNU toolkit, even if Bash can get pretty nasty in its own way. Both shells are built for their environments.
Or they could take a few days, learn the *nix toolkit and then not have to invoke a shell that's going to have to load.NET, a bunch of libraries that will themselves have to be wrappers to replicate Win32 calls. It's going to be like Cygwin in reverse, and run just as badly.
Because, of course, there's no way to do remote admin on Linux. Thank fucking god that Microsoft came along to help us all do what we've been doing on *nix systems for fucking decades.
Jesus Christ, do any of you shills even know what's being going on in the *nix world since Windows was a 16-bit kludge running on top of DOS?
Ever heard of static linking? If it's that big a concern to you, then just throw it all in one binary. Or as one big ass self-contained application under/opt. But really, most developers out there know how to use the major distros package managers, so they take the extra 15 minutes it takes to convert and test an rpm as a deb file or whatever. Fuck me, but either you're an idiot, or the laziest human being alive.
Most of the advantage of Powershell comes from access to WMI and other core API functions. As an actual shell goes, it's a horrible bloated monstrosity that is the exact opposite of the Unix philosophy. And without a lot of the hooks, or basically some compatibility layer to turn convert Windows API calls into/proc and/etc hooks, one can imagine it will be even slower than it is on Windows, and with limited functionality. And really, the whole philosophy of Powershell, with its OOP nature, comes out of its origins as basically a CLI for.NET. There really isn't anything comparable in the *nix world save perhaps for some of the GUIs out there.
I get it. This is some way to try to attract a wider base to its toolset, and maybe a bit the other way, but I cannot imagine anyone going through the bloat of bringing up a Powershell script when something like bash will be that much faster and far more intuitive for someone steeped in the *nix world.
Powershell and the whole way the Windows ecosystem is evolving makes truer every day that those who do not understand Unix are doomed to reimpliment it badly.
While von Braun wanted to go into space, the Nazis were interested solely in military applications. And so, really, where the Americans and Soviets. The space program was as much about developing ICBMs as it was about putting monkeys and humans in space.
You do understand, I trust, that the American space program greatly benefited from German scientists hustled into the country after the war. Werner von Braun ring any bells. Both the Americans and the Soviets plundered the wreckage of Nazi Germany for its technological innovations, and in particular for aeronautics technology. Whether it was guided missiles or jet aircraft, the Germans had come a lot further in their research and development in these areas.
If you want to turn your browser into a glorified version of Mosaic, be my guest. Some of us actually want to view the web of 2018, not the web of 1995.
It seems ludicrously seld-defeating in the long run. Most fast food joints require a not insignificant amount of training, so if you're targeting your hiring towards those with no experience, sure you can offer a lower wage, but then the training time is extended, so you still end up paying more money, both for the training period and in the time it takes the new worker to ramp up to something approaching normal productivity. In the meantime your customers get pissed off at poor service, and that will hit your sales.
Honestly I wished I lived in an area like that. I'd open a fast food joint, lure away their experienced staff with higher wages and benefits, and while they flounder because of a moronic policy whose only purpose seems to be to suppress wages regardless of the ill effects on every other aspect of the bottom line, I'd have happier and more productive employees and happier customers.
This kind of "keep the wages low" mindset works when unemployment is high and you can abuse your employees with little fear they'll walk. But even in that situation, creating a demoralized workforce will still lower productivity and customer satisfaction, and will likely keep retention low, meaning training costs go up.
I sure hope they didn't pay much, because that's so far below the lowest common denominator of modern IT services that the only thing I can think of is that some amateur BBS operator from the mid-90s accidentally fell into an icy lake, his frozen body was found a few years ago, was resuscitated and went into the business of responding to Federal government procurements, with all the knowledge and ability an amateur BBS operator from the mid-90s could bring to 21st century IT.
The fact that FTP is being used at all is a big red flag for me. Unless it's sitting inside a fully encrypted tunnel, an FTP password is so trivial to steal even if it isn't an obvious password. There may be a few cases where one has to use FTP, but where I have been forced to use it (old hardware), it's ringfenced like nuts, and I'm not going to have an FTP server open on the Internet, unless it's some sort of publicly available archive where I don't care who downloads off of it.
Not counting iOS (which is ARM) or the old Apple 8 bits (all 650x machines), Apple has changed Mac architecture three times; 68000-family to start, then PowerPC, and now Intel. That's three times in thirty years. Yes, more than Microsoft, which has largely stuck with x86, despite a few ventures with NT. There's ARM now, and I expect that one will ultimately stick a bit better than the defunct Alpha and PowerPC ports.
It's also the day you should be thanking France, because without French support, you'd probably be part of Canada, and the national holiday would have been four days ago.
Robots don't need minimum working standards. In a generation you're going to see even the people in countries you want to exclude being replaced by machines. Not even the most cheaply paid labor will be able to work that cheaply.
And people give corporations money for the stuff robots build, so I see a solution to this dilemma. Corporations are displacing workers, then corporations can pay the taxes necessary to maintain and/or retrain displaced workers.
If certain moral stances, or at least how strongly they are held or enforced has changed, then right and wrong are not fixed, but rather the product of social consensus. Nudity has never been that big a no no in art, and porn has become so mainstream that even the "smut peddlers" can't compete with the mom and pop shops.
Plop the scripts into /use/local/bin on the machines in mirror fashion. Tools like ssh can be scripted as well. Come on, this ain't rocket science.
And for no -trivial automation tasks? At some point, if you're go to administer any system, you're going to have to learn how it works, and not just throw some poorly-fitting compatibility layer on top of it so system administrators of one system don't have to put the effort into learning another.
That's not really the point. The underlying APIs are very dissimilar and to replicate the kinds of calls PowerShell uses for automation is going to require some sort of translation layer to convert Linux system calls and the configurable settings in /proc and /etc. It's the inverse of Cygwin. I don't care if the whole thing gets compiled to binaries, there's going to be a hit on performance (and it's not like powershell is any speed demon even in a Windows environment). Those wrapper libraries are going to be pretty complex and I imagine you'll never get 100% portability, so you'll be left with all sorts of idiosyncrasies that still means a maintenance nightmare.
I stopped using Cygwin for precisely that reason. Slow, kludgy and some things just don't work. When I'm in a Windows environment, I'll use PowerShell, because despite being a horribly verbose scripting language, it does work. But in *nix I'll use the GNU toolkit, even if Bash can get pretty nasty in its own way. Both shells are built for their environments.
Or they could take a few days, learn the *nix toolkit and then not have to invoke a shell that's going to have to load .NET, a bunch of libraries that will themselves have to be wrappers to replicate Win32 calls. It's going to be like Cygwin in reverse, and run just as badly.
Because, of course, there's no way to do remote admin on Linux. Thank fucking god that Microsoft came along to help us all do what we've been doing on *nix systems for fucking decades.
Jesus Christ, do any of you shills even know what's being going on in the *nix world since Windows was a 16-bit kludge running on top of DOS?
Ever heard of static linking? If it's that big a concern to you, then just throw it all in one binary. Or as one big ass self-contained application under /opt. But really, most developers out there know how to use the major distros package managers, so they take the extra 15 minutes it takes to convert and test an rpm as a deb file or whatever. Fuck me, but either you're an idiot, or the laziest human being alive.
Most of the advantage of Powershell comes from access to WMI and other core API functions. As an actual shell goes, it's a horrible bloated monstrosity that is the exact opposite of the Unix philosophy. And without a lot of the hooks, or basically some compatibility layer to turn convert Windows API calls into /proc and /etc hooks, one can imagine it will be even slower than it is on Windows, and with limited functionality. And really, the whole philosophy of Powershell, with its OOP nature, comes out of its origins as basically a CLI for .NET. There really isn't anything comparable in the *nix world save perhaps for some of the GUIs out there.
I get it. This is some way to try to attract a wider base to its toolset, and maybe a bit the other way, but I cannot imagine anyone going through the bloat of bringing up a Powershell script when something like bash will be that much faster and far more intuitive for someone steeped in the *nix world.
Powershell and the whole way the Windows ecosystem is evolving makes truer every day that those who do not understand Unix are doomed to reimpliment it badly.
While von Braun wanted to go into space, the Nazis were interested solely in military applications. And so, really, where the Americans and Soviets. The space program was as much about developing ICBMs as it was about putting monkeys and humans in space.
You do understand, I trust, that the American space program greatly benefited from German scientists hustled into the country after the war. Werner von Braun ring any bells. Both the Americans and the Soviets plundered the wreckage of Nazi Germany for its technological innovations, and in particular for aeronautics technology. Whether it was guided missiles or jet aircraft, the Germans had come a lot further in their research and development in these areas.
You have pollen from cultivated crops. There's only one way they get there, somebody nearby was planting.
If you want to turn your browser into a glorified version of Mosaic, be my guest. Some of us actually want to view the web of 2018, not the web of 1995.
You need to start attending your cognitive therapy sessions again
It seems ludicrously seld-defeating in the long run. Most fast food joints require a not insignificant amount of training, so if you're targeting your hiring towards those with no experience, sure you can offer a lower wage, but then the training time is extended, so you still end up paying more money, both for the training period and in the time it takes the new worker to ramp up to something approaching normal productivity. In the meantime your customers get pissed off at poor service, and that will hit your sales.
Honestly I wished I lived in an area like that. I'd open a fast food joint, lure away their experienced staff with higher wages and benefits, and while they flounder because of a moronic policy whose only purpose seems to be to suppress wages regardless of the ill effects on every other aspect of the bottom line, I'd have happier and more productive employees and happier customers.
This kind of "keep the wages low" mindset works when unemployment is high and you can abuse your employees with little fear they'll walk. But even in that situation, creating a demoralized workforce will still lower productivity and customer satisfaction, and will likely keep retention low, meaning training costs go up.
Well a sticky key doesn't make much sound at all, so I guess the noise problem is solved one way or another!
I sure hope they didn't pay much, because that's so far below the lowest common denominator of modern IT services that the only thing I can think of is that some amateur BBS operator from the mid-90s accidentally fell into an icy lake, his frozen body was found a few years ago, was resuscitated and went into the business of responding to Federal government procurements, with all the knowledge and ability an amateur BBS operator from the mid-90s could bring to 21st century IT.
The fact that FTP is being used at all is a big red flag for me. Unless it's sitting inside a fully encrypted tunnel, an FTP password is so trivial to steal even if it isn't an obvious password. There may be a few cases where one has to use FTP, but where I have been forced to use it (old hardware), it's ringfenced like nuts, and I'm not going to have an FTP server open on the Internet, unless it's some sort of publicly available archive where I don't care who downloads off of it.
Not counting iOS (which is ARM) or the old Apple 8 bits (all 650x machines), Apple has changed Mac architecture three times; 68000-family to start, then PowerPC, and now Intel. That's three times in thirty years. Yes, more than Microsoft, which has largely stuck with x86, despite a few ventures with NT. There's ARM now, and I expect that one will ultimately stick a bit better than the defunct Alpha and PowerPC ports.
It's also the day you should be thanking France, because without French support, you'd probably be part of Canada, and the national holiday would have been four days ago.
Robots don't need minimum working standards. In a generation you're going to see even the people in countries you want to exclude being replaced by machines. Not even the most cheaply paid labor will be able to work that cheaply.
The kinds of jobs that will be automated.
And people give corporations money for the stuff robots build, so I see a solution to this dilemma. Corporations are displacing workers, then corporations can pay the taxes necessary to maintain and/or retrain displaced workers.
I'm shocked, I tell you, shocked!
If certain moral stances, or at least how strongly they are held or enforced has changed, then right and wrong are not fixed, but rather the product of social consensus. Nudity has never been that big a no no in art, and porn has become so mainstream that even the "smut peddlers" can't compete with the mom and pop shops.
While I admit the attraction of electric trousers, I hope they eventually electrify a whole pair of pants.
(Sorry, I just couldn't resist)
Lots of things have changed since 1938. You can't refuse to serve an African-American, same sex marriage is equal, and so on and so forth.