floatingsmoke

I recently read that supabase.io is using this. https://supabase.io/docs/postgrest/server/about

When you deal with tens of Raspberry Pis, require high availability, and have low traffic bandwidth Argo Tunnel makes really sense.

I use Cloudflare Argo Tunnel for this purpose and am very satisfied. It's easy to setup and if you have TLD on Cloudflare, the daemon(cloudflared) creates new A record for each host and creates a tunnel between your host and the nearest Cloudflare data center. You can also run multiple services on a single host. And all these connections are secure.

Beside horrible, it's terrible, Just upgraded and can't even resize the panes. And the CPU usage is high even when not streaming or do any capture etc.

Also let them fill their credentials in a single form. Two-step login makes password managers experience terrible.

Got it. Why my MBP feels like burning when running zoom then?

> Need to first pan at least a bit vertically

Thinking of it, it would even be a nice feature since we need to pan to the left of the page or zoom out completely to go back in history with touch pad in Chromium based browsers.

> Still nice to see there's progress, and it's already mostly usable with the mentioned caveats.

At least.

Next release should definitely have this double-tap and smart-zoom feature.

Nice try. It works by pinching but double tap and smart zoom to cursor.

And if you zoom in somehow, you cannot pan over the page because Firefox act like you are seeing full screen and trying to go back or forward in browser history.

I actually mean double tap zoom that zooms to HTML element that your cursor on. Amazing feature for browsing experience. Chromium has this feature since a lot.

Still no pinch to zoom. No chance on macOS.

see https://mixart.ist which is a great alternative.

I think ReactXP is not a visionary project but Microsoft's approach to take advantage of javascript developers and make them able to build mobile apps for Windows phones beside indispensable platforms(Android, iOS).

Well, How about multiple return values? How will "check" keyword handle return values other than error?

  func ReadFile(path string) (string, error) {
    b, err := ioutil.ReadFile(path)
    s := string(b[:])
    return s, err
  }

How this function would be written regarding to drafts?. I am really confused.

A bunch of pioneer project like docker, kubernetes, etcd, prometheus etc. has been built with go and I don't believe that the maintainers suffered lack of generics and error handlers. On the other hand, as a new go programmer, I can really dive into their code base and understand each line of code without thinking twice. This comes from simplicity.

But these possible nested error handlers and generics will lead developers to think more than twice during writing or reading a code base. These ideas is not belong to go era but Java, C++ etc which go doesn't wanted to be like.

Someone here has mentioned that internal support of generics for slices, maps and other primitives. I think this can be the best solution for generics in go. For the error handling I think more elegant way could be found.

Please do not rush.