Saturday, 25 August 2012

Matt 10:34 isn't a true verse, it's satanic (Salman Rushdie, please take note)

The 'no true scotsman' fallacy is a favourite. "These aren't true muslims/christians/whatever' when one of them commits a scripture-justified atrocity. Well, I've understood the fallacy to be if you go from a general set to a specific case/token, and then ad-hoc that the specific case/token is not a member of the general set, so as to cover the specific when it mismatches the generalised claims. So Chrisitans usually say theirs is a religion of love, but I say, Matt 10:34 contradicts that claim.

Let me see.

If Matt 10:34 says 'I bring the sword', then this is a specific case that violates the 'general' case of putative NT benevolence. So I'd have done the TS fallacy in this case if I'd said something like: "All verses in the NT are loving, Matt 10:34 is not loving, therefore Matt 10:34 wasn't authored by Jesus or is not a true Christian verse." This of course assumes that 'christian' necessarily means accepting every verse in the NT. I believe I've done the reverse; I've said: Here's a specifc case of a non-loving verse, which means that the general case/claim "NT doctrine is loving" is not completely true. The 'scotsman fallacy' would be to try explain 10:34 away or redefine christianity so as to preclude 10:34 from being 'true'. So, symbolically...

For all Scottish S, it is true that they don't take sugar in their porridge (~P)
Alasdair, born in Glasgow, (A) does take sugar in his porridge, (P), therefore A isn't Scottish (~S)

Interlocutor's claim: for all S, S: ~P (a possibly false generalised premise)
My objection: A, A: P
Interlocutor's false conclusion: therefore A: ~S 

