Comments for talkingCode

Comment on Import into MySQL from CSV/Excel, Ruby by jp

jp — Fri, 11 Mar 2011 15:51:40 +0000

works like a charm! thanks!

Comment on Error #2046: The loaded file did not have a valid signature by Blake

Blake — Tue, 28 Sep 2010 03:54:47 +0000

Check this out:
http://bugs.adobe.com/jira/browse/SDK-28016

Comment on Error #2046: The loaded file did not have a valid signature by Boydell

Boydell — Wed, 22 Sep 2010 16:52:20 +0000

Wow. That was it. You are the only one that had it figured out, and I looked at many sites and many forums, even support forums on Adobe. Funny that you posted this one day before I was trying to track down a solution. If this had happened to me last week I would have been out of luck.

My only problem is, this is not flash I built. It is the Easy Flash Uploader, a special version they built for us that supported what we need. So now I have to see if I can talk them into re-generating it…

Comment on Error #2046: The loaded file did not have a valid signature by mark van schaik

mark van schaik — Wed, 22 Sep 2010 11:23:49 +0000

thanks! was using a beta SDK version for a production app, which stopped working over the weekend and just had me quite frustrated about why. expiry date on the binaries makes sense, and testing showed it to be so.
Of course now I need to upgrade my application, but it’s satisfying to know what the issue is.

Comment on A modest copyright reform proposal by icimuje

icimuje — Sat, 26 Sep 2009 00:16:16 +0000

icimuje... College Basketball Handicapper: College Basketball... ...

Comment on Mysterious ClassCastException from Scala by ezudytubof

ezudytubof — Thu, 24 Sep 2009 11:58:00 +0000

ezudytubof... lamb shank recipes ...

Comment on Mysterious ClassCastException from Scala by nutiqoqoxe

nutiqoqoxe — Fri, 21 Aug 2009 15:04:39 +0000

nutiqoqoxe... Baby Looney Toons Wal Art ...

Comment on Haskell, GTK and Multi-Threading by Sebastian

Sebastian — Sat, 04 Apr 2009 10:41:25 +0000

Steve, I find most asynchronous programming to be incredibly painful. Haskell’s approach is to have a very light-weight threading system which means you can write synchronous code in multiple threads instead which is a far better experience in my opinion. You don’t *need* to worry explicitly about asynchronous programming precisely because you have (efficient) threads. I don’t see how moving to an even lower level of abstraction is helping.
F# doesn’t have lightweight threads so they offer kind of a specialized solution using an “async” monad which allows you to write synchronous-looking code that’s still asynchronous when run. The core principle is the same though – the programmer shouldn’t have to worry about the low-level details of asynchronous programming.

Comment on Haskell, GTK and Multi-Threading by Steve

Steve — Sat, 04 Apr 2009 04:42:12 +0000

> Instead, your main computation happens in other application threads, and all that happens in the GUI thread is updating of interface elements.

I find it unfortunate that a common perception is that threads are a good approach to this problem. While this does work, this approach to threading makes you dance around locking issues just like this article describes.

A better way to handle GUI updates is to use an asynchronous approach. That is, tasks that do IO should use asynchronous IO so that the GUI can remain responsive while something is happening. Tasks that require long computations should launch threads _as workers_ that will come back with an answer. The GUI thread should not wait on these threads by launch them as asynchronous services, and provide a function or message handler that will be called when the task is complete rather than waiting around for an answer. This works just as well by talking to another _process_ instead of a thread, and then you can use IPC methods for communication to ensure safety. Using sockets for communication between processes can even be used in an asynchronous (non-blocking) manner, which might provide _better_ performance than what you would get from copious use of threads and the accompanying sync locking.

Another approach is not to launch threads at all but instead break up the computational loop into several callbacks of a timer, or idle function. This is a way to do asynchronous processing (not blocking the GUI) without even needing to launch threads. Using threads or processes only helps in two ways:

- you can use a local continuous loop for computation, making state management easier
- the operating system knows how to split processes and threads onto multiple CPU cores

Avoiding the misuse of threads and instead learning to think asynchronously will save you BIG headaches in the future, I promise. This is made even easier (than C) in functional languages and languages that support closures because writing asynchronous callbacks using closures is a snap.

Comment on Me, the IWF and child porn by Mike van Lammeren

Mike van Lammeren — Wed, 01 Apr 2009 17:58:08 +0000

To me, there is a mindset around today that gets the idea of individual/society ass-backwards. You can call it ‘leftist’ or ‘collectivist’ or just ‘politically correct’, if you like. I’m not always sure what to call people of that mindset.

However, the part where they are totally wrong is this: They want to punish society for the actions of a few individuals, and at the same time, refuse to punish a few individuals who are clearly deviating from society. Your example here serves the first part, where every-day law-abiding people are subject to more and more scrutiny by the government, which should be the servant of the people, and not the master.

Examples for the second part are also common, such as any time a murderer or rapist gets off with an easy sentence.

I say let the internet be free and shoot the pedophiles.