10 replies

1. Alex Grant 4 min later

   @zachleat

   Endless fumbling around with plugs and sockets is cumbersome, too. We just put the live wires right next to the sink.

   1. Zach Leatherman 6 min later

      @localnerve …oh no

2. Markus Unterwaditzer 4 min later

   @zachleat at work it is, ports regularly conflict across services and their respective dependencies. particularly if you want to develop two services at once and each of them should have a dedicated redis or postgres instance for the sake of isolation, you now have to run one of the redises on a non-standard port which adds more config boilerplate. having one host per service would solve this. not convinced this portless thing is a good solution. HTTPS out of the box is a good aspect of it though, and the permission stuff is a non-issue IMO (again, for work... if a third-party OSS project imposed this onto me I would lose it)

3. Jan Lehnardt 8 min later

   @zachleat nope. https://github.com/hoodiehq-archive/local-tld

   1. Zach Leatherman 24 min later

      @janl 12 years ago!

      1. Jan Lehnardt 26 min later

         @zachleat mac only, but I’d be surprised if there wasn’t some systemd/dbus magic one could pull on linux.

         1. Alex Russell 28 min later

            @janl @zachleat Ah yes, Linux DNS; famously sane!

            https://tailscale.com/blog/sisyphean-dns-client-linux

            1. Jan Lehnardt 34 min later

               @slightlyoff @zachleat I said “possible”!

4. Trygve Lie 29 min later

   @zachleat I would say it depends. Ports are annoying when you need a series of apps (ex; API service A, etc) to run to do what you need and all apps want to start at the same port. Because; defaults.

   Would love a local discovery thing which would give apps a random port and then apps find each other based on something else than the port locally.

5. Peter Wilson 5 hr later

   @zachleat It's been weeks since a successful malware injection attack via NPM. I'm all in.