valbu

Why am I hearing about that specific FW in year 2026, this seems really good, at least the features written if it really supports rules based on parent processes, wildcards, SvcHost granularity without gotchas. Been wrangling with Windows FW for ages, trying to get some badly behaved programs to update like Discord, Teams and others that change install paths or updater executable names or hiddenly use msedgewebview2. PolicyAppId and tagging based rules have given some success but Windows FW is still really broken. Definitely giving Fort a try.

Still use Winamp (actually WACUP) with Milkdrop visualizations almost every day. But true that streaming audio players are so basic featureless pieces of software.

I think the SQL example should be bit more extreme, the count() group by is quite common and has just linear scaling and is plenty fast for majority of use cases. Tested with 1 process thread, 1k stars = 0.285ms; 10k = 2.85 ms; (and 0.1k = 45us that is same as overhead or just selecting 1 row without join and group by). So with 1k stars you need the system to average 3500 calls/s to saturate 1 thread or have meaningful latency impact. Sure, for bigger IO or row counts this does not scale and materialized view is indeed >100x faster.

Yeah it's clear as day that this is the regular old Russian tactic to intimidate or attack and then deny, even tho everyone knows they are behind this.

The pipelines were already closed and will not open in a decade or two anyway because the war and politics. They do not lose any income so why not use it to terrorize and escalate, it's not their first time to mess with foreign underwater infrastructure. Norway->Poland pileline opening is the perfect timing for that.

Not often do I find a comment that brings up very similar experience. Had intermittent data corruption because memory bit error on very upper range that almost always was unused and went unnotced a long time. ZFS backend PC was actually ok, it was main PC that used the share but point remains. After that no more non-ECC memory ever on any computer for me (ok except some laptops).

Because that is completely different approach. When using TST extension then "tab" is like bookmark + history element and not in your short term memory. One of the advantages over those is that visual overview is almost instant and so much clearer with structured tab trees with long descriptive tab names. It reduces brain strain as I no longer have to relay on blind searches in history and bookmakrs menu, google and notes in documents.

For example when getting into some game then all the guides, tips, videos, maps, mods etc. are open below one master tab and it is very easy to go back there after every month or so, back and forward works on tabs and you are like exactly back in this moment where had to stop that time. One such subject domain can be like 50 or sometimes 100 tabs and if your interests and work over about a year revolve around 30 subjects then few thousand tab-s is quite normal usage. Firefox + TST works with max 7999 tabs so there is quite some room.

I think the easily manageable high tab count is not even the primary advantage for starters, the fixed tab width with vertical tabs is as tab label is always visible and usually horizontal screen space is wasted anyway. Then comes the tree structure advantages and then the paradigm change to tabs as usable history when tab count is high.