These are the hardest working and most intelligent people I’ve ever worked with. I truly believe we are about to revolutionize this industry very, very soon, at a similar-to-greater magnitude than SpaceX has managed.
If you’re at all interested in joining our mission, please get in touch. We’re still in our infancy and have plenty of seats that need butts on all sorts of teams. Even the Fusion and Data Engineering teams are growing, where prior aerospace experience is not at all required.
How do you compete with SpaceX? They're titans. They have the customers, contracts, and revenues, and it seems like they could build your design while still sending off tons of payloads using their existing infrastructure.
What makes your product so different, and how do you grow to anything close to their revenue and volume without them eating you first?
I ask these sincerely and in earnest! You're working on such a fascinating and awe-inspiring problem. I wish you the best of luck, because the field needs competition.
Everyday Astronaut did a fantastic video of his visit to Stoke Space, that goes into a lot of detail on what makes them so interesting. It's a really nifty design, and they do the same kind of rapid development that SpaceX does.
Given that Starship is so big, I think it could work out for Stoke to start with a smaller but fully reusable rocket, giving cheap rides to people who don't want to rideshare. Plus, governments tend to be interested in having multiple launch providers.
Aside from anything else, if they can position themselves as a clear second in terms of space innovation then that guarantees them billions in government contracts.
The space force is willing to pay a premium to avoid anyone getting a monopoly, we see that with the ULA contracts today.
Yours is definitely the correct historical take. Frontend frameworks really started to take off when componentization became the norm, first in early angular with directives, and later when components were immortalized with React. Web components tried to bring us back from the land of JS, but the implementation left much to be desired for those who had already taken the leap into framework land.
- working outside
- wood is a joy to work with: touch feels good, looks good, smells good too
- you get to build cool things that are actually useful like sheds, car ports, house extensions, bridges, even simple furniture
- when it's done, it's done
- it's both intellectual and physical work, it's good for your body and your mind
- learn new things
Some similarities; with a small amount of math, planning, and investment in understanding tools, you can quickly achieve things that the non-practitioners think are cool and useful. Plus the tactile experience provides a nice antidote to the endlessly ephemeral working experience of gazing on the computer screen.
Someone maintaining a dependency of cypress itself should add a dependency on cypress-debugger out of protest. Every single cypress installation would begin failing en masse
What you’re talking about is unidirectional data binding, and what you’re replying to specifically mentions its failure to scale with complex applications.
It’s not the kind of problem you can appreciate when taking any framework for a spin with a form input.
These are the hardest working and most intelligent people I’ve ever worked with. I truly believe we are about to revolutionize this industry very, very soon, at a similar-to-greater magnitude than SpaceX has managed.
If you’re at all interested in joining our mission, please get in touch. We’re still in our infancy and have plenty of seats that need butts on all sorts of teams. Even the Fusion and Data Engineering teams are growing, where prior aerospace experience is not at all required.