If you look at their leadership. They have no one who knows how to code & understand's their core product at the helm. No one in their leadership team could use cypress themselves.
Decision like this come from the leadership team, and I don't think they have people with enough sense of what they're actually doing -- breaking trust with their end customers to understand this is terrible idea.
It smells a lot like what happened with Unity a few weeks ago. It's the same story. Leadership team weren't actually users of the product, they didn't understand that the company's key value was the trust they've built with the customers and they broke it.
A few years ago I was evaluating cypress as an eng director at a large tech company. The cypress team came out to visit. It’s true the ceo was a sales guy but the founder came also and he was a true hacker. Maybe he’s not involved anymore?
> Can you share a link that shows their leadership?
I don’t know how accurate this is, but it’s a start https://craft.co/cypress-io/executives. It also appears that in February they added former MongoDB CEO, Max Schireson to their board.
Rainbow Insurance | Backend Engineers, Frontend Engineers (Senior & Staff) | 140k to 170k + equity | SF (onsite 2 days a week) | Full Time
We're a seed stage insurance technology company building insurance for small businesses. The team is small (just over 10 people),
but experienced. We have folks with 20+ years of insurance expertise as well as a strong engineering culture from folks who've been
working in fintech for decades. We're backed by top investors who've also invested in Asana, Vercel, and Brex.
Our Stack:
- React / Typescript Frontend
- GraphQL API
- Golang Backend
- On AWS
If you're interested reach out with a resume or a link to your linkedin at jobs@userainbow.com.
It’s a chemistry pun about the process of oxidation, oxides (such as rust) have a chemical formula of XO3 where X is the oxidized element. The library is called Py Oxide (PyO3) where the oxidized element is Python
He had leverage. Facebook's massive growth meant that he could command the terms of the investment, and he ensured that he would always continue to control the board even as he was being diluted with later rounds.
I've been looking for exactly this for a long time! I have also hosted a static (11ty) site on Netlify for a long time!
...and so I can't help thinking there's some dots not being connected somewhere, either in my brain (likely) or in Netlify's communication of their products and offerings (possibly?)
Agree. The best way I can describe it, is that it's a design pattern for a lightweight runtime.
You can use monads to implement exception handling, global state (without actually having global state), and async/await.
It's difficult to explain how all those features can be implemented through one generic interface. But it's easy to see how each of those things would require a "lightweight" runtime.
Decision like this come from the leadership team, and I don't think they have people with enough sense of what they're actually doing -- breaking trust with their end customers to understand this is terrible idea.
It smells a lot like what happened with Unity a few weeks ago. It's the same story. Leadership team weren't actually users of the product, they didn't understand that the company's key value was the trust they've built with the customers and they broke it.