3 ms·
It's a good well worn tactic. You list in very high detail every single step of any process you don't like. It makes that process seem overly complex, then you
by syspec 1y ago
It's a good well worn tactic. You list in very high detail every single step of any process you don't like. It makes that process seem overly complex, then you can present your alternative and it sounds way simpler.
For example, making a sandwich: You have to retrieve exactly two slices of bread after finding the loaf in the fridge. Apply butter uniformly after finding the appropriate knife, be sure to apply about a 2.1mm level of coating. After all of that you will still need to ensure you've calibrated the toaster!"
- deleted 1y ago[deleted]
- jongjong 1y agoPretty much. In this case, WebSockets is simpler to implement than HTTP2; it's closer to raw TCP, you just send and receive raw packets... It's objectively simpler, more efficient and more flexible. It's a tough sell to convince me that a protocol which was designed primarily for resource transfer via a strict, stateless request-response mode of interaction, with server push tacked on top as an afterthought is simpler than something which was built from the ground up to be bidirectional.
- bobmcnamara 1y agoI fixed a few bugs in a WebSocket client and was blown away by the things they do to trick old proxies into not screwing it all up.
- fenesiistvan 1y agoI would be interested in those tricks
- bobmcnamara 1y agoA big one is 'masking' all client requests that a proxy can't effectively cache the response since the request always changes. The RFC explains it: https://datatracker.ietf.org/doc/html/rfc6455#section-5.3 https://datatracker.ietf.org/doc/html/rfc6455#section-5.3
- AtlasBarfed 1y agoAren't websockets the only way to some sort of actual multi-core and threaded code in JavaScript, or is it still subject to the single background thread limitation and it just runs like node does?
- nothrabannosir 1y agoDo you mean web workers? https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers...
- deleted 1y ago[deleted]
- hombre_fatal 1y agoOn the other hand, we're doing the worse tactic of getting held up on the first tiny subheader instead of focusing on the rest of a decent article. Also, their alternative is just a library. It's not like they're selling a SaaS, so we shouldn't be mean spirited.
- NetOpWibby 1y ago> ...we shouldn't be mean spirited. Am I on the right website? checks URL People find anything to be mean about on here.
- dizhn 1y agoBut it is frowned upon.
- waynesonfire 1y agoAbsolutely. The author conveniently leaves out the benefit that websockets enable ditching the frontend js code--included is the library the author is plugging. The backend shouldn't send back an error message to the frontend for rendering, but, instead, a rendered view.
- procaryote 1y agoThe loaf shouldn't be in the fridge, and 2.1mm is way too much butter, especially if applied before putting the bread in the toaster
- goosejuice 1y agoToo much butter? You're not living if thats too much butter!
- iandanforth 1y agoSandwich code review is what HN is for.
- dcow 1y agosanwy.ch is the name of the YC25 startup tackling AI sandwich tech.
- accrual 1y agoI think we need a function that returns the correct butter height given the dimensions of the input bread. We may also need an object containing different kinds of bread and the ideal amount of butter for each depending on the absorbtion characteristics of the bread, etc. The user's preference for butter might also need to be another parameter.
- plasma_beam 1y agoYou butter bread before it’s toasted? My mind is honestly blown (as I move to kitchen to try this).