lpinca

There is NO WAY in hell the Italians have tested over 200,000 patients for SARS-Cov2 in a matter of 2-3 weeks due to

See https://lab24.ilsole24ore.com/coronavirus/#box_6 that graphs shows the number of tampons per day.

https://lab24.ilsole24ore.com/coronavirus/#box_5 total tampons: 233222. The source is the Italian Ministry of Health.

Also in Italy, unlike what happens in other countries, all deceased people positive to the test are classified as "Covid deaths", regardless of the simultaneous presence of other serious diseases.

How is this better than https://httpstatuses.com/

I'm not sure how the append only mode works but I tried to run a script (appendfsync directive set to always) which sets a new key in an endless loop and kill the server in the middle of the execution.

No changes are written to the AOF so I guess the operation is atomic.

Did you ever try to disable permessage-deflate with ws? It will never be as lightweight as uws because ws is built on top of `net.Socket` but I think you hit this ws issue https://github.com/websockets/ws/issues/804 in the WebTorrent tracker.

I think ws will use 3/4 times more memory than uws with permessage-deflate disabled which is a lot, but far different from 47 times as advertised.

It's your idea of transparency which I don't like, not your project.

Yes, for 100k connection, using Alex's own benchmarks I saw that uws is up to 2x faster/more lightweight than ws except for the short message throughput where uws really shines and is up to 10x faster. It is a lot, don't get me wrong but the numbers on the README are obtained comparing the C++ server with ws which is totally wrong imho.

For 100k connections your own benchmarks showed a different story. Now I didn't try with 1 million and I guess it gets worse so I trust you but I can try with removing the upgrade request, the event emitter, etc from ws to start at least with a fair comparison.

`ws` is another popular WebSocket implementation for Node.js

Congrats for this achievement. For anyone using this in Node.js I strongly suggest to run your own benchmarks as uws is no way 47x 18x 33x and 2x times faster/more lightweight than ws. Also check how the improvements are obtained.

I'm still confused. You are announcing 1.0 but the actual version is 1.1

I'm confused. 1.1 has been released 13 days ago https://github.com/deepstreamIO/deepstream.io/releases/tag/v...

Take a look at https://github.com/primus/primus.

The project is young but looks promising.

I wonder what was the WebSocket module used in Node. There is this new module https://github.com/alexhultman/uWebSockets which is very promising.

This is great.

  Location: Perugia Area, Italy
  Remote: Yes
  Willing to relocate: It depends on the offer
  Technologies: JavaScript (Node.js, Primus, Express, jQuery), SQL (MySQL), Redis, MongoDB, PHP, Linux, Bash, Git, CSS, HTML
  Résumé/CV: Will send via email
  Github: https://github.com/lpinca
  Email: luigipinca (gmail)

I won a promo code for a .HOST 85% off from the same anniversary game.

I will not use it, so if you are interested let me know.

Maybe a bit out of topic but take a look at this https://github.com/sindresorhus/awesome-nodejs and this http://nodeschool.io/

It's nice, but why should i pay for this when i can write a simple bot that runs 24/7 and does the same thing for free? At least add a free plan.

Title updated.

Yes it does, but if you are building something that works perfectly only using websockets (e.g. a command-line utility), why would you use engine.io?

You can tell engine.io to only use websockets, but what's the point if you can use websockets directly and have the same API?

You can't use both. In Primus you can select only one transformer, listed above by V1, but if something doesn't work, you can just switch it with a single line of code. No rewrites, no need to learn a new API.

Congrats for the release, but i will keep using https://github.com/primus/primus.

No module lock-in!

Yes i'm a bit biased.

Silly.

Cool idea!

Yeah, but it's a limitation.

Playing a file in another domain works with http://www.schillmania.com/projects/soundmanager2/ or http://www.jplayer.org/ (http://jsfiddle.net/Q4LMV/18076/)

https://github.com/CreateJS/SoundJS/ instead respect same origin security policy (http://jsfiddle.net/SeUD7/) like your library.

That being said, i like your lightweight library, well done.

http://jsfiddle.net/mt6Tt/1/

Value is not of type AudioBuffer. Origin null is not allowed by Access-Control-Allow-Origin.

You should add a link to return to the original post then.

Like the design.

Nice and clean. Well done.