![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
2 bytes would be 0-65535 and 8 sets is ~3.4×10^(38) addresses
2 bytes would be 0-65535 and 8 sets is ~3.4×10^(38) addresses
Also if you want a domain but dont care about the actual address, a .xyz domain composed entirely of numbers with less than 10 digits is $1-2 + same as renewal fee per year. $1.22 for me on porkbun
Just be sure to redact the whois information bc you will get a call from scammers trying to get you to register your domain on some “internet map” for a small fee acting as if its some step in your setup process you havent done yet
A slow Internet connection causes the UI to absolutely shit itself and freeze
SendToBoardingSchool()
One example I could think of is title-tagged posts given the lack of a tag implementation
I have more than once found a post my exact problem with an exact solution and sources, only to go back and realize it was my own post from n years back
I’ve noticed slow Internet can significantly slow the client side UI for some reason. Perhaps something with the tracking or DNS is different in private and the additional network usage is causing it to lag
I’m exaggerating a bit there. This problem is fairly easy to implement iteratively (e.g. keep a list of unbrowsed folders and keep adding to it), but that is not the case for all problems. Some will be easier to solve in one way, though fundamentally solvable either way
It depends on if the problem is recursive or iterative, and how much it needs to be optimized.
For example, you may use a for loop for a simple find and replace scheme for characters in a string, where you check each character one by one until you find one which matches the target, and then substitute that.
There are certainly recursive ways to do string replacement in strings which might be faster than an iterative search depending on implementation, but that’s more optimization than I might need 99.9999% of the time
A recursive problem that’s difficult to solve iteratively is browsing all the files in a folder and it’s subfolders. Each folder may have several subfolders, which you then need to search, but then each of those folders can have subfolders. This problem can be solved fairly easily recursively but not as easily iteratively.
That’s not to say it can’t be solved that way, but the implementation may be easier to write
Recursive code, however, is more frequently prone to bugs which causes infinite recursion leading to crashes, as it is not a tool which is often used and requires several more fences to prevent issues. For example, in the folder example, if one were to encounter a shortcut to another folder and implement code to follow that shortcut as if it were a directory as well, then placing a shortcut to a folder within itself might cause the code to recurse infinitely without having a maximum recursion depth and or checking for previously seen folders.
isalpha
documentation:
Return value
Non-zero value if the character is an alphabetic character, zero otherwise.
You should be either checking for not equal to 0 instead of true, as its not necessarily guaranteed to be 1
~= true
, or removing the comparison entirely
Also make sure that your loop condition is < and not “& lt” without the space unless that’s a weird formatting issue
For more information, make sure to check the documentation for the standard library functions
If I had to guess, negotiating POE voltage. Some stuff uses nonstandard voltage like some older ubiquiti gear
Not just this week but the past year or so
During covid many companies hired a ton of people due to the growth of many industries, particulalry consumer electronics and platforms like Plex and Netflix, and places like Amazon, Google, etc. Because many people were off work, there was greater demand. Obsiously infinite growth is not possible, and when things slowed down after covid, they moved to dump the employees they no longer needed
It doesnt necessarily have anything to do with AI; AI implementations are still extremely rough and moves to implement them at this point means providing an inferior experience. That said, some companies have been implementing AI, which will likely lead to worsening layoffs down the line
It’s essentially the traveling salesman problem