Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

worst advice for starting programmers

Name: Anonymous 2008-10-05 16:24

do you have common knowledge of programing? or are you starting from square one?

If you have a understanding of structuring a language then go ahead and jump into something like Visual Basic or C++, depending if you want to program object oriented or not...

but if you have no knowledge, start with something easy like Pascal, just to learn how to structure things...

Alex broke it down pretty well...

Name: Anonymous 2008-10-08 14:12

I wonder if people are confusing VB and VB.Net.
VB has been functionally dead (read: legacy) for 7 years now.
VB.Net is a new language based on the VB syntax.
There is a new version of VB comming out but it is focused on being a scripting language.

It would not be bad advice to tell someone to start programming with VB.Net and the .Net framework.
-It is a proper class based OOP language.
-The library is extensive, useful, source code availble and not faggy like Java's. Seriously, JButton (JavaButton). JButton as opposed to what? CButton? Fuck proper namespace useage.
-It is cross platform, kinda. The .Net CLR is a publshed standard and so is C#. VB.Net just isn't part of that but compiled code will run on other platforms with something like Mono.
-You can use it to make desktop apps, web apps (with an extensive framework for that), mobile apps etc.
-Your knoweldge of the .Net framework does not go to waste with other languages as 25+ are supported.
-You can actually get a job with it.

Name: Anonymous 2008-10-08 14:22

>It would not be bad advice to tell someone to start programming with VB.Net and the .Net framework.

I lol'd heartily

Name: Anonymous 2008-10-08 15:03

-It is a proper class based OOP language.
Wonderful, more newbies who think OOP is da bestest.

Name: Anonymous 2008-10-08 15:28

>>43
Just ignore them until they realise that OOP is not the only way to do things

Name: Anonymous 2008-10-08 16:29

Seriously, JButton (JavaButton).
No, JButton (Swing) as opposed to Button (AWT, which predates Swing).

If you weren't completely ignorant of the history and philosophy of the Java language, you would understand.

Name: Anonymous 2008-10-08 16:41

Little-known fact: the J in all Swing classes stands for JUDAISM.

Name: Anonymous 2008-10-08 16:56

>>45
What the fuck does J have to do with Swing?

Name: Anonymous 2008-10-08 17:09

>>47
Swing is Java's standard GUI toolset. It really isn't that difficult.

Name: Anonymous 2008-10-08 17:36

>>48
a) You have been trolled by >>47.
b) >>47 is stupid.

Name: Anonymous 2008-10-08 20:16

>>49
Or, possibly,
c) >>48-49 are ignorant of J[1]

[m]----
[1] - J Home http://www.jsoftware.com/

Name: Anonymous 2008-10-08 20:17

MY EYES! THE GOOGLES DOES NOTHING

Name: Anonymous 2008-10-08 20:25

>>43
>>43

Self indulgent shit heads. No one said OOP was the only way. The idea here was that if you were gonna OOP, you should OOP correctly. Was that simple sentance too hard for you to understand.

>>45

If you weren't completley ignorant to what makes a good library you would understand the stupidity of naming a button jbutton and not a more descriptive name like button because that is what the fuck it is. Or can java devs not namespace correctly. Why call it an int, when we can call it a jint!

Name: Anonymous 2008-10-08 21:46

>>48
But AWT was Java's standard GUI toolset beforehand.  It's no less Java than Swing.  The whole J prefix is just fucking stupid and inconsistent.  They could have at least used S or Sw for a prefix, that would have made SOME sense.

Name: Anonymous 2008-10-08 22:23

>>52
You listed OOP as its selling point. Be more clearer.

Name: Anonymous 2008-10-08 22:42

>>52
Jesus Christ, do I have to spell everything out for you people? AWT was the standard widget toolkit for Java 1.0. It turned out to be unpopular, so was effectively superseded by Swing in 1.2. Now you can't expect everyone to go around calling everything by the fully qualified names javax.swing.Button and java.awt.Button, can you? Hence JButton. Why the J? Because Swing is now the de facto widget toolkit in Java. Case closed.

