Qishloqi 👨‍💻

New QUERY http verb just landed in RFC 10008 standard. It solves a couple real issues.

1. GET request bodies are not standardized across the web, any server/proxy/middleware decides what to do with it, and in most cases your GET bodies don't reach the sever.
2. This is just side effect of 1. That we're forced to cram everything into search params, there's (a) encoding instabilities and (b) length limits.
3. POST requests that we're using to send bodies for fetching resources can't be safely cached, and retried.

QUERY declares itself as safe and idempotent, it adds standard body to request that everyone who's implementing it must support. And your body can be of any type, as long as you supply/respect server's Accept-Query and send proper Content-Type. RFC states the cache key must incorporate URI, request body and it's Content-Type.

Moreover, to a QUERY request server can return headers Content-Location and Location. Content-Location is where results of your specific request are kept, and query is NOT re-executed on subsequent calls. Whereas Location is for re-runnig the query without sending the whole body for fresh data. You should be able to safely GET both locations.

Standard explicitly mentions not to use it for simple queries and encourages to rely on it once industry catches up.

https://datatracker.ietf.org/doc/html/rfc10008

https://tanstack.com/blog/search-params-are-state

https://dev.to/hijazi313/why-search-params-arent-the-state-management-silver-bullet-2doh

⚠️ 2k chars limit.

Also, I think search params state design should be part of the good UX.
User should be able to understand and edit them. I personally do it all the time when I use websites.

If you're somewhere near js. You have heard of Major GC, and Minor GC.

Now introducing, MomGC. It's got time complexity of O(1) thanks to no reference counting or tracking of what's in use. It'll randomly pick objects out of heap and free them.

Intensity can be set using --guests-coming-over flag.

https://youtu.be/sqm4-B07LsE?si=cfNEkNyQ3IVY5x9u

Rost aytyapti. 2-3 gapdan uzunroq postlar yozishga to'gri kelsa VIM ishlataman. O'rganib olingandan keyin, nafaqat kod balki plaintext bilan ishlash ham ancha oson bo'larkan.

Vim o'rgana boshlaganimda ishlatgan bazi manbalar (videoda ham bor):
https://vim-adventures.com/
https://devhints.io/vim
https://vim-racer.com/ ( https://vim-racer.com/game-mode/randomized/ ham sinab ko'ring)

Here, have my treat for lunch:

https://youtu.be/mYBxnojY-JA?si=zf4yKPwBSJInPNRO

Boomerang, palindrome, ping-pong playback bu video ohiriga yetganda qayta 1-kadrdan boshlanish o'rniga, ortga ohirgi kadrdan qaytib keladi - huddi bumerangdek.

Packagelarni check qilib qo'yinglar:

https://tanstack.com/blog/npm-supply-chain-compromise-postmortem#appendix-a--affected-versions

https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx