Wow, javascript sux.

So I had to dirty myself and work on a bit of javascript myself. I needed to find out what communication protocols and techniques are available to me, and how the jax-rs implementation handles various things.

e.g. I needed to pass the parameters derived from a dynamically created user interface, plus some other structures such as an array of objects to the server.

I went with a form as then I don't need custom marshalling code on the browser end, but then I needed to manually encode/decode the array. It didn't take too many LOC to do it in the end, but it took a long time to find out what those LOCs were (albeit most of the time trying to work out how to access the app server jaxb context and how to use it to decode some json embedded in a form field).

But what surprises me about 'javascript' is just how un-script like it is. i.e. it only provides fairly low level of functionality and one has to code a lot of stuff directly. And that's before you get to some of the nasty per-browser differences. So because of both you end up with a pile of half-arsed helper api's which should really be part of the browser - and would be if the vendors could stop stabbing themselves in the back at every turn.

e.g. although you can submit a form, if you want to submit it silently you need to manually create the HTTP data packet yourself ... which is something you don't even get close to having to worry about at the server end anymore and haven't had to for years.

And the other problem is that clearly most people who author javascript just aren't coders, or aren't very good ones. So many of the solutions one finds on the net are full of bad advice, misinformation, or are just pretty much crap examples as a direct result of the blind leading the blind. So perhaps my previous issue is just a matter of finding the wrong blog post or stack overflow question ... but who can tell? (On stack overflow, it seems to be starting to suffer from the wiki-disease a bit, anal 'save the children' do-gooder watch-dogs who want to get thingy about asking precisely the right type of question in precisely the right location: I hope this attitude gets killed quickly as such crap can rapidly deteriorate).

The language itself is ok enough I guess - although anyone wedded to IDE auto-completion (like my work-mate) is lost due to it's dynamic nature, but the browser supplied run-time platform is a total joke. This is pretty much what I suspected and wrote about previously but to have it confirmed is no point of joy.

I'm still left convinced that Apple's embrace of 'HTML5 will save the world' for example is just a cynical part of their marketing campaign against Adobe, and additionally an avenue for people to buy their hardware, realise it just isn't up to the job, and force them to write custom applications then tied exclusively to their proprietary platform. The greedy pig-fuckers.

The weekly ups and downs

So I noticed in the analytics graphs an obvious pattern emerge on my google code pages, which is probably due to the hit-rate getting high enough to rise above the noise (the point of which incidentally coincides with when I put up a test release of jjmpeg).

(the numbers have been truncated)

The pattern seems to have been there before, but now it's glaringly obvious. And that is that people are hitting the site only on during working days in the USA (there aren't enough hits yet to determine if there is a trend in the hours too).

