G33ky-Sozialzeugs

G33ky-Sozialzeugs

@markus @edwinb I'm minded to agree, tbh. This is a perfectly reasonable reaction to last century's type systems.

@pigworker @markus although even with last century's type systems, I'd still rather have them then not, as a tool for helping me structure my thoughts. I find that more useful than the fact they prevent some errors.

@edwinb @pigworker @markus as shown by eg scheme programmers using mechanically-unchecked types in comments - but maybe pseudotypes were more useful than 20th century types?

@markus I mean… in most languages it's totally possible to have a email type that kinda validates it's content and throws errors?

Only, as @aartaka already wrote, nobody actually does that (though I do know a couple model layers that do)

I'd find it nice to have that, only I don't really think it's solving much of a real world problem?
replies
1
announces
0
likes
0

@dat one can always parse the email into an object/structure/whatever, true. But one might also need it as string for e.g. interop/serialization.

And sometimes it does feel weird to have a type just to wrap primitives into it (not the same as parsing, might be a separate case!)

@markus