rfc-leadership-council
hurl
rfc-leadership-council | hurl | |
---|---|---|
2 | 42 | |
6 | 11,552 | |
- | 8.6% | |
2.7 | 9.9 | |
12 months ago | 3 days ago | |
Markdown | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rfc-leadership-council
-
Rust has been forked to the Crab Language
This fork promises "All of the memory-safe features you love, now with 100% less bureaucracy!" Compelling, until you realise that all the commits are auto-merges of rust-lang/rust's main branch. Which means the same teams doing the same work, under a different name.
Rust is experiencing growing pains because they're still figuring out a governance structure that works for everyone. They want to simultaneously keep the current structure of bottom up development where each team (compiler, lang, crates.io, cargo) has the autonomy to make decisions for themselves, but the project as a whole can speak can come to a consensus and speak with a single voice. That's what this RFC tries to capture (https://github.com/rust-lang/rfc-leadership-council/blob/mai...). But the project isn't there yet, and is making these frustrating missteps in the interim. The lack of transparency into these missteps manifests as "bureaucracy" to outsiders like us.
If Crab lang actually attracted people doing the real work of development, they would have the exact same "bureaucracy" as teams tried to figure out how to build consensus and speak with one voice. The fact that they don't have bureaucracy is a direct consequence of them not doing any work right now. None of the people involved in regular Rust work, as far as I can tell, so they might not be aware of this.
Lastly, I want to note that the top comment in this thread is blaming the Foundation, which is simply bizarre. The Foundation very explicitly tries to stay hands off on technical decisions and does not interfere in how the teams organise themselves. You may disagree with that, but it's an inaccurate characterisation.
-
Hey Rustaceans! Got a question? Ask here (15/2023)!
Read eg. https://github.com/rust-lang/rfc-leadership-council/blob/main/text/3392-leadership-council.md as start
hurl
-
Bruno
I tried Hurl after Insomnia went the way of Postman. The highlights you list were the strong drivers for testing it out. Where Hurl fell short was composing requests. Example: X.hurl response has authToken. Y.hurl uses authToken. Z.hurl uses authToken. There's no import ability[1], so you've got to use other tooling to copy X.hurl into Y.hurl and Z.hurl.
Ultimately settled on Bruno. It's backed by readable text files[2] as well. The CLI works for scripting. And the GUI is familiar enough that I've managed to convert Postman holdouts at my dayjob.
[1]: https://github.com/Orange-OpenSource/hurl/issues/1723
[2]: https://docs.usebruno.com/bru-language-samples.html
-
Is there a good REST API development tool like Postman written in Rust?
I haven't used it myself, but maybe something like Hurl? It's not a GUI like Postman though
-
Insomnia REST client now requires an account
No, you got what's you write. If you want, you can see the run curl's command, save it in a script and replay it without Hurl. You can check the source code here [1]
[1]: https://github.com/Orange-OpenSource/hurl
-
I was wrong about Vim and Neovim
You might check out hurl for a RestAPI tool replacement. There is also a vim plugin for it, although I have not used it. Someone already mentioned dadbod (which I think works great on its own), but if you are curious there is also a plugin to add a UI on top of it.
- Hurl, run and test HTTP requests with plain text
-
Encrypted API request Docker Container?
just write a simple frontend on top of https://github.com/Orange-OpenSource/hurl
-
Hurl 4.0.0
We've a more "classic" changelog in GitHub [1], I see the blog post as an editorial view of the changelog: highlights of main features/changes with some context.
[1] https://github.com/Orange-OpenSource/hurl/releases/tag/4.0.0
-
Hurl, a terrible (but cute) idea for a language
I must say that the name is already taken by another tool language https://github.com/Orange-OpenSource/hurl which is a very good idea(similar to httpYac)
-
Hurl 3.0.0, run and test HTTP requests with plain text and curl
GitHub: https://github.com/Orange-OpenSource/hurl
-
Hoppscotch, web based Postman alternative, can now be fully self hosted
That's why we have hurl
What are some alternatives?
crab - A community fork of a language named after a plant fungus. All of the memory-safe features you love, now with 100% less bureaucracy!
websocat - Command-line client for WebSockets, like netcat (or curl) for ws:// with advanced socat-like functions
mimalloc_rust - A Rust wrapper over Microsoft's MiMalloc memory allocator
glow - Render markdown on the CLI, with pizzazz! 💅🏻
hashes - Collection of cryptographic hash functions written in pure Rust
plugin-openapi - Step CI OpenAPI support
rumqtt - The MQTT ecosystem in rust
libcurl - A command line tool and library for transferring data with URL syntax, supporting DICT, FILE, FTP, FTPS, GOPHER, GOPHERS, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, MQTT, POP3, POP3S, RTMP, RTMPS, RTSP, SCP, SFTP, SMB, SMBS, SMTP, SMTPS, TELNET, TFTP, WS and WSS. libcurl offers a myriad of powerful features
rust-playground - The Rust Playground
Karate - Test Automation Made Simple
crates.io - The Rust package registry
stepci - Automated API Testing and Quality Assurance