pkolaczk

15 ms·

151.
by pkolaczk 3y ago
Therefore I cited the core of the program as well. It also does a bunch of non trivial async processing there. I’ve written at least two other non-toy Rust programs and I haven’t hit “lifetimes everywhere” problem there either. I guess the
152.
by pkolaczk 3y ago
I rarely use lifetimes and I don't deeply copy everything. This tool is probably the fastest in its class - does this code look like having a lot of lifetimes, cryptic syntax or deep copying? - https://github.com/pkola
153.
by pkolaczk 3y ago
> The real questions here is why people given opportunity to not have children jumps at it. Point taken, but that opportunity was not there until about 60 years ago. I don't think people unwillingness to have kids changed, they didn
154.
by pkolaczk 3y ago
Ask them after they have their first child. BTW: 2.1 is still quite good. Here in Poland (a formerly pretty much catholic country), we are at birthrate = 1.3 now and still going down.
155.
by pkolaczk 3y ago
Not owning a house is not a reason people don’t have kids. After WW II the birth rates in Poland were crazy high despite obviously huge problems with housing - often 2 families had to live in one small 2-room apartment (not a house). Now m
156.
by pkolaczk 3y ago
Message passing is not any easier or safer though. For every problem with shared memory concurrency you can draw a dual problem in message passing. See: https://songlh.github.io/paper/go-study.pdf For me, single-thread
157.
by pkolaczk 3y ago
Criterion has a warmup phase. So I guess both measurements were using a hot cache.
158.
by pkolaczk 3y ago
Rune - https://github.com/rune-rs/rune
159.
by pkolaczk 3y ago
> Meaning you should be programming just about 99% of your time in Python. No, not me, because I’m less productive in Python than in Rust, assuming the same level of final product quality, even excluding runtime performance. > Turns o
160.
by pkolaczk 3y ago
Diesel has efficiency of 40% not 25%.
161.
by pkolaczk 3y ago
> it has one of the most advanced type systems Well, that's a bit of a stretch. It is definitely one of the most complex type systems due to interactions between nominal sub-typing and type classes which is a bit hairy. But in term
162.
by pkolaczk 3y ago
This. Gradle wastes tremendous amounts of time on non-compile tasks. So even if Java takes a few seconds to compile, the whole build is often much, much longer. Interestingly, my impression is that maven is significantly more snappy.
163.
by pkolaczk 3y ago
> Javac itself is absolutely on the same order of magnitude speed as Go per loc Not really when it has to run on a cold JVM. And before it warms up, it’s already done. Then you are in territory of keeping the compiler process between the
164.
by pkolaczk 3y ago
So maybe I was just unlucky with gradle and lucky with cargo. A project that is a mixture of 20k LoC Scala and 300k LoC Java took 6 minutes to compile, and incremental was still several tens of seconds. Cargo/Rust cold compiles a proj
165.
by pkolaczk 3y ago
Gradle is faster than what? Than maven? Maybe. But not than Go or Cargo.
166.
by pkolaczk 3y ago
Not really, because it covers only memory while linear types cover all types of resources with a limited lifetime. GC won’t help you with „this operation is valid only within that context”, e.g. you can write to a file only as long as it i
167.
by pkolaczk 3y ago
Because we don’t know how to measure output properly and corporations often misattribute success. I’ve seen it happen a few times where someone delivering crap quickly is praised (oh, look how productive he is, so many tickets closed) or so
168.
by pkolaczk 3y ago
Yes
169.
by pkolaczk 3y ago
Unused variables in Rust are warnings, but in Go they are errors. Warnings are way more pragmatical - you can still get the code to compile when prototyping, but you get a chance to fix them before shipping. Go’s resistance to introduce war
170.
by pkolaczk 3y ago
I’m not saying it was trivial to implement internally. But from the perspective of developers this is not a new feature, but a new ability to compose existing features. Also, their existence does not change how you write idiomatic code. Exi
171.
by pkolaczk 3y ago
Those are not new features. Those are relaxing limitations on existing features and making things more orthogonal. Rust already has had generics, now you can use them in more places consistently. Similar thing with `impl Trait` in traits.
172.
by pkolaczk 3y ago
Scala has a lot of complexity due to OOP and Java interoperability. Rust does not.
173.
by pkolaczk 3y ago
Having written a few Rust projects, I cannot disagree more. As for writing code, I am just as productive in Rust as in Java, despite having way more experience in Java (15+ years). I spend less time hunting for bugs in Rust and less time th
174.
by pkolaczk 3y ago
You’re not a 10x if you can’t share your knowledge by mentoring others, writing good docs and writing code that’s easy to read and change by others. By this standard, they were not 10x. 10x is not about number of lines of code produced.
175.
by pkolaczk 3y ago
The examples given in the article do not match the final conclusion. This is all non sequitur argument. They chose a commonly known, boring tech stack (Spring boot and Angular) and then used them incorrectly and the project failed. And the
176.
by pkolaczk 3y ago
> discharge to 80%, keep it there Where? AFAIK this is a feature you need a third party app like Aldente for. The OS does not offer any way to control battery charging level. Yes, it tries to be smart and guess when you need full charge
177.
by pkolaczk 3y ago
No, I meant binary compatibility. Upgrading to a newer version always required recompiling all dependencies. One dependency didn't get an update and you were essentially locked on the old version. Some projects took years to upgrade fr
178.
by pkolaczk 3y ago
I'm not taking about bugs but error handling. For bugs there are panics and they do print stacktraces. For error handling stacktraces are just noise.
179.
by pkolaczk 3y ago
In Poland changing location of the job or other important characteristic of the job requires employee's agreement and signing an annex to the contract (yes, every employee must have a contract here). If the employee does not agree, the
180.
by pkolaczk 3y ago
Stacktraces are not useful for end users of the program and should never be shown unless there is a bug in the program. It is silly how many Java or Python programs display stacktraces on trivially preventable problems that are not bugs (e.

More ›