JavaScript Daily

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 🔥

JavaScript based, automated data exploratory analysis and visualization tools. (Licence: AGPLv3) https://github.com/Kanaries/Rath

What JavaScript concepts did you understand embarassingly late?

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/

What's the best article you've read in the JS or front-end space lately?

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 🔥

What do you think? https://react.dev/learn/start-a-new-react-project

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

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

Web component JS frameworks overview by their syntax and features https://component-party.dev

#EvanYou thread on the report... 🔥 Follow @javascriptdaily 🔥 https://twitter.com/youyuxi/status/1633249827755814912

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. https://www.builder.io/blog/wtf-is-code-extraction

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. https://astro.build/blog/2023-web-framework-performance-report/

import function from "something.js"; https://www.freecodecamp.org/news/javascript-modules/

There wouldn't be any need to use Typescript? https://dev.to/smpnjn/types-may-finally-be-coming-to-javascript-56a2