You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that Nimbus v0.1.0-alpha is out in the wild, I want to talk about where we can take this project and, more importantly, I want to hear your wildest ideas.
The Philosophy Behind Nimbus
When I started building Nimbus, the core principle was simple: Developer Experience should come first, and a bit of magic is okay.
What do I mean by that?
Traditional API clients make you manually configure everything:
Copy-paste URLs.
Manually type headers.
Rebuild request bodies from scratch.
Switch contexts between your code and external tools.
Manage authentication.
Understand cookie values on your own.
etc.
To me that sounded like friction and wasted time. Everytime I was trying to quickly test my rest api endpoints I was frustrated and thinking "It could've been better".
What "Not Afraid of Magic" Means
In the Laravel community, there's sometimes hesitation around "magic". Things that happen automatically without explicit configuration. Sure, magic can be bad when it's unpredictable or makes debugging impossible.
But good magic is good magic. That is the magic that will make the DX a breeze without comprimisng predictiabilty and configurability.
Nimbus already does some magic:
Automatically extracting validation rules.
Generating realistic test data based on field names.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hey everyone! 👋
Now that
Nimbus v0.1.0-alphais out in the wild, I want to talk about where we can take this project and, more importantly, I want to hear your wildest ideas.The Philosophy Behind Nimbus
When I started building Nimbus, the core principle was simple: Developer Experience should come first, and a bit of magic is okay.
What do I mean by that?
Traditional API clients make you manually configure everything:
To me that sounded like friction and wasted time. Everytime I was trying to quickly test my rest api endpoints I was frustrated and thinking "It could've been better".
What "Not Afraid of Magic" Means
In the Laravel community, there's sometimes hesitation around "magic". Things that happen automatically without explicit configuration. Sure, magic can be bad when it's unpredictable or makes debugging impossible.
But good magic is good magic. That is the magic that will make the DX a breeze without comprimisng predictiabilty and configurability.
Nimbus already does some magic:
Looking forward to your ideas!
All reactions