Lack of interesting conversation here...

F

FarligOpptreden

Executive Member
Joined
Mar 5, 2007
Messages
5,396
Reaction score
31
Location
Gauteng
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? :p

Where's dequadin with his daily WTF posts, butterflies and factory-building-factories-factory?
 
I've been seriously busy with "rich internet application" technologies. i.e. client side javascript rendering of the html and not on the server
 
Will one of you hire me please. I don't charge much. I have to get out of design.
 
Veroland said:
I've been seriously busy with "rich internet application" technologies. i.e. client side javascript rendering of the html and not on the server
Click to expand...

It's a fad, the same as Flash. The web will go back to clean, light-weight, server-side generated pages... :p
 
Veroland said:
Problably, but right now it seems people want the rich feature type applications almost like fat clients, which in way this is, especially flex
Click to expand...

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

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. :cool:
 
FarligOpptreden said:
Fat clients eat to much McDonalds... I like my clients to be lean, mean, bandwidth-saving machines!
Click to expand...

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.
 
FarligOpptreden said:
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? :p

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

i call it honeymoon :D, but alas i'm back now :eek:

been decrypting my code i've done before i left, i mean who leaves notes ;)
 
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.
 
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.
 
Necuno said:
i call it honeymoon :D, but alas i'm back now :eek:

been decrypting my code i've done before i left, i mean who leaves notes ;)
Click to expand...

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

AcidRaZor said:
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.
Click to expand...
Ek laaik jou nuwe handtekening...

Veroland said:
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.
Click to expand...
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.
 
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.
 
Veroland said:
I've been seriously busy with "rich internet application" technologies. i.e. client side javascript rendering of the html and not on the server
Click to expand...

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 ;)
 
AcidRaZor said:
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.
Click to expand...

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.

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


:D
Click to expand...

Congratulations

icyrus said:
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 ;)
Click to expand...

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.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X