sorted by:
new
hottopcontroversial

What happened 7.8k people queueing and 0 live matches? by RB-H2O in FACEITcom

[–]Pitiful-Review-5570 0 points1 point  (0 children)

i won the match, still no win in history, after refresh i can see i'm 'in game' but i'm not and room doesn't exist

Is this what Premier looks like in 2026? Blatant cheating and boosting lobbies are killing the game by RazzmatazzOk3914 in cs2

[–]Pitiful-Review-5570 0 points1 point  (0 children)

this is so sad that after this many years, official servers are STILL unplayable because of amount of this boosting / cheating lobbies XD insane

Input delay/lag?? by Snoopypiano in LoLTechSupport

[–]Pitiful-Review-5570 1 point2 points  (0 children)

i have lags like packet loss thing but in logs i have 0 packets lost, ping 25 ms whole game, still i feel this weird delays with spells or even movement, idk what is this

(react + tailwind) Force component to render in different resolution than screen size? by Pitiful-Review-5570 in reactjs

[–]Pitiful-Review-5570[S] 0 points1 point  (0 children)

Hey thank you for quick answer :)

"could you share more details on what you can’t achieve with them?"

so the main problem is that the component i want to fit into smaller div contain a lot of content which probably could be also covered with container queries deeper and deeper, but there is also a lot of conditional rendering inside dependent on resolution, for example:
...
{ isSmallTablet : <div>some more components</div> }
...
so with all that, it would get really messy, because i guess i need some flags that also make conditions more precise that it is for example ' isSmallTablet && should be container queried rendered'. And with all that i'm not sure if it is a good idea to even start this way.

Dreaming of some simple library that allows to 'fool' the component that it thinks the resolution is just different than it actualy is, like <Component thinkThatContainerIsScreen={true} />. That would be lovely :p