Why write the executable with an upper-first letter? Looks quite silly and not professional imo.
Makes it feel like windows or something - ick
Trex: A package manager for Deno
11–20 of 25 posts
Re: Trex: A package manager for Deno
#12I don't know how trademarking naming works, or if they would even care, but Trex is already a big Composite Decking manufacturer. They have trex.com.
Re: Trex: A package manager for Deno
#13I don't know how trademarking naming works, or if they would even care, but Trex is already a big Composite Decking manufacturer. They have trex.com.
That's not how trademarking works. They are in quite different industries, there should be little to no confusion that a package manager is going to ship a deck to you.
Re: Trex: A package manager for Deno
#14I don't understand the point of this. The Deno runtime is its dependency manager, so having an external one is redundant.
Re: Trex: A package manager for Deno
#15I don't know how trademarking naming works, or if they would even care, but Trex is already a big Composite Decking manufacturer. They have trex.com.
IANAL but from my little bit of research on trademarks it's not the same industry, so not likely a confusion... Don't think anyone would think a company that creates Deck and Software were the same. Kinda like they have Docker containers and Dockers pants.
Re: Trex: A package manager for Deno
#16So, to me, this just looks to wrap the import map functionality with a nicer cli. For the same number of times as in days I'm torn on wether this is good. On one hand, it's a bridge for node people and adds some nice comfort tooling. On the other, it means you don't get to really understand how packages and bundling are supposed to work. I may just end up writing a post on this tonight.
It also reintroduces one of the main problems of node back into deno. https://youtu.be/M3BM9TB-8yA?t=581
not really since it is around imports map something native to deno, the purpose is to make it something familiar like npm
Re: Trex: A package manager for Deno
#17Why write the executable with an upper-first letter? Looks quite silly and not professional imo.
it's really a problem that the first letter is upper?
Re: Trex: A package manager for Deno
#18Was not one of the main motivations for deno to not use a package manager?
what trex does is, downloads and caches the modules and stores them within the name aliases provided by the import map
Re: Trex: A package manager for Deno
#19Earlier quoted context omitted.
It also reintroduces one of the main problems of node back into deno. https://youtu.be/M3BM9TB-8yA?t=581
not really since it is around imports map something native to deno, the purpose is to make it something familiar like npm
npm should not be a model to be imitated. npm modules make security audits impossible.
Re: Trex: A package manager for Deno
#20Earlier quoted context omitted.
not really since it is around imports map something native to deno, the purpose is to make it something familiar like npm
npm should not be a model to be imitated. npm modules make security audits impossible.
Trex currently uses deno.land/std, deno.land/x, nest.land and any repository. nest.land provides a blockchain-based service, we just take the way npm is used for our CLI. Trex doesn't try to look for the same npm issues, we just take the import maps and create a tool to manipulate them in a friendly way for those who already know the nodejs ecosystem