Tootfinder

Opt-in global Mastodon full text search. Join the index!

@frankel@mastodon.top
2026-04-30 17:15:00

Why I don’t #chain everything in #JavaScript anymore
allthingssmitty.com/2026/04/2…

Why I don't chain everything in JavaScript anymore - Matt Smith
JavaScript chaining looks clean at first, but it can hurt readability and hide extra work. Here's when to break chains into simpler steps.

@cheeaun@mastodon.social
2026-03-04 01:23:50

Always forgetting to use `.at(-1)` to get last element in an array.
#JavaScript

@mrysav@social.linux.pizza
2026-03-05 02:49:21

It's honestly kind of impressive how much raw compute `npm install` can just suck down. #javascript #jshate

@aral@mastodon.ar.al
2026-02-11 16:50:05

Made a little logo for JSDB (JavaScript Database)
Better (six years) late than never? :)
#JavaScriptDatabase

JavaScript Database (JSDB) logo: it’s the common flowchart symbol for a database (stacked cylinders based on the disk packs used in early computing) on the lower right-hand corner of a yellow background. The yellow is the colour of the JavaScript icon and the location of the database symbol matches where the JS letters are on the JavaScript logo.
@cyrevolt@mastodon.social
2026-02-10 12:37:33

In case anyone finds #JavaScript for #UEFI funny/weird...
news.ycombinator.com/item?id=4

@kubikpixel@chaos.social
2026-02-15 10:10:18

npmx
A fast, modern browser for the npm registry.
./ #javascript #npm

npmx - Package Browser for the npm Registry
a fast, modern browser for the npm registry. Search, browse, and explore packages with a modern interface.

@simon_brooke@mastodon.scot
2026-03-15 10:58:28

"The code points represent every letter of the US alphabet when fed to computers, but their output is completely invisible to humans. People reviewing code or using static analysis tools see only whitespace or blank lines. To a #JavaScript interpreter, the code points translate into executable code."
Sigh.

Supply-chain attack using invisible code hits GitHub and other repositories
Unicode that's invisible to the human eye was largely abandoned—until attackers took notice.

@benny@norden.social
2026-04-06 17:00:05

JavaScript-Rendering kostet Google Geld. Pro Seite. Bei jedem Crawl. 💸Googlebot muss für JS-lastige Seiten eine Headless-Chrome-Instanz starten, DOM rendern und auf API-Responses warten. Bei 50.000 URLs summiert sich das. Wenn Google entscheiden muss, wo Rendering-Budget hinfließt – wer sagt, dass es dein Shop ist? Server-Side Rendering ist kein Nice-to-have, sondern Crawl-Effizienz.
#JavaScriptSEO