Lack of interesting conversation here...

[FarligOpptreden]

So, what's up with all the software / web development guys and gals? The quality of interesting conversation seems to be on a steady decline in this section. Is everyone as busy as me at work?

Where's dequadin with his daily WTF posts, butterflies and factory-building-factories-factory?

 

[guest2013-1]

I gave up on interesting conversation. I'm not at the forums: www.how-to-murder-your-clients-and-get-away-with-it.com

 

[Veroland]

I've been seriously busy with "rich internet application" technologies. i.e. client side javascript rendering of the html and not on the server

 

[midrange]

Will one of you hire me please. I don't charge much. I have to get out of design.

 

[guest2013-1]

I'm actually applying for "postman" and PA jobs as we speak...

 

[FarligOpptreden]

I've been seriously busy with "rich internet application" technologies. i.e. client side javascript rendering of the html and not on the server

It's a fad, the same as Flash. The web will go back to clean, light-weight, server-side generated pages...

 

[Veroland]

It's a fad, the same as Flash. The web will go back to clean, light-weight, server-side generated pages...

Problably, but right now it seems people want the rich feature type applications almost like fat clients, which in way this is, especially flex

 

[FarligOpptreden]

Problably, but right now it seems people want the rich feature type applications almost like fat clients, which in way this is, especially flex

Fat clients eat to much McDonalds... I like my clients to be lean, mean, bandwidth-saving machines!

 

[midrange]

I like my clients to be lean, mean, bandwidth-saving machines!

Tut tut. The rest of the world doesn't give a fvck about saving bandwidth. Write the clients obese, fadey-outy, fadey-inny, and ajaxy. More is more.

 

[Veroland]

Fat clients eat to much McDonalds... I like my clients to be lean, mean, bandwidth-saving machines!

They should stay away from mcBytes and mcMegs for sure.

In essence though, with the rich javascript engines and the like of flex (in theory) only the first download is big (+- 300 kb for flex, 180 kb for the javascript engine I'm looking at) for the engine's, then after the application components have come down and they only get downloaded on a if needed base then only data goes up and down which makes it much smaller than sending html to the client the whole time.

Especially using ajax you do not ever need a page refresh in your whole application.

 

[Necuno]

So, what's up with all the software / web development guys and gals? The quality of interesting conversation seems to be on a steady decline in this section. Is everyone as busy as me at work?

Where's dequadin with his daily WTF posts, butterflies and factory-building-factories-factory?

i call it honeymoon , but alas i'm back now

been decrypting my code i've done before i left, i mean who leaves notes

 

[guest2013-1]

One site I'm busy with (not SEO'ed btw) is about 100kb big, if I cache the images and load the jquery library from google's cache, it should be around 35kb you download, less if I cache the js files I use and follow some best pratices around that.

Then all that's in there is to process/show/insert data. Which keeps bandwidth usage super low.

 

[midrange]

Are you concerned about paying for high bandwidth usage on your server? I routinely create sites with a single image greater than 100k. I'm awesome like that.

 

[FarligOpptreden]

i call it honeymoon , but alas i'm back now

been decrypting my code i've done before i left, i mean who leaves notes

Is there a congratulations in order for the latest member of the miser... er, joy called marriage?

One site I'm busy with (not SEO'ed btw) is about 100kb big, if I cache the images and load the jquery library from google's cache, it should be around 35kb you download, less if I cache the js files I use and follow some best pratices around that.

Then all that's in there is to process/show/insert data. Which keeps bandwidth usage super low.

Ek laaik jou nuwe handtekening...

In essence though, with the rich javascript engines and the like of flex (in theory) only the first download is big (+- 300 kb for flex, 180 kb for the javascript engine I'm looking at) for the engine's, then after the application components have come down and they only get downloaded on a if needed base then only data goes up and down which makes it much smaller than sending html to the client the whole time.

Especially using ajax you do not ever need a page refresh in your whole application.

Meh, I'm still in favour of having my processing happen on server-side. You just have much greater control over what the client can see or do.

 

[Veroland]

Meh, I'm still in favour of having my processing happen on server-side. You just have much greater control over what the client can see or do.

Yep, security is a issue, but then again, it always is.

 

[guest2013-1]

There's a fine line to be walked when dealing with client side/server side and what should happen where. But once you find the balance its pretty much straight forward.

The programmers at my previous company basically adopted ajax so well that the most basic problems they get are solved by using the same hammer to smash in the same blocks into different holes. Quite amusing sometimes.

 

[Necuno]

Is there a congratulations in order for the latest member of the miser... er, joy called marriage?

i knew it was EOL when i checked my finger the next morning and saw a ring

Ek laaik jou nuwe handtekening...

Everytime i touch my code, i give birth to ten new bugs

 

[icyrus]

I've been seriously busy with "rich internet application" technologies. i.e. client side javascript rendering of the html and not on the server

When you say client-side rendering of HTML I assume you mean client-side composition of HTML? Isn't the rendering always handled client-side

 

[icyrus]

Meh, I'm still in favour of having my processing happen on server-side. You just have much greater control over what the client can see or do.

Surely no-one is putting business logic into the js layer?

 

[Veroland]

The programmers at my previous company basically adopted ajax so well that the most basic problems they get are solved by using the same hammer to smash in the same blocks into different holes. Quite amusing sometimes.

Isn't that what happens almost everywhere? Business pushes you to put something in without giving you time to build it properly and then expect you to just throw in fixes when stuff go wrong! The square peg in round hole example.

i knew it was EOL when i checked my finger the next morning and saw a ring

Congratulations

When you say client-side rendering of HTML I assume you mean client-side composition of HTML? Isn't the rendering always handled client-side

Yep, what I mean is there is no html being sent to the client side, just data (json, xml etc) as well as tag libraries, css etc. and the html gets generated on the browser. From there it's ajax up and down containing only the data unless the user want's to access a piece of functionality for the first time.

Look at Apache Shindig for example.