Striving to become a master Go/Cloud developer; Father ๐จโ๐งโ๐ฆ; ๐ค/((Full Stack Web|Unity3D) + Developer)/g; Science supporter ๐ฉโ๐ฌ; https://coder.today
I presume you talk about browsers, for backend we have performant choices.
You should also check out Flamegraphs charts, and Dev tools have very mature performance monitoring and analysis tools.
Having the words JavaScript and performance in the same article feels .. weird.
Engines developers, same as JVM and probably .net optimize their engines based on most common practices, so if you write good enough code it will run fast. V8 team have some good talks on youtube about this topic.
Striving to become a master Go/Cloud developer; Father ๐จโ๐งโ๐ฆ; ๐ค/((Full Stack Web|Unity3D) + Developer)/g; Science supporter ๐ฉโ๐ฌ; https://coder.today
Lighting McQueen fast
Other devs can read my code very fast ๐
I presume you talk about browsers, for backend we have performant choices.
You should also check out Flamegraphs charts, and Dev tools have very mature performance monitoring and analysis tools.
Having the words JavaScript and performance in the same article feels .. weird.
Engines developers, same as JVM and probably .net optimize their engines based on most common practices, so if you write good enough code it will run fast. V8 team have some good talks on youtube about this topic.
Actually, it's not weird. APM for NodeJS is a whole business.
If a team wants performance for its key components and paths will not use nodeJS, it can only go so far ...