Having used a plethora of languages over many decades every language sucks the big one big time except for assembly language and the new language I'm developing of course. When developing a new language you pretty much need an attitude like that to get over the morass that everyone - including more likely than not, you, although I'm willing to give you the benefit of the doubt - throw at language and system developers.
Assembly just sucks because it's so focused on the pesky details but it does so elegantly since it's the real hardware level so it doesn't suck big time. Assembly is the most powerful language after all as it is what is really happening (baring bugs in the processor). Now you might claim that micro-code is the real hardware but who ever programs in THAT today? Oh right the CPU, GPU, ASIC and FPGA guys. Ah whatever that's hardware not a general purpose programming language.
This new language - more than a language, it's a system - has new features that will knock your socks off. Like the core ideas of Lisp, Smalltalk, Erlang, Clojure but without all the horrifying warts that make your mind do crazy mental gymnastics just to solve problems and write awesome and fast compiled safe parallel native code.
If you're like most programmers then you'll love this new language. It's got it all, the homoiconic aspects of Lisp where programs are data and data are programs; it's got the uniform message passing paradigm of Smalltalk but improved so that every operation is a message including all meta operations, thus it also has all the distributed message passing capabilities of Erlang without the cryptic functional goo that lacks even basic notions of objects; it's got Clojure beat hands down which is easy since to know Clojure is to know the nine gates of hell, it thumps Clojure by providing a different paradigm where the user doesn't have to become a cryptozologist digging through the bizarre Clojure primitives just to get on with their work; all in all, it's a huge advance. Oh, and with it's improved Full Block Closures it can do things and meta things that functional languages and Smalltalk never dreamed of.
One of the biggest benefits is that it provides a means of doing multi-core multi-node native threading in a safe parallel programming environment for the bulk of common parallel operations within one program, across multiple programs and even across distributed nodes with many programs running. It can even do so efficiently.
Every aspect of the language and it's system is written in itself including all of the execution engine which provides not only homoiconic aspects but also Mobius Loop aspects when the language and it's system evolve via generational rewriting to the next level - which is really where the message passing meta operations on all parts of the language/system come into play and shine. You can't have a language/system that evolves itself if it can't rewrite all of it's parts and just about all languages fail at that.
Oh, it's not a virtual machine since it actually uses the full power of the computer hardware it's running on with it's intimate direct native code connection to the CPU and GPU and other hardware it's running on. Virtual Machines suck big time, in part because their machinery is hidden in inaccessible primitives providing a locked in frozen in time binary; in part because byte codes are pathetic primitives. This new language provides the interactive feel of Dynamic Languages with Full Interactive Development Environments (e.g. Smalltalk like Integrated Development Environment but without the VM). Naturally it's a fully dynamic language.
The long term end goal for this language is for it to disappear utterly leaving only the system aspect being what the users interact with as a fully evolved object networked messaging system is a much more powerful means of programming than using a set of ASCII (or UNICODE) characters in a linear stream as we do now. In the future text based programming (even with a full IDE like Smalltalk's which can't be beat today) will become obsolete and this language and it's system aim to accomplish that.
Facing reality it must also connect with the horrifying existing computing operating system ecosystem (Window, Unix, *BSD, Mac, iOS, bla bla bla) so parts of the libraries deal with connecting with system calls and DLLs and shared libraries. Shivers.
Now maybe you're not interested in any or all of the above which is fine, you don't have to use this - not named here - in development and evolving language/system. Not all languages are for all people.
Constructive comments are always welcome. What do you need to have in your programs that you want to create?