Web Application VS Windows Application
-
@IT-ADMIN said:
what i do all the time is : pick up a free template and inject my code in it, sometimes i find it difficult to adapt the logic of my application into the template, in that time i content my self with only HTML code (bad looking design lol) for this reason i move to windows application because i'm not into design
I think you are getting a skewed view of programming web applications because of that. You are starting with a content management system, I think, or a web site design and trying to add code behind it. Nothing wrong with that, of course, but you would never do that with a desktop app right? You would never start with a form full of buttons and try to write an application to use that interface? You don't with web design either.
Web design is just like desktop design in that regards. You write a strong application, design is not even the programmer's job. That's a designer's job. The application and the design should not be connected.
You can add a template for good design on top, that's what Twitter's Bootstrap option is. It is relatively plain but looks modern, works well and is free. But it is just a template that modifies what you have done. It's not a website on its own that you modify. It's nothing like a template for Wordpress or something like that.
-
@scottalanmiller said:
@IT-ADMIN said:
if i work with web application, i will work with JEE, otherwise if i work a desktop application i will use vb.net, because java in windows application is a headach but in web it is OK
Oh, do you mean J2EE? I've never heard anyone call it JEE.
JEE is fine for web applications, what framework(s) do you use with it?
JEE is definitely not an efficient langauge for web development, though. Can you do it? Sure, but would you? Just because you know that language does not mean that it will make things easier. I know Java too, but I'd much rather learn Ruby to leverage Rails, for example, when actually making a web app. People use the "right" language for the "right" task for a reason.
VB.NET I would never use for anything
why you would never use VB.NET ??
-
@IT-ADMIN said:
why you would never use VB.NET ??
It's not exactly that VB is terrible, but basically. It is a legacy language that is only kept for supporting old code. It's poor to write and no serious developers work with it. It has no advantages on its own and has long ago been abandoned for good reason. The .NET framework that it runs on is excellent but C# and F# are the serious languages there.
Using VB not only means that you yourself have to deal with the unnecessary pain of a poor language but it also means that you have long term business problems. It is harder to hire someone to maintain your code - have you ever met a serious VB programmer? Not since the 1990s and even then almost no good developers would touch it. VB is a level of "tied to Windows" beyond .NET. Everything about the language is a negative. On the technical side the downsides are small, but there. On the cultural and business sides, they are rather large.
Pretty much working with VB relegates you to people who have worked in code a little starting long ago and failed to move on to better things, those that can't be hired anywhere else or those that really don't code at all and were incorrectly led astray by someone else that doesn't know how to program that "VB is easier", which it never was, leading to a history of misinformation around the language.
-
i totally agree with you, but what force me to work with vb.net the fact that the management application we have now in the company was programmed with vb.net so i have to work with this language, otherwise i have to repeat everything from scratch which is not possible at all,
-
if i want to develop and add new feature into the application i have to use vb.net
-
@IT-ADMIN said:
i totally agree with you, but what force me to work with vb.net the fact that the management application we have now in the company was programmed with vb.net so i have to work with this language, otherwise i have to repeat everything from scratch which is not possible at all,
See, that is what makes it bad - it's all about supporting legacy apps that were made poorly by people who long ago didn't know how to choose good products. So it is one bad decision followed by another or at least by an inability to update and replace.
VB.NET is very limiting, locking you to Windows, tying you to legacy thought processes. You "can" use VB.NET to make modern, good MVC based ASP.NET enterprise applications, for example, but realistically no one does this and it would make no sense.
-
-
for example if i want to change an action of a specific button, i have to edit vb.net code, this is what i mean
-
-
i swear i never use vb.net before, all the time i have that idea that vb is used by beginners and those who are not familiar with programming because it is more close to human language, i had previous experience with c++ and java but only small project but c# was my favorite,
now the company i work in, we have a programmer who is with me, and he is the one who is in charge of development, i'm in charge of everything IT except programming, now the management decided that i have to handle them both, in addition to my job i have to help the programmer because he was overwhelmed and there are too much work pending so i have to integrate with him to finish the work as soon as possible, i liked the idea and consider it a good opportunity to improve myself especially i have a background in programming
the problem now is that programmer is using vb.net all the time, every program in our company is vb.net, and i'm not familiar with vb.net not wanting to learn it lol
i do not have a choice i have to learn it in order to help developing the 3 year legacy programs we have already, in the same time i cannot change the programmer's mind -
@IT-ADMIN said:
i do not have a choice i have to learn it in order to help developing the 3 year legacy programs we have already, in the same time i cannot change the programmer's mind
"Programmer" might be a generous term
-
If you are going to make your own code, make it in something practical. If the "developer" can't program at the level of the "non-developer" maybe that should be exposed rather than everyone catering to the "developer" that can't learn a modern language to show that he's the least capable person to be doing the work.
-
@scottalanmiller said:
@IT-ADMIN said:
i do not have a choice i have to learn it in order to help developing the 3 year legacy programs we have already, in the same time i cannot change the programmer's mind
"Programmer" might be a generous term
sorry, i didn't understand ??
-
ah i see, programmer is not correct, i have to use the developer
-
@IT-ADMIN said:
@scottalanmiller said:
@IT-ADMIN said:
i do not have a choice i have to learn it in order to help developing the 3 year legacy programs we have already, in the same time i cannot change the programmer's mind
"Programmer" might be a generous term
sorry, i didn't understand ??
If he can only work in VB, I think calling him a programmer is likely too kind. Not that working in VB is that bad, it's just not a good choice for intentional development. But the reason that he is working in VB, because he is likely confused and unable to do development at even the level of a decent high school student (my fifteen year old niece who hates computers even knowns C#), makes it seem excessive to refer to him as a programmer. If he is below the competence of an intern in programming (we'd never consider keeping an intern that couldn't get beyond VB, right?!!?) then giving him a title like programmer is misleading.
-
wait i forget hhhh,i have to be fair with him, he has developed a PHP web application
-
How is his code? Does he turn out some surprisingly awesome VB? Or does it seem like he struggles to do the basics?
-
@IT-ADMIN said:
wait i forget hhhh,i have to be fair with him, he has developed a PHP web application
That's a little better.
-
To be fair, NTG did all VB 6 and then VB.NET development in the early years. Our head of development was a long time VB guy and really dedicated to it (but he also had extensive C and C++ experience, had written a CPU in software at 18 and for fun wrote a hypervisor in a week) and refused to stop using VB until we made it company policy that it was banned.
But once we did and he had no choice other than to switch to C# he spent a few days acclimating and was then very happy that we had done it. He coded better, faster and our products were seen as more serious. It was a win all the way around.
-
vb.net has very bad reputation then hhhhhh
someone has to be shy if he tell to people : well i'm a vb.net developer, shame
