I don't think we'll go back to Assembler because chips are not getting that much faster :-D
I don't even know if the speed of the actual language will be the sole determining factor in the future, right now it's not, at least for many types of apps.
So yeah, speed is important, but it's not all there is to programming languages, especially in a world of microservices and distributed computing with IO bound apps.
Probably in serverless environment languages with a fast startup time will have an edge but still... Azure only support JavaScript, Google only supports JavaScript and Python, AWS Lambda is the only one supporting a wider array of languages.
Perhaps not speed so much as language design. When parallelism is the name of the game, some languages are much more appealing than others.
That being said, there are a lot of ways to scale horizontally and the language rarely seems to be the actual bottleneck. It's just part of the stew of decisions that needs to be made.
AWS Lambda, being a real container and not a managed language isolate, should finally allow uploading binaries (as the entry point, no more neon-bindings, srijs/rust-aws-lambda, lando or various other ligma) and optionally provide its events/responses in a binary format like flatbuffer.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't think we'll go back to Assembler because chips are not getting that much faster :-D
I don't even know if the speed of the actual language will be the sole determining factor in the future, right now it's not, at least for many types of apps.
So yeah, speed is important, but it's not all there is to programming languages, especially in a world of microservices and distributed computing with IO bound apps.
Probably in serverless environment languages with a fast startup time will have an edge but still... Azure only support JavaScript, Google only supports JavaScript and Python, AWS Lambda is the only one supporting a wider array of languages.
Perhaps not speed so much as language design. When parallelism is the name of the game, some languages are much more appealing than others.
That being said, there are a lot of ways to scale horizontally and the language rarely seems to be the actual bottleneck. It's just part of the stew of decisions that needs to be made.
AWS Lambda, being a real container and not a managed language isolate, should finally allow uploading binaries (as the entry point, no more
neon-bindings,srijs/rust-aws-lambda,landoor various other ligma) and optionally provide its events/responses in a binary format like flatbuffer.