1,115 karma · joined March 17, 2015
In the neoliberal world order, government exists to ease the flow of international capital ("These regulations make it hard for us to scale our sales beyond the {US,China,Germany}. Please Mr. President, we need common-sense solutions!"). It has jettisoned its role of solving real problems for ordinary people ("Lord Fontleroy, Biff's dog killed two of my pigs.") as it once did.
One of the very real problems that cryptocurrency enthusiasts are concerned about (but IMO totally failing to actually solve) is that it seems like a really bad idea to leave such basic functions of state in the hands of difficult-or-impossible-to-regulate transnational enterprises. When will these players realize that they've got more "state-iness" than most actual states, and how will they use it?
You mean the secret court, with secret rulings, where only the government's case is heard, and 99.9% of requests are granted?
These things actually are important, because regular people do have strong feelings about them, but they matter to elites only to the extent that they can be used to gin up votes without having to dissent on any of the things that they all agree on: killing lots of foreigners with expensive weapons systems, preventing anything resembling a realistic safety net, pro-capital/anti-labor tax and immigration policies, unlimited dark money in politics, etc.
First-past-the-post systems like the US make this particularly easy, since third parties have no chance. If policies like universal healthcare and non-interventionist foreign policy are simply never adopted by either party, voters are forced to make their voting choice based on things that at least are different between the two parties, and elites have arranged for these to be things that barely matter to them at all. They don't have to interact with our barely-there social safety net, worry about health insurance, send their sons to die in foreign wars, or tolerate any of the daily parade of indignities that constitute life for working people.
In short, it's good strategy to manipulate the poors with cheap rhetoric about the 2nd amendment, so that you don't have to have messy debates about expensive things the elites oppose, like universal healthcare.
Specifically, the second return value from this macro is a procedure that generates URLs given a handler function. This allows one to go both ways in URL-handler mapping (generating URLs from handlers/controllers) instead of just one-way (mapping requests to specific handlers/controllers) as in a conventional router in Rails or Django.
Once you learn about this pattern, you start to see it in more places. A slightly different example, I am working on a mail router (something akin to procmail) in Racket, and have used a similar pattern to map from predicates (procedures taking an email and returning true or false depending on certain conditions) to symbols representing those predicates in a DSL. A hash table with procedures for keys lets me do this mapping in both directions should I need to.
(Note that I am not actually sure whether dispatch-rules itself uses procedure-keyed dictionaries or hash tables under the hood.)
America's puritan relationship with work, and it's toxic interaction with free-market economics has reached it's ultimate conclusion in an economics that calmly and rationally lays out an argument that the working class, who:
1) for perhaps the first time in history have their essential needs met without spending most of their lives at toil, and
2) who indeed are happier than similar cohorts have been in the past, should
3) have their leisure time taxed in order to encourage them to go back to work for capital earning wages they don't want, instead of spending their time as they please.
This article really lays bare the grim reality of our world order: the owners want us working, even if there's nothing for us to gain from it. Indeed, any potential surplus which might under a rational system result in leisure, will instead be sucked up by an owner-controlled state through confiscatory taxes which are designed solely to get us back into the mines lest we enjoy ourselves too much playing Overwatch, being with our families, or just generally not wasting our lives in low-paying retail and service jobs.
Likewise, if you get a royal flush in a hand of poker, you probably won't get as good a hand next time. Again, this is not because the deals aren't independent events, but because it is always unlikely to get a royal flush.
The HTDP languages all look like Scheme, as most Racket languages do, but you can actually swap or modify the reader as well, to produce Blub-y languages (for example, someone has implemented ECMAscript: https://docs.racket-lang.org/ecmascript/index.html) that interoperate with other languages in the Racket system (including Racket itself).
At the same time, Racket is "real" in the sense that you can build production systems in it (not in the HTDP languages themselves, but it all interoperates), and it has a pretty good batteries-included core lib and contrib packages. For example, you could integrate the students' code (in a simplified pedagogical language) with the webserver (from the "real" language), so that they can see their code doing stuff out on the web where others can look at it, or they can show their parents, rather than trapped in some educational IDE that's only installed at school.