3 ms·

Wow, what's even the actual work besides creating some wrapper config files with other names for the parameters?

automato 5y ago
When you need to create some software, I guess you start by writing your own OS first? This is how all OSS works - you build on top of other projects.
- squeaky-clean 5y ago
  If you're not melting your own sand into silicon ingots and slicing them into wafers, are you even a real programmer?
- hamburglar 5y ago
  I think what people are complaining about is the fact that the linked project is not the project that actually solves the problem stated in the title. This linked project did not enable “using a raspberry pi as an airplay server,” it just packaged someone’s project that already did that.
cptskippy 5y ago
Having someone smoothing over the out of box experience for a lot of OSS is of value to me. A lot of projects I undertake get bogged down or stymied by setup instructions that trivialize or one-line non-trivial tasks (e.g. setup OpenCV, configure a reverse proxy in Nginx, etc). A lot of this comes down to the fact that software moves quickly and instructions are written for a given piece of hardware on a specific version of a distro. One of the benefits of having a common platform like the Raspberry Pi or shipping Docker Images is that you can ship a MVP that anyone can easily setup like Hassio, Pi-Hole, or PiWebcam.
yoz-y 5y ago
The wrapper itself? Isn’t Unix philosophy to build up software from simpler components? The project is also quite prominently attributed.
- martin_a 5y ago
  It seems like the original project is easy enough and does not need a wrapper. Building a wrapper this thin reminds me of the Hacktoberfest "contributions" to projects.
  - yoz-y 5y ago
    Maybe the problem with posting this instead of the original project is akin to posting a homebrew formula github repo instead of the actual tool. However many projects now use github as a way to have canonical paths to stuff so here we are. You need to host the wrappers somewhere right?

When you need to create some software, I guess you start by writing your own OS first? This is how all OSS works - you build on top of other projects.

squeaky-clean 5y ago
If you're not melting your own sand into silicon ingots and slicing them into wafers, are you even a real programmer?
hamburglar 5y ago
I think what people are complaining about is the fact that the linked project is not the project that actually solves the problem stated in the title. This linked project did not enable “using a raspberry pi as an airplay server,” it just packaged someone’s project that already did that.

cptskippy 5y ago

Having someone smoothing over the out of box experience for a lot of OSS is of value to me. A lot of projects I undertake get bogged down or stymied by setup instructions that trivialize or one-line non-trivial tasks (e.g. setup OpenCV, configure a reverse proxy in Nginx, etc). A lot of this comes down to the fact that software moves quickly and instructions are written for a given piece of hardware on a specific version of a distro. One of the benefits of having a common platform like the Raspberry Pi or shipping Docker Images is that you can ship a MVP that anyone can easily setup like Hassio, Pi-Hole, or PiWebcam.

yoz-y 5y ago

The wrapper itself? Isn’t Unix philosophy to build up software from simpler components? The project is also quite prominently attributed.

martin_a 5y ago
It seems like the original project is easy enough and does not need a wrapper. Building a wrapper this thin reminds me of the Hacktoberfest "contributions" to projects.
- yoz-y 5y ago
  Maybe the problem with posting this instead of the original project is akin to posting a homebrew formula github repo instead of the actual tool. However many projects now use github as a way to have canonical paths to stuff so here we are. You need to host the wrappers somewhere right?