Recent submissions

Comment · 1 year ago
Same but with editing a message on a browser and trying to delete a word with Ctrl+w
Comment · 1 year ago
We already have two keys, they are called Shift and Enter
Comment · 1 year ago
Comment · 1 year ago
if a gpg signature check fails, is it a correctness issue? a security issue? or both?
Comment · 2 years ago
Comment · 2 years ago
Relevant or not, python 3.13 shows the same thing:

Python 3.13.0: 799.6559143066406 ms

Node 18.20.4: 59.34080000221729 ms

Comment · 2 years ago
Note that the book uses python 2
Comment · 2 years ago

  "draw a line under the last word in this line"
                                           ____
Comment · 2 years ago
It depends how you measure the time i guess. I would say from 4 hours to 6 hours on an average workday (thats what wakatime says at least).

But is writing code, stopping for reading docs / thinking and continue writing code counted as 1 big unit of coding, or 2 small?

I dont code that much outside of my work anymore, buy i could go for 17+ hours when I was younger.

Comment · 2 years ago
For being a relatively new language, there are almost no "entry level" positions.

Just take a look at https://rustjobs.dev/. Most of them are well paid remote jobs, but they are asking for +3 years of "professional experience" with rust, "with a proven track record of building and deploying production-quality code", and more. Hell, iirc, i saw one asking for proof of contributions to the rust repo (eg, being a core maintainer).

edit: to be fair, i saw one position a while ago asking to be willing to learn rust

Comment · 2 years ago
Also, the site is really slow. The only thing that the site manages to turn on is the computer fans.
Comment · 2 years ago
> Yes. I was confused by its output, i.e. 2541.91s

Thats the output of the shell command `time` (im using zsh so the output differs from other shells) eg `time cargo build`.

system is the cpu time spent calling kernel functions and user is the cpu time spent outside kernel functions. The time is measured per core, so if the program runs for 2 seconds with 16 threads, the user time would be around 32.

Notice there is a cpu metric (1341% cpu), if you do: (user + system) / cpu * 100 / 60 = ~3.29 minutes = 3m:17s

Comment · 2 years ago
Yes, in linux there is a file system type called tmpfs which is mapped to memory (most of the time iirc).

> Filesystem Size Used Avail Use% Mounted on

> tmpfs 31G 22M 31G 1% /tmp

Try running `cargo build --timings`, it creates a report about build times. My guess would be storage speed, i would not expect memory speed to be that much of an issue.

edit:

> Windows compilation 8min took less time than Linux 45min?

I dont think i understood this correctly, but in the case you are asking (for clarification) about my compile times, i got around 3m:18s on linux, and around >8 minutes on WSL.

Comment · 2 years ago
I directly cloned to /tmp. 64GB ddr5, No overclock.

edit: (also, the machine was recently rebooted and had very few processes running)

After i posted the comment i tested on a laptop running windows with wsl (i7-12850HX 16c 24t) and the first build was going above 8 minutes.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton