alloyed

Real time, on a I7-3770/GTX970 combo. It says so in the video description

Not an effective store of value, too volatile.

Plus, somebody has to trade the cash they get for bitcoin, and then they're responsible for the stack of cash they can't do anything with.

Off of the top of my head, with varying difficulty

* js has UTF-16 strings with the same semantics(compare-by-value, immutable, interned) as lua strings. you could store UTF-16 in normal lua strings, but then you'd need some way of marshalling them for C code that expects const char* values

* JS has a lot of type coercions when doing binary operations, etc. replicating that seems like a source of indirection

* Lua tables have no explicit length, or any way to preallocate, so it's not entirely obvious what Array(len) or a.length = newlen would do

This a property of static typing, not object oriented design. Take for example Typed Clojure, where you could define an Employee as a hashmap with a set of static constraints which can then be analyzed for, without having to invoke any of its proper OO constructs.

If the choice were between safeguarding the right to privacy and slowing the rate of innovation, I would pick privacy every time. It's the whole "trading liberty for security" thing: Civil liberties are the prime mover in any society, and losing it has a much more far-reaching impact.

What about the old let-over-lambda?

  do
    var state = init
    fn renderP()
      ...
    end
  end

Depending on what you wanted the state for, I think it satisfies most of the properties you'd be missing with a persistent, not-in loop state. It wipes itself on refresh, it has a distinct owner, it can be individually refreshed just by re-evaluating everything inside the do-block, etc.

I'd hope that the same community that takes "concatenation" and "list comprehension" and "mutability" to be household words would be able to get over some jargon weirdness so long as it's explained adequately.

Feel free to tell me if I'm reading this wrong, but we're talking about Lua as a platform for re-implementing elisp, not as a replacement (completely ditching elisp is a non-starter for obvious reasons). And not having dynamic binding, no native support for the full numeric tower, not having a native list type, etc. would be serious road blocks for running elisp on the Lua VM that aren't there in Guile's case.

That's not how I read gp, exactly. What he is saying sounds more like taking the AST of a program, desugaring at much as possible, and then re-sugaring it in such a way as to produce a consistently styled codebase, sort of like gofmt but more opinionated and linter-like.

This looks great, but it's a shame that the chromecast itself is hostile to personal testing or use. If I didn't have to go through at least 4 bullet points just to get my chromecast listed on a central registry I'd be much more willing to try this out.

FYI, when an ars article ends with the wired logo, that usually means it's a reprint. The original can be found at http://www.wired.co.uk/news/archive/2014-07/01/kite-bricks

A reputation system would be trivial to circumvent, though, through a shell entity. an easy way I'd imagine to limit bogus claims would be to make it so that a bogus claim has a negative effect, in the small. Normal law has this pretty well figured out: you win, you get reimbursed, you lose, pay up.

That would be really interesting to see, actually: with a tiny bit of projection math it sounds doable, and very trippy, to get the field of view of a side-eyed animal.

I suspect a lot of people will be unable to read it if they use HTTPS everywhere: the 4chan blog does not support https and the EFF is currently in a ruleset freeze so they cannot reflect that until the next stable version is out.

From what I gathered, that is what they did try to do, only the Supreme Court wasn't buying it at all. Ars gives a few choicer quotes:

http://arstechnica.com/tech-policy/2014/04/at-oral-arguments...

>"What the local antenna person doesn't do but you apparently could do... is with the same kind of device pick up every television signal in the world and send it... into a person's computer," said Justice Stephen Breyer. "And that sounds so much like what a CATV (Community Antenna TV) system does or what a satellite system does that it looks as if somehow you are escaping a constraint that's imposed upon them. That's what disturbs everyone."

>Justice Elena Kagan noted that "from a user's perspective, it's exactly the same as if I'm watching cable."

Technically, Lua is a strongly typed dynamic language: it's just that most things happen to be of a single "supertype" (the table). If you need a more rigorous approach, Lua's integration with C is good enough that you can write the architectural bits in C/C++ and just use Lua for the long tail of behaviors, or go one bit better and use a language like Terra [1] that provides a C-like static language inline with your Lua code.

[1]:http://terralang.org/