Someone else but mee...

that have get used to the fact that Firefox crashes frequently?

"Blåser av lite ånga" för att tala svengelska, "som du gör".

Adobe är ett företag som är som en nagel i ögat,
man blir alltid besviken på dom.
Inte nog med att dom har svindyra priser på sina produkter
dom har mutat in en alldeles förstor del av marknaden med
sitt PDF format (visst PDF är en öppen specifikation, eller
till och med en öppen standard, vad vet jag. Och sure bellman
det funkar säkert skitbra inom trycke industrin med väl
inkörda rutiner kring det formatet)

Men har du prövat att läsa en PDF på en PalmPilot någon gång?

Inte nog med att man måste konvertera skiten innan man dunkar upp
den (vilket tar otroligt lång tid att göra om PDF-filen är något
längre). När man väl laddat upp skiten tar det 200 år (ingen överdrift
jag har mätt) att öppna varje sida. 200 år!!!
Mao skiten är oanvändbar.

Just läsa dokument på en Palm är imo en av dom stora fördelarna.
Du kan ha med dig ett helt (mindre) biblotek (om det är pdf blir det
ännu mindre) på ett SD-kort, dvs läsning för hela semestern, i en
liten hand-moj. Du kan till och med ta med dig ett par långfilmer.

Men om du tänker ta med dig PDF får du ladda upp ditt tåla mod.
Och när du ändå håller på ladda upp lite för mig med, jag
tänker inte göra det!!

"Now where did I put that shotgun?"

/Yours 'psychotic bastard' truly


Base Ad:
http://basecamphq.com/?referrer=colliberty
If your not already using it, start us it NOW.
(and remember to say colliberty when you join up :-)

Thing I really hate (today)

Java applets on websites!

Adobe software, and specially PDFs, but the rest of their shit such pretty much too.
(So why can't I find a replacement for Indesign or Photoshop for instance, haven't got a clue?)

Flash IDE environment, it's not programming, it's something else.

I think I hate Java Applets (pretty much all about Java I hate) and Adobe more than I dislike Microsoft. Microsoft maybe striving for monopoly but hey if they are successful it's only because the other guys wasn't good enough. Microsoft product have had a not always bad reputation, some of the stuff they do is accually quite good in comparison.

Things I'm considering switching to Apple and MacOSX though. I'm willing to try it anyway.
Linux on the desktop, haven't been convinced so far.

Oh yeah, I almost forgot.
Using webbapplications instead of REAL applications, SUCKS!
The reason is that webbrowsers do not deliver the stability that you expect from a modern OS.
E.g. your browser may crash, because your doing several thing at the same time (as you DO) and one of the things you do is loading PDF file, which crashes the whole fucking thing.
Ok, you could run two different instances of the webbrowser (at least with IE) and if one crashes it only crashes that instance, but when you dont have tab-browsing and if your supposted to keep all things seperat you would consume allot of resources of each instance (because you DO have allot of browser windows going).
And also, the point oyu remember to create the browser in seperate instance is always right after it crashes.

No, ajax webapps are the same thing throwing yourself back in to Windows 95 or MacOS 9, is that really what you want! I suggest you thing about that for a while before going the Ajax route for your next application.

This said it doesn't mean that Ajax is bad for webapps (they already have this problems anyway), just dont try to replace REAL applications with webapps just because Ajax make it look and feel like one.

Johari Me

http://kevan.org/johari?name=JohanC

Something I tried too avoid...

I always been a strong Zope advocate, but I find myself willing to step of the band-wagon because Zope isn't developing in the direction that I like. It's starting to become something that I was trying to avoid when I "joined up" (that would be J2EE like mastodont frameworks).

As you might have notice I'm not a big fan of Zope 3, and I see Zope 3 (and CMF) as technologies that are blocking Zope from evolving into that I would like to have.
Also the key feature of Zope, the Object Database (ZODB) is starting to get in the way, it just hasn't evolved enough to battle the competition from the rising of the ORMs.

