Fr0sT.Brutal

Works for me

Oops my fault. Debian has no order in names. But Android and Ubuntu have. However Ubuntu changes names inside major releases which is also confusing. Example of insane naming is also MS Windows. 3.1, 95, 98, Millenium, NT, 2000, XP, Vista, 7, 8, 10, 11, ... In the same time server versions are named after years so you also have to remember - kernel of which "user" version has this server version 20XX?

If only they chose city names sorted like do Google Android, Debian, Ubuntu... but no, pure random. And ridiculously loooong name for 11. I have some really wonderful options for Succ(v12) releases: Schmedeswurtherwesterdeich Llanfair­pwllgwyngyll­gogery­chwyrn­drobwll­llan­tysilio­gogo­goch Taumatawhakatangi­hangakoauauotamatea­turipukakapikimaunga­horonukupokaiwhen­uakitanatahu and many more really cool names here https://en.wikipedia.org/wiki/List_of_long_place_names

Ah, that one. Workaround in fact. Well, you're right here - each approach has its pros and cons. So it's nice when you can choose

Easy, just add some anime kitties and giant robots to win their hearts! Or... giant kitty robots!

Haven't tried it myself but try moving a window beyond the screen (Window.X := Screen.X + someMargin)

Release it as 13.9 for double-hit!

WebDAV is just a protocol. You'll have both sides of your channel custom so you can extend it for your needs.

What's the 2nd solution? I guess it's not free? Well, the benefit is native implementation, free from insane upgrade policy of OpenSSL; moreover, RTL socket/http uses it as well, and so does default cURL build. To add more, there are some OpenSSL forks/analogs now (WolfSSL, BoringSSL) which could be more suitable for some needs. Abstraction of TLS layer would be awesome. Extending the subject wider, I periodically dream of a universal handler stack in TWSocket to enable things like Socket.handlers := [ ThrottleHandler, TLSHandler, HTTPTunnelHandler, TLSHandler ] (enable throttling, connect via TLS to HTTP tunnel proxy and do TLS connection to remote server) that would provide a simple interface for any combination of protocols. That way TTLSSocket would be nothing more than TWSocket with auto-created TLSHandler. Want cascade of 5 TLS HTTP tunnel proxies? No problem! Want HTTP inside MsgPack inside Protobuf inside TLS-encryption? Easy. Want custom encrypted protocol? Just write handler. Please don't take this as criticism, I admire your efforts to keep ICS up-to-date.

Ah, blimey. That "U" was a phantom in my eyes. Friday 🙂

Quite a non-trivial task if there's an intensive data stream over one channel while control channel must remain responsible.

They just use OBJ just like with Zip and RegExp

Code formatter Depends on modelling Written in .Net Seems like a candidate for "Top most weird tech decisions"

And even if the lib is not ready, in most cases it's enough to use package for the latest version.

So the typical "List.Count - 1" construction now emits "unsigned converted to signed" warning? Well done, EMB. From my experience: unsigned numbers are inconvenient. Once you want to use a subtraction op, you get lots of warnings. And the apogee of lurking bug: i: Cardinal; for i := 0 to List.Count - 1 do on an empty list which, with int overflow checks disabled, will either raise OutOfBounds on index 4B or loop 4B times - depending on a body.