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
JavaScript Daily
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?β¦
#EvanYou thread on the report...
π₯ Follow @javascriptdaily π₯
https://twitter.com/youyuxi/status/1633249827755814912
π₯ Follow @javascriptdaily π₯
https://twitter.com/youyuxi/status/1633249827755814912
Twitter
I have a lot of respect for the work the Astro team has been doing, but I want to share some important caveats that everyone should be aware of when reading, and especially publishing this kind of reports: (0/n)
π2π1
Web component JS frameworks overview by their syntax and features
https://component-party.dev
π₯ Follow @javascriptdaily π₯
https://component-party.dev
π₯ Follow @javascriptdaily π₯
component-party.dev
Component Party
Web component JS frameworks overview by their syntax and features: Svelte 5, React, Vue 3, Angular Renaissance, Angular, Lit, Ember Octane, Solid.js, Svelte 4, Vue 2, Alpine, Ember Polaris, Mithril, Aurelia 2, Qwik, Marko, Aurelia 1
π15π₯1π1
TypeScript 5.0 rebuilt to use ECMAScript modules
With TypeScript 5.0, the TypeScript development team has restructured the entire codebase to use ECMAScript modules, reducing package size and improving performance.
TypeScript 5.0, due from Microsoft as a production release on March 16, has been restructured around the use of ECMAScript modules, a major infrastructure change for the strongly typed JavaScript variant.
Users of TypeScript 5.0, which currently is in a release candidate stage, will need to run Node.js 12 at a minimum. In return, npm installs promise to execute a little faster and take up less space, with the typescript package sized reduced by roughly 46%, Microsoft said in a March 9 bulletin. TypeScript too will be faster, with build times cut by 10% to 25%. API consumers of TypeScript likely will be unaffected.
π₯ Follow @javascriptdaily π₯
https://www.infoworld.com/article/3690342/typescript-50-rebuilt-to-use-ecmascript-modules.html
With TypeScript 5.0, the TypeScript development team has restructured the entire codebase to use ECMAScript modules, reducing package size and improving performance.
TypeScript 5.0, due from Microsoft as a production release on March 16, has been restructured around the use of ECMAScript modules, a major infrastructure change for the strongly typed JavaScript variant.
Users of TypeScript 5.0, which currently is in a release candidate stage, will need to run Node.js 12 at a minimum. In return, npm installs promise to execute a little faster and take up less space, with the typescript package sized reduced by roughly 46%, Microsoft said in a March 9 bulletin. TypeScript too will be faster, with build times cut by 10% to 25%. API consumers of TypeScript likely will be unaffected.
π₯ Follow @javascriptdaily π₯
https://www.infoworld.com/article/3690342/typescript-50-rebuilt-to-use-ecmascript-modules.html
InfoWorld
TypeScript 5.0 rebuilt to use ECMAScript modules
With TypeScript 5.0, the TypeScript development team has restructured the entire codebase to use ECMAScript modules, reducing package size and improving performance.
π6β€1
32 Awesome JavaScript Snippets (one-liners) You Should Use
Some useful JavaScript stuff I have saved and I think it can help make your life as a developer easier.
π₯ Follow @javascriptdaily π₯
https://www.rahul.biz/blog/32-javascript-snippets
Some useful JavaScript stuff I have saved and I think it can help make your life as a developer easier.
π₯ Follow @javascriptdaily π₯
https://www.rahul.biz/blog/32-javascript-snippets
π13β€3π₯2π₯°1π1π1
π3
ECMAScript excitement π
These proposals advanced #TC39 this week π
3οΈβ£ Async Explicit Resource Mgmt
3οΈβ£ Import Attributes (*)
2οΈβ£ AsyncContext
2οΈβ£ Float16Array
2οΈβ£ Iterator.range
1οΈβ£ Await Dictionary
1οΈβ£ Class Method Param Decorators
1οΈβ£ Promise.withResolvers
1οΈβ£ TZ Canonicalization
π₯ Follow @javascriptdaily π₯
These proposals advanced #TC39 this week π
3οΈβ£ Async Explicit Resource Mgmt
3οΈβ£ Import Attributes (*)
2οΈβ£ AsyncContext
2οΈβ£ Float16Array
2οΈβ£ Iterator.range
1οΈβ£ Await Dictionary
1οΈβ£ Class Method Param Decorators
1οΈβ£ Promise.withResolvers
1οΈβ£ TZ Canonicalization
π₯ Follow @javascriptdaily π₯
π20β€2π1
What's the best article you've read in the JavaScript or front-end space lately?
π2
Storybook provides a workshop to build UIs in isolation. It helps you develop hard-to-reach states and edge cases without needing to run the whole app.
https://storybook.js.org/
https://storybook.js.org/
Storybook
Storybook: Frontend workshop for UI development
Storybook is a frontend workshop for building UI components and pages in isolation. Thousands of teams use it for UI development, testing, and documentation. It's open source and free.
π21π₯°3π₯2
JavaScript based, automated data exploratory analysis and visualization tools. (Licence: AGPLv3)
https://github.com/Kanaries/Rath
https://github.com/Kanaries/Rath
GitHub
GitHub - Kanaries/Rath: Next generation of automated data exploratory analysis and visualization platform.
Next generation of automated data exploratory analysis and visualization platform. - Kanaries/Rath
π4π₯3β€1
Dear Oracle, Please Release the JavaScript Trademark
Ryan Dahl
2022-09-03
In 1995 Netscape partnered with Sun Microsystems to create interactive websites. Famously Brendan Eich spent only 10 days to create the first version of JavaScript - a dynamic programming language with a roughly syntactic lineage from Sunβs Java language. As a result of this partnership Sun held the trademark βJavaScriptβ. In 2009 Oracle acquired Sun Microsystems and the JavaScript trademark as a result.
The trademark has no commercial value. Other than Oracle's JavaScript Extension Toolkit, Oracle does not have any products using the trademark and presumably no planned usage. Oracle doesnβt even participate in the development of any of the JavaScript engines like V8, JavaScriptCore, or Spidermonkey. It seems very likely that JavaScript trademark infringement would be unenforceable in court due to non-use.
Nevertheless the trademark is a dark cloud looming over the worldβs most popular programming language. Careful law abiding engineers bend over backwards to avoid its use - leading to confusing terms like ECMAScript.
The best value Oracle could derive from the trademark would be from the goodwill it receives by granting it into the public domain. Itβs understandable why this hasnβt yet happened - it would require a very forward thinking and high level Oracle employee to propose something so intangible. Yet it is obviously the right move to trade a worthless trademark for brand marketing and goodwill.
Oracle, please release the JavaScript trademark.
Source: https://tinyclouds.org/trademark
π₯ Follow @javascriptdaily π₯
Ryan Dahl
2022-09-03
In 1995 Netscape partnered with Sun Microsystems to create interactive websites. Famously Brendan Eich spent only 10 days to create the first version of JavaScript - a dynamic programming language with a roughly syntactic lineage from Sunβs Java language. As a result of this partnership Sun held the trademark βJavaScriptβ. In 2009 Oracle acquired Sun Microsystems and the JavaScript trademark as a result.
The trademark has no commercial value. Other than Oracle's JavaScript Extension Toolkit, Oracle does not have any products using the trademark and presumably no planned usage. Oracle doesnβt even participate in the development of any of the JavaScript engines like V8, JavaScriptCore, or Spidermonkey. It seems very likely that JavaScript trademark infringement would be unenforceable in court due to non-use.
Nevertheless the trademark is a dark cloud looming over the worldβs most popular programming language. Careful law abiding engineers bend over backwards to avoid its use - leading to confusing terms like ECMAScript.
The best value Oracle could derive from the trademark would be from the goodwill it receives by granting it into the public domain. Itβs understandable why this hasnβt yet happened - it would require a very forward thinking and high level Oracle employee to propose something so intangible. Yet it is obviously the right move to trade a worthless trademark for brand marketing and goodwill.
Oracle, please release the JavaScript trademark.
Source: https://tinyclouds.org/trademark
π₯ Follow @javascriptdaily π₯
Oracle
Oracle JavaScript Extension Toolkit (JET)
Oracle JET - JavaScript Extension Toolkit
π9π1