Qishloqi 👨‍💻

4 hours of sleep = 4 shots of espresso. And I'm back at it on a Saturday

I think this is important:

https://keepandroidopen.org/

Android 17 is the first since 3.x to add new APIs without releasing to the AOSP
Article, Comments

Tmuxda bir nechta windowlarda Claude sessionlarni ishlatsangiz qo'l keladi:

https://github.com/abdulaziz-srp/claude-tmux-window-sync/blob/main/README.md


README.md faylni claudega copy paste qiling yoki shunchaki linkni tashlab bering. O'zi o'rnatib oladi.


@qishloqi_uz

The hub is down. Uyga boringlar ish vaqti tugadi deyapti shekilli ))

Hallo, halloo

Behind the scenes of Bun install.

#article #bun #js
@thedevs

https://thedevs.link/Tf3nU5

Weekend

Yaxshi maslahatlar

They announced TypeScript 7.0.


Let's goo!

@qishloqi_uz

Landed a SWE role at Silk Road Professionals Fergana. The hiring rounds were some of the most unique I've been through. Totally new stack, new environment, new language. I'm excited to learn and teach a lot.

What stood out to me was everyone's enthusiasm for optimizing processes and systems across the whole company.

@qishloqi_uz

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.

Read the spec.

@qishloqi_dev

Saw someone do this with metamethods. Looked interesting.

Your version?

@qishloqi_uz

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.

@qishloqi_dev

The Labor Illusion: How Operational
Transparency Increases Perceived Value

@qishloqi_dev

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.

@qishloqi_dev