3 ms·

All spoken here do not understand .Net enough. I worked for tagworld.com and this web project is "quite" big. Viewstate and drag'n'drops and the like are nowher

All spoken here do not understand .Net enough. I worked for tagworld.com and this web project is "quite" big. Viewstate and drag'n'drops and the like are nowhere used. .Net is NOT for web sites, it is for web projects, really big and heterogeneous, with lots of services behind. For other please use php and the like, with "quick submit to db" approach.

ratsbane 19y ago
Simple little websites like Facebook and Wikipedia seem to get by quite nicely with the quick and dirty PHP approach :-)
- jamongkad 19y ago
  Yeah ha ha "simple" in every sense of the word. You can toss in another "simple" app by the name of Flickr.
- rustartup 19y ago
  They are really simple. Try comparing them to some enterprise solution if you had a chance to work on one.
- cellis 19y ago
  its not exactly quick and dirty...its rapid development, which means they eventually can get something very complex (which I'm sure facebook has in place), but if they need to start over, they can do so quickly.
- jacquesm 18y ago
  they are relatively simple in terms of business logic. As long as you can 'shard' a problem parallel servers can solve your problem easily. As soon as that is no longer possible because of business logic constraints the real fun begins.
joe 19y ago
Could you elaborate on what makes the tagworld.com project so "big"? Edit: Also, I find it interesting that on a site so big (I mean MySpace, and thusly, on a site that should have a fair number of smart developers working on it), they have not changed the default IIS error message for something a little more site-specific and user friendly. To see what I mean, click the story's URL. :) Or is doing something like that deep voodoo on a robust web platform like .NET+IIS?
- rustartup 19y ago
  they didn't change it for the same reason that they didn't do nice design, IMO. tagworld.com is really complex thing despite its simplicity from the outside. It has unique user base and handles around 1000 requests per minute. It uses around 20 web servers and 20 other servers for db, file storage, video/photo converting. All code is written from scratch and .Net is great in maintaining the developement process. C# compiles and most errors get caught before deployment. In addition there is a buit in mechanism for validating dynamic pages, which also helps a lot. For some time we used to deploy the whole thing daily, with active users on the site. .Net is more for the corporate world with lots of legacy code and outside apps. It just can't be done almost with any language except java.
mpc 19y ago
See my comments above

ratsbane 19y ago

Simple little websites like Facebook and Wikipedia seem to get by quite nicely with the quick and dirty PHP approach :-)

jamongkad 19y ago
Yeah ha ha "simple" in every sense of the word. You can toss in another "simple" app by the name of Flickr.
rustartup 19y ago
They are really simple. Try comparing them to some enterprise solution if you had a chance to work on one.
cellis 19y ago
its not exactly quick and dirty...its rapid development, which means they eventually can get something very complex (which I'm sure facebook has in place), but if they need to start over, they can do so quickly.
jacquesm 18y ago
they are relatively simple in terms of business logic. As long as you can 'shard' a problem parallel servers can solve your problem easily. As soon as that is no longer possible because of business logic constraints the real fun begins.

joe 19y ago

Could you elaborate on what makes the tagworld.com project so "big"? Edit: Also, I find it interesting that on a site so big (I mean MySpace, and thusly, on a site that should have a fair number of smart developers working on it), they have not changed the default IIS error message for something a little more site-specific and user friendly. To see what I mean, click the story's URL. :) Or is doing something like that deep voodoo on a robust web platform like .NET+IIS?

rustartup 19y ago
they didn't change it for the same reason that they didn't do nice design, IMO. tagworld.com is really complex thing despite its simplicity from the outside. It has unique user base and handles around 1000 requests per minute. It uses around 20 web servers and 20 other servers for db, file storage, video/photo converting. All code is written from scratch and .Net is great in maintaining the developement process. C# compiles and most errors get caught before deployment. In addition there is a buit in mechanism for validating dynamic pages, which also helps a lot. For some time we used to deploy the whole thing daily, with active users on the site. .Net is more for the corporate world with lots of legacy code and outside apps. It just can't be done almost with any language except java.

mpc 19y ago

See my comments above