21–25 of 25 posts
Why 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?
So, 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
1) Trex is supporting multiple module registries, not just one. (Thus not necessarily centralized) 2) Trex is not associated with one entity in particular. This means that they have no company dedicated to hosting modules in house (another reason that they aren't centralized) 3) Node's package.json included many other things than just imports. Using Trex is completely optional, and if you do use it, an import map does not hinder one's development workflow. In my opinion, it makes dependencies easier to manage.
I 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.
Was not one of the main motivations for deno to not use a package manager?
I believe so. I always wondered why `go mod` existed until we had dependencies break fairly frequently from a certain domain and were forced to vend the dependency.
Earlier quoted context omitted.
it's really a problem that the first letter is upper?
Not really for people who have their shells configured to auto-(de)capitalize the name of a command or binary, but for those that don't, it's a departure from what's normal. It's easily solved through an alias or similar, but still: why introduce the impedance?