I need to learn some web programming shit, cause nobody wants a programmer who doesn't know shit about the web. What's a good resource to start learning this shit? What's a good "project" to do to get some of this under my belt? Any books or anything? I'm plenty good at C# and my Java is rusty. I've got VS2010 at my disposal.

Thx in advance, and try to keep the trolling to a minimum.

And, just to make BobbyDigital happy, no, I don't think throwing a flag at my computer will be productive, now fuck off.

7/27/2011 5:26:59 PM

Web programming encompasses about 20 different languages. At least define the language you want to learn.

7/27/2011 5:30:09 PM

You should start with HyperText Markup Language:
http://www.w3schools.com/html/default.asp

7/27/2011 5:31:14 PM

^that was going to be my first link I posted, but after hearing C# & Java it sounded like he wanted to program a web app, not a webpage. I agree though, html is the first place I'd start for webpages.

7/27/2011 5:34:35 PM

that's what I am asking. I don't know if I should make some straight up HTML or go w/ ASP.NET or whatever the open source alternatives are. No clue. please guys, I have a match tonight

7/27/2011 5:37:34 PM

If you want to stick to C#, I'd guess you probably want to do ASP.NET. I was just screwing around with code-behind the other day for this (http://www.rockpaperazure.com/) and it seems pretty straightforward

http://webproject.scottgu.com/CSharp/HelloWorld/Helloworld.aspx

Depending on what you want to do, you need to learn HTML, then CSS, then optionally some javascript (with heavy use of jquery).

Write a simple web app approximating a blog or twitter. Login, logout, post shit, delete shit. Easy.

7/27/2011 5:59:33 PM

^ yup. learn ASP.NET MVC. build a simple blog system or something just to learn the ropes

7/27/2011 6:08:29 PM

hey noen, when are we going to be able to deploy WPF apps to the web and have the CLR convert XAML to html/js/css?

web "languages" suck and i'd rather do xaml.

7/27/2011 6:11:53 PM

another good way to learn

subscribe to the top users of a technology you want to learn on stackoverflow

if you want to learn html, css, javascript and jquery, subscribe to these guys rss feeds
http://stackoverflow.com/tags/html/topusers
http://stackoverflow.com/tags/css/topusers
http://stackoverflow.com/tags/javascript/topusers
http://stackoverflow.com/tags/jquery/topusers

[Edited on July 27, 2011 at 6:22 PM. Reason : .]

7/27/2011 6:22:00 PM

Definitely dig into HTML/CSS first.

After that go I would say go ASP. I went PHP/MySQL and sort of regret it. A lot of jobs i find require ASP expertise.

Once you get your language and database down, i'd learn some java script / jquery to do some advanced functions.


[Edited on July 27, 2011 at 6:30 PM. Reason : s]

7/27/2011 6:30:39 PM

^^I love wasting my time reading shit, don't get me wrong (wish I could find some good development blogs/podcasts).

But in my experience, most stackoverflow questions are about really obscure language behavior or someone trying to do something seriously complex. I usually only go there when I have a problem. I'm not sure how browsing those would help a beginner.

[Edited on July 27, 2011 at 6:32 PM. Reason : ^^]

7/27/2011 6:32:09 PM

^^ just to nitpick at you...ASP usually means classic ASP (very old, pre-.net rarely used anymore). ASP.NET usually means ASP.NET WebForms (old but still used in a lot of places) or ASP.NET MVC (the most recent web platform). i wouldn't recommend investing any time in classic ASP, and very little in WebForms

^ i'm not saying read every one in depth

i browse through them quickly in google reader and if i see a question that looks relevant to something I might do, I read the answer. otherwise move on


[Edited on July 27, 2011 at 6:41 PM. Reason : .]

7/27/2011 6:39:56 PM

Learn LESS: http://lesscss.org/

7/27/2011 6:55:37 PM

Sure. While we're at it: http://jashkenas.github.com/coffee-script/

7/27/2011 7:05:33 PM

^^ see also: SASS, SCSS

7/27/2011 7:06:41 PM

Quote :

"^^ just to nitpick at you...ASP usually means classic ASP (very old, pre-.net rarely used anymore). ASP.NET usually means ASP.NET WebForms (old but still used in a lot of places) or ASP.NET MVC (the most recent web platform). i wouldn't recommend investing any time in classic ASP, and very little in WebForms"

yep shows you how much i know about it. Will dig into one day. Thanks for the clarification though.

7/27/2011 8:15:44 PM

^^but LESS is more because you don't have to run an external program to make the CSS from it

7/28/2011 8:05:47 AM

itt we act like we don't all recycle the same CSS 99% of the time.

7/28/2011 8:56:07 AM

I wouldn't want something as critical as CSS to be dependent on JS

Besides, the variables are neat, but the rest looks like a clusterfuck of bad ideas

7/28/2011 9:04:33 AM

dumb question, but why not just output the CSS from your server side scripts?

7/28/2011 10:35:26 AM

Well, there are a couple of reasons:

1) If you're looking to use one of these for something reasonable, the stuff you'd be looking to dick around with in a stylesheet is stuff that happens client-side, so server-side does you no good -- especially in this age of feature-detected over browser detection. PHP can tell you that a browser is a browser, but not that it's running at a resolution of 800x480.

2) It puts more load on the server for no real reason and you there's the potential that your generated CSS file could take longer to serve than your page does. If you let JavaScript do it, you offload that responsibility to the client-side.

3) CSS files should cache pretty heavily (because they generally don't change often) so you may not always serve the proper CSS file if the URL is static but the content isn't.

If you really need CSS variables use something that generates static CSS files. Using JavaScript or a server-side language to do it on-demand is just silly.

[Edited on July 28, 2011 at 10:46 AM. Reason : .]

7/28/2011 10:44:36 AM

Being that I work on a relatively small, but commercial web application, I can tell you that we would be fucked without a solution similar to lesscss. Granted, we do our variable replacement as a design-time script, not a runtime script. But there's nothing that says lesscss can't be used the same way as well.

It saves a ton of time, especially when you're managing multiple themes for an application.

7/28/2011 11:58:24 AM