171–180 of 182 posts
Very abstract question, but the code is compiling, I'll bite right in. I think the 'ingredients' for my ideal language are more or less the following, in decreasing order of importance: - Quality of the ecosystem. You can't buy or engineer this, it kind of has to happen naturally. Good FFI and trying not to be a "let's rewrite the world" language help immensely. It's controversial to put this as the most important bu…
Good question! From the top of my head: non-opionated memory management, nice syntax (and meta-semantics), strongly statically typed, "interpreted with possibility of AOT compilation" execution model and easy and performant native interop. Let me expand the points in order. Non-opionated memory management means that I am in the ultimate control of each allocation it does. Even if it requires GC it should allow me to…
I like to answer your post title and brainstorm at a bit higher plane (but it will have implications for the things, such as toolchains, that you highlighted). The germinating thought was remembering the frustration of having to choose between abstraction and performance . Sure, there are languages out there that do address this generally mutually exclusive dual to some degree of success. But there are other duals ou…
Since I'm not doing lowlevel stuff, for me it would be a statically typed language that has a typesystem so powerful that it never gets in my way and lets me express all constraints in types that I need for my domain (so it must be a value-dependent typesystem or similiar). In addition, the syntax must be terse so that it's easy to define (business) datatypes and mappings easily, so that someone can come in and read…
Something that takes PL theory concepts and puts them into practice: - dependent types - algebraic effects - linear types - algebraic data types - higher kinded types - homoiconicity (so it'd have to be Lisp-like, but typed) - borrow checking, and beyond, such as region borrow checking - cross-platform, JITed, as well as ahead of time compilation in release mode - static metaprogramming
Ruby. To quote the creator Yukihiro Matsumoto: > I believe that the purpose of life is, at least in part, to be happy. Based on this belief, Ruby is designed to make programming not only easy but also fun. Writing Ruby code feels natural, from creating classes, all the way to its basic types. Knowing everything is an Object makes it easy to work with. The tooling is amazing as well, from managing gems through bundler…
TypeScript, but the only supported module system is ESM (including extension being required like it is in the browser), there is no interface and enum (types and type unions are used instead), there are nameof and typeof operators in the language and there is syntax for getting a runtime value representing a type (for example string union into a string array) or even straight up option/syntax to selectively (up until…
To me what matters the most isn't the language but the ecosystem: - versatility: create desktop apps, mobile apps, websites, CLI - quality of IDE / tooling - lots of libraries to deal with all sort of corner problems - lots of knowledge I can google - if used professionally: lots of talents available For the language itself, I only really care about one thing: statically typed, just because it eliminates all sort of…
Something that takes PL theory concepts and puts them into practice: - dependent types - algebraic effects - linear types - algebraic data types - higher kinded types - homoiconicity (so it'd have to be Lisp-like, but typed) - borrow checking, and beyond, such as region borrow checking - cross-platform, JITed, as well as ahead of time compilation in release mode - static metaprogramming
A bunch of them already show up in languages like rust. Generics are the more ergnomic impl of HKTs and with ownership after you pass an entity it off to another context, you cant use it again, which I guess isnt exactly linear per se
Earlier quoted context omitted.
Libraries exist: https://github.com/haxscramper/nimtraits https://github.com/andreaferretti/patty https://github.com/alaviss/union Again we are not new to this problem and already offer alternatives.
This is something that should be in the core language, not in a deprecated library