Hacker Newsnew | past | comments | ask | show | jobs | submit | zja's commentslogin

They just implement the fetch api from the web, does the fetch api allow get’s to have a body?


Node allows it. Curl allows. Not having it is a breaking change and undesirable for node compatibility.


A body is technically allowed on any http request but it doesn’t mean anything on a get, a server is free to ignore it, anything in the middle is free to strip it, etc.


And yet many don't, Istio/Envoy for example. There are enough usable applications that utilize it that ignoring the body comes with a cost.


If you need bug-for-bug node compatibility you should be using node.


Your "bug-for-bug" compatibility ensures Axios, Elasticsearch, many GraphQL implementations, etc. works. Hence I will use node as mentioned in my original comment.

You should use bun :)


> Why precisely is it that we feel like we do not?

Because we don’t, our representatives work for companies like Meta, not ordinary people.


Isn’t proving a market exists, building a proof of concept, etc, all examples of exploring an idea? Those seem like perfectly reasonable expectations.


If the proof of concept takes an hour to code up, or proving the market exists just takes a bit of googling, then sure, you can prepare that before the first meeting where you suggest the idea.

If the proof of concept requires spending a few days in the machine shop making jigs and parts, purchasing equipment, and a custom PCB, then I really hope you'll bring it up for discussion beforehand in a meeting. Ten minutes of discussion with colleagues might be as useful as several iterations of prototyping. Not so that they'll shoot it down, but because someone might say "oh yeah, we have a spare mcguffin from last year's demo that you can use, should save you lots of time."



It means if you sail through it, Iran will launch drones and missiles at your ship.


> This architecture has a variety of advantages including increased security, no need for patching, fast upgrades and recovery.

SmartOS was developed by Joyent for their cloud computing product, it's primary use case isn't desktop computing. I think the advantages mentioned above were probably a bigger factor than the disk space. I would also guess that PXE would be the standard way to boot in a datacenter, not USB.


Fair enough


The are some great points



Love the top level domain haha! Incredible.


> Join our Discord for support and sharing feedback

I’m surprised to see Google directing people to Discord, do they do that for other products?


They had an invite only one in the bard days before it was rebranded to gemini. You didn't just need to get the invite link but actually link your discord to your google so I didn't bother.

Just goes to show that google's attempts at chat have been a big flop and even though google chat exists they don't use it.


They did for the new copilot agent builder products, thats where I get most early invites.


They used to have a lot of IRC channels on freenode for Android.


I recall them taking about one for NotebookLM.


Jules, their cloud AI agent.


> otel is at odds with the observability business because these actors have little interest to contribute back to telemetry agents since anyone can reap the rewards of that.

But all major vendors _do_ contribute to OTEL.


Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: