anonymous_union

i'm with you

the obvious solution, local storage.

yes. simplify your expectations. realize that not every piece of technology is worth using. biggest benefit is they say no.

did they reinvent email threading

in some other systems the concept has become overloaded. instead of multiple real people as users, different software with different permissions are different users. its not a bad abstraction.

kubernetes is dying, isn't it?

holy shit this guy knows no shame

your personality for sure is represented in the software you write. no different than any other creative profession.

yes

c++ is so bad. when i see threads like this one praising it, i feel bad for all the mental energy these people have put into understanding an unorganized and unelegant garbage dump of ideas. even his coworkers at bell labs tried to convince him c++ was a bad idea.

ken thompson wouldn't use it. then he invented go to spite him.

native racism in the prairie provinces has been awful. in alberta indigenous population appx 7% but inmate population appx 50%. saskatchewan and manitoba likely similar.

https://en.wikipedia.org/wiki/Demographics_of_Alberta#Visibl...

https://open.alberta.ca/dataset/0238e596-4add-46ee-81eb-2dbf...

pkg-config seems like all you need these days

apple ships it

interesting that code size is important to you. hey everyone, write shorter programs :)

right yea, modern CPUs seem to have all sorts of abstract optimizations. its kind of strange how we meet in the middle with hardware ISA manufacturers. they do all sorts of tricks on their side to make code go faster, and we try to generate machine code that we think will go faster, but neither side works with the other (compiler writers and ISA developers). i bet there is easy low hanging fruit here.

oops im dumb, convert argv[1] and argv[2] to integers first.

im not sure. given a hypothetical arch with only 1 free register, which local variable do you allocate to it?

  1 int
  2 main(int argc, char *argv[])
  3 {
  4         int sum = 0;
  5         int sum2 = 0;
  6
  7         if (argc >= 2)
  8                 for (int i = 0; i < argv[1]; i++)
  9                         sum += i;
 10
 11         if (argc >= 3)
 12                 for (int i = 0; i < argv[2]; i++)
 13                         sum2 += sum + i;
 14
 15         return 0;
 16 }

its fascinating how register allocation is not a solved problem. thinking about it, it seems like optimal allocation would depend on input/workload, so any ahead of time selection will always be a compromise.

because raccoons like shiny things

this is slightly orthogonal but i find manuals written by the original equipment manufacturer are better than 3rd parties (ford vs haynes for instance)

yes

the install process in OpenBSD has to be the most simple i have ever used, it is not surprising that it is easily automatable.

overall such a solid operating system. learning about it pays off quickly because they don't change things often, and your knowledge will be applicable for decades to come.

who could live without concatenate_five_strings()?

did you see the notes? it is confusing.

Notes This repository will be abandoned once Linux or FreeBSD is stabilized with write support. OpenBSD is not the main area of interest.

i have never had a problem with the filesystems.

seriously the best operating system i have ever used, and i've tried ubuntu, debian, alpine, gentoo, osx, windows, solaris, freebsd, netbsd, openwrt.

it's also one of the best products i have ever used, staying consistent, being well documented, extreme application of principle of least surprise. learn it once, use it forever kind of product.

regularly scheduled updates, extreme focus on technology, hardly any politics. if we want software development to become engineering, this is probably what it's going to look like.