Male 18-year-old FOSS and GNU/Linux activist and user

  • 1 Post
  • 158 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle









  • Richard@lemmy.worldtoNo Stupid Questions@lemmy.worldWhy limit immigration?
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    2 months ago

    If immigration leads to more unemployment, then that is an economic problem, especially in the hypothetical case where the social benefits system is getting more and more strained by an influx of unemployed people. But generally, I think that you can expect that the immigrants will soon find employment. Besides that, there’s the cultural aspect that @jet@hackertalks.com mentioned. You could also make the point that the country’s infrastructure is more and more stressed as the population grows, but that is fixable and potentially counteracted by the labour potential of the immigrants themselves (i.e., qualified immigrant work forces can make a large-scale infrastructure overhaul possible that will lead to greater national capacities and a net benefit for the entire population).

    Aside from these things, I would argue that most of the other reasons boil down to xenophobia or racism.









  • Yep, I agree. Though one could make a hypothetical argument for expanding the array dynamically when needed. Of course, due to the varying sizes of NIDs resulting from CIDR (which you correctly mentioned), you would need to have a second array that can store the length of each NID, with 5 bits per element, leaving you with 3 bits “saved” per IP address.

    That can end up wasting more memory than the 32-bit per NID approach, e.g., when the host identifier is smaller than 5 bits. And there’s the slowness of memory allocation and copying from one array to another that comes on-top of that.

    I think that it is theoretically possible to deploy a NID-extracting and tracking program that is a tiny bit more memory efficient than the 32-bit implementation, but would probably come at a performance overhead and depend on you knowing the range of your expected IP addresses really well. So, not useful at all, lol

    Anyway, thanks for your contributions.