I do know the camera and interface ips, issue is how to change it without connecting to it since the connection function is fucked (not that the builtin library functions are much help, since you need to reset the camera, either through manual means or closing the the ethernet connection for them to take effect).
Presumably if the library you have is shit you'll need to delve into the device's native API to figure out how to directly command it to change its IP address.
I'm still pretty new at this stuff. I dont know what that is.
For IPv4, you should be able to assign its MAC address to a static IP in your router settings.
for(let update in this.dynamic){
for(let theFucking in this.dynamic[update]){
update[theFucking].display();
}
}
In the submillisecond range, you're likely measuring noise, either random noise or page-dependent noise.
So Javascript code being executed on my shit ass pc can do several mathematic calculations and update the DOM pretty much instantly? Makes it easy to optimize my code then.
The JavaScript interpreters in modern browsers are made of pure black magic. There have been thousands and thousands of man-hours put in them to make them run as fast as possible. Not to mention that the computer they run on can do billions and billions of them per second. So unless by "several" mathematical calculations you mean hundreds of billions of them, execution time generally won't matter that much. The DOM is also heavily optimized, JS simply submits some shit to the browser which updates some data structures in C/C++ really fast. Unless you're updating thousands of DOM objects with complicated CSS and extensive tangles of event handlers, that too will be negligible.
One thing to note here is that you're measuring with console.time(). JavaScript is JIT compiled, so at first the browser executes the code with interpreting it. After a function ran a couple of times it is then compiled down to machine code and thus gets faster. So it very well can be that you measured the cold start for your header and footer and for your mathematical code you measured the optimized output.
Good on you for writing code instead of reading all day, but inheritance is a key feature of OOP languages and you should do some research into it. It can be overused to poor effect but with planning is very useful.
1. Are you storing a bunch of functions but no variables in an object? Try using namespaces.
You'll find a balance of when you should refactor code, but it's part of anything that grows.
Your post is largely on point, but this part is kind of a meme. GCC and Clang still miss plenty of vectorization opportunities, and compilers for more niche languages leave all kinds of low-hanging fruit unpicked simply because they lack the manpower or prioritize other tradeoffs.
Yeah, they're also sort of 'one-size-fits-all' solutions, there's always going to be shit that falls through the cracks.
Vectorization has a limited number of use cases, and IIRC it has certain qualities that make it really hard for compilers to take arbitrary code and SIMDify it. I think certain optimized functions use weird half-unrolled loops when there isn't an intrinsics-based or assembly implementation for the platform.
This is an implementation problem with the languages and not a problem with compilers in general, and he seems to be most interested in mainstream languages anyway.
I'll read into it.
A few objects are all functions. Like I have one called calc that I store most of the mathematic functions in and another one called events that loads all of my event listeners.
Yes actually. I have a nested object in data called handle and its for all of the localstorage functions. I also have an object with two nested objects, there is one called type that has a bunch of items in the game and another one called get that calculates the properties of some of the items in my game.
bjarne wins once again
Learning shit on your own is an important skill to gain, but this always reminds me of that stuff Feynman said about explaining it to a 5 year old. Why can't you just tell him instead of sending him on a journey of self discovery in the Himalayan mountains?
I've heard async Java is actually pretty decent. In fact I've heard it is one of the easiest languages to do async in. The JVM and async are apparently Javas only real benefits. This comes from someone who hates Java with a burning passion btw.
I hate him for not just making C with classes but I must admit he is right about C++ in relation to rust.
... java...