I think your second point is actually dangerous advice and it's one of the reasons I prefer Nick Ienatsch's book [1] and the Yamaha Champions [2] school to Keith Code/CSBS. You don't want to be adding throttle and lean angle at the same time and accelerating through a turn gives you less options to deal with mid-corner surprises. You can add throttle as you stand the bike up and drive out of the corner.
Even on the road it's safer to trail the front brake into corners and keep weight on the front tire. Keeping the front suspension compressed will also make the bike turn better. None of the fast guys ride the way Code describes [3]. You can see Marc brake all the way to the apex with zero throttle.
That's pretty cool! I started trying to learn perl6 and write my first interesting program. I have a copy of 'ray tracing in a weekend' and am trying to translate the basic ray tracer from c++ to perl6.
It's remarkably slow right now.. It takes 1.5 minutes to generate an image. I tried to do the same thing in Julia and it takes 1.5 seconds. So I guess I must be doing something wrong!
Probably not wrong but quite possibly in a way that's not been optimised well. I'm sure people on Freenode IRC #perl6 would be interested in your work. Don't forget `perl6 --profile script.p6` gives nice profiler output out of the box!
I don't know about the X220, but I can tell you about my experiences with setting up an X200 I bought off ebay. Its not quite trivial..
You need to get access to the SPI flash chip on the mother board. They sell some fancy little clips to attach wires, but I just had one of the hardware guys at work tac some wires directly to the chip. Then I used a raspberry pi to flash the image across using their tools. Maybe I had a dodgy connection, but it took several tries of flashing to get it to work correctly.
Once installed it isn't much of a bios. It is mostly just GRUB, you lose all the existing bios settings completely. It lets you boot from different images and thats about it. It does work well once it's set up though.
I recently setup a small personal project on Gitlab as well. I've been very impressed. I was able to setup a private repo, with a CI setup that builds my code and runs my tests every time i push a commit.. all on their servers. For free.
Maybe we have different definitions of 'unreadable'. I'm typing this on an XPS 13 with 1080p screen and 1x scaling (Fedora 25). The text is perfectly readable.
I think you're giving it a bit more credit than necessary. Don't get me wrong, it's cool that they've got it running on a RPi, but it's almost word for word what you'd write in C (right down to needing to inline assembly to get a busy loop to work). The C implementation wouldn't need to bring in a bleeding edge nightly build, worry about name mangling etc..
The purpose of the article was to show how to get up and running with rust on a Raspberry Pi, not to show how that rust is easier to use than C for programming a Raspberry Pi.
Plenty of things I do are are word for word the same in C and python. (import math vs. #include <math.h> , math.sin(x) vs. sin(x), etc.)
It is when you want to build something more complex than a blinking light that the differences between languages come out.
Even on the road it's safer to trail the front brake into corners and keep weight on the front tire. Keeping the front suspension compressed will also make the bike turn better. None of the fast guys ride the way Code describes [3]. You can see Marc brake all the way to the apex with zero throttle.
[1] https://www.amazon.com.au/Sport-Riding-Techniques-Develop-Co... [2] https://www.youtube.com/watch?v=Wvrgn5akOm4 [3] https://www.youtube.com/watch?v=cS3DTWq0QV8