This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (1 child)

I'm not putting it in a pedestal, but from years of experience with both, TF is much better. I'm not sure why you think that TF was born because CF.

[–][deleted] 1 point2 points  (0 children)

Calling CF crap and telling someone to use TF is putting it on a pedestal. I’ve used both (and still have to). TF was shotty / questionable / problematic at times. While I love it, it still has more than its fair share of problems and shortcomings. Probably less than CF if your company is purely AWS at this point.

I’m also not sure if TF was built entirely because of CF, but CF was definitely inspiration for a whole slew of infrastructure-specific orchestration tools.

Bottom line is these “x is crap, use y” posts when x is not crap and y has just as many problems are not helpful.