How difficult is JavaScript?
Suggest a number randomly from 0(most easy) to 10(most difficult),
and tell how difficult is this ?
Suggest a number randomly from 0(most easy) to 10(most difficult),
and tell how difficult is this ?
π39
Did you use Memoization in JavaScript ?
In a nutshell, Memoization is a programming technique which allows you to reduce the functionβs time cost for space cost. That is, the functions which are memoized gain speed for a higher use of memory space.
https://betterprogramming.pub/understanding-javascript-typescript-memoization-6e0333b62406
In a nutshell, Memoization is a programming technique which allows you to reduce the functionβs time cost for space cost. That is, the functions which are memoized gain speed for a higher use of memory space.
https://betterprogramming.pub/understanding-javascript-typescript-memoization-6e0333b62406
Medium
Understanding JavaScript/TypeScript Memoization
A JavaScript and TypeScript tutorial
π41π2
Python has π
PHP has π
What's your emoji for JavaScript?
PHP has π
What's your emoji for JavaScript?
π₯388π€―53π40π21π18π13π13β‘9π9π©9π€¬6
As 2022 ends, we will start looking forward to 2023. The JavaScript world is evolving quickly, and there are lots of growing projects, some of which deserve your attention, and some that do not. In this article, we will look at six JavaScript projects to watch in 2023.
https://byteofdev.com/posts/javascript-projects-2022/
https://byteofdev.com/posts/javascript-projects-2022/
ByteofDev
The 6 JavaScript Projects to watch in 2023
We look over some of the JavaScript projects to watch in 2023.
π27π₯7π―2
π18π1
JavaScript Daily
JS Promises While synchronous code is easier to follow and debug, async is generally better for performance and flexibility. Why "hold up the show" when you can trigger numerous requests at once and then handle them when each is ready? Promises are becomingβ¦
Introducing the WebAssembly JavaScript Promise Integration API v8.dev/blog/jspi
v8.dev
Introducing the WebAssembly JavaScript Promise Integration API Β· V8
This document introduces JSPI and provides some simple examples to get you started in using it
π6π₯4
Did JavaScript just got faster ?
Bun is a modern JavaScript runtime like Node or Deno. It was built from scratch to focus on three main things:
- Start fast (it has the edge in mind).
- New levels of performance (extending JavaScriptCore, the engine).
- Being a great and complete tool (bundler, transpiler, package manager).
Bun uses the JavaScriptCore engine(WebKit), which tends to start and perform a little faster than more traditional choices like V8.
Bun is written in Zig, a low-level programming language with manual memory management.
Most of Bun is written from scratch including the JSX/TypeScript transpiler, npm client, bundler, SQLite client, HTTP client, WebSocket client and more.
https://bun.sh/
π₯ Follow @javascriptdaily π₯
Bun is a modern JavaScript runtime like Node or Deno. It was built from scratch to focus on three main things:
- Start fast (it has the edge in mind).
- New levels of performance (extending JavaScriptCore, the engine).
- Being a great and complete tool (bundler, transpiler, package manager).
Bun uses the JavaScriptCore engine(WebKit), which tends to start and perform a little faster than more traditional choices like V8.
Bun is written in Zig, a low-level programming language with manual memory management.
Most of Bun is written from scratch including the JSX/TypeScript transpiler, npm client, bundler, SQLite client, HTTP client, WebSocket client and more.
https://bun.sh/
π₯ Follow @javascriptdaily π₯
π₯21π19β€1π―1
There wouldn't be any need to use Typescript?
https://dev.to/smpnjn/types-may-finally-be-coming-to-javascript-56a2
https://dev.to/smpnjn/types-may-finally-be-coming-to-javascript-56a2
DEV Community
Future Javascript: Types may finally be coming to Javascript
With the promotion of Type Annotations to Proposal Level 1 Stage, Javascript is one step closer to...
π19β€2π₯°2π’1
There has been some buzz recently in the frontend world around the term "Signals". In seemingly short order they seem to be everywhere showing up in everything from Preact to Angular.
But they are not a new thing. Not even remotely if you consider you can trace roots back to research in the late 1960s. At its foundation is the same modeling that enabled the first electronic spreadsheets and hardware description languages (like Verilog and VHDL).
Even in JavaScript, we've had them since the dawn of declarative JavaScript Frameworks. They've carried various names over time and come in and out of popularity over the years. But here we are again, and it is a good time to give a bit more context on how and why.
π₯ Follow @javascriptdaily π₯
https://dev.to/this-is-learning/the-evolution-of-signals-in-javascript-8ob
But they are not a new thing. Not even remotely if you consider you can trace roots back to research in the late 1960s. At its foundation is the same modeling that enabled the first electronic spreadsheets and hardware description languages (like Verilog and VHDL).
Even in JavaScript, we've had them since the dawn of declarative JavaScript Frameworks. They've carried various names over time and come in and out of popularity over the years. But here we are again, and it is a good time to give a bit more context on how and why.
π₯ Follow @javascriptdaily π₯
https://dev.to/this-is-learning/the-evolution-of-signals-in-javascript-8ob
DEV Community
The Evolution of Signals in JavaScript
There has been some buzz recently in the frontend world around the term "Signals". In seemingly short...
π8β€1π’1
2023 Web Framework Performance Report
- How do modern web frameworks compare in real-world usage & performance?
- Does framework choice influence a siteβs Core Web Vitals?
- How related is framework choice to JavaScript payload size, and what is the impact?
Take a look at the report by #FredSchott from #Astro. Please keep in mind of the methodology and limitations.
π₯ Follow @javascriptdaily π₯
https://astro.build/blog/2023-web-framework-performance-report/
- How do modern web frameworks compare in real-world usage & performance?
- Does framework choice influence a siteβs Core Web Vitals?
- How related is framework choice to JavaScript payload size, and what is the impact?
Take a look at the report by #FredSchott from #Astro. Please keep in mind of the methodology and limitations.
π₯ Follow @javascriptdaily π₯
https://astro.build/blog/2023-web-framework-performance-report/
Astro
2023 Web Framework Performance Report | Astro
A look at how different web frameworks perform in the real world in 2023. Based on real-world, production data from HTTP Archive and Google Chrome.
π2π₯°1
WTF Is Code Extraction
By #MiΕ‘koHevery (Builder.io / #Qwik)
We are full-stack developers! That means we write both client and server code. But where should we place the server and client code? Conventional wisdom says that we should put them in different files. Except, it is not so simple; we also have code that runs both on the server and client. After all, we do Server-side rendering (SSR), so most of our client code also runs on the server.
I want to challenge the conventional wisdom and convince you that there is an existing trend of putting server and client code together and that it is better. Letβs call it: βcode collocation.β
The idea of placing server and client code together is not new, and it is already happening in NextJS/Remix/SolidJS.
But we have a problem to solve. We need to provide code to the server and code to the client, and as of right now, server code canβt access the DOM API and client code canβt read server dependencies such as databases. So there needs to be a way to separate the code.
The act of separating the code and creating server and client code bundles is called code extraction. Three different strategies starting with the most basic to advanced ones, are:
- Export extraction
- Function extraction
- Closure extraction
Letβs dive into them.
π₯ Follow @javascriptdaily π₯
https://www.builder.io/blog/wtf-is-code-extraction
By #MiΕ‘koHevery (Builder.io / #Qwik)
We are full-stack developers! That means we write both client and server code. But where should we place the server and client code? Conventional wisdom says that we should put them in different files. Except, it is not so simple; we also have code that runs both on the server and client. After all, we do Server-side rendering (SSR), so most of our client code also runs on the server.
I want to challenge the conventional wisdom and convince you that there is an existing trend of putting server and client code together and that it is better. Letβs call it: βcode collocation.β
The idea of placing server and client code together is not new, and it is already happening in NextJS/Remix/SolidJS.
But we have a problem to solve. We need to provide code to the server and code to the client, and as of right now, server code canβt access the DOM API and client code canβt read server dependencies such as databases. So there needs to be a way to separate the code.
The act of separating the code and creating server and client code bundles is called code extraction. Three different strategies starting with the most basic to advanced ones, are:
- Export extraction
- Function extraction
- Closure extraction
Letβs dive into them.
π₯ Follow @javascriptdaily π₯
https://www.builder.io/blog/wtf-is-code-extraction
Builder.io
WTF Is Code Extraction
Code extraction allows you to collocate client and server code in the same file. Let's take this idea to 11.
π12π₯3β€2