Show HN: Zero – A fast, zero-configuration server for React, Node.js, Markdown

Post by progx » Tue, Feb 26, 2019, 5:07 PM UTC

wesleytodd wrote: post #66

Wow, I love that people can wrap express and many of its components and end with something so different from its foundation. That being said, this level of "batteries included" approach has a cost. In this example, it is the complexity of this file[1] and the fact that if you were to write this as a single express middleware you could probably write it in less than 20 lines. Guess this is just not my cup of tea? [1]…

Post by isostatic » Tue, Feb 26, 2019, 5:10 PM UTC

cytzol wrote: post #65

beefhash wrote: post #57

Earlier quoted context omitted.

> If security is a concern At the risk of being presumptuous... When is security ever not a concern?

> When is security ever not a concern? Internal applications where the entirety of the userbase are trusted employees. (Preferably, the userbase is small, too.) Nobody’s going to bother finding vulnerabilities in an application where, if they break it, their own job gets harder.

Post by q3k » Tue, Feb 26, 2019, 5:15 PM UTC

q3k wrote: post #26

> File-system Based Routing: If your code resides in ./api/login.js it's exposed at /api/login" rel="nofollow">http:// /api/login . Inspired by good ol' PHP days. > Auto Dependency Resolution: If a file does require('underscore'), it is automatically installed and resolved. You can always create your own package.json file to install a specific version of a package. This sounds like a security nightmare. EDIT: to be c…

    # curl -v --path-as-is 127.0.0.1:3000/../../../../../etc/passwd
    root:x:0:0:root:/root:/bin/bash
    [...]

Post by wesleytodd » Tue, Feb 26, 2019, 5:22 PM UTC

progx wrote: post #71

wesleytodd wrote: post #66

Wow, I love that people can wrap express and many of its components and end with something so different from its foundation. That being said, this level of "batteries included" approach has a cost. In this example, it is the complexity of this file[1] and the fact that if you were to write this as a single express middleware you could probably write it in less than 20 lines. Guess this is just not my cup of tea? [1]…

Yes, writting an express backend is really simple, some plugins, error-handling etc. and you can run it in less than 1 hour. But the Frontend with webpack needs definitely more time, hours and hours to fiddle webpack to your needs. This project has a definded strucutre and support defined modules (react), so it could save you a lot of webpack config time, but you can not do everything with it. You have to use it as i…

Post by leowoo91 » Tue, Feb 26, 2019, 5:28 PM UTC