Socket socket=new Socket()

Socket socket=new Socket()

Javafags will defend this writing socket thrice before I get my fucking socket

>pic related has more examples of absolutely fucking retarded verbosity

Other urls found in this thread:

github.com/google/guice/search?utf8=&q=new
twitter.com/SFWRedditVideos

Object s = new Socket();

There, only write it once

Only Nemerle did it right
def s=Socket();
def means immutable by the way.

You disgusting inbred, how much do you suck at OO to not even get that one never initializes objects explicitly outside of "hello world"-level toy code samples.

>implying OOP isn't literally the kiddie programming paradigm

This.

>using new
>2016

Are you even a programmer?

Runtime runtime = Runtime.getRuntime();

:^)

Runtime runtime = (Runtime)Runtime.getRuntime();//just to make sure it's Runtime

Runtime.run()

I'm suck at OO. What do you use in the real world?

>using the smiley with a carat nose

>Muh factories
>Muh builders

public class GPUThread {
public static void main(String[] args) {
System.out.println("AMD or Nvidia?");
}
}

Intel

Just werks, play anything on high at 1080p.

Was zur Hölle.

Stay in school, kids! That way you won't end up like most people in this thread who have obviously never worked a day in their life.

Most CS majors are useless.

Many can't even average two ints in C

Dependency injection

Went will you faggots realize that NONE of that matters? What matters is if you can make money. If you make money writing outdated shitty code, so be it. But that's not even the issue at hand. You people are boycotting the industry's most celebrated paradigm. Fucking retards on this board, I swear. If I had a button right here that would kill everyone on this board, including me, I would push it.

var socket = new Socket();
C#

Clearly not college grads. Let me guess... coding bootcamp? Keep telling yourself that a bunch of jew dropouts made a website that can actually compete with Princeton's education quality. I want to see what kind of mental gymnastics you can pull off on yourself here.

See

I know, typing is so hard...

How does that make you not use the "new" keyword?

Just head over to the mechanical keyboard thread and invest into a keyboard that will make your life easier!

Are you actually fucking retarded?

Saying I'm retarded is pretty rude coming from someone not being able to answer a retarded question properly.

People use frameworks for depdency injection, like guice. New is never used

How do the people writing these framework avoid using new?

>muh pointless framework and layers of needless abstractions and overengineering and muh design patterns and shit
fuck oopfags

When I read code I don't want to be distracted by fluff

They don't. Javascript kiddos only like to think about the most top level shit possible. No problem if it runs like trash.

How else can you be sure it's a socket? And you need the freedom to call it something else.

Socket opsAss = new Socket();

I think you're a bit lost here.

What's a socket?

Do you even public static void?

Why is dependency injection good while `new` is bad? I feel like you guys are messing with me.

You're right. I drank about six litres of beer tonight.

I can't believe someone really solves captcha just to say basically nothing worth anyone's time.

So why not use Python?

Of course you do. Otherwise the program wouldn't run. Are you a pajeet or something?

>programmers NEVER use new!
>except for virtually everyone writing frameworks and libraries that wrap constructors within dependency injections

It's not even what dependency injection is for.

int soc = socket(AF_UNIX, SOCK_STREAM, 0)

no allocation/de-allocation, just a fucking integer

OOP was a mistake

You're either retarded or never used guice.

github.com/google/guice/search?utf8=&q=new

>99% of them art test files

Yup, you're retarded

Why is it when I rewrote my old code with OOP, it turned out way cleaner and easier to use?

winrar

Stroke?

because you rewrote your code

not because you rewrote your code using OOP

It won't help you.
If it's not runtime, runtime casting will cause a runtime error.

fuck this is wrong
DELETING THIS

Imagining writing code without objects gives me a headache.

>instead of passing an object into a function, pass an array containing the same values
>no type hinting, so have to either memorize or write down the index of each value
>or I can copy the value to an initialized value in the function
>but then what if I want to replace an array of values... I'd need a 2 dimensional array
>instead of objectname.value I'd have objectname[index] all over the place
>God help me if I decide I want to add or remove values in the array

God, it just hurts.

>>instead of passing an object into a function, pass an array containing the same values
you mean a struct, right?

You don't fucking index an array of varying types lmao

..unless that is something java lets you do, which is retarded

Java syntax doesnt require you to name your socket socket.
Also you forgot to close your statement with a semicolon.
Looks like the 30 minutes you spent learning java on codecademy were a total waste of time after all.

Struct = class with only public variables. It's part of OOP.

You can have an array of varying types in many other languages, like python.

>He doesn't know what he typed

You could rewrite it like so
Socket sock = new Socket()

Now you've written it only twice.

Object sockonfeet = new Socket()

Now youve written it only once.

Learn how to code fag

pfft, yeah right. I can cast a non-runtime to runtime. Want to see an example?

A struct is not OOP, retard.

Yes it is.