I really like Vlang. It has built-in monads but they don't feel like a monad. Similar to go but much more ergonomic. I know some people might say they are scrictly monads, but it is good enough. It gives a nice middle ground. Also, since Vlang just compiles to C it has a wealth of libraries it can use. It is really light weight.. The main downside of it, I don't know C. Also, it is still beta software, but it is getting close to a 1.0 release even though after that it should still be adding many features. It aims to be like Go in that it is very stable. Stability and simplicity is what I want now. I've only built a small app with Vlang. So, I'm not sure how it would do with large code bases and what snags that I would run into in a real world enterprise application.
I would say it would be D-tier or on the language design itself, but it is omnipresent and the only way to do web development so that boosts it dramatically.
Idk I think types really shine at scale. When there's just a few developers working on a codebase then it's possible everyone understands the intricacies and can run with dynamic but as soon as you get to a few dozens there's no way everyone remembers what each type is.
@@HAMYLABS I said they are helpful, because you can avoid some types of bugs. But you still can write a very large dynamic project without that help and be ok. Especially with helpful things like dataclasses, enums and other type-like constructs and modern IDEs giving you so much information about everything. You don't "remember what each type is" because you have no types. You are supposed to check and duck-type, right? Hints are just... hints. Both python and TS. On the other hand you have typescript... which i feel robs javascript of all the small things that were good in it and makes it a poor mans compiled language. Weird that you make golang, which is a fast language with strong typing lower tier than the fine mess typescript is :P
@ It is verbose, I wouldn't say it is a nightmare. It requires you to be explicit about a lot of things so there is just a lot of stuff to type (and that is pretty rare) but none of it is particularly bad, in my opinion. As for async Rust, there is a lot of room for improvement I will admit. But even in its current state it goes a long (all the) way. It's just that there is a learning ~~curve~~ whirlwind to it.
@@mire6134 The amount of !'?:: reminds me of bash :P It's like they took C syntax and made it even more symbol heavy. But yeah, either that or Zig is the way to go in systems programming, hence its A for me. Wouldn't ever write anything that is not high-performance or system in this though, since the complexity is not worth the cost imho.
I really like Vlang. It has built-in monads but they don't feel like a monad. Similar to go but much more ergonomic. I know some people might say they are scrictly monads, but it is good enough. It gives a nice middle ground. Also, since Vlang just compiles to C it has a wealth of libraries it can use. It is really light weight.. The main downside of it, I don't know C. Also, it is still beta software, but it is getting close to a 1.0 release even though after that it should still be adding many features. It aims to be like Go in that it is very stable. Stability and simplicity is what I want now.
I've only built a small app with Vlang. So, I'm not sure how it would do with large code bases and what snags that I would run into in a real world enterprise application.
This sounds cool - might need to check it out!
JS in B tier? You've gotta be trolling
Yeah, definitely should be D
I would say it would be D-tier or on the language design itself, but it is omnipresent and the only way to do web development so that boosts it dramatically.
You don't need types at a scale. Their helpful but not necessary.
Idk I think types really shine at scale. When there's just a few developers working on a codebase then it's possible everyone understands the intricacies and can run with dynamic but as soon as you get to a few dozens there's no way everyone remembers what each type is.
@@HAMYLABS I said they are helpful, because you can avoid some types of bugs. But you still can write a very large dynamic project without that help and be ok. Especially with helpful things like dataclasses, enums and other type-like constructs and modern IDEs giving you so much information about everything. You don't "remember what each type is" because you have no types. You are supposed to check and duck-type, right? Hints are just... hints. Both python and TS.
On the other hand you have typescript... which i feel robs javascript of all the small things that were good in it and makes it a poor mans compiled language. Weird that you make golang, which is a fast language with strong typing lower tier than the fine mess typescript is :P
Rust is S tier.
S for sh*t
Rust syntax is a nightmare, Async rust is a nightmare^nightmare.
Definitely A though.
@ It is verbose, I wouldn't say it is a nightmare. It requires you to be explicit about a lot of things so there is just a lot of stuff to type (and that is pretty rare) but none of it is particularly bad, in my opinion.
As for async Rust, there is a lot of room for improvement I will admit. But even in its current state it goes a long (all the) way. It's just that there is a learning ~~curve~~ whirlwind to it.
@@mire6134
The amount of !'?:: reminds me of bash :P It's like they took C syntax and made it even more symbol heavy.
But yeah, either that or Zig is the way to go in systems programming, hence its A for me. Wouldn't ever write anything that is not high-performance or system in this though, since the complexity is not worth the cost imho.
Nope.