Hacker News Reader

Comment by Ericson2314 | Hacker News Reader

I get mad at the Haskell tools I use every day, and then I remember that nobody else is really in better shape.

Rust's Cargo is incredibly well thought-out and will make you despise everything else.

From the little development I have done in Rust, I have to agree.

On the other hand, I’ve been working with react-Native and typescript recently, and it’s a constant mess. Every invocation of yarn leaves at least a couple of warning messages about things that are out of my control. Installing packages is slow and at least every few days I have to wipe out node_modules and nuke any iOS build folders in order to get it working again. That said, RN is promising technology and hopefully my frustrations are due to more inexperience than the tools or language and ecosystem. I just wish all of the JavaScript stuff were faster. I’m on a gigabit connection and fast hardware but still it seems sometimes yarn has to download or unpack 6500 files or something

NPM claims to have taken the lead from Yarn in terms of install speed in the latest versions. Still, I prefer Yarn because NPM has such a history of suckage.

Meanwhile, the former CTO of NPM released a new (alpha) package management system last week at JSConfEU (the conference where NodeJS was first announced); see https://github.com/entropic-dev/entropic/blob/master/docs/RE...

I saw those claims in the past few days and have tried both, for me yarn still seems faster although I didn't actually time them.

Nope. Absolutely not. Cargo makes the simple things easy but is less thought out than Rust itself.

We are making a Cargo-like build toolchain for C/C++, if anyone is interested: https://build2.org

Web browsers have the best software distribution story. You type a natural language query about what you want, click and it installs and runs the latest version of everything you need, usually in less than a second.

From the click user point of view, yeah.

From the dev user or packager point of view, no.

First, there is no namespace in JS. Secondly, the import instruction standard is not implemented everywhere, so we need a bundler. First, the network makes everything harder. And finally, JS has virtually no stdlib.

Add to that that we we are stuck in npm land, with acute lefpadite, packages breaking the public API every sunday, and a mad hatter packager like webpack as our lord and savior, and you have a recipe for terrible times.

Python packaging is not hard really. It's just that there is way to much of obsolete or incomplete information on the web.

Here is what you need to know: https://news.ycombinator.com/item?id=20132303

Honestly, it's not much. It's enough to live a happy life as a Python dev.

This. I still use pip, venv and setup tools and I've packaged everything from third party dlls given by a supplier to my flask applications with html and everything.

I keep seeing pipenv and poetry and wonder how all these came about? Is it because people come from other languages and want to do this the way they did it in those?

May I know if you package 3rd party dlls in your flask app, does it run on *nix platform?

Racket has by far the best I have ever used.

Here is everything you need to know about it in a 7 minute read.

https://docs.racket-lang.org/pkg/getting-started.html

Yes I'm familiar with Racket.

It good?

Not good, is gooder!

Racket is respectable but I prefer types all the way down.

probably I know I'm the outsider here, but Maven can do everything any other tool can, but then also a ton of stuff more that none other can, Gradle et al. included: Namely, enabling you to do proper dependency & version management with parent projects (POMs). Massively useful if you have gigantic projects with hundreds+ of dependencies.

It's impressive how so many people struggle with this :)

Reply on news.ycombinator.com