Well depending on the “depth” of the stack Rust is probably the first choice by now for new projects in “the” industry (speaking of experience, a lot of companies are evaluating this choice now).
Have you tried Zig instead for low level stuff? It’s a little bit simpler AFAIK and probably a good choice when the project doesn’t get too big (in which case I would prefer Rust because of its safety guarantees). FFI is always an option…
With JSdoc and IDE support I can still understand why one would choose Javascript instead of Typecsript (having worked with both more extensively) and with e.g. https://github.com/tc39/proposal-type-annotations the boundaries will slowly fade. (mainly to avoid a massive stack of bundling and tooling software)
But I would absolutely avoid either honestly if possible Javascript (or the “static” typing Typescript is adding on top) is still not really comparable to a real strict statically typed language (apart from all the weirdness that consists in either). The way I want to program in it (functional, composable, avoiding this) is unfortunately relatively inefficient… I still don’t get why it was “chosen” as the web language…
I don’t use low level languages much anymore, but I’m glad to hear Rust is taking over for new projects (as it should imo)
. C++ is a monstrosity of a language that’s overly complicated.
Maybe it’s because it’s the language I learned computer science in, but I feel (maybe hope is a better) that C will stick around. I firmly believe it’s the best tool for students to learn how a computer intuitively works.
As for JS/TS, I only skimmed the github link you sent, but I don’t understand how that’s too different from TS. Seems to be a slightly different way of accomplishing static typing.
Also I mostly do front-end with TS, but what issues do you run into doing functional programming with TS out of curiosity? Never tried to do that
I firmly believe it’s the best tool for students to learn how a computer intuitively works.
Yeah C is certainly a language students should learn (in contrast to C++ IMHO). It’s a dead simple language (well for what it is capable of at least, also to write a compiler for, which is a good academic task) that was very influential and is still here to stay for quite a while (not necessarily directly the language itself, but rather the ABI I think).
how that’s too different from TS
well it’s really baked into the language, no intermediate transpiler or compiler is necessary, and the ecosystem should be a little bit nicer to use (as less bundling is necessary, which I kind of detest after having gone into that rabit hole a little bit too often and “wasted” quite some time with (configuring) it).
functional programming with TS out of curiosity?
It’s not really issues, but I know that something like this:
is concise and reading like how it should be done, but it’s just less efficient than just looping over the array and doing all the things in place (because every time filter or map or reduce or all the functional niceties is used, a new array is allocated and you want to absolutely avoid allocations if possible).
Javascript is a little bit dumb when it comes to allocations (in design itself, something like V8 can’t really help here at least most of the time).
In Rust the same is often even more efficient than manually looping over, doing it in place it (probably because of aliasing guarantees). I saw a few interesting posts way back on reddit, that found this out, the (performance) equivalent imperative version was ugly to read. So the default way one would approach the problem in Rust is often also the most efficient, which is obviously very nice to have.
Or another thing I would like to use more often in Java/Typescript is factory functions, something like this:
functioncreateMyObject(param1, param2) {
// do something with param1 and param2// a few functions that could be seen as methodsfunctionmyMethod() {
param1 += 1 + param2;
}
returnObject.freeze({
myMethod,
param1
})
}
But also here, everytime createMyObject is run, all of the stuff/methods inside is allocated again (instead of creating/compiling function references), maybe this can/will be optimized at some time (probably with a transpiler/compiler again, yay -.-).
So in general: writing nice (to read) code in Typescript/Javascript often leads to a lot of allocations, and I detest that a language is designed in a way where you want to write nice looking code but you’re punished for it with inefficiency.
Well depending on the “depth” of the stack Rust is probably the first choice by now for new projects in “the” industry (speaking of experience, a lot of companies are evaluating this choice now).
Have you tried Zig instead for low level stuff? It’s a little bit simpler AFAIK and probably a good choice when the project doesn’t get too big (in which case I would prefer Rust because of its safety guarantees). FFI is always an option…
With JSdoc and IDE support I can still understand why one would choose Javascript instead of Typecsript (having worked with both more extensively) and with e.g. https://github.com/tc39/proposal-type-annotations the boundaries will slowly fade. (mainly to avoid a massive stack of bundling and tooling software)
But I would absolutely avoid either honestly if possible Javascript (or the “static” typing Typescript is adding on top) is still not really comparable to a real strict statically typed language (apart from all the weirdness that consists in either). The way I want to program in it (functional, composable, avoiding
this) is unfortunately relatively inefficient… I still don’t get why it was “chosen” as the web language…I don’t use low level languages much anymore, but I’m glad to hear Rust is taking over for new projects (as it should imo) . C++ is a monstrosity of a language that’s overly complicated.
Maybe it’s because it’s the language I learned computer science in, but I feel (maybe hope is a better) that C will stick around. I firmly believe it’s the best tool for students to learn how a computer intuitively works.
As for JS/TS, I only skimmed the github link you sent, but I don’t understand how that’s too different from TS. Seems to be a slightly different way of accomplishing static typing.
Also I mostly do front-end with TS, but what issues do you run into doing functional programming with TS out of curiosity? Never tried to do that
Yeah C is certainly a language students should learn (in contrast to C++ IMHO). It’s a dead simple language (well for what it is capable of at least, also to write a compiler for, which is a good academic task) that was very influential and is still here to stay for quite a while (not necessarily directly the language itself, but rather the ABI I think).
well it’s really baked into the language, no intermediate transpiler or compiler is necessary, and the ecosystem should be a little bit nicer to use (as less bundling is necessary, which I kind of detest after having gone into that rabit hole a little bit too often and “wasted” quite some time with (configuring) it).
It’s not really issues, but I know that something like this:
array.filter(e => <condition>).map(e => <some mapping function>)is concise and reading like how it should be done, but it’s just less efficient than just looping over the array and doing all the things in place (because every time
filterormaporreduceor all the functional niceties is used, a new array is allocated and you want to absolutely avoid allocations if possible). Javascript is a little bit dumb when it comes to allocations (in design itself, something like V8 can’t really help here at least most of the time).In Rust the same is often even more efficient than manually looping over, doing it in place it (probably because of aliasing guarantees). I saw a few interesting posts way back on reddit, that found this out, the (performance) equivalent imperative version was ugly to read. So the default way one would approach the problem in Rust is often also the most efficient, which is obviously very nice to have.
Or another thing I would like to use more often in Java/Typescript is factory functions, something like this:
function createMyObject(param1, param2) { // do something with param1 and param2 // a few functions that could be seen as methods function myMethod() { param1 += 1 + param2; } return Object.freeze({ myMethod, param1 }) }But also here, everytime
createMyObjectis run, all of the stuff/methods inside is allocated again (instead of creating/compiling function references), maybe this can/will be optimized at some time (probably with a transpiler/compiler again, yay -.-).So in general: writing nice (to read) code in Typescript/Javascript often leads to a lot of allocations, and I detest that a language is designed in a way where you want to write nice looking code but you’re punished for it with inefficiency.