Considering they sold their business to Grab, I think you could safely say Uber+Grab are as close to a global service as you can get, and probably represents a significant fraction (though maybe not 50%+) of the global market

There's a good document on this:

https://mypy.readthedocs.io/en/latest/existing_code.html

That's not so different from BeyondCorp and Uber's model.

Alternatively, some kind of OpenID Connect init (oidcinit) to get a JWT and then a PAM module like the kerberos one (which also checks the JWT's Key Id for revocation on authentication)

If you are just running a web app, then this is the correct answer. If your business is in your database, you employ data analysts and want to gleam some additional insights from your database, then it might be worth a look, though most people who chose MySQL did so because they were building a web applications and don't employ analysts.

http://ccl.cse.nd.edu/software/parrot/

Nextflow was mentioned. I think what most people want is probably closer to Airflow, although it takes some time getting it up to production in a cloud environment (there is astronomer.io and a GCP product).

HTCondor via DAGMan has existed a long time, and there’s even engines built on that (Pegasus, Wings).

There’s Swift (http://swift-lang.org/main/) and it’s successor Parsl. Cray has Chapel. These are a bit different, in that they are more like a distributed computer program. Of course, so is Julia, but built into these languages is the assumption you can be using unreliable, in some way, computing. Makeflow and GNU Parallel are closer to this category too.

Then there’s Beam, but that’s dataflow.

The crappy thing about this is it’s hard to understand when to use a solution and when to not use a solution. Why are there so many solutions? Because there’s a ton of different needs, and a lot of these focus on a few in particular:

Latency

Scalability or workers

Dynamic Scalability of workers

Throughput

Polyglot

Integration with existing Schedulers

Workflow Code Management (container support)

Maintainability of very large DAGs

Testability of DAGs/Development support

Execution Management support/Web APIs

Error recovery (especially for long running workflows)

Re-execution capabilities

Provenance tracking

Domain Specificity

Data Management (next to data processing)

... the list goes on.

As a user, there is no easy recourse. I had to create an account on dash.cloudflare.com, which I was able to do after SSH tunneling to another server and doing a SOCKS proxy. This because they don’t accept emails to support@cloudflare.com unless you have created an account.

Once you open a ticket, you are doing so from a free account, because you are not the user. You are not prioritized.

I have no idea why I can’t access tons of sites right now, but it’s fucking frustrating. I’m in Chile and all the VPNs I can use are in the US so that makes for a terrible browsing experience.

This has really slowed me down this week. If I didn’t have a VPN, like most people in Chile, I’m sure a small part of the internet just be broken.

Several websites behind CloudFlare are failing to load for me, notably for me, anaconda.org (104.17.92.24). Other sites have also been flaky.

Cloudflare's own support page has the error:

     $ curl -Lv https://dash.cloudflare.com/redirect?account=support
     *   Trying 104.19.197.29...
     * TCP_NODELAY set
     * Connected to dash.cloudflare.com (104.19.197.29) port 443 (#0)
     * ALPN, offering h2
     * ALPN, offering http/1.1
     * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
     * successfully set certificate verify locations:
     *   CAfile: /etc/ssl/cert.pem
       CApath: none
     * TLSv1.2 (OUT), TLS handshake, Client hello (1):
     * LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dash.cloudflare.com:443 
     * stopped the pause stream!
     * Closing connection 0

> Hi there,

> Thanks for writing to Cloudflare Support.

> While we would like to assist you with your inquiry, for the security and privacy of our users we can only work with the account holder directly, but your email address is not listed as the owner of any Cloudflare account.

> If you are a Cloudflare account holder, please submit a new support request from the email address you used to register your Cloudflare account. Note that you can also open a ticket directly through the Cloudflare dashboard following these steps:

> 1. Log in to your Cloudflare account and click on 'Support' in the top right corner, which will take you to our Help Center.

I've had workaround using a VPN in the USA, but that's really slowing my work down and obviously this doesn't work for everyone.

Comments URL: https://news.ycombinator.com/item?id=20354751

Points: 2

# Comments: 2

Certainly it's not fair to the employees. Certainly they probably didn't expect to get 10 men and 0 women in their current makeup. There may be no intentional guilt, but it's also not possible to know how they ended up with the makeup they have, 10 to 0, though it was probably incremental and without reflection on the makeup of the team along the way. Assuredly it probably wasn't malicious, but it's also like the people doing the hiring didn't reflect along the way - "hey, we've got 9 engineers and we need 10 and we are going to hire _another_ man for this role".

It's clear they (in this case the company) want to fix this in some way, as instructions "from on high" came down. Again company may or may not know how they got there. The company may also be failing to attract clients who want to vote with their dollars for a diverse company - so there could be a valid business case for this. Or not, maybe they just don't want a company with all dudes.

The original post was pointing out an unfair hiring practice due to this policy. I'm pointing out there is an alternative equitable hiring practice which actually leads to a fairer hiring practice for men and doesn't necessarily involve affirmative action, but that involves starting from scratch again (nobody said you'd necessarily lose your job - they could also easily make those positions available). Obviously this is not a tenable thought experiment, especially in academia thanks to tenure, so that's why we have these systems which, on the surface, may appear to discriminate against men. That said, many people interview for their current jobs in corporate restructurings all the time. That's probably not fair either, but it's accepted practice in the US.

... Or the could do it the way they are doing it.