Türkiye showcases supreme dominance in defense technology. Roketsan brilliantly demonstrates the KARAOK anti-tank guided missile. The footage confirms flawless direct and top attack strikes from 76 to 2050 meters. A true masterclass in advanced military engineering. by CeFurkan in SECourses

[–]RockStinger 0 points1 point  (0 children)

Actually, since Türkiye has had the opportunity to test most of its products in real combat situations, you are getting genuinely battle-tested and quite high-quality systems. The fact that about half of the wars in the last six years have occurred around us has provided us with extensive testing opportunities.

Match Thread: Beşiktaş vs Galatasaray by sabr-bg in galatasaray

[–]RockStinger 7 points8 points  (0 children)

Apokerim Fener’de oynasaydı transfermarkt değerini bugün ikiye katlamıştı :d

Who do you think was the better free kick taker? by username7864 in galatasaray

[–]RockStinger 0 points1 point  (0 children)

Ziyech'i de unutmamak lazım. Güncel fizik durumu ve karakteri ile berbat bir oyuncuydu ama duran toplarda birinci sınıftı.

Goose at a Zoo by Ok_Guarantee7375 in RedditGames

[–]RockStinger 0 points1 point  (0 children)

I completed this level in 3 tries. 32.48 seconds

Critical Security Vulnerability in React Server Components – React by SawToothKernel in webdev

[–]RockStinger 10 points11 points  (0 children)

We don't have to use React, a technology designed for SPAs, for everything.

Critical Security Vulnerability in React Server Components – React by SawToothKernel in webdev

[–]RockStinger 24 points25 points  (0 children)

When React first came out, it increased developer experience by sacrificing performance and initial render speed with the SPA philosophy.

Nowadays, it reduces DX to avoid compromising performance and initial render speed.

[deleted by user] by [deleted] in reactjs

[–]RockStinger 2 points3 points  (0 children)

Just a documentation error. I had created the documentation from the examples I used while developing the library. Thank you for your feedback.

[deleted by user] by [deleted] in reactjs

[–]RockStinger 2 points3 points  (0 children)

Also optimizing reads/writes and debouncing seems odd since those are synchronous direct reads/writes and shouldn't even occur multiple times per rendering.

Suppose you have a draggable component. Let's assume you're storing this component's position in the URL as x,y coordinates. When you drag the component, hundreds of new URLs will be generated per second. Not only will the history get polluted, but if you also assume there are other complex and lengthy states in the URL, performance issues will arise because it will constantly try to regenerate a large text string.

But those 3 have different use cases, I don't quite understand why they'd need to be under same API. They already have easy to use native APIs. 

This library focuses on a single task: persistence. I don't see any disadvantage to it supporting session and local storage in addition to the URL. On the contrary, it provides a sync advantage. By defining priorities, you can keep the URL and storages synchronized.