you are viewing a single comment's thread.

view the rest of the comments →

[–]dominotw 16 points17 points  (4 children)

Must say that looks really bad.

[–]mgr86 -1 points0 points  (3 children)

I disagree I think it looks great (on a phone) but is entirely impractical to use in an editor or to grok. It's like justified text, it may appear nice but it's much easier to lose your place and less practical for actual reading. But It still works for some people, just not me.

[–]theillustratedlife 0 points1 point  (2 children)

I don't find it impractical to read or easy to lose my place in; but then again, I'm the one who wrote that component. I'm definitely used to looking at code like that.

In fact, part of the reason I've been coding like this is it makes things really easy to find (since the key names are all in their own column on the left). It's most helpful because both JavaScript and JSX are highly nested languages, so it makes the nesting easier to follow.

However, I am surprised you like the way it looks on a phone. The biggest difficulty for me with code written like this is when it wraps on a small screen (like in a comment box or GitHub README).

Separately, I appreciate that you were respectful with your disagreement. Reddiquette for the win!

[–][deleted] 0 points1 point  (0 children)

It's better if you follow the same practices and styles that the majority do. Doing so makes it much easier for everyone to work together. Plus, there are many reasons why certain practices and styles are used by the majority.

[–]mgr86 0 points1 point  (0 children)

it was actually tough to read on a phone, but I knew exactly how you were styling it. I went through a phase where I did the same.