I remember it as just beer and cider, with the addition of blackcurrant making it a Purple Nasty, and all sorts of tales of how they allegedly reacted to make a vicious drink more than the sun of the parts that I am sure was fiction.
And for Americans, this means alcoholic ciders, since they also call raw apple juice cider, and most Americans have no idea what a blackcurrant is (a delicious intense berry that was illegal to cultivate in the US for a lot of the recent past).
I’m now 1 year in to working in Go having been mostly C++ and then mostly large-scale Python dev (with full type annotation).
Frankly, I bristle now at people giving Python a hard time, having worked with Go and I now hate Go and the de-facto ethos that surrounds it. Python may be slow, but for a lot of use cases not in any way that matters and modern computers are very fast. Many problem areas are not performance-limited, and many performance problems are algorithmic, not from raw statement execution. I even rewrote an entire system in Python and made it use 20% of the CPU the former C++ solution used, while having much more functionality.
The error returns drive me nuts. I looked around for explanations of the reasoning as I wasn’t seeing it, and only found bald assertions that exceptions get out of control and somehow error returns don’t. Meanwhile standard Go code is very awkward to read because almost every little trivial function calls becomes 4 lines of code, often to do nothing but propagate the error (and errors are just ignored if you forget…). With heavy use of context managers, my error and cancellation handling in Python was always clean, clear, and simple, with code that almost read like whiteboard pseudo-code.
The select statement can be cool in Go, but then you realize that literally 98% of the times it’s used, it’s simply boilerplate code to (verbosely) handle cancellation semantics via the context object you have to pass everywhere. Again, literally code you just don’t need in exception-based languages with good structures to manage it like Python context managers.
And every time you think “this is stupidly awkward and verbose, surely there’s a cleaner way to do this” you find people online advocating writing the same boilerplate code and passing it off as a virtue. e.g. get a value from a map and fall back to a default if it’s not there? Nope, not offering that, so everyone must write their own if foo, ok := m[k]; !ok {...} crap. Over and over and over again the answer is “just copy this chunk of code” rather than “standard libraries should provide these commonly needed utilities”. Of course we can do anything we want ourselves, it’s Turing Complete, but why would we want to perpetually reinvent these wheels?
It’s an unpopular language, becoming less popular (at least by Google trends) and for good reason. I can see it working well for a narrow set of low level activities with extreme concurrency performance needs, but it’s not the only language that could handle that, and for everything else, I think it’s the wrong choice.
Go code is always an abomination.
Along with “it’s sometimes hard to detect your own stink”
Dynamic typing is shit. But type annotation plus CI checkers can give you the same benefits in most cases.
Once you need performance
If you need more performance. Many things just don’t.
Also depends on your variant of English, because North American Biscuits are very different from the rest of the anglophone world’s biscuits. Many of them are unleavened, just as most gods don’t have a strong position on whether you should use leavening at any time of the year, let alone now.
deleted by creator
Windows will never come close to replacing Linux! There’s way more Linux out there than there is Windows.
Presumably you mean on the personal desktop. In which case I still disagree in the very long term. I think at some point Windows will be replaced by *nix based systems in the vein of OSX and Chrome OS.
Wow. .08 is ridiculously lax IMO. I agree punishments should scale by inebriation level but I never expected people to think .08 was too strict.
Coupling is a fucking gem. I’ve still never been able to bring myself to watch the final season that has no Geoff though.
But then you have to eat Tillamook cheese… I has no idea cheese could be so bland before I moved to the NW USA. And orange, for some reason.
I thought it was stating that something is God’s will for your own purposes. AFAIK it’s not just using terms for God as a curse.
When bzr, and then git, turned up and I started using them, I was told “this is DVC, which is a whole new model that takes getting used to”, so I was surprised it seemed normal and straightforward to me.
Then I found out that Sun’s Teamware, that I had been using for many years, was a DVC, hence it wasn’t some new model. I’d had a few intervening years on other abominable systems and it was a relief to get back to DVC.
Regarding the original post, are there really people around now who think that before git there was no version control? I’ve never worked without using version control, and I started in the 80s.
Sharing your work without cost to people who need it is pretty solidly left. But it certainly isn’t red vs blue, not least because party political colors vary by country and in the US, neither refers to a left-wing party, and in most countries red aligns with left.
Pretty bizarre if people do this. I’ve never heard it to mean anything but linoleum.
But a lot of people in the US use the word “turf” to specify not turf (i.e. artificial turf), so there’s no reason for words to mean things.
What? One of linoleum’s benefits is not off gassing and not being made from fossil fuels. Are you thinking of vinyl?
why is there no switch to enable type checking at runtime?
Have you got problems this would solve? I’ve done a lot of type annotated Python at scale and I can’t think of an example.
Edit: given nobody in their right mind allows code that’s not checker clean.
Meshtastic is fully dominant in user numbers, but is fundamentally broken by design for what most people actually want to use it for, which is a distributed zero infrastructure communication network. As soon as numbers rise it is crushed by the weight of its own administrative traffic. Also, it’s way too easy to set nodes up as ROUTER nodes, which crushes the mesh and swallows traffic ironically.