JulianMorrison

201 ms·

1891.
by JulianMorrison 13y ago
The solution I've found to the "package main" problem is to put the "main" as a sub package. -src-myapp-main1 \shared_code \main2 That way main can import "myapp/shared_cod
1892.
by JulianMorrison 13y ago
I think the fundamental difference UK versus USA, is that it is very hard to inflame passions in the UK about abstractions. Concrete examples of abuse are needed to arouse our ire, and we only get angry at the actual abuse, not the potentia
1893.
by JulianMorrison 13y ago
This looks like it could be useful as a way to prototype a real program.
1894.
by JulianMorrison 13y ago
This is like printing "may contain arsenic" on candy.
1895.
by JulianMorrison 13y ago
https://github.com/imvu-open/istatd/wiki is my favouite. C++, compile to a binary and then it can send updates in a tree of agents to a master node, and maintain a replica of the master, and it does graphs too, ev
1896.
by JulianMorrison 13y ago
Unvetted cryptography is worth 1 cereal packet sekrit decoder ring.
1897.
by JulianMorrison 13y ago
ECB mode encryption is like the kind of cereal box cyphers you probably played with as a kid. For any given key, a fixed block of data goes in, a fixed block of data comes out. It won't usually be the whole of the password, but maybe &
1898.
by JulianMorrison 13y ago
It strikes me that this only grows the length of your typed in password by one bit: did they use PwdHash? Y/N. The other components of the salt, namely the site details, are implicit.
1899.
by JulianMorrison 13y ago
That's only true if your business is crudely comparable to the iterated prisoner's dilemma. But any given recruiter can expect to fall off the end of the mental space you've allocated to $BAD_RECRUITERS by the time they con
1900.
by JulianMorrison 13y ago
Everyone has an incentive to lie. The recruiter, to place people who may be unsuitable. The job-seeker, to get a job that pays more than they're worth (and then get themselves poached). The employer, to cut out the middleman and underp
1901.
Google backs modular smartphones with the launch of Project Ara(independent.co.uk)
3 points by JulianMorrison 13y ago|0 comments
1902.
by JulianMorrison 13y ago
fizz = [nil,nil,'Fizz'].cycle buzz = [nil,nil,nil,nil,'Buzz'].cycle (1..100).zip(fizz,buzz) {|a| n,*fb=a.compact; puts fb.empty? ? n : fb.join } I can't claim credit for this one. Very elegant, I thought
1903.
by JulianMorrison 13y ago
> What if you could take the percentage of taxes that you spend every year and choose whom to help with it. Then it would be spent on pet shelters and the national trust instead of homeless shelters and the national health, because middl
1904.
by JulianMorrison 13y ago
Yup, that's a phone alright. Rectangular, shiny.
1905.
by JulianMorrison 13y ago
I was trying to stream the table entries into a "tallying" type process. And of course it came out with the wrong numbers. Frustrating. I finally replaced the whole "chaser" process with a repeated full table scan with S
1906.
by JulianMorrison 13y ago
Well, they aren't getting instant gratification now, are they? I suspect a lot could be cached - that is you take a list of questions up front, what comes back from the "ticket reply" contains any further questions you'd
1907.
by JulianMorrison 13y ago
The answer is that you can't structure the transaction as a realtime query. You have to structure it as something that's sent and gives you a ticket, and the reply associated with that ticket will come back in its own time. Stick
1908.
by JulianMorrison 13y ago
I suspect that what they call unfairness, I'd call abusive behaviour. Unreasonable, unpredictable, unapproachable, blaming, personalizing, forcing agreement and then holding you ransom to what you agreed, applying a double standard to
1909.
by JulianMorrison 13y ago
No, they were stable all right, once the writes had settled down. The trouble is that sometimes it would write rows with an ascending ID sequence like 1 1,2 1,2,4 1,2,3,4 …and a read transaction that captured "1,2,4"
1910.
by JulianMorrison 13y ago
I've had keyset paging fail for me in MySQL, once or twice in every ten thousand rows, in a "chaser" process that was trying to keep up with a table under heavy write load. I obtained data with holes in it; I think MySQL ha
1911.
by JulianMorrison 13y ago
Oh that's an easy one, make it a self-steering bullet[1] too. After all, it can already GPS track. [1] http://www.theregister.co.uk/2013/04/26/darpa_gps/
1912.
by JulianMorrison 13y ago
If the task is read-heavy (example: shared cache), it's mostly harmless.
1913.
by JulianMorrison 13y ago
What were the general techniques you learned for optimizing Go?
1914.
by JulianMorrison 13y ago
Exploding things? I would say there are very few legitimate uses for those in an airport.
1915.
by JulianMorrison 13y ago
A harmless prank, srsly? An exploding pop bottle can take your hand off or cut an artery, if you happened to pick it up because it was behaving curiously. Or it could take a child's eye out, or a (sniffer) dog's.
1916.
by JulianMorrison 13y ago
I wonder if it's because they anticipate capital flight - from America, and the dollar. They would dearly love a de-dollar-ized world.
1917.
by JulianMorrison 13y ago
Hardware patents shouldn't exist. Business method patents shouldn't exist. Drug patents shouldn't exist. Gene patents shouldn't exist. All patents are bad.
1918.
by JulianMorrison 13y ago
Turing completeness, your argument is invalid. But seriously, it's not just possible to be memory safe in Go, it's fairly easy . You basically have to remember to never lock without defer mutex.Unlock() unless it can't pos
1919.
by JulianMorrison 13y ago
Patents shouldn't exist.
1920.
by JulianMorrison 13y ago
True. Although, panics do run defers, so with good coding practise it's possible to ensure that either you don't share things (but rather pass them around over channels) or things like locks are safely cleaned up.

More ›