HackerTrans
TopNewTrendsCommentsPastAskShowJobs

cramforce

no profile record

Submissions

Show HN: A TS SDK for Building Chatbots Across Slack, Teams, GChat, Discord etc.

chat-sdk.dev
2 points·by cramforce·5 months ago·2 comments

We Ralph Wiggumed WebStreams to make them 10x faster

vercel.com
2 points·by cramforce·5 months ago·0 comments

Show HN: Just-Bash

justbash.dev
2 points·by cramforce·5 months ago·0 comments

Vercel's sleep-deprived race to contain React2Shell

cyberscoop.com
1 points·by cramforce·6 months ago·0 comments

Our $1M hacker challenge for React2Shell

vercel.com
4 points·by cramforce·7 months ago·0 comments

"use workflow": Understanding Directives

useworkflow.dev
2 points·by cramforce·9 months ago·0 comments

Scale to One

vercel.com
2 points·by cramforce·10 months ago·0 comments

Addressing security and quality issues with MCP tools in AI Agents

vercel.com
1 points·by cramforce·10 months ago·0 comments

Stress testing Biome's noFloatingPromises lint rule

vercel.com
2 points·by cramforce·10 months ago·0 comments

Preparing for the worst: Our core database failover test

vercel.com
3 points·by cramforce·11 months ago·0 comments

If agents are building your app, who gets the W-2?

vercel.com
2 points·by cramforce·11 months ago·2 comments

The serverless compute to database connection problem, solved

vercel.com
3 points·by cramforce·11 months ago·0 comments

comments

cramforce
·2 months ago·discuss
Author here. Let me know if you have questions!
cramforce
·5 months ago·discuss
I would not over-read into that doc. In practice, the only missing stuff are extreme edge cases of the type that is actually not consistent between other implementations of bash.

In practice it works great. I haven't seen a failed command in a while

[Disclaimer: I made the thing]
cramforce
·5 months ago·discuss
In practice it is actually extremely fast because there is no process fork. You're talking nanoseconds for common commands

[Disclaimer: I made the thing]
cramforce
·8 years ago·discuss
Counter anecdote: As a Google engineer it always seemed like Edge implemented the sparsest possible version of the web platform to make major Google products work–and literally nothing else. That works to launch the browser, but then basically any product change runs a chance to no longer fall into that sparse subset and break in a browser. If Edge had implemented a more robust set of features, it would have massively improved compatibility down the road.