|
|
|
|
|
by atomicnature
1270 days ago
|
|
1. hurl.dev seems to do a lot more, with a focus on testing/CI/CD. I am focusing more on simplifying the request/response flow alone. I primarily care about interactive usage. IMHO, tests and CI/CD are better done through project languages, such as Python. 2. hurl.dev seems to focus less on team/collaboration aspect. For me, the first and foremost usecase is onboarding new teammates, ability to link APIs in code reviews, finding diffs in API, etc. Ease of use is paramount. So, I have developed a VSCode extension (https://marketplace.visualstudio.com/items?itemName=hexmos.L...), and want to focus on developing integrations with various other editors as well. 3. Another agenda I have is to develop good documentation and communication around a Plain-Text based API workflow for teams. I believe explicitly explaining how a Plain-Text + Editor GUI workflow can remove the need for expensive solutions is an important point. 4. I believe the syntax for hurl.dev is not exactly "memory-friendly". Example: HTTP/1.1 200
[Captures]
csrf_token: xpath
"string(//meta[@name='_csrf_token']/@content)"
# Do login!
POST https://example.org/login?user=toto&password=1234
X-CSRF-TOKEN: {{csrf_token}}
I am resolved to keep the syntax simple/readable first and foremost so that I can onboard new people into the language real fast, with less dependency on repeatedly referring to documentation.5. Lama2 is implemented in Golang (while hurl is in rust). |
|
[1] https://hurl.dev