4 ms·
I think any user should be responsible for vetting their tech choices. Why would the author put a disclaimer instead of fixing the issues? In this case, the p
by wesleytodd 8y ago
I think any user should be responsible for vetting their tech choices. Why would the author put a disclaimer instead of fixing the issues?
In this case, the project is clearly too new/unstable/insecure to use in any real sense. It's presence as #1 on HN says more about the audience than the project itself I think.
- tlrobinson 8y agoIMHO a project with a trivial directory traversal vulnerability[1] is not ready for a shiny marketing site like this. 1. https://news.ycombinator.com/item?id=19256230 https://news.ycombinator.com/item?id=19256230
- joshstrange 8y agoWe can talk in generalities but since in this case we have more specifics let's go that route. This is an open-sourcing of, presumably, an internal tool used at CodeInterview. It's "shiny marketing site" feels very cookie-cutter to me and I'd be shocked if that wasn't either a template or a very few handful of components from something like bootstrap/similar. And it was posted to "Show HN", which is important given the rules of Show HN [1]. > In Comments [0] https://codeinterview.io/ https://codeinterview.io/ [1] https://news.ycombinator.com/showhn.html https://news.ycombinator.com/showhn.html