You're an NPC and you took "your" opinions off Reddit so if I wanted dogshit arguments I'd hunt for NPCs there instead of talking to you, homosexual maggot.
[ is a command like touch or finger. You can't say touchdick or fingerbutthole, so why would you say [tongue-eqanus? (But really its just interesting ancient shorthand that still carries on. Its really just "test": https://www.man7.org/linux/man-pages/man1/test.1.html )
[...] >doing it by hand
yowch
[...]
because you're a troll
Because you're a moron
>unironically thinking bash is faster than go
What happened to common sense ?
I know right? The mouth breathing homosexual maggot subhuman Black personcattle goy Black person golem NPCs ITT don't know and will never know that feeling. They're too busy LARPing as le cynical programmer who hates bloat and popular languages/software like bash, JS, javascript, react, cuckernetes, etc.
>look mum I'm automating
2 weeks ago
Anonymous
>look mom I'm doing everything manually
kek
I know right? The mouth breathing homosexual maggot subhuman Black personcattle goy Black person golem NPCs ITT don't know and will never know that feeling. They're too busy LARPing as le cynical programmer who hates bloat and popular languages/software like bash, JS, javascript, react, cuckernetes, etc.
plebs, they will never learn
2 weeks ago
Anonymous
He's breathing manually through his mouth. Your response?
2 weeks ago
Anonymous
I wrote a bash script for that
2 weeks ago
Anonymous
DUDE I HATE #LE_POPULAR_THING, I'M A REAL PROGRAMMER!!! I'M A GVMER BRO!!!
They're too busy breathing to the mouth to have an original thought and therefore an opinion of their own so instead they just copy paste le_cynical_statement because NPCs think the more you know the more cynical and boomery you must become.
I'd like to see your scripts that don't use anything from GNU besides bash
2 weeks ago
Anonymous
they're pretty basic I'll confess, but good enough to automate basic tasks you do on a regular basis
for example determine which of your repos need a pull or push
attaching a header to your programs
and now that I use windows, for example I have one to open tor from the command line, another to open yt entretainment channels and another to open yt music channels that I like to follow
I should do one for my 4chins tabs 2bh
But with bash you can do so much more, if there's something you do on a regular basis, you can bash it
2 weeks ago
Anonymous
>this is the automation he was talking about
lel that's pathetic
2 weeks ago
Anonymous
>he does it manually
lawls
2 weeks ago
Anonymous
man you are calling a script that opens tor, yt and yt music automation
shut the frick up hahahahahahahahahhahahaahahahhahahahahahah
2 weeks ago
Anonymous
>doing it manually
Oof
2 weeks ago
Anonymous
you sound like a neet
2 weeks ago
Anonymous
>determine which repos need pull or push
post this script here, I'd like to see the AI you created that can analyze code I wrote and determine if it's ready to be pushed to production
I know right? The mouth breathing homosexual maggot subhuman Black personcattle goy Black person golem NPCs ITT don't know and will never know that feeling. They're too busy LARPing as le cynical programmer who hates bloat and popular languages/software like bash, JS, javascript, react, cuckernetes, etc.
>refuses to parse correctly if you don't include spaces inside brackets or if you include spaces around =
why does it have to be so fricking moronic about syntax? was the original implementer just that lazy?
some opinionated soitard decided that this is how variable declaration should look >foo='totalBlack persondeath'
and now you have to deal with it. Same kind of "logic" as the subhumans that decided keyword arguments in python should be written as >bar='peepeepoopoo'
instead of >bar = 'peepeepoopoo'
Reason given: >we're gay and moronic and in a less liberal society we would've worked for a sewage company cleaning turds all day
[ is a command like touch or finger. You can't say touchdick or fingerbutthole, so why would you say [tongue-eqanus? (But really its just interesting ancient shorthand that still carries on. Its really just "test": https://www.man7.org/linux/man-pages/man1/test.1.html )
man you are calling a script that opens tor, yt and yt music automation
shut the frick up hahahahahahahahahhahahaahahahhahahahahahah
shell script is literally a pile of hacks of hacks, that's why everything is idiosyncratically shit. It's a example of legacy UNIX cruft, which sadly will not be replaced in the near future (anyone who needs more won't use bash, so it's good enough).
...yeah, just use Python for anything more than 10 lines in Bash, that's fine.
You should only do complex Bash scripts if you're already good at it, it's a clumsy language for programmatically configured scripts, otherwise, you'd probably be doing everyone a favor by using Python instead.
Virtually every mainstream Linux distro comes with Python preinstalled, and frick the Wingays.
As far as I understand, perl would be a better scripting language than bash, even if fewer people can make use of it. But Python comes with a ton of batteries included. So perl occupies an odd niche in my mind, where if I want to quickly write a simple script, bash is right there. But if I want to make a more complex script or small program, I'm probably going to leverage Python's packages or general-purpose programming features, so perl wouldn't be ideal there either.
I'm just not sure what I would use perl for often enough that it would be worth dedicating time to learning it.
dude, judge a programming language's adequate usage by its features and semantics, not by fricking trends or based on what people who don't know it say about it
in the terminal, it's the best language/command/tool. perl oneliners are unparalleled
in a short script, idem, for the same reasons that its oneliners mog the competition
in 100 to 500 to 1000 lines scripts, idem
for things longer, perl has modules, namespaces and OOP just like Python. anything of that size in any scripting language will always be nothing more than a prototype anyway. imo for really big program you need a strong and static type system and compile time guarantees, type polymorphism, powerful metaprogramming features like macros, have the language be expressive otherwise the long program will be even longer and take even longer to write, and speed. that's why all big programs in python or ruby are no less toys than big programs in perl
2 weeks ago
Anonymous
I agree with your broader points, but trends do matter. I could invent my own scripting language that would be perfect for what I want, but no one else would be able to work on my scripts or make use of them without going through the initial barrier of either learning the language or installing my interpreter, respectively.
What do you think about Raku? Some of the features I had heard of seemed unique and very cool, but I know it was divisive in the perl community.
2 weeks ago
Anonymous
>I could invent my own scripting language that would be perfect for what I want
same but I'm more than considering it. chances are no one will use my programs and if they do, learning a new language is not hard at all, especially if the language is consistent
>What do you think about Raku?
It's going nowhere. They started working it in 2000, a very implementations were made but none were complete and the spec changed. The main implementation was supposed to run on a separate VM (Parrot) but the project changed its goals, decided to be a VM for all scripting languages and in the end it was too ambitious and it died. At the same time it took forever to the guys writing the bytecode compiler, to bootstrap it and to implement the very large spec which was evolving. In 2016 perl6 it officially came out on the MoarVM. The main dev and creator of this VM contributed almost nothing in 2 years.
On the language side.
It was supposed to be a powertool for parsing and DSL and it's just not. It's too fricking slow to be usable and the semantics, 10 years of Larry Wall reflections, are stupid and complex. Because Raku is itself parse by this "parser engine" the startup time is horrible. And because this parser engine is also the regex engine, the regexes are slow and unusable.
$ raku -v
Welcome to Rakudo™ v2024.04.
Implementing the Raku® Programming Language v6.d.
Built on MoarVM version 2024.04.
$ time raku -e 'say "hello"'
hello
real 0m0.265s
user 0m0.329s
sys 0m0.030s
2 weeks ago
Anonymous
Raku completely lost the simple semantics of perl (various weird distinction between "lists" and arrays, weird scalar semantics, simple references replaced with "containers" bullshit and subtle semantics of = assignement vs := "binding") and it feels more clunky imo. It has a load of builtins, destructuring assignement like perl but still no structural pattern matching wtf.
The metaoperators are amazing. You can define new operators (not new metaoperators).
Raku has this entire concept of junctions that sort of adds a layer to expression evaluation, certainly a level of indirection. It's a false good idea imo, half assed, half way between various ways of imagining what it is or could be. It's logical operators but not really, set theory stuff but not really, parrallel evaluation stuff but not really, array leading axe theory stuff but not really, syntactic macros but not really.
It has every kind of scoping in existence and more.
Macros are supposed to come soon, they need to finish refactoring the front end first.
It has a gradual type system, type polymorphism apparently, multiple dispatch and a fricked up type hierarchy: https://docs.raku.org/type/Any#typegraphrelations. The function parameters are nice, you can have named parameters mixed in with "positional" parameters, have default values, types, readwrite/readonly stuff and "guards" (where $x > 10).
If you like OOP then it's great (mixins/roles) but it's taken to extremes, OOP makes their dick hard so they have an OOP metamodel which I still don't understand what purpose it serves. (>dude, it's for implement OOP systems). (oh yes, I think reflection is one of the reasons). The amount of indirection in terms of late binding/method resolution kind of stuff in insane.
2 weeks ago
Anonymous
The VM has a JIT, not sure how good it is but the VM does fancy type specialization optimizations on a separate thread. It has a fancy generational parallel but not concurrent GC.
The concurrency is great. Unicode support is great. Calling native code is simple apparently.
2 weeks ago
Anonymous
>destructuring assignement like perl
it has real destructuring assignment I think, perl only has "list assignment" (one level deep only destructuring of arrays basically)
2 weeks ago
Anonymous
The parsing/DSL/regex were the features I'd heard praised, but it sounds like it's falling short of those ideals. The weird dance where they announced that perl 7 would take after perl 5, but then backtracked on 7, made me lose interest for the time being in both languages. I know that isn't totally fair, considering that perl 5 is obviously plenty usable as-is. I was concerned more about the leadership.
And I really wanted to defend that rough start-up time by saying that raku likely wasn't in memory the way Python might be, but the version call beforehand should have taken care of that. Brutal to see. If the language were really as convenient at handling specialized tasks as the designers want, however, then it would certainly have a place in use cases where startup speed (or even potentially run speed) don't really matter.
Raku completely lost the simple semantics of perl (various weird distinction between "lists" and arrays, weird scalar semantics, simple references replaced with "containers" bullshit and subtle semantics of = assignement vs := "binding") and it feels more clunky imo. It has a load of builtins, destructuring assignement like perl but still no structural pattern matching wtf.
The metaoperators are amazing. You can define new operators (not new metaoperators).
Raku has this entire concept of junctions that sort of adds a layer to expression evaluation, certainly a level of indirection. It's a false good idea imo, half assed, half way between various ways of imagining what it is or could be. It's logical operators but not really, set theory stuff but not really, parrallel evaluation stuff but not really, array leading axe theory stuff but not really, syntactic macros but not really.
It has every kind of scoping in existence and more.
Macros are supposed to come soon, they need to finish refactoring the front end first.
It has a gradual type system, type polymorphism apparently, multiple dispatch and a fricked up type hierarchy: https://docs.raku.org/type/Any#typegraphrelations. The function parameters are nice, you can have named parameters mixed in with "positional" parameters, have default values, types, readwrite/readonly stuff and "guards" (where $x > 10).
If you like OOP then it's great (mixins/roles) but it's taken to extremes, OOP makes their dick hard so they have an OOP metamodel which I still don't understand what purpose it serves. (>dude, it's for implement OOP systems). (oh yes, I think reflection is one of the reasons). The amount of indirection in terms of late binding/method resolution kind of stuff in insane.
Overall this makes the language sound like a mess, even though I know you're focusing on its negative aspects. But it reminds me of how C++ became an everything bagel of a language, and so each project has its own preferences on edition and features to use, because many people don't know or regularly utilize all the features. I realize that's also unfair, because C++ and raku aren't targeting the same use cases, but it still puts my hair on end.
The "guards" do look neat for function overloading, and I remember hearing someone once describe how the signatures (at least of the main function) allow for easy formation of a CLI interface largely off said signatures alone.
Absolute dogshit example
I don't even know what this is doing, but here's how I would write it:
fn_install_menu_bash() {
local title="$1"
local caption="$2"
local options="$3"
local c1 c2 c3 c4
while IFS="," read -r c1 c2 c3 c4 || [ "$c1" ]; do
set -- "$@" "$c2-$c3"
done < "$options"
set -- "$@" Cancel
select option; do
case $option in
(""|Cancel) continue ;;
esac
REPLY=${option% *}
return
done
}
Plus it's POSIX compatible aside from the select statement
Bash is fine for what it is--a shell language with an emphasis on interactive use. If your use case requires something more robust like Python, then just use Python and shut the frick up already.
Bash is the only language where I have to look up the syntax of a simple "if" every time I want to use it because it's fricking moronic. Also, the number of pitfalls and ways you can have a nice day in the balls puts even C++ to shame. So far at my company I have caused one incident. Guess what. It was a bug in a bash script
BTW you can't really google anything about bash because it's syntax is mostly special symbols rather than keywords and google doesn't like that
>hurr bash is le bad because "hello world" looks fugly in it!!!!1!!!
You're an npc who takes his opinions from other redditor NPCs.
>do not insult my shitty scripting language or else
You're an NPC and you took "your" opinions off Reddit so if I wanted dogshit arguments I'd hunt for NPCs there instead of talking to you, homosexual maggot.
ok npc
Let me guess, you also hate javascript, java, python, c++, etc. Amor fricky, cucky. Eleutheria! RADICAL FREEEDOOOOOOOOOOOM!
Anything that isn't C = garbage
good morning sir
the command shell is a part of the C ecosystem
Go and write a web server side app in C then.
>app
i despise you both.
filtered
>mad at a word
Are you autistic ?
And yet no company use C for that kind of projects
This was one of my first projects, as well as a chat program server with sockets. A web server in C is easy.
Why would you have anything but hate for interpreted languages? They are more aids than your homosexual ass
>it's the eleutheria schizo
kek
There must be only one moron spamming that made up word.
Powershell is slower than python
Bash is faster than GO
I cannot tell if this is a troll or a moron
Because you're a moron
>unironically thinking bash is faster than go
What happened to common sense ?
Even java obliterates go
bash is so based I can't even
imagine automating pretty much everything you do on a regular basis, with 0 extra dependencies, that's what bash is like
>it's good because it's preinstalled
not a high bar to clear I see
0 reading comprehension
the cope is real
>0 extra dependencies
I can tell that you don't use bash
I do, and all my scripts require 0 external libraries or installs
so I'm automating all my shit, and apparently I'm the one coping, neat
>look mum I'm automating
>look mom I'm doing everything manually
kek
plebs, they will never learn
He's breathing manually through his mouth. Your response?
I wrote a bash script for that
DUDE I HATE #LE_POPULAR_THING, I'M A REAL PROGRAMMER!!! I'M A GVMER BRO!!!
They're too busy breathing to the mouth to have an original thought and therefore an opinion of their own so instead they just copy paste le_cynical_statement because NPCs think the more you know the more cynical and boomery you must become.
I'd like to see your scripts that don't use anything from GNU besides bash
they're pretty basic I'll confess, but good enough to automate basic tasks you do on a regular basis
for example determine which of your repos need a pull or push
attaching a header to your programs
and now that I use windows, for example I have one to open tor from the command line, another to open yt entretainment channels and another to open yt music channels that I like to follow
I should do one for my 4chins tabs 2bh
But with bash you can do so much more, if there's something you do on a regular basis, you can bash it
>this is the automation he was talking about
lel that's pathetic
>he does it manually
lawls
man you are calling a script that opens tor, yt and yt music automation
shut the frick up hahahahahahahahahhahahaahahahhahahahahahah
>doing it manually
Oof
you sound like a neet
>determine which repos need pull or push
post this script here, I'd like to see the AI you created that can analyze code I wrote and determine if it's ready to be pushed to production
I know right? The mouth breathing homosexual maggot subhuman Black personcattle goy Black person golem NPCs ITT don't know and will never know that feeling. They're too busy LARPing as le cynical programmer who hates bloat and popular languages/software like bash, JS, javascript, react, cuckernetes, etc.
bash's default regex capabilities are trash.
Or you could just not be moronic and use something like dialog or fzy/fzf
nice comment
skill issue
>refuses to parse correctly if you don't include spaces inside brackets or if you include spaces around =
why does it have to be so fricking moronic about syntax? was the original implementer just that lazy?
some opinionated soitard decided that this is how variable declaration should look
>foo='totalBlack persondeath'
and now you have to deal with it. Same kind of "logic" as the subhumans that decided keyword arguments in python should be written as
>bar='peepeepoopoo'
instead of
>bar = 'peepeepoopoo'
Reason given:
>we're gay and moronic and in a less liberal society we would've worked for a sewage company cleaning turds all day
[ is a command like touch or finger. You can't say touchdick or fingerbutthole, so why would you say [tongue-eqanus? (But really its just interesting ancient shorthand that still carries on. Its really just "test": https://www.man7.org/linux/man-pages/man1/test.1.html )
>doing it by hand
yowch
because you're a troll
shell script is literally a pile of hacks of hacks, that's why everything is idiosyncratically shit. It's a example of legacy UNIX cruft, which sadly will not be replaced in the near future (anyone who needs more won't use bash, so it's good enough).
Use dash.
you're using it wrong, bash is for glue code, not actual logic. Use perl or python for that.
...yeah, just use Python for anything more than 10 lines in Bash, that's fine.
You should only do complex Bash scripts if you're already good at it, it's a clumsy language for programmatically configured scripts, otherwise, you'd probably be doing everyone a favor by using Python instead.
Virtually every mainstream Linux distro comes with Python preinstalled, and frick the Wingays.
You mean perl not python. Frick snakes!
this
perl > python + bash
As far as I understand, perl would be a better scripting language than bash, even if fewer people can make use of it. But Python comes with a ton of batteries included. So perl occupies an odd niche in my mind, where if I want to quickly write a simple script, bash is right there. But if I want to make a more complex script or small program, I'm probably going to leverage Python's packages or general-purpose programming features, so perl wouldn't be ideal there either.
I'm just not sure what I would use perl for often enough that it would be worth dedicating time to learning it.
dude, judge a programming language's adequate usage by its features and semantics, not by fricking trends or based on what people who don't know it say about it
in the terminal, it's the best language/command/tool. perl oneliners are unparalleled
in a short script, idem, for the same reasons that its oneliners mog the competition
in 100 to 500 to 1000 lines scripts, idem
for things longer, perl has modules, namespaces and OOP just like Python. anything of that size in any scripting language will always be nothing more than a prototype anyway. imo for really big program you need a strong and static type system and compile time guarantees, type polymorphism, powerful metaprogramming features like macros, have the language be expressive otherwise the long program will be even longer and take even longer to write, and speed. that's why all big programs in python or ruby are no less toys than big programs in perl
I agree with your broader points, but trends do matter. I could invent my own scripting language that would be perfect for what I want, but no one else would be able to work on my scripts or make use of them without going through the initial barrier of either learning the language or installing my interpreter, respectively.
What do you think about Raku? Some of the features I had heard of seemed unique and very cool, but I know it was divisive in the perl community.
>I could invent my own scripting language that would be perfect for what I want
same but I'm more than considering it. chances are no one will use my programs and if they do, learning a new language is not hard at all, especially if the language is consistent
>What do you think about Raku?
It's going nowhere. They started working it in 2000, a very implementations were made but none were complete and the spec changed. The main implementation was supposed to run on a separate VM (Parrot) but the project changed its goals, decided to be a VM for all scripting languages and in the end it was too ambitious and it died. At the same time it took forever to the guys writing the bytecode compiler, to bootstrap it and to implement the very large spec which was evolving. In 2016 perl6 it officially came out on the MoarVM. The main dev and creator of this VM contributed almost nothing in 2 years.
On the language side.
It was supposed to be a powertool for parsing and DSL and it's just not. It's too fricking slow to be usable and the semantics, 10 years of Larry Wall reflections, are stupid and complex. Because Raku is itself parse by this "parser engine" the startup time is horrible. And because this parser engine is also the regex engine, the regexes are slow and unusable.
$ raku -v
Welcome to Rakudo™ v2024.04.
Implementing the Raku® Programming Language v6.d.
Built on MoarVM version 2024.04.
$ time raku -e 'say "hello"'
hello
real 0m0.265s
user 0m0.329s
sys 0m0.030s
Raku completely lost the simple semantics of perl (various weird distinction between "lists" and arrays, weird scalar semantics, simple references replaced with "containers" bullshit and subtle semantics of = assignement vs := "binding") and it feels more clunky imo. It has a load of builtins, destructuring assignement like perl but still no structural pattern matching wtf.
The metaoperators are amazing. You can define new operators (not new metaoperators).
Raku has this entire concept of junctions that sort of adds a layer to expression evaluation, certainly a level of indirection. It's a false good idea imo, half assed, half way between various ways of imagining what it is or could be. It's logical operators but not really, set theory stuff but not really, parrallel evaluation stuff but not really, array leading axe theory stuff but not really, syntactic macros but not really.
It has every kind of scoping in existence and more.
Macros are supposed to come soon, they need to finish refactoring the front end first.
It has a gradual type system, type polymorphism apparently, multiple dispatch and a fricked up type hierarchy: https://docs.raku.org/type/Any#typegraphrelations. The function parameters are nice, you can have named parameters mixed in with "positional" parameters, have default values, types, readwrite/readonly stuff and "guards" (where $x > 10).
If you like OOP then it's great (mixins/roles) but it's taken to extremes, OOP makes their dick hard so they have an OOP metamodel which I still don't understand what purpose it serves. (>dude, it's for implement OOP systems). (oh yes, I think reflection is one of the reasons). The amount of indirection in terms of late binding/method resolution kind of stuff in insane.
The VM has a JIT, not sure how good it is but the VM does fancy type specialization optimizations on a separate thread. It has a fancy generational parallel but not concurrent GC.
The concurrency is great. Unicode support is great. Calling native code is simple apparently.
>destructuring assignement like perl
it has real destructuring assignment I think, perl only has "list assignment" (one level deep only destructuring of arrays basically)
The parsing/DSL/regex were the features I'd heard praised, but it sounds like it's falling short of those ideals. The weird dance where they announced that perl 7 would take after perl 5, but then backtracked on 7, made me lose interest for the time being in both languages. I know that isn't totally fair, considering that perl 5 is obviously plenty usable as-is. I was concerned more about the leadership.
And I really wanted to defend that rough start-up time by saying that raku likely wasn't in memory the way Python might be, but the version call beforehand should have taken care of that. Brutal to see. If the language were really as convenient at handling specialized tasks as the designers want, however, then it would certainly have a place in use cases where startup speed (or even potentially run speed) don't really matter.
Overall this makes the language sound like a mess, even though I know you're focusing on its negative aspects. But it reminds me of how C++ became an everything bagel of a language, and so each project has its own preferences on edition and features to use, because many people don't know or regularly utilize all the features. I realize that's also unfair, because C++ and raku aren't targeting the same use cases, but it still puts my hair on end.
The "guards" do look neat for function overloading, and I remember hearing someone once describe how the signatures (at least of the main function) allow for easy formation of a CLI interface largely off said signatures alone.
Yeah. Python when Bash gets unwieldy, C++ when Python gets unwieldy. C for fun.
is that.. whitespace in a file name??!
AAAAAAAAAA I'M GOING INSANE better parse this as multiple files
of course it's bad, it was invented by a black guy.
>At the FSF, Fox authored GNU Bash,[6] GNU Makeinfo, GNU Info, GNU Finger, GNU Echo[7] and the readline[8] and history libraries.
wow this guy is king
wtf I love blapipo now
PERL
quit deadnaming raku
raku is dead, it doesn't mind
c go perl ksh
just use perl, it's like bash on hormones
*on steroids
says the new gay that never had to use bourne shell on a SCO 5 server
Absolute dogshit example
I don't even know what this is doing, but here's how I would write it:
fn_install_menu_bash() {
local title="$1"
local caption="$2"
local options="$3"
set --
fn_print_horizontal
fn_print_center "$title"
fn_print_center "$caption"
fn_print_horizontal
local c1 c2 c3 c4
while IFS="," read -r c1 c2 c3 c4 || [ "$c1" ]; do
set -- "$@" "$c2-$c3"
done < "$options"
set -- "$@" Cancel
select option; do
case $option in
(""|Cancel) continue ;;
esac
REPLY=${option% *}
return
done
}
Plus it's POSIX compatible aside from the select statement
i couldn't believe anything uglier than rust existed but here you are showing it off
I think rust is even more hideous but yeah shell is definitely one of the ugliest languages. I'm just dunking on OP for being such a baby duck
>too dumb to run games
>too dumb to read bash
>being proud of it
Bash is objectively bad, but damn useful anyway.
Sell me on bash.
Also Unsell me on bash.
I dare you the first thing, I double dare you the second thing.
>Sell me on bash.
grep
>Also Unsell me on bash.
PHP and JS are better
I'm still fricking waiting.
>Sell
Who needs types?
>Unsell
Frick I wish I had types.
Failed and failed.
NEXT!
only underage luke smith dick suckers think bash is worth anything
>only underage luke smith dick suckers think bash is worth anything
the fact that you're comparing bash to webshitter garbage is a good sign you're 12
Bash is fine for what it is--a shell language with an emphasis on interactive use. If your use case requires something more robust like Python, then just use Python and shut the frick up already.
Both miserable attempts.
moronic reddit ran-out-of-arguments ad hominem.
NEXT!
people in 1990's and 2000's didn't give a single frick to bash, but now all of the sudden it's the best thing since slice bread
mmmmm, why is that?
>webshitter garbage
>shitlang vs shitlang
type check OK
You woke up and your ass is red and itchy?
weird projection
bash shills are gay, what is new
UNIX, much like herpes, is a virus that will be with us always
Bash is simply the best, that's why homosexual trannies get mad.
hehe yeah
So is English, but it gets the job done.
Bash is the only language where I have to look up the syntax of a simple "if" every time I want to use it because it's fricking moronic. Also, the number of pitfalls and ways you can have a nice day in the balls puts even C++ to shame. So far at my company I have caused one incident. Guess what. It was a bug in a bash script
BTW you can't really google anything about bash because it's syntax is mostly special symbols rather than keywords and google doesn't like that
I hate bash
skill issue
>fn in function name
Rust troony detected. Opinions discarded.
bash is fine for simple scripts and for anything else I'll use another language. I don't need another shell though.
old pic I found