There is something captivating in these old pictures that elevates them to pieces of art rather than just computer graphics. The sheer amount of work that went into crafting them makes each one special.
If you want to learn how HM typechecking works by studying working (Haskell) code, I would recommend the papers below. The code in these papers is closer to how you would actually implement a type checker in practice.
My sentiments exactly. The problem is that also traditional media now amplifies this negativity. A bleak world view is now the norm. Things have been much worse in recent past but still people didn't fall in to apathy. Objectively things are not nearly as bad as the common discource leads to believe.
Ah, Ismo; perhaps my favourite Finnish stand-up comedian. (Ali Jahangiri may be second.)
Yes, I can confirm [1] that Finns often struggle with 'b'. An IME very common example: The word "pub" for a drinking establishment has been loaned as-is into Finnish. But the expression "Let's go to the pub" is, I think more often than not, rendered as "Mennään buppiin".
As I understand it, this is because Finns can pronounce the letter 'b' (even though it isn't natively used in the Finnish language), but for many (most?) it takes quite a bit of concentration and leads to some amount of nervous tension. So when you see one coming -- i.e. having just decided that you're going to say "pub" -- you prepare, tense up... And release it too early, at the start of the word (no wonder, since it starts with the treacherously similar letter 'p'). Then, having blown all your tense preparation already (and perhaps just jumbling it up with the other consonant you also had prepared to pronounce), the end of the word comes out as the (again, treacherously similar) letter 'p'.
No biggie, but definitely still a little funny. (At least to me. Sorry.)
___
[1]: Foreigner, but since last spring lived longer (26 years) in Finland than in any other country.
Being old enough to have used both Microsoft and Borland development tools back in the 90s, I think Borland was clearly ahead of the game in Windows development. GUI development with MFC was clunky and tedious. Tools generated ton of boilerplate code that you had to understand and maintain. Borland on the other hand offered much more developer friendly experience, especially when Delphi 1.0 came out on 1995. That was hands down the best development tool for Win16. They maintained the edge in Win32 development as well with Delphi 2.0. So, seeing all the dirty tactics MS employed to steer developers to using their tools just reminds me what an a-hole company they used to be.
Oh! Delphi was way ahead, at least on the user experience, I remember VB6 not having 'undo' actions for form editing so if you sneezed and accidentally moved a bunch of elements in your form, well...
And don't talk about VB redistributable, that weren't funny at all in the dial up era...
You can agree or disagree about the design decisions made by people contributing to Haskell language, but you have to admit that it's a pretty clever bunch of people. Haskell has contributed more to PL research in past few decades than any other language. That alone makes it a language every programmer should learn. Not because they should use it daily, but to learn what functional programming is in its purest form.
I live less than 100 km away from Olkiluoto nuclear plant, and I have never been worried about its safety. I wonder why this incident ever got any publicity outside Finland. Even here it faded away very quickly.
They definitely make press, but my opinion is that it is detrimental to public perception of risk.
Distributed systems are complicated beasts too, and have fascinating failure modes, but they get no press, because there are so many incidents and so many installations.
Centralized systems make a better scapegoat regardless of probabilities.
It reminds me of something Georges Charpak mentioned, paraphrasing: we can detect tiny particles, and now we are scared, but we cannot detect economic crashes, and we should be more scared of that.
> but my opinion is that it is detrimental to public perception of risk.
This would positively affect my perception of the plant's operators. They handled the crisis, and now are laying out the post-mortem for the public in a transparent manner. A culture of secrecy conceals incompetence, and that can lead to disaster. See: Chernobyl
> but my opinion is that it is detrimental to public perception of risk.
The Finnish nuclear unit-nuclear watchdog had found that radiation levels had risen [1], the public does deserve to know and make up its own opinion about it.
Also, centralized systems are a lot more vulnerable and high-risk compared to distributed systems.
The initial reporting was misleading in that it was not clearly communicated that where the radiation levels had risen. So yes, radiation levels rose inside the primary cooling system. This is what triggered the automatic emergency shutdown. But the primary cooling system is anyway 100% isolated from the environment.
In particular, no change of radiation levels whatsoever outside the reactor building was ever detected. But initial reports did not make this quite clear.
Wait until it is common public knowledge that a distributed system failure can cause a loss of life. People like you and I may be interested in these postmortems strictly for the analysis, but the public at large is not.
On the other hand, they're very interested in things that can kill them.
I also wonder if there's more public attention paid to nuclear incidents in the region because of the proximity of a player who does not disclose or cooperate in nuclear incidents.
It's indeed weird, INES 0 events are rarely reported... even levels 1 and 2 rarely are. Just yesterday there was one INES 1 anomaly here in Spain and 2 in France... that said the reading was super interesting, I get why it is on HN.
It was reported about it in the German press. I'm an opponent of nuclear power, but in this case I can only shrug and conclude that everything worked as expected, the issue was identified and dealt with.
Perhaps I am being pedantic, but this strikes me as a strange position to announce. Nuclear power is a broad category of things which includes fission, decay and fusion, all of the above can be used to generate heat.
If you look at a pie chart of how the electric power is generated in your country, and you see "nuclear power", which of "fission", "decay" and "fusion" are you going to think about?
Yes, that's why I qualified my comment. My point is that opposition is more effective when directed at specific design issues. It's about the quality of technical discourse. Just like you wouldn't say you oppose the internet if you have an issue with Facebook etc.
Fusion is a work in progress and it is likely what will power our civilization in the future.
In the meantime there are new types of fission reactors being developed (small modular such as Nuscale, advanced fission deployed in China) and they aim the address shortcomings of older designs.
The problem with current generation of fission plants is that they were primarily designed to be integrated into military-industrial complex that produces fuel for nuclear weapons. You can have safer fission plants by focusing on power generation only.
P.S. Not sure what's up with downvotes, but whatever.
I think that at least within Finland, worries were mostly related to communication delays in informing relevant organizations about a potential nuclear incident. I.e. if this had turned out to be a more serious incident, the response would have been delayed. Glad to see it wasn't serious.
Because nuclear bad. If it was a coal plant accident that killed 15 it would not make headlines outside of the country, but a 0-casualty nuclear accident makes it to the front page
No, it's because a nuclear reactor has a small but real risk for a Chernobyl or Fukushima like event. We are not good at managing risks of this impact size: it's a slippery slope if small disturbances are not taken seriously. It's not unlike the reporting of near misses in aviation.
Both events killed like less than a hundred people directly in total, maybe a few thousand if all externalities are accounted for. Meanwhile dam failures have killed several hundred thousand people. I've always wondered why anti-nuke people weren't also adamant anti-hydro as well.
"154,000 residents evacuated from the communities surrounding the plant due to the rising off-site levels of ambient ionizing radiation caused by airborne radioactive contamination from the damaged reactors." https://en.m.wikipedia.org/wiki/Fukushima_Daiichi_nuclear_di...
Most studies seem to suggest that the evacuation ended up being much worse than doing nothing at all, no?
For example:
> “With hindsight, we can say the evacuation was a mistake,” says Philip Thomas, a professor of risk management at the University of Bristol and leader of a recent research project on nuclear accidents. “We would have recommended that nobody be evacuated.”
For sure there is need for programming language research. Language designers benefit greatly from the work done by the academia - for example in the area of type systems. But, OTOH, scientific community is not very tuned in the everyday problems programmers have. That is why some of the popular languages are basically hobby projects spawned from some lone programmer's personal itch.
I think we should have the best of both worlds; people enjoying the mathematical rigor should do PL research. And hobbyist language designers should pursue whatever ideas they might have. But both camps should acknowledge that the other side is equally important.