This might even generalise as [S -> ~P, P, therefore ~S] or [ S v P ]. (Am I right? - I'm not sure. If it's Sunny, then it's not Precipitating. It's precipitating, therefore it's not sunny. That seems generally true.)

But since A was born in Glasgow (presumably necessary and sufficient for being Scottish), S, which contradicts S, S: ~P, it seems to follow that

A necessarily: S
so all that we've established is that there's a contradiction between
A necessarily: S and
A, A: P -> A: ~S

The fallacy is when you reply "well in this case, sugarless porridge overrules Glasgow", no?

So if no true Christian would say/do something vicious (C, C: ~V)
I ask for an explanation of Matt 10:34, call it M, M: V (vicious Matthew).

Interlocutor: for all C, C: ~V (a possibly false generalised premise)
to which I reply: M, M: V,
To which my interlocutor has to reply: therefore M: ~C 

Which suggests that arguing that M is not christian is a scotsman fallacy. A, A: P, therefore A: ~S

where I have

M, M: V, therefore M: ~C

Which is analogous.

So to reply that Matthew 10:34 doesn't represent christian values is a scotsman fallacy. One has to abandon the first premise that (P, P: ~S) or (C, C: ~V) - ie accept that to be christian is to be sometimes vicious, and to be scottish is to sometimes put sugar in your porridge.

Incidentally, the context of the verse is about giving up your family to follow Jesus, it’s not specifically about violence.

Thursday, 23 August 2012

Why I prefer spotlight to the Dock, but still hate spotlight

Hi Apple.

Spotlight is really annoying - sorry.

1. It indexes inserted flash disks by default. What is the point? It should not index attached disks unless you explicitly say so. Maybe when the person starts typing in the "find" column in the finder, then do the indexing, or just use the unix Find utility underneath. I don't WANT it to index my 1 TB backup drive with +- 1 million files. PLEASE. I know I can drag the icon into "privacy" in the system prefs, but that's a schlep. How about you just make it NOT do that by default, and only make it do that (index) if I try to "find" something on the drive. And anyway, what's with spotlight giving a progress bar while it indexes an external drive? I want to be able to search my internal drive while it is indexing the external. Plus it maxes out the CPU and your average joe user has no idea why his mac is overheating and phones me to ask.

2. I'm very seldom going to keep contents on a flash disk constant. A flash disk is just a piece of junk that I copy stuff onto and GIVE to people or lend to them, and I format/erase it every time. Why waste my time indexing it? Especially when I copy lots of stuff onto it? It just slows my mac down and annoys me and fills the flashdisk with a database file of search results that aren't going to work on their windows(tm) pc anyway!

3. The choices/search results are incredibly annoying. Most of the time, I want to show a file in the finder, not open it, and I want it to show me the most recently found or opened item that matches that string typed. Suggestion: when it shows a found result, make it have a button next to the item saying "show" and another saying "open", or something (eg rightclick the item found and it says "show in finder", leftclick it and it opens it. I realise there are workarounds (open the file, rightclick the title in the titlebar, etc)

--edit: Angelo Kyrilov tells me: "There is a simple way to get it to do what you want. If you hold down the command key while clicking on an item, it shows that item in Finder. I too often find it more useful to find the item's location rather than open it."

4. If I have a folder called 12-01 from december 2001, and a file called 12-01.pages which I made on 1 december 2011, SURELY it should offer the latter file first when I search for 12-01? I get it that it thinks it's a calculation, but ...If I have two files called 12-01, e.g. a spreadsheet, a wordprocessing file, etc., which I just edited a few seconds ago, it should offer the most-recently-modified items first? The same applies to apps. Offer the most-recently opened first.

5. If I type ADOBE, I don't want to see all the cruft that Adobe installs on my filesystem, like the help viewer and the auto updater, I want it to offer Photoshop first, then Acrobat, then Distiller, in the order of what I am most likely going to use. So like with iTunes stars or number of times a track is played, keep track of which are my favourite or most opened apps, and offer them first.

This would be great, because then I could get rid of the dock, which is unusuable, because I have so many app icons and minimised windows that I cannot see what I'm looking for, and always end up giving up and going to spotlight to open something that is actually visible (microscopically) in the dock. Eg at the moment I have 40 icons open - and I'm just surfing. 8gb RAM. Your apps take so long to open that I never quit apps. Now, when I'm working seriously, it gets to about 50 items in the dock including minimized windows. Icon size goes down to about 10-15px. I realise I can enable the magnify effect, but that just makes the icons wobble and move, and hard to hit, and I STILL have to scrub the whole dock to find what I want. I also realise I can turn off magnification, scrub the dock, and see the item names, but that wastes my time, because I have to do an exhaustive search from top to bottom (my dock's right-vertical aligned).

It would just be faster if I could hide the dock and ONLY use spotlight, and it only showed my most recent apps. In fact, the only reason I keep the dock open at all is to drag files into app icons to overrule the suffix app default, e.g if I want to force an html file to open in BBEdit rather than Safari (for just one case).

I ALSO realise there's a "defaults write" hack to enable this in the dock (show most recent items), which helps a little, but the icons it opens are massive and it brings up a scrollbar. Here's a rule of user interface design: avoid scrolling as much as possible. It's horrible and annoying and wastes time. Try show everything at once, tiled, visibly, with file titles. Like the App Launcher thing on iOS that you moved into Lion/MountainLion. Preferably without a paginator - just shrink the icons to a user-defined limit (icon size minimum and numofdisplayeditems maximum being calculated by icon size limit and screen size). IE a version of dashboard/exposé/launchpad/launcher/whatever you want to call it today, that works.

6. Another example, if I type 2012, I expect to find first items CALLED 2012-something (find ./ -name). I have several. it should list all of them, files first, then folders. After that, I expect to see files that CONTAIN the string 2012 (grep) inside them. After that, I expect to see items that I used or opened in 2012 (find ./ -mtime), in most-recent date order first. Surely this makes sense?

7. Why on earth would the find function in the Finder give completely different results? They should be the same. Find in the finder seems to do a grep only, or show date modified only, when I search for 2012. It should come up with the file called 2012, first, then the folder. Moreover, why on earth is its default scope my entire computer? That's ridiculous. Most of the things I'm searching for are either files I misplaced or mis-sorted, or email contents, in my local homedir.

8. Can we use operators in our spotlights/finder searches? If not, why not? If so, where is/are the manual/instructions? Can I say &, |, !, -, etc? I tried it, and it seems to do something weird; it seems to assume, for example, that 2012 is always a date search and never a string filename search. I tried filename:2012 & .pages, and it still didn't bring up my file called 2012.pages. You know, I really miss the Find command from System 7. That rocked.

Thanks for listening.

Thursday, 16 August 2012

memorising morse code

As you're no doubt aware, Morse code is a series of dots and dashes for letters of the alphabet. Assuming you don't care to memorise something so difficult, and that you can write out numbers as words, and that you speak english and don't care for diacriticals, the following sequence is what you get if you turn morse code into computer binary:


How did I work this out? Well, let's start with dashes are zeroes and dots are ones.

morse as binary: dot = 1, dash = 0

a 10 = 2
b 0111 = 07
c 0101 = 05
d 011 = 03
e 1  = 1
f 1101 = 13
g 001 = 001
h 1111 = 15
i 11 = 3
j 1000 = 8
k 010 = 02
l 1011 = 11
m 00 = 00
n 01 = 01
o 000 = 000
p 1001 = 9
q 0010 = 002
r 101 = 5
s 111 = 7
t 0 = 0
u 110 = 6
v 1110 = 14
w 100 = 4
x 0110 = 06
y 0100 = 04
z 0011 = 003

t, m, o = 0, 00, 000 = - -- ---
e, n, g = 1, 01, 001 = . -. --.
a, k, q = 2, 02, 002 = .- -.- --.-
i, d, z = 3, 03, 003 = .. -.. --..
w, y = 4, 04 = .-- -.--
r, c = 5, 05 = .-. -.-.
u, x = 6, 06 = ..- -..-
s, b = 7, 07 = ... -...
j = 8 = .---
p = 9 = .--.
L = 11 = .-..
f = 13 = ..-.
v = 14 = ...-
h = 15 = ....

starting at zeroes:
tmo (0), eng (1), akq (2), idz (3), wy (4), rc (5), ux (6), sb (7), jplfvh (8,9,11,13,14,15)
10 and 12 in binary are missing.

so, if you remember to exclude binary for 10 and 12, morse code is:
tmo eng akq idz, wy rc ux sb, jplfvh (0,1,2,3,4,5,6,7,8-15)

and if you remember four batches of three, then four batches of two, then the rest as jplfvh:

gives you the alphabetic order of morse code rendered as computer binary. So you just have to remember a different alphabetic order, and how it unpack it. 


alternatively, arrange the alphabet into order of binary values:

t 0 0
m 00 00
o 000 000

e 1 1
n 01 01
g 001 001

a 10 2
k 010 02
q 0010 002

i 11 3
d 011 03
z 0011 003

w 100 4
y 0100 04

r 101 5
c 0101 05

u 110 6
x 0110 06

s 111 7
b 0111 07

j 1000 8
p 1001 9
l 1011 11
f 1101 13
v 1110 14
h 1111 15



Or sort into frequency of letters:


e .
t -
a .-
o ---
i ..
n -.
s ...
h ....
r .-.
d -..
l .-..
c .-.
u ..-
m --
w .--
f ..-.
g --.
y -.--
p .--.
b -...
v ...-
k -.-
j .--
x -..-
q --.-
z --..


Or sort into sequence of dots/dashes with dashes (zeroes) coming first:


one bit letters:
t -
e .


two-bit letters:
m --
n -.
a .-
i ..


three-bit letters:
o ---
g --.
k -.-
d -..
w .--
r .-.
u ..-
s ...


four-bit letters:
j .---
h ....
c .-.-
l .-..
f ..-.
y -.--
p .--.
b -...
v ...-
x -..-
q --.-
z --..

Wednesday, 1 August 2012

mac laptop black screen of death problem - black screen after sleep

If your mac laptop screen goes black for no reason after a sleep, it's called the 'black screen of death':

MacBook Pro Video Update 1.0 (Snow Leopard)
This update addresses an issue where MacBook Pro (15-inch Mid 2010) computers may intermittently freeze or stop displaying video. For detailed information about this update, please visit: The update is for Snow Leopard.

Some people claim it is fixable. Apparently if you boot with the shift key down, it turns the screen back on. I tried it and it seemed to work. The reason I was forced to investigate was MY laptop started doing this. So much for apple quality. At any rate, there was another webpage that says that after you've booted, delete /var/vm/* - ie open terminal, type

sudo rm /var/vm/*