"The Art of Violin Making" that the sibling comment mentioned is very good and is often referred to as "the Bible" of violin making.
"Violin Making - a practical guide" by Juliet Barker is also very good
I purchased the DVD series "When Trees Sing" by Peter Paul Prier (he was the founder of the Violin Making School of America in Salt Lake City). The DVD series wasn't cheap but it was worth it.
There is also an online course by Lucas Fabro, https://www.lucasfabro.com/en/online-course/, that I know is also very highly regarded. Fabro also has a number of free YouTube videos that are great to just get a feel for what's involved.
Oh so many, great. I have to admit, I've never heard of bubble tea before, but it looks really interesting! Do you prepare them? And are there many different variants or flavors to choose from?
I draw rarely but I think I draw instinctively well (sort of gifted if you want, nothing to be proud of, nothing spectacular neither, just some ease). No doubt if I had training I'd be a decent artist (I'd be mostly interested in drawing anatomy, natural things, etc.). But well, I sort of totally preferred computers the last 40 years so, drawing was not much developped :-)
I learned cooking on my own with a book that is given in some schools where they teach catering and cooking. So I got the basics of french cuisine (I'm french speaking). Took me 2-3 years to understand things. I'm more in traditional cuisine, which is old be heavily documented (and hard to master nevertheless :-)). I did it because I wanted to do something else than coding and something that doesn't require spare time: I cook for the family :-)
Learning to draw should be more frustrating if you don't "have it", but you can for sure (people undersestimate how good they can draw). OTOH, learning how to cook gives much quicker rewards !
Javascript has a lot going for it from async-everything to conveniences like destructuring. And it works in the browser and has things like Typescript.
I have to find good reasons to use another dynamically-typed language over Javascript.
I would argue async-everything the biggest hassle with Javascript. Most of the time, I need things to run synchronously. Do this thing, then do that thing based on the result of the first thing. The need for async is the exception. So what we end up doing is expending extra effort forcing all the async stuff to run synchronously when that should be the default case.
I get what you're saying, and yes, async/await is much better. But the entire reason it has to exist (and be used everywhere) is because javascript's default async behavior gets in the way so often. The irony is that when I do want some sort of async behavior, I often have to reach for something like bluebird anyway because I want better control over the Promises. So either I'm circumventing JS's default behavior by using async/await, or using a library that makes promises manageable. Almost never is it preferable to me to use JS's standard plain async behavior.
Thank you for summarizing this so succinctly. The true use case for async in the browser is rare. Sure, you're not blocking the UI while making server calls, but how often do you need to click around while waiting for something on the server to happen?
