5 ms·
>why wouldn't you do the binary protocol stuff in a C module and expose a nice easy api in the scripting language as is the usual practice You guys have been g
by unclebucknasty 13y ago
>why wouldn't you do the binary protocol stuff in a C module and expose a nice easy api in the scripting language as is the usual practice
You guys have been going at it for a while on this thread. I thought what cbsmith was saying the entire time couldn't have been clearer. I also think your statement here completely concedes his/her point.
You went from calling him/her an "old man" (your words) for not accepting your contention that Javascript can do it all, to advocating the use of C to handle the stuff it doesn't do well.
C. That pretty much says it all.
- TheZenPsycho 13y agoOkay so he/sh was preaching to your choir. But s/he needs to work a little harder to persuade or teach someone who isn't already convinced. I never said javascript could do it all. I said that it happens to not be true that javascript doesn't have a native way of dealing with binary. It turns out it does. that's not everything. That's one thing.
- unclebucknasty 13y ago>But s/he needs to work a little harder to persuade or teach someone who isn't already convinced It was pretty clear. You just didn't seem to be in learning mode. Your "old man" comment was dismissive on its face and you made assumptions rather than ask thoughtful questions. You said yourself that you understood once you went back and re-read. There wasn't anything new there. >that's not everything. That's one thing. It's the thing with regard to that discussion.
- TheZenPsycho 13y agoI honestly have no idea what you are talking about. He had nothing but dismissive comments about the language. There was nothing to learn or ask questions about. it only finally slipped out of him almost by accident what he was actually trying to get at, and even that isn't much of a relevant point. I don't buy your depiction of events at all.
- unclebucknasty 13y agoAnd just when I thought you were finally getting it. From cbsmith's very first post on the thread: >We're talking about a language that still doesn't have a standard way of reading and writing bytes... for talking to hardware. Think about that for a moment. You directly took exception to this and even quoted from that part of the post in doing so. You don't have to "buy" my depiction. Just go back and read (for at least the third time, apparently).
- TheZenPsycho 13y agoWhat's your point? You quoted a fact that he stated, which happens to be wrong, and I pointed out that it was wrong. That's evidence for my view of things, not yours. It's not a teaching moment, he had nothing useful to say. He still doesn't so far as I can see. Where we are now is let's just re-iterate the same wrong point over and over again, and pretend like it means something. Maybe if you're so concerned about me getting it, you can point out what his actual point is, which you seem to think is so obvious? spell it out for me.
- unclebucknasty 13y agoMy apologies. You are correct that I thought it was obvious. I'd started typing a reply that outlined what just happened, but it would essentially be a strange Cliff's notes recap of the thread. I'm not sure that I want to continue or that it would be sufficient in any case. So, apparently I'm not as concerned about your getting it as I initially thought I was. Perhaps someone else can jump in here and "spell it out" for you but, as it is, I'm content to leave things where they are. Good luck.
- TheZenPsycho 13y agowell, you don't have to recap the whole thread. just write something useful or insightful. Keep in mind that he criticised javascript for not having a standard way of reading and writing binary bytes (even though it does) and then suggested lua (which does not, at least not anymore than javascript does). My vague understanding of the point he was trying to make is that since javascript wasn't originally designed to deal with hardware, it's not a good fit. I don't find this to be a compelling argument though. It's more of like, a thesis, with no supporting evidence or premises, and the only point being the binary bytes thing, which is pretty debunked. There's no other point. No detailed analysis about exactly what it is about javascript that he thinks is unsuitable. Just vague handwaving. Do you have anything to add which might flesh this out? You do know the difference between an argument and a vague complaint right?