The main benefit of having an transparent object database in the bottom is that persistent isn't an issue, it's handled automatically. Well you get that with an ORM too, and you don't have to rely on the database to handle version, your don't get a rigid object hierarchy (in fact you can have high dimensional object hierarchies if you'd like), you have index and fast query facilities from scratch without having to define your model twice (once for the objects and once for the ZCatalog).

Conclusion, Zope was great when it came, it was new it was object-originated, it was dynamic typing and dynamic data models, it was fresh.

Now it grown out of proportion and does seem to keep up, it's heavy, it's a dinosaur.

Flexibility vs. Productivity

I've always been a fan of flexibility in the framework, it's something that attracted me with the Zope framework from the beginning (you could add a property to any object at any time without having to change your application model, the AM was in a sense real-time changeable.

Again quoting David Heinemeier Hansson:

"I often find I want to trade flexibility for productivity. i am fine with saying, I could just do it this way, or I could do it 10 times faster."

Now, David isn't just good looking and smart, he's "hyper cool".

I find that I now days also want to trade flexibility for productivity. I don't have the time configuring Zope 3 apps, I just want the damn thing on the net with a minimums of effort.

Ok, so I'm starting to compare Zope 3 and Rails. Not have had a particularly close look at Rails (yet) I'm starting to get the feeling that both Zope 3 and Rails try to do aspect-originated stuff.
The main difference is that Rails stay true to the philosophy of the language (Ruby) where Zope 3 stray of into different non Pythonic creations, adding the flexibility but with the cost of bad usablility. Rails stray for beauty in code, and I believe code is the best way to make programs, not configurations (which Zope 3 relies on heavily).

For where I am now Rails seems to lack the co-location problems (which IMO is one of the largest problems with Zope 3). Rails also seems more true to the MCV pattern, even though Zope 3 has that pattern, it's not very well constituted to the user (calling controllers view classes for instance, it's just confusing).

Ruby on rails Partials!!!

We do it right (when Zope doesn't).
Ruby on rrails have partial which are sub-template that ar like includes but like subrutins at the sametime, os you can pass arguments.

Well, that just kicks TAL macros in the ...

I rebember how surpriced I was when I realized that METALs didn't compile to "module like" objects ith sub-routines. Haven't use TAL since then (the system I made was just over complicated and ugle, and no I didn't put business logic in the templates).

More excellent quote from the creator of Ruby on Rails framework David Heinemeier Hansson:

"... because javascript is, what's the word, Horrible!"

Finally someone that can "think"!!!

"I like Ruby so much I want to use Ruby everywhere (in Ruby-on-rails), in the model, in the controllers, in the confituation, and in the VIEWS.
And now some of you who has been burned badly before by using a real programing language in the templates are screeming "NOOOO, you can not do this. If you do that the end of the world is coming, people will flood their views with logic and conditions, and it will be a mess and you never recover."
Ah, No! Because there is no such thing as taking the logic out of the view. The view will always have logic, it will always have loops it will always have conditions. You just call them something else if that make you feel good. your still putting logic in the view, and the key realization is that that's not a bad thing. Logic belong in view because we are making dynamic web applications not just this static things. So logic in views good!" -- David Heinemeier Hansson, creator of Ruby on Rails framework (freely quoted by me :-)
Told ya!

All Go for Django...

I'm most probably gonne use Django for my little project.
I need a framework that I don't have to fight but still provides me with an efficient tool to make things fast.

My initial assuption that Django would get in my way have been shattered enough to make me put my hopes in Django. Another reason is that I don't have time or want to search any more, I want to start prototyping.

I think an apology might be in place

I must admit I didn't give Django a fair examination, now that I have visited it I am much more happy about it. As I mention before it does what I want but not in a fasion I like.

Well, the easy of making applikations with Django have convinced me that running
setup commands to get started isn't that bad after all.

I'm suspecting I will run into limitations of Django but reading the tutorial was really fun.
Allot of stuff is made for you automatically.

I think I'll keep reviewing this for a while.