Hacker News Reader

Comment by commandlinefan | Hacker News Reader

> now what

stop trying to save a couple of bucks by reusing functionality that's not that hard to just develop in-house maybe?

only helps if people developing the functionality that is difficult to develop in-house do the same. i'm not going to build my own AWS cdk.

Do something better -- self host!

Everyone decloud and only use the standard libraries compilers provide. What a wonderful world! Everyone is forced to do some system programming. Going to be pain in the beginning but then whoever really passionate about programming (not shipping products but programming) is going to be happy.

OK just joke :/ Although I do secretly wish to wake up one morning and find out we have to do things like in the early 90s.

This wasn't AWS CDK, it was a package to fake data and a package with some ANSI escape sequence constants. The comparison doesn't make sense. The problem is that developers apparently can't even differentiate between when you should use a library and when you shouldn't; they just pull in the first result from an NPM search. You can probably trust AWS, which is good because CDK is complicated. You can't necessarily trust random NPM package authors, which is good because rewriting `colors` is not a Herculean task.

It wasn't a comparison.

As the article states, AWS CDK depends on colors, if I want to use AWS CDK, I have to use colors too. I don't get the choice to re-implement that myself unless I want to stop using the official CDK library

Well, my comment (in this case) was directed at the people at AWS who decided to use the "colors" package instead of just spending a half hour adding their own ANSI escape sequences.

Reply on news.ycombinator.com