6 ms·

As repeatedly pointed out, Apple has been using these ports for audio streaming functionality since 2004. If your web framework is so inflexible that it hard-co

by ribit 5y ago

As repeatedly pointed out, Apple has been using these ports for audio streaming functionality since 2004. If your web framework is so inflexible that it hard-codes ports to collide with OS functionality without an easy way of reconfigure it, that's on the framework, no?

baq 5y ago
what if there IS an easy way to do it, as is the case here?
- vadfa 5y ago
  Then you don't post a new thread ;)
eloisius 5y ago
On airports or what? I used Mac as my development environment for ten years and never had a conflict using port 5000. It’s not about inflexible web frameworks, lazy or stupid developers that use Macs. 5000 is a popular default port for web frameworks, and if it stops working one day, there’s nothing wrong with wondering why. It might be a small headache to get your entire team to redefine the default port in your project’s dev environment if half of them use another OS, or you happened to upgrade MacOS before everyone else. Of course, the most likely outcome will be switching to another port, but what is with all the hostile comments in this thread about someone asking why something that’s worked for so long broke?
- breakfastduck 5y ago
  It hasn't 'broke' - the latest OS update includes functionality for macs to operate as an Airplay host and so the port they've always used for that functionality is now used by this new feature.
- elzbardico 5y ago
  System programmers and project managers for airplay are probably not familiar with popular web frameworks. Besides that this usage is secondary to a public service. If a developers workflow Is so brittle as such an inconsequential change is enough to create a burst of outrage, this developers workflow sucks. You shouldn’t expect a port to be available and hard code them all over your configuration. Use the opportunity to refine your craft and make your development practices more repeatable and deliberate.
- ribit 5y ago
  Of course there is no problem with asking why things broke and how to fix them. My comment was however directed at the silly fad of blaming Apple for all and everything, because “big corp always bad and FOSS always guud”. This is irrational, unfair and anti-intellectual. There are more then enough valid reasons to criticize Apple. In this particular instance however they did not do anything wrong. So yes, if one spins the tale like it’s “evil Apple” deliberately breaking everyone’s work environment again (with Tim Cook supposedly maniacally giggling in the background), will indeed be met with a hostile response from my side.
mschuster91 5y ago
The problem is not the inflexibility of frameworks - it is that, once the frameworks adapt to the change, a lot of guides, stackoverflow posts etc. will break and people will blame the framework for the issues.

by ribit 5y ago

baq 5y ago

what if there IS an easy way to do it, as is the case here?

vadfa 5y ago
Then you don't post a new thread ;)

eloisius 5y ago

On airports or what? I used Mac as my development environment for ten years and never had a conflict using port 5000. It’s not about inflexible web frameworks, lazy or stupid developers that use Macs. 5000 is a popular default port for web frameworks, and if it stops working one day, there’s nothing wrong with wondering why. It might be a small headache to get your entire team to redefine the default port in your project’s dev environment if half of them use another OS, or you happened to upgrade MacOS before everyone else. Of course, the most likely outcome will be switching to another port, but what is with all the hostile comments in this thread about someone asking why something that’s worked for so long broke?

breakfastduck 5y ago
It hasn't 'broke' - the latest OS update includes functionality for macs to operate as an Airplay host and so the port they've always used for that functionality is now used by this new feature.
elzbardico 5y ago
System programmers and project managers for airplay are probably not familiar with popular web frameworks. Besides that this usage is secondary to a public service. If a developers workflow Is so brittle as such an inconsequential change is enough to create a burst of outrage, this developers workflow sucks. You shouldn’t expect a port to be available and hard code them all over your configuration. Use the opportunity to refine your craft and make your development practices more repeatable and deliberate.
ribit 5y ago
Of course there is no problem with asking why things broke and how to fix them. My comment was however directed at the silly fad of blaming Apple for all and everything, because “big corp always bad and FOSS always guud”. This is irrational, unfair and anti-intellectual. There are more then enough valid reasons to criticize Apple. In this particular instance however they did not do anything wrong. So yes, if one spins the tale like it’s “evil Apple” deliberately breaking everyone’s work environment again (with Tim Cook supposedly maniacally giggling in the background), will indeed be met with a hostile response from my side.

mschuster91 5y ago

The problem is not the inflexibility of frameworks - it is that, once the frameworks adapt to the change, a lot of guides, stackoverflow posts etc. will break and people will blame the framework for the issues.