Monday, January 3, 2011

Language Trends (Predictions for future?)

Programming Language Trends (Dec. 2010)
Programming Language Trends (Aug. 2010)
 
Not a clue - but interesting to see java in forefront and an increase in objective-c (certainly not my favorite :P)

Shakes fist at iPhone

Saturday, November 27, 2010

Eclipse Update :: Android update :: OS Update

When free-software costs you development time, it's not free - its costing you! Now that I have your attention here's my disclaimer:

I have had equally horrid experiences with other expensive OS' and development tools.

My dilemma has always been with trying to reconcile the differences and find what works best for me.

So who is to blame when a working development environment just "stops" after a week of updates. So Ubuntu had a minor distro release (10.10) - I waited over a month before installing, Eclipse (3.5.2) had a series of seemingly innocuous updates, and the latest version of android development had a minor bump (.7 to .9 release). To make matters even more convoluted, I'm also running an x64 bit OS on top of it all.

What is the issue - the Android project type is no longer available from the Eclipse IDE? Compiler can't reconcile imports, keywords etc. Horrible. So like any good troubleshooter what do I do?

I tinkered with various settings (for awhile - how bad could it be) then I remembered it took less than 30 minutes to set-up before. I un-installed everything (downloaded the latest of all-the-above - installed) - and restarted; no love - no joy - but a slew of half-muttered obscenities.

The real tragedy of this is that I've been working with both Linux::Eclipse and Windows::MonoDroid and I actually preferred the Linux set-up.

It was clean, seemingly more stable (has been a plugin provider for a long time), generally unobtrusive and the resulting program responded better - i.e. very snappy!

So after wasting half-a-day tinkering with Eclipse - I'm removing it completely for now. If I want to develop on the Unix side of things maybe I'll try Netbeans with Android, though it seems younger and potentially more unstable than Windows with MonoDroid (as it is in its .2 release). 

I'm so frustrated at this point - I don't know if I'll continue for today. Ah well, live learn.

UPDATE: Just because I can't leave well enough alone. I figured out a solution to aforementioned problem(s).  This assumes that you've unpacked the SDK to the same path as before (and that you've already added to PATH).

With the new Android SDK - make sure ALL Shell Scripts have execute permissions (under \tools) chmod +x

Completely uninstall everything from Eclipse.

Delete the .eclipse folder under home (with whatever reside exists in there)

Reboot (for good measure)

Run android script (follow Google destructions as before)

Reinstall Eclipse/ADT Plugins/ etc. -> will be golden afterwards.

MORAL: Living on-the-bleeding-edge hurts (just a little).

NOTES: Not at all impressed with NetBeans 6.9 after trying it out - feels like a work in progress.

Friday, October 1, 2010

iPhone and MonoDevelop

Seems that initial reports (back in April) about Apple dropping support for anything but Objective-C was aimed primarily against Adobe - and not Novell. So MonoDevelop (w. MonoTouch) can still be the choice development-platform for i(Whatever) applications. Full article (complete with dispelling misconceptions, etc.) stumbled upon here.

Saturday, September 4, 2010

Google University - laid back

Who doesn't love Google? Ok, don't answer that! They've recently made course material available to to public. Which is kind of cool since I've established an interest in the Android platform of late - and have been experimenting with the DI containers available for the platform; specifically Gin and Guice. I just know Snoop Dogg would be proud!

Saturday, July 31, 2010

Android

I've been disappointed with Windows Phone development tools of late; and am hesitant/resonant  to install over a working copy of Studio 2010. I think it's great that the preview express tools are available - and if I had a spare computer I would probably install them.

Instead I decided to take a look at the Android platform - all things considered, isn't that bad. Up and running quickly on a Linux distro with Eclipse and the SDK in less than 15 minutes! Plenty of resource materials available for the platform and a wealth of Google APIs just waiting to be leveraged.

Java still, unfortunately is the ugly older step-sister of C#, and I miss a lot of the features I've grown to love with the .NET CLR. The Android emulator is great - although it takes 30 seconds to initialize (from a monster machine). Another interesting development is that of MonoDroid; which promises to bring CLR goodness to the platform.

Another funday saturday!

UPDATE:
Interesting work - it really appears to me that anyone working in the enterprise NOT focusing on REST/OData services (sans the Entity Framework - of course!) is living on borrowed time.

(Case in point)

End-users expectations are rising, and they will want their same business applications (to a greater or lesser degree) on their desktops, laptops, tablets and phones.

Why am I wasting time writing this? There are oodles of code to be written.

Of Interest
Restlet and OData
Interop. Services
Sharing is Caring (OData or GData) - or is it?
End-to-end

Clouds without tears?
Lokad Development Tools the Windows Azure Partner of the Year 2010 (June 23rd)

How I came by Lokad
http://abdullin.com/journal/2010/7/29/lokad-cqrs-v1-for-windows-azure-in-september-2010.html

http://abdullin.com/journal/2010/6/12/lokadcloud-vs-lokadcqrs.html

Monday, July 5, 2010

Silverlight in an Occasionally Connected World

And the answer is...anyone?...anyone at all? Microsoft Sync Framework! (I didn't believe it either.)

Until then (roll-your-own) in isolated storage.

Saturday, May 1, 2010

Unity + Silverlight 4.0 + VS2010 + Prism = Heartache

Found an issue yesterday that caused me to lose half-a-day. It seems that The latest V4 drop of Prism (including the Unity container) has an issue resolving partial classes. The signature: Container.Resolve[shell]();

Would not compile - at all! Note: for those of you paying attention, replace the brackets with the appropriate greater-than, less-than signs!

It seemed as if the source code was not in sync, which is typically the case with most SL projects. Nope, was absolutely horrendous experience. Turns out someone also "discovered" the issue and promptly when to CodePlex to report it, I'd give them "props" but I am unable to link to the original issue - which for all intensive purposes is not on the site anymore. Curious.

To be fair - I wouldn't typically resolve to a concrete instance anyway, but when dealing with newness, I find it best to take smaller steps! I'm abandoning Unity for present and looking into Ninject to meet my Silverlight needs. Might consider MEF if it wasn't so attribute "dirty". It feels unclean to drive the heart of your composition framework with attributes; also I'm not sure how I feel about the sheer "randomness" of potentially IMPORTING multiple modules within a given view. Silverlight Goodness (with Blendability in mind!) Another funday morning.