npm VS GitUp

The fact that JSON doesn't support comments is so annoying, and I always thought that Douglas Crockford's rationale for this basically made no sense ("They can be misused!" - like, so what, nearly anything can be misused. So without support for comments e.g. in package.json files I have to do even worse hacky workaround bullshit like "__some_field_comment": "this is my comment"). There is of course jsonc and JSON5 but the fact that it's not supported everywhere means 10 years later we still can't write comments in package.json (there is https://github.com/npm/npm/issues/4482 and about a million related issues).

Things like the sparkline charts on npmjs (e.g. https://www.npmjs.com/package/npm ) are interactive SVGs. I think they're pretty common for data visualizations of all kinds

I actually did a POC 7 years ago about this - https://github.com/tanepiper/steal-ur-stuff

It was reported to npm at the time, but they chose to ignore it - https://github.com/npm/npm/issues/17724

Every time this pops up, I'm reminded of the day that the NPM registry started returning 418 responses.

I remember being at a training course that day and my manager asking me what we could do to fix it because our CI was failing to pull dependencies from NPM.

Trying to explain that NPM was returning a status code intended as an April Fools joke and which was never meant to see the light of production was quite difficult

https://github.com/npm/npm/issues/20791

I should really get around to how I discovered this 6 years ago and still nothing done about it

Whenever something like this comes up I usually have to tap the sign (and the original report)

NPM is not "Node Package Manager". https://www.npmjs.com/package/npm

> which can be overriden with env setting

Support for this is not great. Lots of packages still don't support this properly. My experience matches the 2015 comment https://github.com/npm/npm/issues/775#issuecomment-71294085

> Not sure why "symlinks" would be involved.

If you make your node_modules a symlink, multiple packages will fail. Even if you're not interested in doing that, others are.

> What NPM does is leaps and bounds ahead

Unless you change your node / gyp version. It doesn't really have a concept of runtime version. You can restrict it, but not have two concurrent versions if they conflict.

[email protected] was released in May 2017 and it seems to address many of the issues that Yarn aims to solve. Do keep an eye on it!

I think it's had been supposed to do that since forever. Apart from some bug in npm 5.3. Are you sure your package-lock versions actually conform to the semver ranges in your package.json?

FWIW, the per line staging functionality in GitUp (https://gitup.co/) is quite easy and straightforward. Very lightweight program that you can open via cli (`gitup` when in a git directory)

Not quite true, though while I was there, many fellow employees misunderstood the rules to mean that you couldn't use GPL software on your machine. At least as of a few years ago, the official ruling was that any open-source software _required_ for you to do your job had to be approved by an internal council of sorts, and GPL and AGPL software was right out. You could, however, use any open-source software you wanted (including GPL and AGPL) so long as it was (1) for personal use, (2) not absolutely mandatory for you to do your job (e.g. some niche software or library propping up your employment), and (3) there was some other alternative tool that you could use if necessary.

So, for instance, a GPL-licensed git client like GitUp[1] was fine to use, and didn't require clearance. You could totally also install a newer version of Nano if you wanted, too.

But, the rules _were_ somewhat vague and scary-sounding, so many engineers I worked with took the rules to mean "absolutely no GPL software under any circumstances".

What email is actually talking about is the option to bundle Nano _with the OS_, which Apple can't do with GPLv3 software. That's why for years, macOS has had an absolutely ancient version of bash (before the license was updated to GPLv3), and switched to zsh in newer versions of the OS.

[1]: https://github.com/git-up/GitUp

Gitup \Mac only]) and the command line at the same time. There are some esoteric commands I can’t remember so it’s nice having a GUI to do it and it’s nice having visual feedback incase of a screwup.

I only use it to keep track of certain projects. Gitup (Mac only) is another GUI client I use for visualizing progress and undoing mistakes.

A git client: Fork (paid), GitFox (paid), or Tower (subscription) for git version control. Which one you use is personal preference / price sensitivity. It's Ford vs Chevy. GitUp is free but a little weirder UI, though very powerful.

I typically use the CLI, but GitUp is the best git visualization tool I've ever found (although it's mac-only).

I Ctrl+F'd for GitUp based on the title, it deserves mention here.

It's all-in on Mac, unfortunately.

https://github.com/git-up/GitUp

> GitUp is built as a thin layer on top of a [Mac-only] reusable generic Git toolkit called "GitUpKit"

I thought Windows Sandbox would be more useful but over time I just haven't fired it up... I kind of forgot about it. I do use Hyper-V.

Every Windows user should run WizTree on their personal machines at least once a year to get a lightning fast report on disk space usage. Cleanup should start wih the largest items or you're just wasting your time! https://news.ycombinator.com/item?id=33893815#33894842

Bitvise SSH Server is also now free for personal use. I've been using it for over a decade since it offered simple multifactor authentication before OpenSSH (IIRC) and can block most bots by client identifier (libssh) -- security through obscurity works spectacularly here because OpenSSH does not yet support this. Their free-as-in-beer SSH client is a great GUI for port forwarding, SFTP, etc. but I dislike the built-in terminal's clipboard handling.

A Mac-only recommendation: https://gitup.co a GPL3 Git client with a unique UI and undo. https://news.ycombinator.com/item?id=27579701&p=2#27580659

If you use Pandora, check out the pianobar cli. For Twitch, there is Chatty (+streamlink cli & VLC).

I set up signald with a Google Voice number but haven't continued down the path of automating Signal.

I tried Tailscale (2021?) but it seemed a bit early, couldn't log out yet. So I went with ZerotTier. https://news.ycombinator.com/item?id=30284754

The tool used to visualize Git Tree: GitUp (looking for something better)