News for hackers. Stuff that matters.
Re:I/O is no longer the bottleneck by kragen on Saturday November 26, 2022 @09:29AM (#33752908)
yeah, a friend of mine wrote a logfile parser in 01996 in c, and when i rewrote it in perl (also in 01996) it was about one tenth the size and ten times slower

whether i/o is the bottleneck depends on what you're doing and on which computer, and that's been true for at least 50 years

Re:I/O is no longer the bottleneck by computator on Saturday November 26, 2022 @10:21AM (#33753343)
May I ask what's the rationale for writing 01996 rather than 1996? I've seen this before but I haven't seen an explanation of the advantage of it.
Re:I/O is no longer the bottleneck by mcculley on Saturday November 26, 2022 @10:29AM (#33753405)
Re:I/O is no longer the bottleneck by withinboredom on Saturday November 26, 2022 @11:49AM (#33754236)
Haha, I thought it was some architecture I’ve never heard of.
Re:I/O is no longer the bottleneck by bqmjjx0kac on Saturday November 26, 2022 @12:06PM (#33754420)
But it looks like an octal literal.