|
Considerably more power than cmd, less user acceptance issues than PowerShell.
What's not to love?
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Yes. I guess MS have been jealous of the superior commands available in bash that don't exist in MS Dos.
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|
|
Absolutely. Command chaining is a very powerful feature that cmd has sorely lacked. If for that alone, it's worth it.
It also doesn't hurt to have a common command interface for each box in the server farm.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Nathan Minier wrote: Considerably more power than cmd, less user acceptance issues than PowerShell.
You must not read Slashdot.
When MS announced Bash for Windows 10, the resulting discussions were all about how this does nothing to sway any of them back to MS.
Going at it the other way around, when MS announced PowerShell for Linux, the resulting discussions were all about how nobody in their right minds would pollute their pristine Linux systems with MS garbage.
"Less user acceptance issues", my @$$. They just can't win. The attitude in the community makes me want to ignore Linux more than any technical issue or learning curve.
|
|
|
|
|
dandy72 wrote: You must not read Slashdot.
No, that sounds like horribly kinky fan-fiction featuring Dot from Animaniacs, though.
I don't think anyone cares about Linux fanbois, not even Linux fanbois. I was actually talking about Windows user acceptance, as in an enterprise environment I've seen a lot of (IT) people that are so intimidated by PowerShell that they won't use it. They will, however, use bash, since they've had to learn how to when administering appliances.
Maybe the issue here is that when I say "User", I'm meaning anything from baseline User to SysAdmin. To me it just means !Developer.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Just don't ever edit a *nix config file using a windows editor.
While most are smart enough not to screw up line endings, they don't understand how to handle the *nix permissions tucked away in the file system. With the result that the first time one does a safe write:
0) Write to filename.ext.temp
1) delete filename.ext
2) rename filename.ext.temp to filename.ext
you end up losing all the *nix permissions on the file and then your *nix breaks. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Several articles I've read agree. They all give me the impression that using one OS's tools to modify the other's files tend not to end well.
Speaking of said articles, I asked this question here because (a) I knew the answers would range from helpful to classic CP buffoonery, and (b) asking it on Google and Duck*2Go resulted in everyone and their sister's blog on how to install it and run a few bash commands, but precious little on what to actually do with it once you've got it.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Well, if they had implemented the USB syscalls, we could have used it to develop for android but since they didn't then adb can't talk to any android devices for debugging. Makes Bash/Ubuntu on Windows mostly a silly toy.
|
|
|
|
|
Although I have not tried it yet on win 10, I've used windows text editors on unix and linux for years, with no problems at all. You just need to use wordpad instead of notepad (it happily will use just the single byte newline, unlike notepad which uses CRLF), and save directly to the *nix machine to preserve the permissions, all one byte of them.
|
|
|
|
|
|
"[D]umb as a stump," may be apropos, but it was easier than trying to remember all the arcane keystrokes, then losing the file by quiting without having saved it. I have always maintained that vi was someone's revenge on the world.
|
|
|
|
|
Where does VM/dual boot come into play with bash? bash implementations for Windows are available as components of several different packages.
(And: does a [lamp stack] require a specific OS?)
|
|
|
|
|
Member 7989122 wrote: bash implementations for Windows are available as components of several different packages.
Pardon me for my sin of ommission. I should have said "VM/dual boot/Cygwin/any other bash-on-Windows implementation I've never heard of or looked for."
Member 7989122 wrote: (And: does a [lamp stack] require a specific OS?)
Well, considering the 'L' in LAMP stands for Linux ... 
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
As per my experience, git clone works far better on BASH for Win10 than on actually Windows.
Also you must keep in mind that Win10 has file path lenght limit, so actually cloning some repositories will keep them intact.
Last but not least, this is more about looking into the future.
For example, today, to run Docker for Windows, you need a full Linux installation inside Hyper-V. In the future, in an inception like scenario, you might for go Hyper V completely, and run Docker using pure Windows Containers, some pure Windows and some others hybrid, using the USL. Since the USL will be feature complete in 2 years time, you could run any container possible, even non Ubuntu ones. 
I am the one who knocks...
|
|
|
|
|
Maybe get a decent install of Clang or gcc on Windows for once? Both mingw and cygwin have versions of gcc and its supporting libs that are not completely compatible with the *nix versions.
Haven't tried yet, to be honest. I need Win 10 on a machine first.
|
|
|
|
|
FAST FOOD
A restaurant packing fried chickens in packages of 6, 9 and 20...
Which is the largest number of chickens you can NOT order?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: largest number of chickens you can NOT order?
All of them.
Diner: "Hi, I'd like to not order all of your chickens."
Waiter: "Wait, what?"
Diner: "Please don't bring me ALL of your chickens"
Waiter: "Uh, is this some kind of prank?"
Diner: "It absolutely isn't quite true that it may not be not a prank."
Waiter: "Get out."
|
|
|
|
|
So if I want 1 to 5 chickens I have to order the 6?
|
|
|
|
|
Yo can not order 1 to 5...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I can not order whatever I want.
|
|
|
|
|
Just order the 6 and ask them to put in how many you want between 1 and 5. You'd still pay the price for 6 pieces though but most fast food places would be happy to oblige. 
|
|
|
|
|
Any number - I don't go to fast food chicken restaurants.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Is this KFC or Chick-Fil-A?
|
|
|
|
|
Los Pollos Hermanos
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Is there any uncertainty in your assertion?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
