coleifer

What are the use-cases, and when would such a policy have led to a drastically different outcome (in the case of a crime being committed, industrial espionage, or what-have-you)?

If I have a laptop encrypted with luks or whatever, then what? What are the consequences of non-compliance?

I love using tcl/tk and Python's tkinter module.

The complaint that it looks old-fashioned is addressed partly by using ttk (themed tk) but also just about every aspect of the widgets can be styled using a simple xresources-style config.

It's fast and lightweight, free forever, stable as hell, and there's lots of resources online.

Anecdotally, my Aunt had banned all guns and violent toys from her house. One morning, after serving breakfast, she noticed that my cousin had bitten his toast into the shape of a gun and was making "pew-pew" motions. They laugh and laugh about that. It is what it is.

This old saw again?

Shit. Just don't use Ubuntu. The writing is on the wall.

>t. Not a Linux user.

Google it bro

OpenBSD dabs on this list from the towering arches of the heavens.

I suppose I shouldn't be surprised at this level of pedantic cherry-picking, but yet... I still find myself bristling.

No, like choose to follow Sweden's example.

Time will show.

Contrarian view here.

I really liked Redis for a long time. Simple, fast data-structures in-memory. That's it. Along the way there have been some nice enhancements like Lua, which solves a lot of the atomicity issues. But somewhere after 4.0 I feel they have lost their way. First they saw all the attention Kafka/event-stuff was receiving, so they baked-in this monstrous, complicated, stateful streams feature. Now we have SSL (do people really expose Redis on the internet??), ACLs, cluster stuff, and most relevant to me a new wire protocol.

To my thinking, Redis fit very well in the "lightweight linux thing" category. It seems they aspire to be enterprise software, and this may be a good move for Redis-the-Business, but it's not good for users like me who just want simple in-memory data-structures and as little state as possible. Forcing a new protocol that adds very little value (in my opinion) also seems like a great way to alienate your users.

Virus going to do what it's going to do. People can choose to stay home but this shelter in place stuff is wrecking the lives of the poor and the people who are most vulnerable.

Tcl/Tk dabs on your gui frameworks from the unreachable pinnacle of the heavens.

>Projecting this hard.

The shortcomings of snap are well documented. I assumed anyone reading the comments would have been aware of them. But apparently some people will jump on any chance to virtue-signal.