How do you organize your Java packages?
Currently I have one package named after my company which contains 40+ class files
>>60241061
>How do you organize your Java packages?
Right here.
>>60241152
>recycle
>>60241177
Not for you to recycle your erased data, if you know what I mean.
>>60241152
Seriously this. Please let java die
>>60241239
Seriously Java is still a good language
>>60241250
Hating it without a good reason is popular
I used to hate Java, and then I got a job as a Java developer.
There are many things that could have been way better in Java, but there are also great tools: annotations, reflection are two of them.
Stop hating on the JVM, and learn to love it.
>>60241390
>reflection
>good
I mean it works, but it's generally better if you can use something else
I would say RMI is neater than reflection
also a good standard library in general, especially Collections
>>60241061
if your Java application is properly modular, organizing the modules into separate packages shouldn't be a problem and come naturally
>>60241390
>there are also great tool
>reflection
i don't even know if you're serious
try C# ffs
>>60241390
wtf is reflection
>>60241061
If you don't know how to do something as simple as organizing your code in packages then I shudder at the thought of the incredibly shitty spaghetti code you must conjure.
>>60242433
wtf is search
>>60241258
Go to bed grandpa.
>>60241390
how about gc
>>60241390
Spring and dependance injection in java is awesome. Reflection is something i only use if i fucking have to. Anotation based frameworks are based, like lombok
>>60244962
>Spring is awesome
yeah fucking around with XML sure is nice
company
technology or classification (repeated as necessary)
Class
For example, at work we built some authentication libraries that we use in most of our projects, so our structure is:
company.security.authentication