dimeatree
Joined 6 years ago
Joined 6 years ago
I found this statement to be confusing; https://vanjs.org/tutorial#state-val-is-immutable While you can update State objects by setting the val property, you should never mutate the underlying object of val itself.
Then beneath is an example of the following;
const text = van.state("VanJS")
...
input({type: "text", value: text, oninput: e => text.val = e.target.value})
Which looks like a mutation - after reading a bit more around it is clearer that .val has a setter; but at a glance it just isn't obvious what is happening which I feel isn't intuitive.I got into powerlifting over 2 years ago and I have not looked back since. I got myself a PT/Strength coach, and to meet my goals I had to expand my knowledge to fill my daily needs, fix my sleep habits and manage my stress.
Don't focus too hard on the exercise / food, you need to change your whole mindset. It's a journey!
Sometimes you just don't know any better, or you're stuck for what ever other reason. I am 100% certain if it was easier to walk away from situations, anyone really would.
Regardless, congratulations on being sober for 22 years.
Then I remembered my experience of working with an SQL-like based API, that was a pleasant surprise and joy to work with.
I do not see why we can't use it from a client-side perspective, and safely re-cast it server-side.
In my situation I am finding the lack of consistent environment a reoccuring issue, the developer environment does not match production. However I kept it simple with Google App Engine Standard and Flex environments, I found the deployment process simple and was enough for me (at the time) - however I am finding we are going to step into dockerland; however I feel like it is very over my head!
The real threat that I can see, is if the hackers end up releasing more personal details.
But regarding the source code, this will end up being a boon for the modding community.