Don't invent some other file format please, just use whatever most people use unless you have a real specific reason for it.
[deleted]
Architect – A Serverless Framework
21–30 of 76 posts
Re: Architect – A Serverless Framework
#22Great! Another file format for me to learn. Why can't everyone use one of the standard file types, like YAML/JSON?
I really wish people wouldn't use JSON for configuration. The lack of comments and shortcomings in formatting abilities make it particularly ill-suited. { "_comment": "this is a comment" } is cringeworthy to. It's great for transport, but horrible for static file config. YAML is good, but not to everyone's taste. I've been using it for a long time (as a ruby developer) but many people I know find it ugly. I think Arc…
Rather than inline-comments I've always had separate documentation. This helps prevent trying to cram all the edge case caveats and everything into the configuration file.
Re: Architect – A Serverless Framework
#23Lambda and SNS are super expensive. I'll skip it.
Lambda is not super expensive if you have only small amounts of traffic... it's actually super cheap in that situation.
Re: Architect – A Serverless Framework
#24Great! Another file format for me to learn. Why can't everyone use one of the standard file types, like YAML/JSON?
I really wish people wouldn't use JSON for configuration. The lack of comments and shortcomings in formatting abilities make it particularly ill-suited. { "_comment": "this is a comment" } is cringeworthy to. It's great for transport, but horrible for static file config. YAML is good, but not to everyone's taste. I've been using it for a long time (as a ruby developer) but many people I know find it ugly. I think Arc…
Then use json5. Super weak excuse. Or use yaml or some other format and pipe it into some to-json converter.
Also, json has json schema which tools like VS Code support. They can autocomplete your config. Pretty promising over most other tooling.
But coming up with your own config has pretty much all the downsides. Yeah, you can invent some cuter syntax. But now your users can't even get syntax highlighting in their editor. Awful UX.
Re: Architect – A Serverless Framework
#25I think this whole idea of pushing "serverless" as a concept to engineers is deceptive at best and damaging at worst when you think about all of the naive new developers entering the industry having to shovel all of this shit into their minds alongside proven technologies and conventional formats.
What does "serverless" framework really tell veterans? Who are you selling to? What are the considerations for adoption?
There's so many questions that pop up before I even look at the software, and once I did, there's more questions which obscure the point. Why should I use your bullshit?
Worse, 5 years in after a company has adopted this junk, some poor sap is going to have to maintain it after being 100k SLOC deep in it, with no vision of how to port out of it alongside meeting existing technical task completions, at which point this will have become completely irrelevant.
Re: Architect – A Serverless Framework
#26Great! Another file format for me to learn. Why can't everyone use one of the standard file types, like YAML/JSON?
I really wish people wouldn't use JSON for configuration. The lack of comments and shortcomings in formatting abilities make it particularly ill-suited. { "_comment": "this is a comment" } is cringeworthy to. It's great for transport, but horrible for static file config. YAML is good, but not to everyone's taste. I've been using it for a long time (as a ruby developer) but many people I know find it ugly. I think Arc…
If you want human, you can look at TOML
https://github.com/toml-lang/toml
Its the thing Pipfile uses.
The point is, don't invent file types!
Re: Architect – A Serverless Framework
#27Great! Another file format for me to learn. Why can't everyone use one of the standard file types, like YAML/JSON?
I really wish people wouldn't use JSON for configuration. The lack of comments and shortcomings in formatting abilities make it particularly ill-suited. { "_comment": "this is a comment" } is cringeworthy to. It's great for transport, but horrible for static file config. YAML is good, but not to everyone's taste. I've been using it for a long time (as a ruby developer) but many people I know find it ugly. I think Arc…
It's interesting. can you have @js more than once? can you have @app more than once? pretty sure ಠ-ಠ is a valid app name, but ಠ_ಠ isn't.
i also can't quite tell how to say map of maps. i'd guess it's
@this-section-has-a-map
hello-world
name child-map
ಠ-ಠ a
ಠ_ಠ b
Re: Architect – A Serverless Framework
#28Don't invent some other file format please, just use whatever most people use unless you have a real specific reason for it.
Author here: we did? Pretty well documented issues w JSON and YAML (coming from CloudFormation perspective). Both have problems (that are unique to each) so we created a format for solving that.
If you like JSON and YAML and don't mind those issues you are well served by existing solutions. Cheers!
Re: Architect – A Serverless Framework
#29Great! Another file format for me to learn. Why can't everyone use one of the standard file types, like YAML/JSON?
To summarize: a three line .arc file yields a 700+ CloudFormation YAML document. Let me know if you have any more questions!
Re: Architect – A Serverless Framework
#30Earlier quoted context omitted.
I really wish people wouldn't use JSON for configuration. The lack of comments and shortcomings in formatting abilities make it particularly ill-suited. { "_comment": "this is a comment" } is cringeworthy to. It's great for transport, but horrible for static file config. YAML is good, but not to everyone's taste. I've been using it for a long time (as a ruby developer) but many people I know find it ugly. I think Arc…
It's interesting. can you have @js more than once? can you have @app more than once? pretty sure ಠ-ಠ is a valid app name, but ಠ_ಠ isn't. i also can't quite tell how to say map of maps. i'd guess it's @this-section-has-a-map hello-world name child-map ಠ-ಠ a ಠ_ಠ b but it's hard to tell. Also, i'm not exactly a fan of { "_comment": "this is a comment" }, but i've run into several situations with yaml where i want to bui…
Hey, one of the .arc authors and maintainers here.
Only one of each section is what we designed for though the validations for that might be broken (and if so we can fix right away). Nesting is limited to one level. No need for more that we've seen yet.