tupshin

12 ms·

61.
by tupshin 10y ago
GC has non-zero overhead compared with linearly typed de-allocations, but that's not the main point. The title mentions predictability, and one of the big blockers to using almost any GC-ed language is the lack of predictability about
62.
by tupshin 10y ago
Sure, but rust benefits from must_use annotations, which effectively turn those annotated affine types into linear types. Turns out they are both useful in a very overlapping venn-diagram kind of way.
63.
by tupshin 10y ago
Have you considered https://getchip.com/pages/chippro ?
64.
by tupshin 10y ago
It does, but within what bounds? The CAP theorem doesn't specify. One could assume that it means before the partition is restored, but that is only one possible valid interpretation. The PACELC theorem, which is by no means the last wo
65.
by tupshin 10y ago
Can confirm that this is absolutely not the case. I have encountered a number of companies that are absolutely fine with [L]GPL but not going to consider AGPL. Whether rightly or not, https://www.theregister.co.uk/2011/
66.
by tupshin 10y ago
This might be deeper than you are looking for, but this is the theory it's based on, and even has diagrams. :) https://arxiv.org/abs/1311.3903
67.
by tupshin 10y ago
Trivially, by never allowing either half of a partition to make progress while the partition is in place. Since the CAP theorem, by itself, doesn't put a cap(oof) on latency, it is valid to consider a system CA, if it if always availab
68.
by tupshin 10y ago
It is heavily inspired by Darcs, and is based on an alternative "theory of patches" that reportedly has much better worst-case performance characteristics. It is written in Rust, instead of Haskell, also contributing to better&#x2
69.
by tupshin 10y ago
While I largely agree with the positioning and much of the reasoning, this statement is so false as to be farcical: "All solutions necessarily have to come from the middle ground. " Just no. All good solutions should be taking in
70.
by tupshin 10y ago
Mock the wife
71.
by tupshin 10y ago
By passively accepting this situation your are part of the problem. Morality aside, your coworker that denigrates employees by calling them girls is opening your 15 person startup to justifiable lawsuits (discrimination and hostile work env
72.
by tupshin 10y ago
Cassandra
73.
by tupshin 10y ago
Given that none of those things are important to me, and that threaded messaging is important to me, I suspect we have very different answers to that question.
74.
by tupshin 10y ago
By your own admission, what you are asking for would require dependent typing. I am hugely in favor of rust eventually acquiring such capability, but it would be a huge change, and there are reasons why dependent typing hasn't hit main
75.
by tupshin 10y ago
That is an extreme mis-characterization of stymaar's excellent summary. in short, there are no runtime checks for iterating through an array, and since the general case of random access to an array can't be safe (without dependent
76.
by tupshin 10y ago
I believe the idea is that tokio, because of its zero-cost abstractions will be able to be efficiently be the foundation of those styles. Check out https://github.com/dpc/tokio-fiber/ for co-routines being re-envi
77.
by tupshin 10y ago
There is a lot of work already done, and more to do on this topic. The best source is the main tracking issue: https://github.com/rust-lang/rust/issues/2369
78.
by tupshin 10y ago
while it's still in early days, keep you eye on the tokio project https://github.com/tokio-rs/tokio which looks to be the foundation for higher level activity in this area
79.
by tupshin 10y ago
rustdt has been my daily rust environment for months. has some warts, but mostly just works
80.
by tupshin 10y ago
Edward Snowden responds to the HPSCI report on his disclosures https://twitter.com/i/moments/812014048866877440
81.
by tupshin 10y ago
This capability is still a work in progress for rust/cargo, but check out http://doc.crates.io/faq.html#how-can-cargo-work-offline
82.
by tupshin 10y ago
exactly the goal: https://github.com/jameysharp/corrode
83.
by tupshin 10y ago
Except that the source article is exclusively about the problems with tech in China, largely due to government and cultural reasons that have very little to do with Taiwan, and the fiction that there is actually a single China, inclusive of
84.
by tupshin 10y ago
These were the links in the article that provided background (the own-site links have their own references) https://openmedia.org/en/bill-c-51-just-passed-where-do-we-g... http://www.tomshardware.com/ne
85.
by tupshin 10y ago
FWIW,after spending a couple of years with rust as my primary programming language, I'm convinced that they made the right decision wrt mutability (immutable by default, but mutability availale when needed), as rust's lifetime sys
86.
by tupshin 10y ago
In what way is Rust's use of affine lifetimes insufficient to implement "function programming with no garbage collection"? Genuine question, given my previous interest :) https://twitter.com/tupshin/statu
87.
by tupshin 10y ago
Is anybody still thinking about Idris and HoTT? https://github.com/fmota/HoTT-Idris/blob/master/README.md I don't see anything more recent than the 2014 discussions.
88.
by tupshin 10y ago
The claim is that it is a blazingly fast hash function compared with other hash functions , and it is also written in Rust. Rust is an enabling technology, but not able to be dramatically faster than a comparable C/C++ implementation,
89.
by tupshin 10y ago
Personally I love Rust's error handling, but I do think that I understand your perspective. At least part of your objections would seem to be addressed by the combination of the ? operator to make it trivial to do the equivalent of re-
90.
by tupshin 10y ago
https://www.quora.com/What-are-the-views-of-the-Thiel-Founda...

More ›