Web programming vs software programming [closed]?

If you want to write web-based software, then concentrating on web-based programming would be ideal. Conversely, if you want to write desktop software, then concentrating on desktop-based programming is your ticket. More seriously, if you're looking for career advice, then programmers.stackexchange.Com and your local job listings would probably be a lot more productive than this particular site.

Either way, you'll probably be writing code in some language that could be used for both (java, c#, whatever) so you'll want to have solid knowledge of that. If you're just starting out a career in programming, then web-based programming is often easier to get going in just because the bar to entry is often lower (free tools, simple environments). Furthermore, don't believe any hype you hear out there, desktop software is not going to disappear any time soon, and neither will web applications.

Both paradigms are useful and appropriate in different (and sometimes even overlapping) circumstances. Both are useful skills to acquire and perfect.

There is no 100% correct answer to this, but the trend seems to be moving toward cloud computing (web apps). Personally I hated CS in college and it wasn't until I realized that I could combine working on the web with programming that it became interesting to me again. So, I would say do what you are passionate about and that will be the best for you.

Software programing is an all inclusive term. The application you build to run in a web browser are as much software as the application you build to run on directly on an operating system. And the difference between them is really only noticeable in the UI layer.So the choice between which type to build should be based on the demands of your application and your target audience.

Proper development practice will teach you to septate your concerns. Your business logic (the meat and potato of your application) should be separate from your UI logic. The reason for this, is that if you follow such a a practice, your business logic is then shared by each type of application and only a UI layer would need to be created for the different platforms..

It probably does. So what's the difference? If you're developing only on the server side, you have the same performance concerns.

If you're developing only on the client side, your only difference is whether or not you have to know all the esoteric bugs that make each browser slightly different. These are subject to change with time, so it's probably not as important to "keep up to speed" on them if you're not doing a job that requires you to know them.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.