So I wonder what that means; it is just working people looking for some free code? Students doing class-work? It seems to suggest that hobby programmers are probably not that interested in it; or that the vast majority only hack during the week-days (which i don't think likely, not to this extent). The only communications i've received have been from cost-free-code snarfers and students, so at least that data point correlates - although the sample is so small it doesn't amount to hard data.

Well whilst i'm on statistics of the site I'll dump a few other observations:

• Rather modest numbers for a-hackers-craic: I broke 2K posts/month for the first time last month, and also broke 20K for its lifetime.
• I always find it pretty funny how many people searching for an image of 'g-spot' end up loading the picture on one of my rant posts. It's a photo of an ibm keyboard. It's usually in the top-10 searches for the month!
• Java FFT is still high on the search hit-rate.
• Beagleboard/XBMC still gets plenty of hits even though I haven't worked on it or posted about it for over a year. The XBMC wrap-up post is usually in the top 10 for the month
• Together the java fft and beagleboard xbmc wrap-up post are over 10% of all hits of the life-time of the blog.
• More direct searches either for my name, the blog or the projects i have on google code. jjmpeg being fairly useful is an obvious reason, but also from more activity in various forums (e.g. opencl), and more consistently using my URL or google login for drive-by commenting elsewhere.
• My google code projects are now my top referrers, although having a link off the Aparapi project added a good number of hits.
• I get a lot of hits on rambling mind-dump posts which don't contain particularly useful information: like `opencl images and arrays', or 'sse gcc and amd'.
• Quite a few people seem to be interested in 'kobo hacking'. But going by the lack of interest on the forums for anything other than a plugin to enable a few simple features, and no communications on my efforts, I would presume they're more interested in removing the advertising from the advertising-subsidised version, or cracking the drm.

The new blogger

So just this minute I was fortunate enough to have the obviously-ever-increasingly-evil google force me to use the new blogger interface as they've been threatening to do for a few months.

One side effect is that if you visit the blogger dashboard with javascript disabled you get a completely blank screen. Nice one fellas.

Other than that, it's mostly a pointless bit of re-learning that I could have done without. The old blogger GUI was pretty fugly but the new one is hardly the madonna's tit either. The way the 'Save' button changes whilst it auto-saves is surprisingly distracting and very annoying.

Oh and I forgot about that really tedious two-step extra-tab preview. Because I unfortunately had 'convert newlines to <br>' set when I created the blog (or maybe that was the only option back then update now it seems to strip <br> tags and convert to newline, so maybe i can change it now without screwing up all the old posts) I have to check newlines around every image or list or pre-formatted block all the time. Having a tab switch and a re-load makes the preview feature harder to use (i really couldn't give a flying fuck about the actual style-sheet used, I force fonts and sizes so I know nobody else sees what I see anyway).

Only plus is that the 'edit' button is back when i read the blog - that vanished a few months ago for no apparent reason.

Might be time to revisit 'wanki-ee' - maybe all that JavaEE stuff came at a fortuitous juncture after-all. Well, maybe if i had "another day every day" at any rate, as it is there is just not enough time to fix everything wrong in this world.

Web N Shit ... N Stuff.

Hmm, so i've been poking away at webifiying[sic] our client's application.

Overall i'm making pretty good progress: worked out the async ajax stuff / XMLHttpRequest, 'hidden' form submission, RESTful resource mapping, handling long-running tasks and so on. The Enterprise bean stuff is pretty good, and particularly things like JMS, all the bean types, jax-rs, and jaxb. The latter two helping to hide some of the horrible shit going on under the bonnet.

But I dunno ... it's just boring. I probably would've found this stuff neat 5 years ago, and had a puppy over it 15 years ago, but now it's still enough of a pain in the arse having to deal with that given a choice I wouldn't be doing it.

Probably help if i'd had more than 4 hours sleep each day this week ...

Kobo

So i've mostly just been using my kobo for reading lately (not a lot, but i'm usually so tired I cna barely go 5 pages before i fall asleep) - and it's crappy software is giving me the shits, particularly when reading text files. I'm not sure I could do much better, but at least I could try ...

It even got me riled up enough to have another go at working out suspend: but again I had no luck. I just can't tell how it's going into suspend mode. If I could work out that I would have enough to keep me happy and I would do some more work on ReaderZ.

But without it i'm just stuck and it just pisses me off.

Update So it occurred to me later that the problem might be more related to the wifi adaptor since I'm always doing this stuff from telnet. If I try to suspend using /sys/ it never recovers and I need to reset the machine.

Easy Burmese 'tofu'

So yesterday I managed to get away from the machine for most of the day. Actually I got a bit sunburnt pulling out weeds and doing some gardening. Also mowed the lawn and did some work on the compost pile. And planted some winter vegetable seeds in pots: I have never had any luck whatsoever with winter vegetables (if I ever get the seeds to germinate they struggle and usually get eaten to death by bugs), but maybe this time ...

Well, I've been watching SBS's latest food show lately - Luke Nguyen's Greater Meekong - with all the advertising they fill each half hour slot with now it really needs to be a full 1 hour show - but Luke is a good presenter and although the editing could be a bit better he always finds interesting food and people who want to share it.

This week he had some chick-pea 'tofu' soup thing from Burma. The soup itself looked a bit heavy for my liking but although i'm no vegetarian I'm partial to some of the fare they like. I also like to learn about ethnically or geographically important staple grains. Actually it's a bit of a bummer looking for recipes with such ingredients because all you come across is vegatarian and vegan nutters who are looking for a filling main meal - not a tasty snack or accompaniment. It also involved a great deal of work - from a stone grinder, to muslin cloths to a giant stirred pot.

Because i'm lazy, the overnight soaking of the chick-peas seemed enough work for me, so instead I just blended the fuck out of them. I first tried topping up with water but that wasn't enough and I lost track of just how much I added. But I blended for at least 10 minutes and ended up with something akin to cream at the end of it. Enough blending that you could barely taste the fibrous material you otherwise end up with.

Then I cooked it on low with a good dose of salt and a bit of tumeric (as recipe I found suggested). At this point it was pretty much just making polenta. The old man used to make that and toast it on the AGA (which doubled as our only source of hot water as kids) all the time, and we all used to turn our noses up at it; and unfortunately I never learnt to make it before he died, so I had to learn how to make it by trial and error. It's also not something I make very often so I usually forget the finer details ... but I guess 'stir constantly until you're sick of it' pretty much sums it up. It didn't go quite as hard as the polenta i've made, but then again maybe it had more water in it. By the time it turned into a bubbling lava-pit my arms were tired so I decanted it into a cotton-lined dish and let it cool.

It looks and smells like polenta but tastes a lot better. Texturally it was fine: soft and creamy with no hint of fibrousness, I'm sure not straining it affected the result but what I ended up with was quite ok.

I diced and fried some up and it was pretty much like tofu in texture on the outside, moist on the inside, and tasted ok just on it's own (closest flavour I know would probably something like a papadum). Tofu isn't something i'd normally buy since it's pretty bland and I just don't know how to select it. The pre-cooked stuff is dry in addition to bland.

Since I also made up some hummus with some of the chick peas, I had a bit of a anti-pasto arvo snack. Some olives, hummus, biscuits, fried tofu, chilli sauces, and some fresh chillies as well (and beer and wine of course).

Amongst the chillies I picked I scored a triple-habanero from the garden ... I get doubles fairly often but this is the first triple. Unfortunately my habanero crop isn't so great this year, but I noticed I still have a few hundred (~5litres) in the freezer from last year so i've started trying to use them more often - but as they are so potent, I'm sure I will still end up with more than a winter's supply worth!

Web N Shit

So, as inevitably happens, the client wants to look at some mobile interface to some of the application we have.

Which for various reasons at the moment, means: web/html5/all that jazz. Fortunately someone else is working on the browser stuff so I get to avoid javascript ...

I get to play on the backend, so that means Java EE 6 ... Boy it's been a long time since I used any of this. Well I had a play with a wiki/documentation system a couple of years ago for fun but the last time I was paid to work on it was around 12 years ago: you know back when CORBA was mentioned on the first page ...

Java EE 6 has a fairly sleep learning curve - and a lot of reading required - but so far i'm pretty impressed. As you might imagine, with a decade of maturity behind it, there is a good bit of polish in the design. Some of the errors you get from the implementations could be a bit more meaningful though - array index out of bounds exception because one didn't specify proper attributes on the class or method don't help much. So after a couple of days of swearing violently ... it starts to fall into place really well.

I knew this was coming so for the last month or so I'd been re-architecting the desktop application in a more tiered and re-usable fashion so much of the jax-rs interface just slotted straight over the top with only a couple of lines of code for each request type. But that's the easy stuff: I also need long-running async tasks, so thats another big chunk of api to get to grips with.

And the winner is ...

Well I kept poking somewhat disinterestedly at some JNI code generator ideas. Just feeling pretty blah over-all, maybe it's the weather ... hay-fever, sleep apnoea, insomnia, all a big pita over the last few days.

I started looking into m4, and it could probably create a fairly concise definition and generator: but boy, the escaping rules and special cases are such a prick to learn it just isn't worth the effort. For all the intricacies of learning m4 there's very little pay off - it isn't a very useful tool in general and as I wont be using it all the time i'd just have to learn it all again whenever I looked at it. No thanks.

The cpp stuff is still an idea, but the definitions are clumsier than they need to be; one cannot automate the parameter passing convention inferencing which is often possible.

But the exercise did provide useful for the programme design. I took the way it worked and ported it to perl instead (now perl is a tool which is easy to learn with a massive pay-off; definitely not the one to use for every problem though). Macro processors do more work than they appear to on the surface, but after a bit of mucking about (and some fighting with weird perl inconsistencies with references and so on) I had something going. Well I suppose it's an improvement; it halved the amount of code required to do the same thing so that's gotta be better than a poke in the eye.

Because the jjmpeg binding generator is the oldest it's also the crustiest - so when i care I will look into it i'll probably replace it: it isn't a high priority since what is there does work just fine.