Speaking as a German and a software developer: just because you can, does not mean you should.
Sometimes it is easier and better to not stuff words together and give readers a bad time than to write “Schiffsschraubeneichungsvorgabenverordnungsüberwacher”.
Sorry for replying this late, totally missed it but i like the analogy. But what would be the alternative? Creating a new word for every function?
P. S: Also SchiffsSchraubeenEichungsvorgabenVerordnungsÜberwachung is much more readable: That’s why sir Pascal mounted a camel and created PascalCase and camelCase!
An English software developer would write that as, ShipPropellerCalibrationSpecificationRegulationSupervisor so only the camel case would make a difference here
Speaking as a German and a software developer: just because you can, does not mean you should.
Sometimes it is easier and better to not stuff words together and give readers a bad time than to write “Schiffsschraubeneichungsvorgabenverordnungsüberwacher”.
Sorry for replying this late, totally missed it but i like the analogy. But what would be the alternative? Creating a new word for every function?
P. S: Also SchiffsSchraubeenEichungsvorgabenVerordnungsÜberwachung is much more readable: That’s why sir Pascal mounted a camel and created PascalCase and camelCase!
From google translate: “Ship propeller calibration specification regulation supervisor”
An English software developer would write that as,
ShipPropellerCalibrationSpecificationRegulationSupervisorso only the camel case would make a difference hereOnly a Java dev would write that abomination
Not quite, for Java you still need the Factory part at the end!
I hope it implements the
ShipPropellerCalibrationSpecificationRegulationSupervisorFactoryInterfaceGerman’s more extreme compound words seem like a good linguistic use case for CamelCase.
Technically you mean PascalCase - camelCase starts with an uncapitalized letter :)