ioquatix

11 ms·

61.
by ioquatix 7y ago
The email operator.
62.
by ioquatix 7y ago
Talking about factually wrong... If you look at the full picture: https://trends.google.com/trends/explore?date=all&q=%2Fm%2F0... "DarwinPorts" was originally released in 2002. You can see it trending and
63.
by ioquatix 7y ago
ELI5. Can you retrofit coal generators with natural gas?
64.
by ioquatix 7y ago
Improvements like...?
65.
by ioquatix 8y ago
Here is an implementation of a Ruby based kv store build on top of rugged, which is built on top of libgit2: https://github.com/ioquatix/relaxo-model It's so much fun, but not that practical for scalable websites.
66.
by ioquatix 8y ago
aka let's just put everything in the application layer because solving it at the protocol layer is too difficult.
67.
by ioquatix 8y ago
Completely agree. If you want a generic parser for HTML-like tags, templates or anything where the context isn't a full HTML page, you definitely want syntactically correct/valid markup.
68.
by ioquatix 8y ago
Someone is apparently in NZ court for sharing the video as it is now deemed objectionable material. http://www.scoop.co.nz/stories/PO1903/S00171/sharing-shootin... I can personally see the logic of this. This
69.
by ioquatix 8y ago
I think since Hongli is the main developer of Phusion Passenger, it's logical for him to want to explore the problem space. While I agree with you, I also see no harm in experimentations and changes to the status quo for the sake of tr
70.
by ioquatix 8y ago
I agree with you. Actually, we've been having a lot of success developing an in-house tool to solve this problem and it's helped us build agile modular systems using C++. https://teapot.nz It's a one stop shop for
71.
by ioquatix 8y ago
Or just use ZFS and send/recv over the network? It's super simple, guarantees reliability, and very easy to replicate, e.g. offline backups.
72.
by ioquatix 8y ago
I would love to see the code.
73.
by ioquatix 8y ago
Can you show me your example code? Also, assuming it scales up linearly is a bit risky, although I agree with that kind of conn/s I am sure it will be sufficient.
74.
by ioquatix 8y ago
On my desktop computer with a single thread, Ruby can handle about 2000/conn/s. I'm just going to check a single thread with a similar C++ implementation.
75.
by ioquatix 8y ago
None of the things you mention really need to be in stdlib. There are plenty of awesome options, and the great thing is, they all have their own pros/cons and you can choose depending on your requirements. The point of C++ is to avoid
76.
by ioquatix 8y ago
I completely agree with this article, it is very well written and makes total sense. Managing dependencies is SO much more important and allows code to move quickly while existing legacy code sticks with what worked at the time it was writt
77.
by ioquatix 8y ago
I wrote a full stack implementation for Ruby: https://github.com/socketry/async Come and chat here: https://gitter.im/socketry/async TruffleRuby folks are trying to support us using native fibers
78.
by ioquatix 8y ago
If you can build a system which measures the latency of task processing and dynamically adjusts the resource allocation, I think you can be robust in the face of changing underlying conditions. It's non-trivial, but easier to look for
79.
by ioquatix 8y ago
After using OpenSCAD for several years, the more you use it the faster you get with it. I can easily whip out quite complex designs in a few hours. Visual CAD tools eventually start to feel very limiting.
80.
by ioquatix 8y ago
> Asynchronicity is just how sequential models are extended to support concurrency. Asynchronicity just means not existing or occurring at the same time, i.e. not synchronised or without synchronisation. How you expand that definition to
81.
by ioquatix 8y ago
There is a ruby implementation too: https://github.com/janko-m/tus-ruby-server
82.
by ioquatix 8y ago
Guilds are just a fancy name for threads or processes at this point. What they ultimately end up being is yet to be seen :)
83.
by ioquatix 8y ago
I personally prefer to call this asynchronous computing broken into parallel (execute at the same time) and concurrent (execution is interleaved) models.
84.
by ioquatix 8y ago
So, that's a good point, and yes the scheduler will have an impact probably several orders of magnitude in comparison. That being said, a good scheduler is basically just a loop, like: https://github.com/kurocha/as
85.
by ioquatix 8y ago
It's the perfect approach except users must deal with mutual exclusion which is tricky for most developers.
86.
by ioquatix 8y ago
Hi, I'm the author, I'm also a Ruby core committer, and yes I'm aware of Guilds. The are a model for parallelism and don't really affect concurrency at all. At best, they provide a 3rd option on top of processes/thr
87.
by ioquatix 8y ago
> I have worked on high volume Ruby applications where the problem with using async I/O combined with poor raw execution of Ruby code resulted in excess garbage to be collected. What async I/O approach did you use and where did
88.
by ioquatix 8y ago
I wrote an addendum https://www.codeotaku.com/journal/2018-11/fibers-are-the-rig... With C++/assembly, you can context about 100 million times per CPU core in a tight loop.
89.
by ioquatix 8y ago
I've thought about this too, and it might be the route C++ takes. That being said, to resume you need to wind through all your function calls executing parts of the state machine, it might actually be slower. That being said, I'm
90.
by ioquatix 8y ago
Hi, I'm the author, and I agree, so since everyone is so interested I'll check my original benchmark and fix the article. Update: I wrote an addendum https://www.codeotaku.com/journal/2018-11/fibers-are-t

More ›