rdc12

Too much Hydro (by percentage of generation) also leaves the power generation at risk if a drought occurs too[1][2][3].

There is just too much uncertainty in long term seasonal rain fall levels, especially with the effects of climate change as well as El Niño and La Niña cycles. Resulting in low production years.

[1]http://www.sandiegouniontribune.com/business/energy-green/sd... [2] https://www.theguardian.com/world/2017/dec/08/malawi-blackou... [3] https://www.theguardian.com/news/2016/mar/30/weatherwatch-ha...

I think part of the beauty of static type systems, for refactoring guiding, is that most (if not all) issues arise at the time of change, when the change is fresh in your mind, locality of reference if you will.

Except it is not a loop[1], but a non-tail recursive function (with dual calls), if the compiler can optimise that to a loop that is actually impressive.

Most likely function call overhead (and in the slower cases, interpreter overhead) is probably what is being measured in the best case.

[1] In that it won't be a jump and check style loop.

"Also, I've been fairly critical of Rust in the past because that view was in-line with the opinions of my friends, but now that I've decided to go out of my way to learn a new programming language, I might as well use this as an opportunity to see if my criticisms were unfounded."

While this is an honest comment, why and how can you be critical of a language you don't know. Skeptical sure, but critical?

Sounds like this could have probably been avoided, if they had done random testing on the swabs themselves to give confidence that they were not compromised by contamination.

With large scale dams there is also huge environmental impacts and displacement of the local population. You have to form a sizeable reservoir lake etc. They also take considerable time to build.

Has been a long time since I watched either of these

Rusty Russell - Advanced C Coding For Fun! - A series of crazy tricks that is quite enlightening. https://www.youtube.com/watch?v=BEQ3sRakIs0

Tridge - Linux powered coffee roaster. Tridge (of Samba and rsync fame) walks through the process he used to reverse engineer a USB thermometer live during the talk. https://www.youtube.com/watch?v=3LQr4At5Z5Q

Linus probably doesn't have contributions (as the code author) in all parts of the kernel anymore, entire subsystems have been created since he transitioned to his more curating role.

From the article he made contributions starting at least in 99 (so 20 years ago), it will probably be non-trivial to remove all the code he has previously written.

Even if you could remove all the code that he has claim too, that would only be for a future release, and most commercial users of Linux tend to use older, battle tested releases (especially for embedded products.

In person and by video of the same material experience can be quite different. One of my current lecturers, is very engaging, with great natural flow in the lecture room, but watching via video somehow fails to capture this.

That is for lectures that I miss due to a clash, not re-watching.

If you were writing D from scratch today, would you go for a full back end solution or would you target the LLVM?

If it can be built by someone with no experience in less then an hour, then is it really building in any true sense.

Or to put it differently is there a real difference between building something and assembling something out of a kit-set?

In the late 90's early 00's, we had a pet cockatiel that could perfectly mimic the sound of dial-up modem dialing. He would also do the tunes to TV theme songs and a few regular TV ads.

Or to put it another way, find something new and valuable as your Trojan horse?

On the other hand part of the complaint in the main article is the lack of basic core utils at a standard that OpenBSD would consider. Or things that could be a base world dependency for them.

How many people would be using bcache in production fullstop, I'm guessing not many.

For me the key concept that comes to mind for a JIT compiler, is profiling at runtime to decide what to compile and how aggressively which this article doesn't deal with. The other big thing is how to make the profiling and compilation not be too expensive to negate itself.

The article author seems to be using GCC not at runtime, but more as a generator for templates (at the machine code level) for the rest of the software to use. You don't really want to be assembling a template at runtime in this context.

You can always remap it in software too, setxkbmap or xmodmap will do it on a Linux, Windows and OSX will have a way to achieve this too.

It is also worth making note, that Intel (and to a lesser extent AMD), have had a fair amount of advantage by being further ahead in chip fabrication technology, having more transistors has played a major role in how Intel kept it's status.

Isn't this line from #3, undefined behavior not mentioned in the article (sequence point violation)

zp++ = xp + *yp;

Languages Rust Ocaml Matlab/Numpy/? Some form of numerical programming environment anyway Haskell (maybe if I have time towards the end of year) ARM/Risc-V assembler (as a target, see below)

More general. I want to finally make a read thru SICP without getting sidetracked halfway. Then move to writing some toy compilers.

Have a few ideas for home embedded computing projects.

I want to work on some DSP projects too.

Sadly there is also a dam in Africa, in similar dire position, due to being built on a geologically unsuitable site.

[1] http://www.newyorker.com/tech/elements/one-of-africas-bigges...

Are the minion cores comparable to the PRU's in the Beaglebone?

In fact, there is occasionally (ok very rarely) sea snakes are found on the coast of the North Island.

http://www.stuff.co.nz/taranaki-daily-news/news/80026544/Ven...

That is a pretty classic joke around NZ.

Land based fauna, there is pretty much nothing to worry about, other then maybe wild pigs. Couple of venomous spiders but they are fairly mild to humans anyway.

Sea based, the usual sharks, sting rays etc. But as most countries attacks are pretty rare.

Your far more likely to get into trouble by either falling, getting lost, or not having suitable gear with you.

I think by default in vanilla zsh, will expand something like 'sudo !!' by hitting tab after the second bang.

Good history ofreverse engineering nature thou.

Primarly this one, "One paper in my collection does that for IIRC Haskell to Forth by implementing a G-machine interpreter or compiler for a Forth CPU. It certainly can be done. Question is whether it's ideal vs a non-Forth CPU."

But a sample of the others could make for some good reading over semester break.

Thanks

Any chance you could link to that paper please?