I'm truly torn with this. The first one seems sensible (action -> target) and easier to read and reason about (especially with long names), while the other one looks more organized, naturally sortable and works great with any autocompletion system.

[–] [email protected] 18 points 6 months ago (1 children)

Not a programmer, but I'd prefer right naming convention because sorting

[–] [email protected] 13 points 6 months ago (1 children)

I am a programmer, and i also like the naming scheme on the right

Especially for things like filenames

[–] [email protected] 9 points 6 months ago* (last edited 6 months ago)

Also a programmer and think method names would be conducive using little endian.

TopicGet()
TopicCreate()
TopicDelete()

Writing this I realize we do this implicitly in some instances.

http.Get() -> httpGet()
http.Post() -> httpPost()

[–] kunaltyagi 15 points 6 months ago (2 children)

We need a new framework, one that allows universal lookup, and makes life easier

x = _.dialog.file.open
y = _.open.file.dialog
z = _.file.open.dialog
a = _.file.dialog.open

Once done, the formatter simply changes everything to _.open.file.dialog

Let's get this done JS peeps

[–] [email protected] 8 points 6 months ago

Aahh you can't just make this problem object oriented!

C programmers don't like that.

[–] [email protected] 7 points 6 months ago (1 children)

Insert xkcd about 15th format

[–] [email protected] 3 points 6 months ago

https://xkcd.com/927/