Israel Olvera

Staff Engineer at @HTech

[Israel Olvera @SkrigueztepDev]

"The 'elvis' operator"!!!.... (?.) 😆🤣😂

[Web Standards @webstandardsdev]

What’s new in Chrome 153. The <camera> and <microphone> elements request media capture declaratively, overflow: scroll clip makes a scroll container on one axis only, and https://t.co/bIwugzjZbO() aggregates several iterators at once. #chrome #browser

https://t.co/JSLJ6QYLt3

[Cloudflare @Cloudflare]

Workers now enables Node.js compatibility by default, supports applications up to 64 mebibytes, and adds a URL-based module registry with import.meta, lazy compilation, shared code caches, and clearer errors. https://t.co/eZxSlcNnLQ

[RustRover, a JetBrains IDE @rustrover]

Have you tried Topcoat, the framework released this summer by the Tokio team?

If not, a Topcoat Tutorial: Full-Stack Rust Web Apps for Beginners just dropped for you.

Watch it, build it, and enjoy the batteries – they’re included 🔋🦀
https://t.co/rzaGiaapYy

[Chrome for Developers @ChromiumDev]

The new Chrome release cycle is here! https://t.co/ywuHgEKDMS

[Chrome for Developers @ChromiumDev]

Handling protected APIs clipboard access, fullscreen mode, or media autoplay requires knowing if a visitor is actively engaged.

The UserActivation API provides clear details about whether a user is interacting with your page or has done so since loading → https://t.co/moSj86a3ST

[Viacheslav Biriukov @brk0v]

🦀 Rust: How Cloudflare saved 100 TB of DNS cache memory.

Fewer allocations, tighter layout: replace Vec with Box, remove repeated data, and pack records into a contiguous byte buffer.

Result: 56% less memory per entry and 19% faster lookups.

https://t.co/scHmcqog7j
#rust #rustlang

[Chrome for Developers @ChromiumDev]

Here's what's new in Modern Web Guidance v0.0.186 → https://t.co/ZzH2rnoZgu

⌨️ New guide on IME-safe textarea submission, along with recs for handling KeyboardEvent.isComposing for IME

🔎 Mandatory code verification step for agents in the global MWG skill

[Miguel Ángel Durán @midudev]

¡Histórico! CSS tendrá propiedad "size".
Un atajo para determinar el width y height.

✓ size: 100px → width y height iguales
✓ size: 200px 80px → ancho y alto
✓ Soporta las unidades de width y height

Llevaba más de 10 años parado y por fin se aceptó.
Safari ya lo implementa detrás de un flag.

[Rspack @rspack_dev]

🦀 Rslib 1.0 is here!

📦 Multiple output formats, including Module Federation
🔀 Bundled or bundleless
⚛️ Component libraries across frameworks
🎨 Built-in CSS and asset support
🔵 TypeScript 7 support for fast declarations

See what's new in Rslib 1.0 👇
https://t.co/xnZ3PpAAVs

[Astro @astrodotbuild]

Astro 7.3 is out: --ignore-lock for astro preview, a runtime logger for custom image services and cache providers, and a finalize() helper for Cloudflare custom worker entrypoints.

https://t.co/0cQjujZvFX

[Miguel Ángel Durán @midudev]

¿Tu IA siempre crea la misma UI? ¡Prueba esto!

Una colección de archivos DESIGN.md con el sistema visual de marcas reales:
Apple, Airbnb, Tesla, Shopify, Stripe, Notion…

Colores, tipografía, espacios, componentes:
→ https://t.co/66H3JKE1fd

[Cloudflare @Cloudflare]

At 250 billion DNS cache entries, one wasted byte costs 250 GB of RAM.

Five Rust optimizations later: 100 TB freed, inserts 43% faster, lookups 19% faster.

We didn't trade speed for space. https://t.co/mMyOYnj0mQ

[Viacheslav Biriukov @brk0v]

🐹 Go: a must-read deep dive into data races and the memory model

Why code that works can still be wrong:
• memory visibility between goroutines
• compiler & CPU reordering
• happens-before guarantees
• atomics, mutexes, channels

https://t.co/hNyDyiZvDm
#golang #go

[No Trust Sec @NoTrustSec]

🍯🍯🍯

[freeCodeCamp.org @freeCodeCamp]

You may have heard about microservices and how they can help with back-end development.

Well, microfrontends represent a similar concept for front-end projects - and Rahul teaches you about them here.

You'll learn about different approaches to creating microfrontends so you can decide which best fits your use case.

https://t.co/gW47Sahzbq

[Buf @bufbuild]

Introducing https://t.co/UyBXPQLaQK a visual, interactive guide to Protocol Buffers.

[Bun @bunjavascript]

Bun 1.4

- Fixes over 2,900 GitHub issues
- +1,517 tests from the Node.js test suite
- Reduces idle CPU by 5x
- Reduces memory usage by up to 35%
- Starts up to 50% faster on Linux
- Rewrites Bun in Rust

Thank you everyone who contributed since Bun 1.3!

https://t.co/3YjnuhjE8s

[ayush🔮👨‍💻🔮 @ayushagarwal027]

The #2 most reported Rust annoyance (right after compile speed) is about to shrink. 🦀

Big target directories were the second most common complaint in the 2025 State of Rust survey. One real cause: Cargo has been storing the same crate metadata twice on disk, once in the .rmeta file (produced early, so dependent crates can start compiling sooner) and again inside the final .rlib file.

Cargo will soon default to -Zembed-metadata=no on nightly, which stops embedding that duplicate metadata into .rlib files.

Real measured numbers, compiling serde and Cargo itself:
→ Release profile, no debug info: up to 33% smaller target directory
→ Cargo's own release build: ~300 MiB saved in absolute terms
→ Dev profile with incremental + debuginfo: a more modest ~5-8%, since debug info and incremental artifacts dominate there anyway

Most people won't notice anything except a smaller target directory. The only real edge case: if you link .rlib files manually outside of normal Cargo builds, you may now need to pass the matching .rmeta file explicitly.

Nightly only for now, with stabilization planned if the rollout goes smoothly. Opt-out available via CARGO_UNSTABLE_EMBED_METADATA=true if you hit issues.

Small on its own, but with survey data showing how many people this genuinely affects.

🔗 https://t.co/cgsMUK3nQZ

#RustLang #Cargo #DevTools #OpenSource

[Cloudflare @Cloudflare]

We found a working remote Spectre attack against Cloudflare Workers. We already fixed it. No exploitation in the wild. Blog post and paper out now:
https://t.co/okdulUT1yB

[Chrome for Developers @ChromiumDev]

We are looking for a few more developers to join our WebDev Insights community → https://t.co/Kpch6QC8s9

This is your chance to participate in user research, test out experimental tools, and directly shape upcoming Chrome features. Grab one of the last spots and help us build the future of the web ecosystem.