Jan Ringoš

TRIM CORE SOFTWARE s.r.o. @trimcore systems engineer and C++ programmer

[Jan Ringoš @JanRingos]

@adent Mě do dnešního dne neskutečně štve, že nám na FB unahlašovali „Klub chovatelů bonsai koťátek.“

[Jan Ringoš @JanRingos]

@itanium_guy @XenoPanther I wish these kind of videos were still made. Even about tiny changes. I'd watch ~10 minute talks on... from how and why was the legacy USER32 desktop color, pattern and wallpaper support removed, to some implementation details of RIO sockets.

[Jan Ringoš @JanRingos]

@CRoPlus No hezky. Damoklův meč hrozí a půlka národa volá po úplném zrušení ČT a ČRo bez náhrady, tak najednou to jde reportovat pravdu a realitu.

[Jan Ringoš @JanRingos]

@SheriefFYI Too late 🫣

[Jan Ringoš @JanRingos]

@PPeckova „Sebevražedná empatie.“

[Jan Ringoš @JanRingos]

@Galvestz @Windows Well, they HAD TO make fonts bigger for the text to be readable. And to be "modern".

[Jan Ringoš @JanRingos]

@Potvora100 @rkaldy Svět by pro nás byl mnohem krásnější.

[Jan Ringoš @JanRingos]

@XenoPanther This is the second video I remembered. It was about threadpools. Not relevant, but this is it: https://t.co/R0m8KvTDr1

[Jan Ringoš @JanRingos]

Yeah, it was bad.

Back in the day one of our customers run dual NetBurst Xeon (so 2×2 cores IIRC) with a whooping 8 GB RAM on 32-bit 2003 R2 and it was PAIN maintaining the SW for it. You added a field to structure somewhere and the whole thing slowed to crawl because it somewhere straggled cache line.

You might find interesting this video, where Arun Kishan (but I could've sworn it was @itanium_guy) explains how they rewrote it:
https://t.co/fU2yXIXnPh

[Jan Ringoš @JanRingos]

@PetrHonzejk Pro svobodomyslnou společnost fungující na ideálech rovnosti a tolerance by mělo být neakceptovatelné importovat negramotné divochy, kterým jsou tyto ideály pro smích a považují je za známku slabosti hodnou akorát využití.

[Jan Ringoš @JanRingos]

IDK about networking. We'd obviously want the best performance, but over my career the most performant way to network (in Windows) changed several times.

Nonblocking sockets -> WSAEventSelect -> overlapped -> I/O completion ports -> and finally RIO sockets.

The API will be modelled after one approach and then inevitably new, better and incompatible approach will be invented.

[Jan Ringoš @JanRingos]

@SapphoSys cmd.exe's "ver" command should display something like that

[Jan Ringoš @JanRingos]

@XenoPanther My System process is running 3200 threads:

[Jan Ringoš @JanRingos]

@NedjoK Yeah

[Jan Ringoš @JanRingos]

With all those new ARM server CPUs, are we finally going to get official Windows Server for ARM?

[Jan Ringoš @JanRingos]

Why is NamedPipeEventSelect not documented? Sounds very useful.

[Jan Ringoš @JanRingos]

@phantomofearth I'm curious if the whole underlaying issue was fixed, or if it's just this one dialog doing some mitigation, and if it is that, then what is it doing precisely, so I can replicate it in my apps.

[Jan Ringoš @JanRingos]

Finally, @reactos is booting in Hyper-V again, and I can start testing my apps. Well, some of them.

[Jan Ringoš @JanRingos]

@MarekKnapek @twtayaan A true old school programmer.