Name: Anonymous 2008-10-08 23:35

>>55
Yeah, but what was wrong with SButton? Because Swing is now the de facto widget toolkit in Java.

Name: Anonymous 2008-10-08 23:36

>>55 drank the kool-aid

Name: Anonymous 2008-10-08 23:47

>>57
There are a lot of legitimate criticisms of Java in general and Swing in particular, but the naming of classes is a very silly one. All focusing on it demonstrates is an ignorance of the actual problems.

Name: Anonymous 2008-10-08 23:49

>>55
Namespaces exist to never be used.  Got it.

Name: Anonymous 2008-10-08 23:51

>>56
No, Swing is now the de facto widget toolkit in Java.

Name: Anonymous 2008-10-09 0:11

>>55
Maybe they should have corrected the libraries so that you wouldn't need to use AWT and Swing simultaneously, thereby avoiding collisions. Or maybe Java should have a kick-ass module system like Haskell's, which allows you to explicitly hide imports.

Name: Anonymous 2008-10-09 2:31

>>54

The point is, if you OOP at least do it correctly. Unfortunately what is correct OOP is up for debate. But there are some fundamentals. One is that there are different kinds of OOP. VB.Net and C# are class based OOP. Everything is an object with them, a fundamental. And there are a host of others. I am not saying they do it the best and they are the only ones. There could be a huge discussion about this and it ends with Smalltalk basically being the only true OOP language because it was created to be exactly that. The point is, at least as of right now, it is a correct class based OOP language.

>>55

So now swing is the de facto. What happens when a new de facto comes out? Impossible you say, well it did happen before. Will we have J2Button?


>>58

You are very correct. I wanted to be quick and succinct and mention a very basic problem. If they can't even name their GUI widgets correctly, you can easily see how there would be many other problems. Like I said, J2Button or maybe JEnterpriseExtremeButton (or similar) is inevitable.

You wanna know another problem with Java that I hinted at, the Java Framework is tied to the Java language. I know other languages have been tacked on with much effort (and no popularity) and Sun has been working hard for a long time now to get dynamic languages on it and apparently failing. At least .Net is not tied to a language, they just released 2 similar languages with 2 familiar syntaxes with it. The .Net CLR and C# were open standards before Sun did the same with Java.

You wanna create an ASP.Net site totally in Python, you certainly can (with visual studio support or without). You want to dynamically compile a block of Python code that dynamically compiles and calls a JavaScript method from C# while all use the base .Net libraries and/or libraries you created in VB.Net? You can do that too.

Can you nativley do that in Java? No.

You wanna create some performant generic/templated functions in Java? No. You certainly can create them, but they have less performance due to the fucking awful concept of type erasure. Let's just incur extra boxing and unboxing instructions all day long.

And those are some of the fundamental very base problems with it. We can delve deeper in a new topic.

But still I wouldn't say telling a noob to learn Java is terrible advice. But there are better alternatives.

Name: Anonymous 2008-10-09 13:18

>>62
No, if that ever happens, we will have JJButton.

Name: Anonymous 2008-10-09 13:26

You wanna create some performant generic/templated functions in Java? No. You certainly can create them, but they have less performance due to the fucking awful concept of type erasure.
What? Erasure means that all that type information only has to be processed at compile time. At runtime you can use pure types, which is faster.

Name: Anonymous 2008-10-09 13:35

>>63
0/10

Name: Anonymous 2008-10-09 14:43

you should maybe figure out what type of programing connects with you better... you know the one that you can look at and somewhat make since of it with out ever running it

Name: Anonymous 2008-10-09 15:22

>>62
Clojure.

As goofy as Java is, the JVM is a stunning piece of technology.

Name: Anonymous 2008-10-10 2:21

If the code was hard to write, it should also be hard to read.

Name: Anonymous 2008-10-10 8:46

JAVA

Name: Anonymous 2011-02-03 2:10


Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List