Learn More
Resend Email
2
apply-eval
3y

In an already verbose, strongly types Java codebase and you see

private String m_strDisplayName;
private boolean m_bIsResolved;
...

I can understand the itch of another teams decided to rename it with correct Java convention. All nice and good, except that these changes were not merged back to master.

Five years, few re-orgs and product restructuring later, I'm staring at 500+ files merging mess trying to bring back these product codebase together.

rant
Favorite
Ranter
Comments
  • 0
    3y
    @rEaL-jAsEs String -> java class, to differentiate from primitives like int/boolean/... 🤷
  • 0
    3y
    @rEaL-jAsEs That's one of the very few things about the Java convention that makes sense. String is a reference type and therefore it's uppercase.
  • 1
    3y
    @homo-lorens the real argument is should Java support primitives at all? Being the forefront OOP language and all.

    C# says "nah", kind of.
  • 1
    3y
    @AlgoRythm I think that the concept of primitives is flawed, and it should be disassembled to its various aspects, which are:

    - Operator support

    - Pass-by-value

    - Exclusion from the type hierarchy; sort of possible with "sealed" but it should be possible to have types that don't derive from Object and can't be cast to anything, mainly because such strict constraints allow for special optimisations.
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment