The Skill Collapse"If Only You Knew How Bad Things Really Are"

what's your main language or languages?

c ?
java?
perl?
smoke signals?

visual basic?????????
I absolutely hate Visual Basic, it has no pointers.

I enjoy Java, C, and C++. I am mostly working in the machine language of FPGA's, which is not programming in the conventional sense. I create libraries the plug into regular programming languages(C++, Python, Java, Rust, R).

My guilty pleasure is Javascript. It is like riding a moped, not cool looking, but cool feeling. I always end up doing complex self-modifying code in it.
 
I absolutely hate Visual Basic, it has no pointers.

I enjoy Java, C, and C++. I am mostly working in the machine language of FPGA's, which is not programming in the conventional sense. I create libraries the plug into regular programming languages(C++, Python, Java, Rust, R).

My guilty pleasure is Javascript. It is like riding a moped, not cool looking, but cool feeling. I always end up doing complex self-modifying code in it.
ok.

sounds kind of legit.

then of course you know what's special about a "protected" variable or method in java?
 
I absolutely hate Visual Basic, it has no pointers.

I enjoy Java, C, and C++. I am mostly working in the machine language of FPGA's, which is not programming in the conventional sense. I create libraries the plug into regular programming languages(C++, Python, Java, Rust, R).

My guilty pleasure is Javascript. It is like riding a moped, not cool looking, but cool feeling. I always end up doing complex self-modifying code in it.
how many h1b visas were being used when you got started?
 
then of course you know what's special about a "protected" variable or method in java?
There is private methods and variables, which can only be accessed within the specific class. Then there is public methods and variables, which can be accessed by any class. Finally there are protected methods and variables, which can only be accessed by the class, or subclasses.

As a general rule, protected variables are a mistake. It destroys the encapsulation of the variable. You can have subclasses that base their entire workings on a protected variable. If you change that, or should I say when you change that, all sorts of classes you did not even know existed start to break.

Back in the 1980's, C++ changed how their strings worked, without telling anyone. Normally everyone's programs would break, but they did encapsulation so well, that no one even noticed. That is the goal.

A major problem with the method and field modifiers for compiler writers is that there are several modifiers before you know if it is a variable or a method. Gosling apologizes for that all the time.
 
There is private methods and variables, which can only be accessed within the specific class. Then there is public methods and variables, which can be accessed by any class. Finally there are protected methods and variables, which can only be accessed by the class, or subclasses.

As a general rule, protected variables are a mistake. It destroys the encapsulation of the variable. You can have subclasses that base their entire workings on a protected variable. If you change that, or should I say when you change that, all sorts of classes you did not even know existed start to break.

Back in the 1980's, C++ changed how their strings worked, without telling anyone. Normally everyone's programs would break, but they did encapsulation so well, that no one even noticed. That is the goal.

A major problem with the method and field modifiers for compiler writers is that there are several modifiers before you know if it is a variable or a method. Gosling apologizes for that all the time.
yes.

just looking for "accessible through subclassing" Mr. wordy words.

lol.

but how many h1b visas holders were in the country when you GOT STARTED?
 
There is private methods and variables, which can only be accessed within the specific class. Then there is public methods and variables, which can be accessed by any class. Finally there are protected methods and variables, which can only be accessed by the class, or subclasses.

As a general rule, protected variables are a mistake. It destroys the encapsulation of the variable. You can have subclasses that base their entire workings on a protected variable. If you change that, or should I say when you change that, all sorts of classes you did not even know existed start to break.

Back in the 1980's, C++ changed how their strings worked, without telling anyone. Normally everyone's programs would break, but they did encapsulation so well, that no one even noticed. That is the goal.

A major problem with the method and field modifiers for compiler writers is that there are several modifiers before you know if it is a variable or a method. Gosling apologizes for that all the time.

'There is'. :palm:
 
wait. is Walt a native born American?
Yes, I was born in the USA, to two parents that were born in the USA, and three out of four grandparents that were born in the USA. I have ancestors who fought in the Civil War, and possibly ancestors who were here in colonial times(that is more questionable).

he's fucking indian that; why he can't do words.
I have no ancestry from India, nor am I a Native American(American Indian). My known ancestry is 100% Jewish, though there is always some intermixing if you go back far enough.

I "can't do words"?
 
Yes, I was born in the USA, to two parents that were born in the USA, and three out of four grandparents that were born in the USA. I have ancestors who fought in the Civil War, and possibly ancestors who were here in colonial times(that is more questionable).


I have no ancestry from India, nor am I a Native American(American Indian). My known ancestry is 100% Jewish, though there is always some intermixing if you go back far enough.

I "can't do words"?
you're perfectly fine at words.

you're just brainwashed by globalist fascist doctrines.
 
it depends of it you want something accessible through subclassing now doesn't it?
It is almost never a good idea to have variables accessed through subclasses. There is no way to control who writes that subclasses, so it destroys encapsulation. Someone will write a subclass that depends on accessing that variable, and then when the implementation changes, it will crash.

Encapsulation is all about separating implementation from interface. That allows you to change implementation without interfering with anyone else. It is the biggest benefit of object oriented programming.
 
It is almost never a good idea to have variables accessed through subclasses. There is no way to control who writes that subclasses, so it destroys encapsulation. Someone will write a subclass that depends on accessing that variable, and then when the implementation changes, it will crash.

Encapsulation is all about separating implementation from interface. That allows you to change implementation without interfering with anyone else. It is the biggest benefit of object oriented programming.
almost.
 
Back
Top