366 karma · joined May 10, 2011
(Folk from Minas Gerais are said to sometimes dip their cheesebread loafs in their coffee; those coming from the West drink their mate cold, from a horn called guampa, and call it tereré, whereas folk from the South drink it hot, from a bowl called cuia, and call it chimarrão.)
Though a bit proverbial, those are all region-specific and common enough that they can be thought of as "reliable enough" as a conversation starter.
Regional identification through manners and/or phonology goes back to the concept of a shibboleth [2]. This is used rather wonderfully as a turning point in many stories (without spoiling too much, I should mention that Tarantino pulled this off nicely in one of his films).
IANAL, but I can definitely see both sides of this debate being highly defensible.
Well, get rid of that and push for a change in your company's workflow. This kind of control shouldn't be deployable to the main servers at all.
Have separate, staging servers and run your tests and debugging interfaces on it, but as much as possible, don't deploy administrator interfaces to the servers that talk to the customer. [1]
[1] I'm undecided which kinds of heisenbugs would justify breaking that lemma.
He made this big, boldface disclaimer with twitter screenshots and all trying to claim "best effort is good enough" and "they won't listen", but all I saw was them listening and him refusing to speak.
For the sake of completeness, my first steps before sorting and plotting were to:
1. take the mean, median and mode of each set,
2. try and fail to use more sophisticated statistical analysis [1],
3. have a look at the minimum and maximum value for each set.
By #3 I already had a good enough guess, but I felt I had to see it.[1] In fact, could anyone point me to a refresher? I'm talking about distribution curves, regression, that kind of thing. I seem to have lost hang of it — couldn't pass my own "5 minutes to implement the simple thing" criterion.
That said, the point of parallel offerings is not to provide identical representations of a given resource. Even XML+XSLT versus XHTML might have different semantical implications, so the best assumption is that no two ways of representing a given content can ever be identical.
Well, that's a Good Thing. If I'm requesting a given resource and I signal preference for a PDF-encoded response, that implies on some level that I want a print-formatted, print media version of that resource, whereas its HTML counterpart can be hypertext and multimedia.
What you as a server are committing to is that both servings are representations of the same given resource, but without prejudice of putting each format to its best use.
This is also beautiful in that if the HTML stack proves to be a bad idea in the long run, rather than being deprecated, it can fall into disuse slowly alongside the slow rise of its successor(s). In fact, there's absolutely zilch stopping us from having more than one canonical format — any server-side MVC (or MVCish) architecture can probably handle that off the box!
EDIT: to be sure, the question of how expensive it is to develop for two different representation formats is a whole other story.
I.
This is a case where Stallman pushes the notion that software freedom === individual freedom. This notion, while defensible, is not necessarily true, and so the assessment that Android phones can't be said to respect my freedom sounds wild and passionate but while being hardly informative.Freedom is one of those words which go deep with most people, but which for the same reason have come to mean a bunch of different, oft-contradictory things. (For some definition of freedom, the GPL can't be said to respect my freedom either.)
II.
The problem here is that Google had commited itself to releasing Android's source code. Withdrawing from it is exactly the same kind of thing as Sony's withdrawing multiboot from the PlayStation: they sold us something and now they're taking it away.In that sense is Android not respecting our freedom: some of us chose Android because of something that was being offered — something Google was commited to — and now that we've voluntarily locked ourselves into that platform, Google takes that decision factor away from us.
Stallman has this weird ability to get cherry-picked for his most passionate quotes. Although I not always agree with him, it's important that we go a bit deeper and try to figure out his actual reasoning.
(My criterion for an upvote here would be if he had himself written and/or explained those programs in his post.)
All in all, can't complain about having found this in the front page.
- http://haskell.org/haskellwiki/The_Fibonacci_sequence
- http://vimeo.com/20655874 ("Faster persistent data structures through hashing")
</nitpicking>
(After refreshing, I could verify that I was not logged in, but I'm not sure if the demo was supposed to go as far as managing session cookies anyway.)
You're absolutely right about its use for password generation & management. I suppose the scheme might still have other uses where the proverbial "off the grid" aspect indeed strengthens security? Are those relevant at all?
Now, I personally couldn't pull this off, but I'd actually love to see the Math done here.
[1] Video: http://twit.tv/show/security-now/315 Transcript: http://www.grc.com/sn/sn-315.htm
But really. Nice job! :-)
I'm still a bit unsure about the part where "you're responsible for asserting that you're still alive." I'd like break it down to its basic premises and see if they actually make sense. :-)
I played around with this a while ago. Didn't think the way it's implemented solves the problem as I perceive it. (Plus, the risk of these confirmation emails ending up in spam felt a bit like a downer.)
once someone has offered something extra, it's hard to take that back.
Further: often when confronted by silence, the blabber will say something that
she didn't plan on saying.
And further: if you observe children, as I did while researching this book, you'll
notice that kids are content to sit with their friends and not say
anything at all for periods of time that would drive an adult to
reveal all manner of personal information.
[1] isbn:081447294XI suppose people sooner call the aliens soulless demons or rethink their whole religion than go half way in one direction and then stop in the middle.
/me leans back on his armchair
That said: strings are lists of chars, and Haskell is strong at pattern matching (esp within lists) in a bunch of different ways, so trivial text parsing tasks are trivial and intuitive in Haskell. For anything slightly more complex, there are regular expression and enumerating libraries which can do the job alright (and efficiently if I may say so).
EDIT: I'm sorry, can you give me an example of a problem so I can give you an example of a solution? :-)