4 ms·

I find all the "Why should I use this when X exist" nonsensical. If you can't see any use for it then it's not for you. There are a whole lot of people who will

I find all the "Why should I use this when X exist" nonsensical. If you can't see any use for it then it's not for you. There are a whole lot of people who will find this more attractive than Perl.

galdosdi 2y ago
Because they've heard the "lol perl is line noise" jokes and taken them very seriously instead of the jokes they are. Perl is way more mature with way more libraries, stability, documentation, etc. I hope I don't have to work with some young fool who decided without trying that perl, an incredibly well documented language, is "too hard" and instead signed our whole team up to work with some experimental 3 month old language with who knows what weird bugs and quirks, none of which youll find info about on stack overflow, because almost nobody has ever used it Reminds me of the days about 10 years ago when all the kids were obsessed with no SQL and MongoDB for use cases that were smaller than SQLite -- purely because they were scared to learn SQL You'll understand where I'm coming from after you get more experience and have had multiple jobs where you had to maintain architecture with poor choices due to an inexperienced original author using cool shiny tech that offers little advantage over the more mature tech, and you spend much of your time working around and maintaining something that has no stack overflow coverage at all
- Legion 2y ago
  Have you stopped to think that maybe people will use this "experimental 3 month old language" for their personal stuff, and that not everything in programming is for your "whole team"?
  - galdosdi 2y ago
    Then they can disregard my advice obviously. But I saw plenty of others in this thread who seemed interested in it genuinely for practical reasons, and with all the times I've seen young devs disregard old mature solutions, I thought it'd be worth mentioning. Besides, "runs anywhere bash does" isn't really useful for a personal project. Work is where you're likely to run into a weird variety of legacy machines, not in a personal project where you have more control. Regardless, the weird aversion to hearing advice that can just be disregarded if it doesn't apply to your case baffles me.
- melodyogonna 2y ago
  My answer still applies to this long... ehh explanation?
galdosdi 2y ago
I'm trying to help people here. I know some young people may not even be aware of older options and not realize this problem has already been solved repeatedly. They are free to disregard my advice, so I find your objection more nonsensical
- tempaccount420 2y ago
  How does this help though? Why should we stick to old software? Why advocate for inertia?
  - Minor49er 2y ago
    Old software has had use, discussion, support, and resources that are usually still easily available. New software may have to reinvent a lot of wheels, so the barrier to entry may be higher despite the language's features. Choosing one over the other is all dependent on the problem that's being solved
  - mlhpdx 2y ago
    Because solving new, current problems is more valuable than re-solving old ones? Is the new thing good? Yes. Is the old thing good? Yes. Both can be true. And, there is some value in better solutions to old problems. But if you're looking for "reason" I think that falls on not re-doing the same thing over and over again.
- pvg 2y ago
  I'm trying to help people here. It just starts a lame language war thread while being dismissive of and incurious about the thing being discussed. Things the site docs ask you to avoid as they reliably generate more noise than interesting conversation.

I find all the "Why should I use this when X exist" nonsensical. If you can't see any use for it then it's not for you. There are a whole lot of people who will find this more attractive than Perl.

galdosdi 2y ago

Because they've heard the "lol perl is line noise" jokes and taken them very seriously instead of the jokes they are. Perl is way more mature with way more libraries, stability, documentation, etc. I hope I don't have to work with some young fool who decided without trying that perl, an incredibly well documented language, is "too hard" and instead signed our whole team up to work with some experimental 3 month old language with who knows what weird bugs and quirks, none of which youll find info about on stack overflow, because almost nobody has ever used it Reminds me of the days about 10 years ago when all the kids were obsessed with no SQL and MongoDB for use cases that were smaller than SQLite -- purely because they were scared to learn SQL You'll understand where I'm coming from after you get more experience and have had multiple jobs where you had to maintain architecture with poor choices due to an inexperienced original author using cool shiny tech that offers little advantage over the more mature tech, and you spend much of your time working around and maintaining something that has no stack overflow coverage at all

Legion 2y ago
Have you stopped to think that maybe people will use this "experimental 3 month old language" for their personal stuff, and that not everything in programming is for your "whole team"?
- galdosdi 2y ago
  Then they can disregard my advice obviously. But I saw plenty of others in this thread who seemed interested in it genuinely for practical reasons, and with all the times I've seen young devs disregard old mature solutions, I thought it'd be worth mentioning. Besides, "runs anywhere bash does" isn't really useful for a personal project. Work is where you're likely to run into a weird variety of legacy machines, not in a personal project where you have more control. Regardless, the weird aversion to hearing advice that can just be disregarded if it doesn't apply to your case baffles me.
melodyogonna 2y ago
My answer still applies to this long... ehh explanation?

galdosdi 2y ago

I'm trying to help people here. I know some young people may not even be aware of older options and not realize this problem has already been solved repeatedly. They are free to disregard my advice, so I find your objection more nonsensical

tempaccount420 2y ago
How does this help though? Why should we stick to old software? Why advocate for inertia?
- Minor49er 2y ago
  Old software has had use, discussion, support, and resources that are usually still easily available. New software may have to reinvent a lot of wheels, so the barrier to entry may be higher despite the language's features. Choosing one over the other is all dependent on the problem that's being solved
- mlhpdx 2y ago
  Because solving new, current problems is more valuable than re-solving old ones? Is the new thing good? Yes. Is the old thing good? Yes. Both can be true. And, there is some value in better solutions to old problems. But if you're looking for "reason" I think that falls on not re-doing the same thing over and over again.
pvg 2y ago
I'm trying to help people here. It just starts a lame language war thread while being dismissive of and incurious about the thing being discussed. Things the site docs ask you to avoid as they reliably generate more noise than interesting conversation.