Open
Conversation
Member
Author
|
I updated the PR to make it less controversial. I think it's now mergeable. |
brillout
added
marketing ✨
and removed
documentation
aleclarson
reviewed
Nov 1, 2024
| Instead of writing server code that only works with Express.js, write server code that can be deployed anywhere: AWS, Cloudflare Workers, Vercel, VPS, ... | ||
| With HatTip you write server code that can be deployed anywhere: Cloudflare Workers, AWS EC2, AWS Lambda, Vercel, Netlify, Deno Deploy, Lagon, ... | ||
|
|
||
| HatTip prevents vendor locking by abstracting away the underlying platforms. Vercel is getting too expensive? Switch to Cloudflare Workers. Node is becoming too slow? Migrate to Bun. Without changing a single line of application code. |
Contributor
There was a problem hiding this comment.
Suggested change
| HatTip prevents vendor locking by abstracting away the underlying platforms. Vercel is getting too expensive? Switch to Cloudflare Workers. Node is becoming too slow? Migrate to Bun. Without changing a single line of application code. | |
| HatTip prevents vendor lock-in by abstracting away the underlying platforms. Vercel getting too expensive? Switch to Cloudflare Workers. Node.js becoming a bottleneck? Migrate to Bun. All without a single change to your application's request/response handling. |
aleclarson
reviewed
Nov 1, 2024
|
|
||
| HatTip prevents vendor locking by abstracting away the underlying platforms. Vercel is getting too expensive? Switch to Cloudflare Workers. Node is becoming too slow? Migrate to Bun. Without changing a single line of application code. | ||
|
|
||
| HatTip is designed so that you can still fully tap into the underlying platform. As the need arises at scale, you can focus on a deployment platform and fully leverage its features that make it special. |
Contributor
There was a problem hiding this comment.
Maybe something like this instead:
Suggested change
| HatTip is designed so that you can still fully tap into the underlying platform. As the need arises at scale, you can focus on a deployment platform and fully leverage its features that make it special. | |
| HatTip lets you use special features of the underlying platform. If you do this, it might be harder to move your app to a different platform later. But you can choose to do this if it helps your app work better. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is purposely controversial :-).
I expect this PR to be rejected (in parts).
We can add back some kind of security warning: maybe we can find a way to sell HatTip as "it's ready" while warning users that it's beta and may have (security) issues.