@chr okay-ish shit

it's good until rust has good coroutines and async io support and frameworks

@CobaltVelvet @chr Go is a god tier language I'll have you know.

@anjum @chr the error handling

the type system

the camelcase method names

the standard lib

goroutines are very well done and the compiler is great but that's stuck on a language that's just modern C. i want to like go rust should just replace it.

@gargron i'm sorry but its syntax is so awful i just can't ever parse it and it costs so much ram and cpu that could be fixed if it wasn't based on such wasteful interpreters

and gems take so long to install i have no idea what it's doing and most ruby dev break compatibility between all versions of everything and it's always so frustrating and tiring to install anything in ruby

@CobaltVelvet @gargron (*sweetly*) what about Elixir?

@wim_v12e @gargron ah well

i hate most of the syntax too but it's using the cool parts of erlang so i have to admit it's technically great

@CobaltVelvet @gargron Well, you would, its basically Ruby syntax. But it's definitely not a memory hog.

@Doshirae sure here's more
- bad syntax, not the worst but not really readable or efficient
- meh package manager
- very slow, but not as bad as ruby
- old aka mostly forgotten and unsupported

@CobaltVelvet Isn't it normal for an interpreted language to be slow ?

@Doshirae it's not because they all do it that it becomes okay

@CobaltVelvet But that must be normal for a language interpreted to be slow, isn't it ?
It's not compiled, it can't be fast

@Doshirae look at v8's performances

the line between compilation and interpretation isn't so simple you shouldn't try to argue using it unless you know what you're talking about

@CobaltVelvet It's because I don't know what I'm talking about that I don't try to argue, I try to understand

@Doshirae well you try to understand quite brutally i'd say

anyway the difference between interpreted and compiled is merely about when you spend time do to optimizations. Perl, Python and Ruby does nearly all of them while running and that's slow. C and Rust does them as a separate step and that's the most efficient but bothering people for some reason. Java and V8 and on different points between and it's more or less efficient. Assembly is an interpreted language "faster" than C.

@CobaltVelvet I'm sorry about that ><
I'm not a native english speaker so I might be rude without noticing it :/

@Doshirae @CobaltVelvet

The object system sucks and functions don't have formal parameters.

It's great for quick, hacky tools, especially when they bloat into large, maintained programs but I find using it for any kind of involved programming to be extra tiring. Also, the syntax is so full of magic that I still make stupid mistakes after 20+ years of using it.

On the plus side, it's ubiquitous, stable and starts quickly.

@icefox @CobaltVelvet With Java already excoriated, I feel like C# needn't even be mentioned.

@Nentuaby @CobaltVelvet perhaps! There's something of a gradient between them, though I say that as a C# partisan so take it with a grain of salt. ;-)

@icefox i don't see much benefit on the dynamic side at all these days, but i tend to prefer js because of how cool v8 is and python because it looks good. i find the only use of C# is to give microsoft their custom language because they thought it would help sell their products. like, everything that has been done with C# could be done equally good with rust and C# doesn't have much reason to exist; the only gap was made intentionally for C# to fill something