with several browsers happy to automatically download whatever is provided to them, making a user download a libblahblah.so is relatively easy, and unless the user was aware of the ramifications of just even having such a file in a folder, might ls, cat, grep, etc in that folder like they do any other day
However, most of the latest versions of the mainstream browsers now intentionally avoid writing out such files to the downloads folder unless the end user specifically OKs it (due to situations like this!)
you can postpone general updates while still having critical/security updates go through at the normal pace
And, shouldn't a workplace be setup for re-imaging if updates go wrong? I know its easy to just store files in C:\user\name\documents, but then it makes it just as easy to be forced to pay $300 for each computer in the network
Many of these systems infected are server systems, not End User Desktops.
That said, yes in a perfect world everyone would have perfect backups, and perfect imaging systems that makes ransomeware a non-event, we do not live in a perfect world and it is easy to monday morning QB the IT Staff.
Most IT depts are understaffed and corners are cut because you have to keep your head above water, business do not want to pay for proper staff or proper infrastructure,
IT is a "cost center" that should be cut every year in perpetuity, after all everything is working so why do I need to pay you to sit there all day
The thing is, Niantic learnt one bad thing from Google: The habit of near-zero community interaction and support.
The player base for Pokemon Go felt very frustrated at multiple times (especially anyone who had a rooted phone, completely disallowed to play, but that didn't stop cheaters!)
They only very recently added PR members to the probably largest PokemonGo forum around, https://redd.it/68nxzx
I don't think anyone really is angered by a modular system, its more the needing-to-pay-attention-to-every-little-bit (especially when those bits are mixed up in really poor naming, corporate speak, etc) is the more practical issue
As far as Alacritty is concerned, modularity can easily come with a cost.
once you add in e.g. tmux for multiplexing and scrollback, then you are bottlenecked at tmux's speeds, as opposed to the terminal emulator's speeds (not like it really matters, but its an interesting effect)
That will be interesting for the tmux (or do we go all the way to nurses??) developers, because tmux has probably always been way faster than any terminal emulator it has been running in.
def on_connection:
send(headers)
send(start of page)
for row in db:
send(row)
send(footer)
will have the exact same effect as what you said (not like that applies regardless, I don't think jinja outputs partial renders, since its made for flask)
The performance comparison is between python managed green threads, and OS managed actual threads. You don't get any new features
Another point is your server can switch context to handle other requests with async.
In real world, your web page consists more than one db (like mysql + redis + some RPC calls to microservices) queries, with async apis, you can concurrently request for all queries at once and join them all at rendering.
The async benefits can add up to a much faster responsive server.
However, most of the latest versions of the mainstream browsers now intentionally avoid writing out such files to the downloads folder unless the end user specifically OKs it (due to situations like this!)