kzvezdarov

Yes it is. I live in Ontario. The provincial (conservative) government literally froze the wages of nurses and other public sector workers in 2019 (see Bill 124), creating a massive exodus of nurses and a severe staff shortage. The provincial government doesn't have money to pay nurses, but it has enough money to build a useless highway (see Highway 413) that just so happens to go through land owned by the Premier's friends and business associates; or to give out millions in license plate rebates just before an election. That's also the same provincial government that intentionally didn't spend about $2.7 billion of federal COVID-19 relief funds (which could have, you know, funded healthcare).

Lastly, Canada's population isn't shrinking. It's growing, thanks to a sensible immigration policy (well, mostly sensible; not recognizing the credentials of healthcare professionals is pretty dumb).

Public healthcare is only difficult to find when your government's priority is to personally engorge on a gravy train powered by corruption. All of the issues facing the Ontario healthcare system are intentionally self-inflicted.

Anyone looking to make good sourdough (or any other kind of) bread should read Ken Forkish's "Flour. Water. Salt. Yeast." Including the OP - there a few things that could use improvement in both their method and recipe:

1. Ideally, for home baked bread, you always want to use a heavy dutch oven. A heavy dutch oven retains a lot of energy, which provides a consistent environment for the bread to bake in (opening an oven door, no matter how hot, rapidly lowers the temperature), but more importantly retains the steam that the bread emits. This both causes proper crust to form (look for the micro bubbles on the skin of the bread) and makes the entire loaf rise significantly more.

2. The hydration at 70% seems low. While low hydration makes handling dough easier, it also changes the taste - in my opinion, for the worse when it comes to bread. With a bit of practice, proper fermentation, shaping, proofing, and enough gluten formation, even a 78% hydration dough is not that hard to handle. I've baked a 1.8 kilo boulé without any shaping support on a simple pizza stone without having the dough "leak" (in general, if it is "leaking" post proofing, the dough has probably been overproofed and the gluten has weakened).

3. Fermentation time seems really low. Most sourdough types I am familiar with take overnight to ferment, and then 4 or so hours in the proofing basket to be fully ready. I've never baked after such a short fermentation period as described in the article, but I would imagine the resulting bread does not have the full airation, flavor, and texture that it otherwise would.

4. Technique - in my experience and as far as I have read, you do not have to knead at all. Most dough need only 3-4 rounds of "folding" during fermentation, where each edge of the dough is stretched and pulled over itself. That forms plenty of gluten. Shaping post-fermentation is similar, where after the edges are pulled over, the loaf is inverted on the seam and gently dragged around to create surface tension. _Definitely do not knead during shaping_.

For what it's worth, making your own bread is great. My first results were barely edible shame-disks with the texture of hardened gypsum, but after I got a handle on the correct techniques (and more importantly - patience) I have not purchased bread in a store for the better part of a year.

Not sure which book the parent was referring to, but that's the premise of Charles Stross' Laundry Files series: too many humans and too many computers doing too much complex mathematics attract tentacled horrors from beyond space-time. Edit: I also like how in it, mathematics is the language of sorcery, and computing devices of any form - the implements.

I think in the TensorFlow case it is just a purely technical decision - I don't see how they could achieve what they aim for with that project in Go (or really, in anything but C/C++ at this point in time). Right tool for the job, etc.

That's interesting and supports the idea that it might be related to genetic factors. I've had two twilight anesthesia procedures done about two months apart and remember the events before and after waking up in a lot of detail. I've also had regular general anesthesia once in my life, with the same result. As a bonus, I seem to resist local anesthetics to a degree that requires 2-3 times the amount a normal person does (and even then, the pain finds a way through).

The IRCv3 work group is making some good progress: http://ircv3.net/ .

It's rather that Rust's standard library and third party library support is incomplete. E.g.:

- last time I checked there was no option to have non-blocking IO which is a pain.

- custom JSON serialization/deserialization from/into custom data structures is extremely painful (for reference, rustc_serialize's Decodable trait).

- thread::scoped leaking destructors under certain conditions. This is more of an example of how a complex language gives rise to complex issues that very are difficult to debug and fix.

This will get better in time obviously but this is the current state of the language. Nonblocking IO in particular is really unfortunate to see in a 1.0 version tag.

I played League for a very brief period, before I got my Dota 2 beta invite, so some of these might not be valid any longer. Also note that those are differences in game design, one is not necessarily better than the other:

- DotA 2 metagame undergoes major changes every patch, whereas League metagame is mostly guided by Riot towards a certain playstyle. E.g. in DotA 2 lane assignments are extremely flexible, under certain conditions you can see any hero in any lane, whereas in League champions are mostly only viable in certain lanes.

- Mechanics wise, DotA 2 is more punishing. If you die, you are dead for much longer, you lose a significant portion of aquired gold. Laning wise, you can deny your own creeps in order to prevent the enemy from gaining gold and experience, and you can modify where the opposing creep waves meet in lane via pulling from the jungle camps. You cannot do that in League. Teamfights in DotA 2 are usually very fast and deadly, due to the presence of strong disables/burst (which is something League shies away from), strong initiators, and the fact that heroes are very asymmetrically balanced.

- The map in DotA 2 is bigger which puts a great emphasis on mobility and positioning on the strategic level - The International 3's Grand finals were a great example of that.

- DotA 2 comes with a lot of complexity. There are a huge amount of synergies, item/spell interactions, and generally mechanical knowledge that a player needs to absorb before they can play semi-efficiently (not that the process is not fun; it just takes a considerable amount of time in comparison).

- On the technical side, DotA 2 has a better client by an order of magnitude. Also, it has a Linux-native version which runs perfectly.

There are some good dependency managers out there. I personally like gb: http://getgb.io/, but there is GoDep and GPM as well (which are more similar to Rust's Cargo in the way they work).