Funny thing is that it does refuse to change the time when the delta is large. So it trusts these random bytes in the TLS handshake blindly, but when it gets the correct time from the time server some seconds later, it doesn't dare to change the time as the delta is too large!
I'm Norwegian too, and remember watching it on a Swedish broadcasting channel when I was a kid. We had two channels, the Norwegian state funded broadcasting channel, and the Swedish state funded broadcasting channel. Good times!
Really inspiring! Nicely structured, and easy to follow along, especially with the "Try it yourself" links. Amazingly addictive to tweak with variables :)
A nice and clear explanation of why tail recursion is necessary and how it works. I usually don't like mathy examples, but it worked fine here. I especially liked the section on trampolines as I didn't know how transpilers usually did that. Well worth the read.
This doesn't sound good at all. On the flipside, I've heard and read several people who say Xamarin has been a critical part of their success and like the ecosystem and libraries.
Three years in IT is a long time, so maybe things have changed? I would love to hear other experience reports too.
PS: "Indian code farm developrs (...) low quality garbage (...)" is a gross simplification and generalization which further strengthen negative stereotypes. I advice a different wording to avoid feeding trolls and haters.
Agree this is interesting. Historically, Mono-applications on mobile was at least 10x bigger than Java application as they included the entire runtime system.
Can the runtime system be shared now? Is .NET Core a thing on mobile, and is the resulting download smaller?
While download size is no longer a problem for me, my guess is it is still a big problem many places in the world.
Bartosz Milewskis Category Theory for Programmers also has nice explanations for all these concepts. Haven't read through everything, but what I've read has been very high quality.
More like "beginning software architecture". While this is "common knowledge" after coding for years, it's actually hard-earned, battle-scarred knowledge. Sharing experience on how to design software is very useful for all the people just starting out.
There's nothing wrong with returning something well-specified from toString, but I agree this should never be relied upon. And even if toString actually return something well-specified, the same functionality should be available as a distinct method.
Any form of (semi-)automatic SomeObject -> String should be treated as a convenience for the developer to avoid getting a non-descriptive memory location reported.
Having the automatic toString isn't the problem, but maybe the name of the method is. It could be called "asDebugHelpRepresentation" or something more descriptive.
I've written an F# introduction for my C# coworkers. It haven't been reviewed, so it probably has many faults. Might still be useful for others. Any feedback is appreciated.