Intel - nodejs logging that plays nice with console.log • Hacker News Board

Re: Intel - nodejs logging that plays nice with console.log

#21

Post by AsymetricCom » Tue, Oct 01, 2013, 12:35 AM UTC

benologist wrote: post #18

ChikkaChiChi wrote: post #7

Name is definitely going to be confusing. I completely expected this to be something Intel was doing nodejs related.

The name is going to be forced to change, the OP should just rename it now while it's not an issue.

Even if there wasn't a copyright issue, what kind of name is 'intel' anyway? Might as well called it 'data' or 'stream'.

Re: Intel - nodejs logging that plays nice with console.log

#22

Post by benologist » Tue, Oct 01, 2013, 1:40 AM UTC

AsymetricCom wrote: post #21

benologist wrote: post #18

Earlier quoted context omitted.

The name is going to be forced to change, the OP should just rename it now while it's not an issue.

Even if there wasn't a copyright issue, what kind of name is 'intel' anyway? Might as well called it 'data' or 'stream'.

You might as well call it Microsoft, HP, or IBM and pretend those are generic names within the confines of our industry.

Re: Intel - nodejs logging that plays nice with console.log

#23

Post by hamburglar » Tue, Oct 01, 2013, 2:57 AM UTC

lfuller wrote: post #20

I'd like to use this on some of my projects but I know the dev is going to receive a cease & desist from Intel sooner rather than later, breaking dependencies. OP - could you rename the library to make us all feel a little bit better about using it?

When naming a project, it seems a lot of people don't stop and think about what it's going to be like to try to Google it.