tuxychandru

6 ms·

1.
The Tale of a Corrupt Backup(blog.cskr.dev)
3 points by tuxychandru 3y ago|1 comments
2.
by tuxychandru 3y ago
> now I only touch nano when I need to de-crappify a vimrc file You can start vim with --clean to fix your vimrc.
3.
by tuxychandru 3y ago
Apple gets a cut of the payments made through them and yet they provide this option to the consumers. The FTC or the govt can force (?. I'm not a US resident and know nothing of US regulatory bodies' powers) card networks and bank
4.
by tuxychandru 3y ago
This is what Netflix's Terms of Use says, "If a payment is not successfully settled, due to expiration, insufficient funds, or otherwise, and you do not cancel your account, we may suspend your access to the service until we have
5.
by tuxychandru 3y ago
Why is it still the norm in the US to allow companies to charge their customers whenever they please, without the customers having any control? In India, businesses are required to get a consent, at the time of subscription, to charge the c
6.
by tuxychandru 4y ago
If the primary concern is the lack of a common packaging format/app store, please consider publishing to https://flathub.org/ . It should solve these for you across all distributions. Testing should also be simpler as m
7.
Updated Debian 11: 11.4 released(lists.debian.org)
8 points by tuxychandru 4y ago|0 comments
8.
by tuxychandru 6y ago
Signal desktop runs as multiple processes. Did you add up all their memory consumption? On my Debian laptop, Signal processes consume about 700 MB of RSS in total, immediately after starting.
9.
by tuxychandru 6y ago
This will mean a virtual memory allocation of 800 GB. Such large allocations can fail, even if virtual, depending on over commit settings.
10.
by tuxychandru 6y ago
What is the collective noun for programmers? Merge conflict.
11.
India's First Covid-19 Vaccine Candidate, Set for Phase I, II Human Trials(ndtv.com)
4 points by tuxychandru 6y ago|0 comments
12.
Connection Leak in PgBouncer Behind AWS NLB(blog.cskr.dev)
1 points by tuxychandru 6y ago|0 comments
13.
Impact of Intel vs. ARM CPU Performance for Object Storage(blog.min.io)
2 points by tuxychandru 6y ago|0 comments
14.
by tuxychandru 6y ago
You can format code as "Verbatim" (Ctrl+T), and it will not be interpreted as wiki text.
15.
by tuxychandru 7y ago
Can you share some details or point to articles describing the design issues with NATS streaming?
16.
by tuxychandru 9y ago
What's the best way to get patent encumbered media working with Fedora for non Americans? apt install ubuntu-restricted-extras, does it in Ubuntu.
17.
by tuxychandru 12y ago
This article points to an attack that applies to AES-256, but not 128. https://www.schneier.com/blog/archives/2009/07/another_new_a...
18.
by tuxychandru 12y ago
I tried rust on this. https://github.com/tuxychandru/golang-challenge-rust/tree/ma... It was shorter in LOC than my go version, mainly due to try!, but the lines themselves were longer. The one difference in
19.
by tuxychandru 12y ago
How do sum types make error handling safer (without also adding exhaustive pattern matching) or easier (without adding do notation or macros)? The point I am trying to make is that adding some features from other languages doesn't prov
20.
by tuxychandru 12y ago
I said 2 things in very first comment. I never claimed rust doesn't have select. This is quoted from my very first comment in this thread, AFAIK, rust also doesn't allow selecting between a send and receive on channels. It only a
21.
by tuxychandru 12y ago
No the select statement of go. It is way more capable that rust's select macro. The tone of your previous comment made me feel that this thread is going in an unproductive direction, so I'll stop here.
22.
by tuxychandru 12y ago
I was referring to select statement, not async messaging support.
23.
by tuxychandru 12y ago
I was wrong about synchronous communication. Since most rust example use async channels, I missed the existence of sync_channel. However, even if that exists, rust's concurrency doesn't follow CSP as much as go's. Like I ment
24.
by tuxychandru 12y ago
Yes, that's what I meant when I said it not clear whether goroutines can be replicated as a library in rust "without compromising rust's core values". In fact, I mentioned no-GC and zero-overhead C calls. Since libgreen
25.
by tuxychandru 12y ago
Rust's multi-threading most certainly is not CSP. CSP requires communication to be synchronous. Rust documentation states that send() will never block and channels have infinite buffer. AFAIK, rust also doesn't allow selecting bet
26.
by tuxychandru 12y ago
This is a good read on the Go scheduler. http://morsmachine.dk/go-scheduler
27.
by tuxychandru 12y ago
Whether goroutine-like mechanism is possible in rust without compromising its core values is not clear, since libgreen attempted it and failed. Something like async..await is in the cards and I guess rust does have plans to implemented it s
28.
by tuxychandru 12y ago
It is not about whether goroutines need to be pooled. Goroutines work very differently from how OS threads. They are scheduled at the user-level by using non-blocking system calls to perform network IO on multiple OS threads. They are also
29.
by tuxychandru 12y ago
All those deal with threads. Rust 1.0 will have multi-threading just like C++, Java, etc. It is very different from how Goroutines work and do not offer similar benefits at all (specifically for network services). libgreen while it existed
30.
by tuxychandru 12y ago
Which library provides goroutine like concurrency in rust?

More ›