303 private links
A great FAQs. CommonJS and ESM is still a mess, especially. Yes I am looking at you NestJS.
Topics covered:
How can I move my CommonJS project to ESM?
Can I import ESM packages in my TypeScript project?
How can I make my TypeScript project output ESM?
How can I import ESM in Electron?
I'm having problems with ESM and Jest
- Implement the Copy trait
- Take parameters by reference
- Use the proper iterator
- Have closures capturing by value also return the value
It's self-explanatory based on the semantic!
The bun single binary performs better!
An introduction from unsafe to safe Rust lifetimes
The boilerplate needed, the first metadata title, link, description and the many additional optional values.
Dates in RSS conform to RFC 882
Each RSS feed has items. Each feed can contain the entire content, unabridged, or a summary of the content and that it should be read on the site.
Atom is XML-based but is a little bit stricter and more finely specced than RSS.
JSON feed is the newest format discussed around. It has similarly.
RSS can be auto-discovered with the link tag in HTML.
Gotchas:
- use absolute URLs for media in the RSS feed. RSS Readers can be disconnected from the origianl domain.
- escape HTML entities in XML or use CDATA wrappers.
- Web-based RSS readers have CORS rules to follow. Setting an
Access-Control-Allow-Origin: *is mandatory header on your XML/JSON files ensures these web-based clients don’t get blocked by security policies. - the readers have limited display
- validation via the W3C Feed Validation Service or the JSON Feed Validator.
Read the RSS 2.0 Specification, the Introduction to Atom, the RFC 4287: The atom syndication format or the JSON feed version 1.1 Explainer.
- Share immutable data in threads
- Mutex while sharing mutable data
An recommended example is provided in the "[Fearless Concurrency]"(https://blog.rust-lang.org/2017/11/14/Fearless-Concurrency-In-Firefox-Quantum.html) post of Mozilla about the success they has in parallelizing the CSS renderer.
A feedback about handling errors properly instead of a one big error enum.
Some CSS variables are computed in JS, and the rest is made by CSS and the browser. Each item is a <div>:
<div class="wall" style="
--start-x: 2560;
--start-y: -2112;
--end-x: 2560;
--end-y: -2496;
--floor-z: 32;
--ceiling-z: 88;
">All the geometry calculation is made in the browser.
JavaScript passes raw DOOM data in. CSS does the trigonometry.
JavaScript runs the game loop. CSS does the rendering.
Beyond border-radius: What The CSS corner-shape Property Unlocks For Everyday UI — Smashing Magazine
As the time of writing, the browser support is 66%
It works in <svg> tags:
<style>
.bg {
fill: #ffffff;
@media (prefers-color-scheme: dark) {
fill: #000000;
}
}
</style>wrappers, pgrx, pgdog, ParadeDB, Neon (Postgres in S3)
It's a cheap version for liquid glass with backdrop-filter: blur(10px) brightness(120%); :D
I didn't read it but look after the strategies: sequences with serial IDs, for update skip locked
So, it's a matter of your requirements. If you need massive scale and throughput (> 100k messages/sec), Kafka will be hard to beat. But if you're not operating at that scale, Postgres is hard to beat.
So, it's a matter of your requirements. If you need massive scale and throughput (> 100k messages/sec), Kafka will be hard to beat. But if you're not operating at that scale, Postgres is hard to beat.
No event listeners. No state tracking. No ARIA updates handled in JavaScript. I focused the button, and the tooltip appeared. I pressed the Esc key, and it disappeared.
popovertargetconnects the button to a popover elementpopovertargetactionspecifies what should happen (show, hide, toggle as default)popoverdeclares an HTML element can be targeted bypopovertarget(ou.showPopover())
Note Floating UI already solves many of these issues. CSS anchor positioning should solve most of the layout stuff
