211–220 of 330 posts
Cool idea. In practice: they already did this and it's called PERL! Why would I ever use this instead of just using perl5, which solves all these problems already and is preinstalled on every Unix machine I've ever seen (and I've seen a lot from HPUX to AIX) since there's always some ancient innards component that depends on it, so it's basically impossible to remove... And even if you don't know perl, you're better…
Cool idea. In practice: they already did this and it's called PERL! Why would I ever use this instead of just using perl5, which solves all these problems already and is preinstalled on every Unix machine I've ever seen (and I've seen a lot from HPUX to AIX) since there's always some ancient innards component that depends on it, so it's basically impossible to remove... And even if you don't know perl, you're better…
But I agree on the perl front.
Cool idea. In practice: they already did this and it's called PERL! Why would I ever use this instead of just using perl5, which solves all these problems already and is preinstalled on every Unix machine I've ever seen (and I've seen a lot from HPUX to AIX) since there's always some ancient innards component that depends on it, so it's basically impossible to remove... And even if you don't know perl, you're better…
Because the syntax in Amber is way easier to grasp. For me that's a very strong selling point
Maybe I lack a bit in creativity: but what purpose does this serve? Almost all machines have a python or even perl interpreter if you really need to go there.
I don't think Python is as ubiquitous as you think is is; but regardless, mere presence is not the only problem. What Python are you even talking about? Which version? How is the user supposed to handle dependencies?
If something like this has utility, it's to minimize the configuration management problem you're giving the user. "Use Python" is definitely not the answer to that.
This doesn't seem to be a terribly good implementation of the idea, but it's not a bad idea, on its own.
Cool idea. In practice: they already did this and it's called PERL! Why would I ever use this instead of just using perl5, which solves all these problems already and is preinstalled on every Unix machine I've ever seen (and I've seen a lot from HPUX to AIX) since there's always some ancient innards component that depends on it, so it's basically impossible to remove... And even if you don't know perl, you're better…
> Why would I ever use this instead of just using perl5 Because the syntax in Amber is way easier to grasp. For me that's a very strong selling point
There's a lot of funky syntax and features available but you do not have to use any of them. If you are writing a new script from scratch it is easy to make it look almost the same as JavaScript but with every variable having a $ on front.
Also, amber is a new indie language. Perl has way more resources. I assure you amber will be harder to master including God knows what bugs are in the compiler you'll have to encounter and work around.
Cool idea. In practice: they already did this and it's called PERL! Why would I ever use this instead of just using perl5, which solves all these problems already and is preinstalled on every Unix machine I've ever seen (and I've seen a lot from HPUX to AIX) since there's always some ancient innards component that depends on it, so it's basically impossible to remove... And even if you don't know perl, you're better…
I know it’s not done to comment only on the websites appearance, but on a small screen the website is a mess: https://pasteboard.co/JoVqLPM106ks.png
Cool idea. In practice: they already did this and it's called PERL! Why would I ever use this instead of just using perl5, which solves all these problems already and is preinstalled on every Unix machine I've ever seen (and I've seen a lot from HPUX to AIX) since there's always some ancient innards component that depends on it, so it's basically impossible to remove... And even if you don't know perl, you're better…
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.
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
Cool idea. In practice: they already did this and it's called PERL! Why would I ever use this instead of just using perl5, which solves all these problems already and is preinstalled on every Unix machine I've ever seen (and I've seen a lot from HPUX to AIX) since there's always some ancient innards component that depends on it, so it's basically impossible to remove... And even if you don't know perl, you're better…
/s
