December 12, 2023  |
Dear readers!
We are taking our end-of-the-year break and will be back on 23 January 2024.
Be well and see you soon!
Axel and Jowe |
|
|
|
|
|
|
Turborepo 1.11turbo.build @gsoltis@mastodon.social github.com/chris-olszewski github.com/NicholasLYang github.com/arlyon [Quoting the blog post:]
Turborepo 1.11 completes our migration to Rust and ships several developer experience improvements:
- Our new Rust-based foundation: We've finished the port from Go to lay the groundwork for better performance, improved stability, and new features.
- Group logs for improved readability: You can now specify
--log-order=grouped to organize your logs into distinct sections separated by tasks.
- Updated examples: Start with an example for Next.js, Svelte, Remix, Nuxt, and more.
|
|
|
|
Stop nesting ternaries in JavaScriptwww.sonarsource.com @philnash@mastodon.social “Prettier, the most popular JavaScript code formatter, recently released a novel way to format nested ternaries under an experimental flag. This has come after years of disagreement over the best and most readable way to format a nested ternary.”
“I have a better idea of how to make nested ternaries clearer: stop nesting them.” |
|
You don’t need JavaScript for thatwww.htmhell.dev @Kilian@mastodon.social “Rule of least power: [...] Choose the least powerful language suitable for a given purpose. On the web this means preferring HTML over CSS, and then CSS over JavaScript.”
“You might be thinking ‘All the things I use JS for, I need JS for’. That might be true, but it’s good to know that both browser makers and specification writers have been porting a lot of functionality over to CSS and HTML that up to a few years ago needed JS. And that’s what this article is about.” |
|
|
Linear matching of JavaScript regular expressionsarxiv.org github.com/Aurele-Barriere github.com/cpitclaudel “This paper provides a novel perspective on JavaScript’s regex semantics by identifying a larger-than-previously-understood subset of the language that can be matched with linear time guarantees. In the process, we discover several cases where state-of-the-art algorithms were either wrong (semantically incorrect), inefficient (suffering from superlinear complexity) or excessively restrictive (assuming certain features could not be matched linearly).” |
|
|
This email was sent to {{ email | default }}. You can unsubscribe from this list here or update your preferences. |
|