168 karma · joined October 4, 2011
IT MAKES NO SENSE>
[1] http://decomplecting.org/blog/2014/10/23/welcome-to-the-dark...
I used it with my (fake) EdTEch Startup Generator[1], to check if my fake startup is actually a real startup. I was surprised how often it happens.
[1] http://eduwampus.herokuapp.com *
* May load a little slow, it's on Heroku free tier.
1) You do not write macros.
2) You do not write macros that violate expectations of normal code behavior.
3) If this is your first time, you must write a macro.
4) Don't think object-oriented.
5) No shirt, No shoes, No dynamic scope.
6) Don't create new scoping rules.
[1] http://stuartsierra.com/download/2010-10-23-clojure-conj-mac...
With blackjack and hookers? Please say with blackjack and hookers.
I'm not completely against OS X... until they finally disable non-App Store software sources, the thought of which is, I expect, giving someone at Apple a massive hard-on at this very moment.
The point is about access to the tools, the skills, and the ability to share; if the vendor controls any of those, FAIL.
Not about money for me, but if I was a little kid hacker again, money would have been a big deal.
Apple developer documentation? comp.os.linux was better documentation, in 1996.
On iOS, on the other hand, it's $99/yr if you even want to run your own code on your own device. And you have to 'provision' your friends' devices if you want to share with them. It's extortion, it's stupid, it's immoral.
The "hacker kids" issue is almost orthogonal, but I can't stand the idea of someone telling me what I can run on a device I purchased.
I don't care what kids code on, I care about access. And forcing people to pay $99 to run their own code on their own devices is beyond unconscionable.
plus, we're not talking about $99 to publish, we're talking about $99 just to run your own code on your own device. I don't know about you, but when I was a 10yr hacker, that would have been a deal breaker.
That being said... I meant what I said about apple's mindshare. Take, for instance, LA County's iPad boondoggle[1]. EdTech is a particularly gnarly sector, and the fact that districts are going after iOS to this degree is a damn shame.
[1] http://pando.com/2013/11/29/ihave-a-dream-the-unanswered-que...
I was a precocious little shit.
In this case, since Zerocoin is actually a university-sponsored project (from the Johns Hopkins Information Securuty Institute), we can hope for a response... hopefully it will be a rebuttal from the researchers and not a kneejerk response from administrators.
Even beyond its obvious utility (for good or ill), zerocoin is a fascinating problem in cryptographic research, and we should be grateful it's occuring in the light of day and not as some super-secret project.
[1] http://www.theguardian.com/commentisfree/2013/sep/10/nsa-mat...
Now that I'm doing the hiring (not something I ever wanted for myself, but we all have to grow up sometime)... I like the people I've hired so far, I would never subject them (or myself) to working with someone who didn't see coding as "more than just a job."
I bet. But this is part of the problem with many of Mozilla's products targeting the education space (Open Badges, I'm looking at you). Teachers, administrators, bureaucrats think they're the cat's meow. But (of course) they want nothing to do with the implementation details. But they do expect them to be usable.
"At the highest level, we're exploring whether it's possible to make a tool that lets non-devs (_not_ you folks!) who currently see their phones as a pure engine of consumption, as a place where they can create something fun or useful."
That's a fantastic idea. So are open badges. But "us folks" are the ones that (whether we work in edu IT, at an edtech company, or are fellow travellers) are expected to make these half-baked great ideas work, reliably, in the real world, for educators and students.
I'm not trying to rant. Mozilla has great ideas for education. But the poor (maybe I should be more generous and say incomplete) implementation of so many of these great ideas (Persona, Open Badges, and now Appmaker) is maddening when they're presented in a way that "not us folks" expect them to be available for production implementation.
Match point.