There's no shortage of builders. You can just compensate those workers with taxes. If you think taxes are also a form of slavery, that's a different discussion.
You can't fulfill a basic human right contingent on enough taxes coming in. If it's really a basic human right, insufficient revenues or unexpectedly high prices are not an excuse. If your country ran out of money, if the builders all started working for foreign companies, and if housing was really being treated like a human right, you'd have to make builders work without pay, or at least involuntarily.
Providing housing most of the time is just a program. Providing housing all of the time with no exceptions, like you would expect from a human right, involves some serious distortions of other values. That's the problem, people are using the word human right when they mean high priority. It's a high priority that I do my laundry, but if society were organized so that I did my laundry at all costs, if we were all convinced that a society where I did not do my laundry did not deserve to exist, then things would get pretty crazy.
A high-priority housing program is how you implement a human right for shelter.
This isn't some paperclip maximalization requirement you adhere to the social contract, and under the wrong conditions will force people into house-building labor camps. Human rights are how you reason about resource allocation. You have a right to a trial by a jury of your peers, but that obviously doesn't mean a judge must preside over your case that same day by threat of force. We can recognize physical realities, while still understanding that if we wanted to, we could provide a social safety net that includes a place to sleep.
> If your country ran out of money, if the builders all started working for foreign companies
If your country runs out of money, many human rights are probably in danger.
I recall a lot of renewed energy a year ago into improving OpenSSL, including funding and support. Has that panned out as I would have hoped? LibreSSL improvements are highly visible (and exciting) but I expect I would have overlooked any OpenSSL improvements.
There has been a whole bunch of changes and cleanups in OpenSSL, it's just stuff like that doesn't seem to pick up as much traction here (they don't really have the blogging / communicating thing down so well, I guess?)
This is the current roadmap. https://www.openssl.org/policies/roadmap.html
Picking out a few highlights:
* "Objective met (2015): The FIPS code has been removed from the master branch, and will be re-integrated more cleanly during a future validation. "
* "Objective met (2015): All use of dynamic memory allocation has been cleaned up and made consistent, and the internal memory pool has been removed. "
Under Coding Style:
* "Objective met (2015): All release branches were reformatted using a script included in the release." (so all code now adheres to a consistent style at least, which is a good starting point)
And amongst their targeted goals now:
* Legacy platforms that are unlikely to have wide deployment will be removed from the code.
.. but ..
* Non-supported platforms requiring regular maintenance activities will eventually be removed from the code after first seeking community owners to support the platforms in platform specific repositories.
Not convinced that's necessarily the right route, but I can appreciate where they're coming from.
I was impressed too. I think the key is that it injects all of the HTML at once. Compare that to e.g. the Backbone.js implementation which uses progressive enhancement: http://todomvc.com/examples/backbone/
The code can be optimized further with Closure Compiler, but I wonder if that decreases startup speed.
The parent navigation needs to be replaced by a jQuery-like .ancestors() macro.
This was an MVP so I wasn't focused on code quality over features; but I'm also learning Rust for the first time, so it came out less than impressive :)
The Octocat used here and in the API control panel[1] reminds me of robot anime (Gundam Wing, etc.) or perhaps Speed Racer. I don't think it's meant to be warrior-like, but futuristic.
Programming for the Atari was one of my favorite coding challenges. I think the web offered a lot of similarities in the past decade (trying to make an unsuitable platform perform magic) and somehow jumping into 6502 assembly and trying to trick beautiful graphics out of the pithy TIA felt extremely satisfying.
