| ▲ | ndusart 3 days ago | |
Yes, that would be concerning indeed... The author couldn't tell why he didn't manage to make run the C or python program but figured it is probably the blame of the language for some obscure reasons. He also mentioned that he should have implemented multithreading in C++ to be comparable with Node, but meh that's probably also not of his concern, let compare them as is ^^` Also he doesn't mention the actual language of the library used, but that would have voided the interest of the article, so I quite may understand that omission :P But at the end, nothing can be learned from this and it is hard to believe it is what "research" can produce | ||
| ▲ | josephg 3 days ago | parent [-] | |
Yeah it’s a rubbish paper. It’s just a comparison of some websocket implementations at some particular point in time. It tells you how fast some of the fastest WS implementations are in absolute terms, but there are no broad conclusions you can make other than the fact that there’s more room for optimisation in a few libraries. Whoopty doo. News at 11. | ||