>having a fight with teammates
>they want to use prefix/suffix "I" to name interfaces in Go
>I am against it because it doesnt make sense to mix subhuman patterns into already superior and clean Go
am I a seething asshole in this story?
are they right?
but like how long are we going to use these types of shit even in newer languages?

can C++/C#/Java fags explain why was it ever needed to add the prefix/suffix "I" to the name?
why do you have to know by glancing over the argument of a function whether its a interface or a class?

>>106017526 (OP)
you name name interfaces without any suffixes or prefixes, and implementing classes should have Impl suffix

this is the only White Man's way of doing interfaces

if you disagree you're tranny, brown etc.

interface WhiteMan {
int favoriteNumber();
}

class WhiteManImpl implements WhiteMan {

int favoriteNumber() {
return 1488;
}
}

you already had this thread and it died. nice roleplay op

>>106017650
fpbp

OP btfo'd

>>106017526 (OP)

>>106017650
but you havent explained why do you need suffix/preffix at all?
do people really need that indicator of what is an interface and what is not?
what are the usecases of knowing that by glance?

>>106017526 (OP)
Long time ago when I took java classes, the teacher said every word ending with ---able were interface.

>>106018028
that is retarded

some interfaces with that make sense, like Serializable, Sortable

but most of the time you will be putting an interface on some business service, or repository

>>106017526 (OP)
>not adding "I" > adding "I"
>adding "I" > adding"Impl" (or creating sub package "impl")
And I'm seeing the last one way too often.

>>106017650
>implementing classes should have Impl suffix
no. it should have NO suffix you stupid cargoculting mongoloid.

either you have multiple classes that can be differentiated by meaningful names from the interface OR you have ONLY ONE FUCKING CLASS WITHOUT AN INTERFACE. YOU DON'T FUCKING CREATE AN INTERFACE WITH ONLY ONE CLASS HOLY FUCKING RETARDED JEET SHITTER

>>106017526 (OP)
also stop posting this thread you removing YEARS from my life expectancy through the sheer amount of anger and stress i experience every time i enter this thread. and no i won't stop

>>106018050
you use adjectives where it makes sense and normal words that describe the function everywhere else

>>106019287
WRONG

>>106019287
>>106019293
wait nvm you good

>>106019293
>OR you have ONLY ONE FUCKING CLASS WITHOUT AN INTERFACE
found the jobless retard

you always try to put a business heavy service behind an interface, because:
- you can expose a single interface from a module and as a dev you instantly see what it does (input -> output)
- super easy to mock the interface for testing. Have a repository interface? then create a fake repo for super lightweight tests that uses a map underneath
- its easy to swap beans based on different profiles / feature flags if they implement a common interface

which I don't expect a jobless retard from /g/ like (You) to know of course, just trying to educate you, so you dont embarrass yourself in the future

>>106019418
>t. it makes it easier to add technical debt

>>106019495
>t. can't code and doesn't do DDD

>>106019418
Actual mental illness kek

>>106019579
it's called being employed and having years of experience building commercial software

>>106019418
literal and unironic skill issue

>>106019593
get a job goober

>>106019588
I also have that, but I don't have enough cognitive dissonance to pretend that commercial software isn't garbage. Everyone realizes this, even you do when you're off the clock and *using* software. You just turn that part of your brain off while you're working on your goyslop apps.
Honestly, I don't have any problems with people doing this cognitive dissonance thing if it allows them to have a normal life and a family. I really mean that. But to go on 4keks and unironically defending this garbage? That's just embarassing. Lmao.

>>106019588
i'm sorry you spend years making shitty code. and yes you can have shitty code AND a working commercial software

>>106019616
i did and i found that in 99% of all cases every single-class-interface could have been replaced with just the class.

if you ever need an interface: guess what? you can just add it! so please spare me going through hundreds of literal boilerplate "interfaces" because someday in your schizo delusions it becomes useful.

PS: use modern libraries

>>106017526 (OP)
Gojeets lost.

>>106017650
A white man cannot be a contract.

Should be the Hyperboreum contract instead.

type Hyperboreum interface {
Tywaz() rune
}


Now every struct that implements the Tywaz function complies with the Hyperboreum contract.

>>106017526 (OP)
>can C++/C#/Java fags explain why was it ever needed to add the prefix/suffix "I" to the name?
Java doesn't have prefixes or suffixes for interface names

basically what >>106019293 is raving about: you don't need to differentiate names of interfaces and classes

>>106017526 (OP)
Superior Java Chat here.
We don't prefix "I" to our interfaces, that's a Cshart thing.
Tell your teammates that they are fags and they should suck a dick

>>106024206
I did
15 min later my manager scheduled an unordinary meeting on Monday with me

>>106024933
is your manager hot? this might be a good thing!

>>106025433
its a bearded married man with kids

>>106025753
>kids
jesus christ anon don't go to that meeting!

>>106017850
>but you havent explained why do you need suffix/preffix at all?
It's an outpost of the Systems Hungarian brainworm, and it's so dumb.
The same people who do that also like to put m_ at the start of member fields and otherwise add type mangling even though nothing needs it. They also can't into actual readable names.

>>106025806
you see back in the days vowels used up more ram cycles and i created a wiki page that explains all of my commonly used abbreviations so it's actually the best practice

>>106019418
don't listen to the jobless shitters

>>106019418
all your points ignore the argument of the interface having only a single implementing class

you can easily do Extract Interface when needed
creating them eagerly is - at best - unnecessary