In the end, it isn't that useful. I only routinely sign digitally to deal with the (Spanish) government, and they provide their own certificates and software to do that.
This is definitely not Stallman's take on "this", "this" being _OP's feelings_ or maybe how to deal with regret generally, not whether having children or not is or isn't a good idea.
Sure, but plenty of type systems are Turing complete. What makes this demo impressive is the (unique?) feature of string literal types and template literal types, which lets you operate on text (like, actual text, with no weird type-level encodings).
Surely you don't mean the Go team, which has had this in the language FAQ since 2009 [1]:
Why does Go not have generic types?
Generics may well come at some point. We don't feel an urgency for
them, although we understand some programmers do.
Generics are convenient but they come at a cost in
complexity in the type system and run-time. We haven't yet found a
design that gives value proportionate to the complexity, although we
continue to think about it. Meanwhile, Go's built-in maps and slices,
plus the ability to use the empty interface to construct containers
(with explicit unboxing) mean in many cases it is possible to write
code that does what generics would enable, if less smoothly.
While that would probably be very valuable, it will probably come with lots of implementation details that won't really matter to you unless you plan to write a database yourself.
I'd suggest this one: https://dataintensive.net/ Its intended for _users_ of databases, that is, developers incorporating databases (and other kinds of data systems) into their applications. It gives just enough explanation on how those systems work and what they can (and can't) provide, and also gives a more general overview of what's available beyond relational SQL databases.
This was also commonplace in Spain, traditionally. Some people, especially old ones, will say "si Dios quiere" literally every time they refer to any event in the future, even if it's just "see you tomorrow". Not doing so would be considered a "challenge" to God, or Fate, more generally.
Curiously, from "inshallah" Spanish got the word "ojalá", a very common term for expressing hope of something happening (and with no religious or any other "deep" connotation anymore; just like you'd use "I hope").
These are two manifestations of the same feature: function arguments's default values are evaluated when the function is defined.
In one case, the value is a non-mutable int, while in the other it's a mutable list, but in both cases each call to those functions will share the same value for that argument (unless overriden).
Other things equal, if companies need to pay severance, employees get paid less each month, because companies need to take into account expected severance costs in their total labor costs and there's less money left for other benefits.
So all employees effectively pay for layoffs, which goes against you if you're not the one that gets laid off.
(I am very much in favor of mandatory severance and generally other kinds of safety nets.)
`curl X | bash` provides _more_ transparency than most other usual methods of software distribution, as I can always inspect X, which is usually a simple, self-contained script.
In contrast, running code from an unaudited source (GitHub, NPM, etc.), or executing a binary from some random website, all less transparent yet just as dangerous, but for some reason raise way fewer eyebrows.
Demos for a couple old versions: https://www.youtube.com/watch?v=NqKyHEJe9_w Demo for Pharo: https://www.youtube.com/watch?v=baxtyeFVn3w