I love Ruby, passionate about clean soft architecture, code performance, readability, simplicity, and maintainability. All of that allows me to build applications with minimum price but maximum value.
I love Ruby, passionate about clean soft architecture, code performance, readability, simplicity, and maintainability. All of that allows me to build applications with minimum price but maximum value.
Well, any usage that solves your current problems is appropriate one. But once it bumps into problems, it could mean two problems: the tool is used in wrong way, the tool itself is wrong. Mostly, it's a wrong way use. IMO, at this time is better to learn the tool deeper rather than switching to some other tool. It could be great to see some example drives you mad. It could clarify things, from my experience I've never had so big YAML files that's hard to parse. And from my experience working with Rails even very big files (translations, usually) don't bring any problems and irritating. Yes, sometimes it's hard to follow indentation. But with JSON it's a hard to follow parentheses, and indentation as well, if it's for humans. So I would say JSON is even worse.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Don't you think that it's not the tool's problem but the way how it's used?
Yes, I'm calling out two uses people should reconcider. I'm giving explanation of the issues so that others don't make the same mistake.
Now I'd argue is that YAML provides too much and draws people to use it inappropriately. It makes me wonder what an appropriate usage is.
Well, any usage that solves your current problems is appropriate one. But once it bumps into problems, it could mean two problems: the tool is used in wrong way, the tool itself is wrong. Mostly, it's a wrong way use. IMO, at this time is better to learn the tool deeper rather than switching to some other tool. It could be great to see some example drives you mad. It could clarify things, from my experience I've never had so big YAML files that's hard to parse. And from my experience working with Rails even very big files (translations, usually) don't bring any problems and irritating. Yes, sometimes it's hard to follow indentation. But with JSON it's a hard to follow parentheses, and indentation as well, if it's for humans. So I would say JSON is even worse.