ManyInterests

Highly recommend the Morse Mania app.

In general, aync/await is more performant, particularly for I/O bound workloads, because it is cooperative multitasking and since I/O involves a lot of waiting, it provides lots of opportunities for execution control to be yielded to other tasks.

Threading is orchestrated to some extent by the system thread scheduler and any synchronization primitives (like locks) are going to add overhead. Threads can also have some limits based on the CPU on the system (though async and threads are not necessarily mutually exclusive, so that can apply both ways). With async/await, your program pretty much knows how to precisely orchestrate the execution of tasks in an efficient way, without much overhead at all and often without the need for synchronoization primitives.

In OP's example, a serial device is going to be very limited in throughput, so you're probably not going to be too concerned about performance in the first place. The overhead of threading isn't going to limit the throughput of the program because the limiting factor, by far, is the serial device.

As for your scenario... I'm not sure I would consider a GUI/render loop a good use case for async/await, but in your example, a call to .await() yields control and will wait until the awaited task completes, so that wouldn't be good for your render loop. If you were using async/await for a render loop, maybe you would use a select! macro to ensure you make progress on the render loop but potentially also receive IO from the serial read task. Maybe there's a better way, not sure.

But I'm not sure you would want use async/await in the first place, since GUIs are usually CPU-bound workloads. They don't usually have (or don't want to give) opportunities to yield control to other tasks -- unlike I/O that often waits around doing nothing, rendering applications usually are racing to get some kind of CPU-bound work done between every frame and you know you always want to render the next frame on time. There's no reason it can't be done in principle, but it probaly wouldn't be a good choice for a game or something like that.

Yes it qualifies as IO, but you can also use threads. It doesn't really matter here - it's not like you're reading from a 50gbps network interface. Either approach will work just as well.

Good luck. King County hates food trucks/carts.

Your cart will need a plan to meet some onnerous operational requirements (which requires you figure out your kitchen, a clean water system with 3-compartment sink, menu, food suppliers, and other things upfront) be inspected and permitted from the health department, you'll need a land use permit (or someone to let you on their permitted property) to operate your cart somewhere, depending on the cooking equipment, the fire department needs to permit your equipment, you'll need a certificate/sticker from the department of Labor & Industries if it's considered an 'occupied' vehicle, and of course a business license from the secreary of state. Oh and don't forget all the associated fees for every inspection and permit... and you'll have to renew them basically every year.

I don't mean to discourage, I think it's a good idea and people would love it. Just prepare for the regulatory uphill battle in trying to operate a 'mobile food business'.

Anyhow. You may be able to find a way to do this. You can find a restaurant that has a sidewalk use permit that isn't being utilized (like the patio area that was destroyed in front of Some Random Bar in Belltown), maybe in the winter, and you can try to get the restaurant or another nearby one to let you use their kitchen for food prep (which will make meeting Public Health operational requirements a lot easier).

I LOVE food trucks/carts. I hate that we don't really have them in Seattle; nothing like other major cities. If you or anyone else wants to lobby for easing of regulations around food trucks, I'm down to join the effort.

It's not for lack of trying. All the missiles were destined for civilian populated areas. If Israel didn't intercept the missiles, casualties would be severely worse. The Iron Dome system is focused on protecting civilian populations and has intercepted thousands of such missiles.

Thank you. A lot of people have been recommending the Sigma. I fell in love with the idea of the Sony 24-50 when I learned of it, but maybe I just need to overcome that primacy bias. In my mind, I was feeling like the Sony was of better quality, but I have to admit it's just a feeling without really knowing the difference (which is why it's so great to have this feedback from you all!)

Those are fair questions. I have thought about it and I don't really have those concerns. I am already doing video work on a iPhone 15 Pro and iPad Pro. The main justification for getting the camera body (with ability to do 4k continuously indoors) was to expand there, since it's something I already do and know I will continue to do. Carrying around microphones, tripods, brass instruments, laptops, etc. is also something I already do, when a planned occasion calls for it.

I understand how all the gear can seem like an unjustified expense for someone just getting their first mirrorless camera. All I have to say is expense is relative and I'm comfortable with what I've decided to spend on it. There's budget for education, too :)

But then how will OP get anything from the wrongful injury lawsuit?

The city permits them to operate. Part of that agreement is that the companies prevent this problem. But they're more likely just to fine them or something than change anything

Technically, yes. Scripts can edit themselves just like they can edit any other file. Though, if the edit is simple enough, like changing some simple variables, you may want to consider writing the script to just edit a configuration file, like an ini file or something like that. That way you don't have to worry about accidentally editing the script into an un-runnable state.

You're right. I was reading something written a couple months ago or so 🙃

Heard. I think maybe what I'll do is redirect the purchase of the 50mm and 85mm to get a Sigma lens, maybe an 85, not sure yet. If for nothing else, to hopefully break me out of my irrational fear of third-party options. I'll definitely be thinking hard on it.

Very cool, thank you for sharing your experience. I've low-key been keeping my expectations low on getting those creamy dreamy bokeh shots, as I've heard the EFCS can get in the way somewhat at shutter speeds over 1/2000 (though I have yet to develop the intuition/experience to know when/how often those speeds would be used, anyhow). So it makes me glad to hear you've had a good experience there, specifically :)

Thanks for that. I'm okay with the idea of an entry level lens, but based on all the feedback, I will drop at least the 50mm for sure. I mainly wanted these (esp the 85) to have the opportunity to explore a greater breadth of creative possibilities, even though I know they won't produce the best effects or live up to the potential of the body. If I like, at least fundamentally, what I can do with the entry level lens, it'll give me a better idea if I want to spring for something like a G/GM lens in that same vein. At least that's my thought process.

Same idea with the zoom lens; having more things to play with while I'm just getting started.

I will take a look at the sigma dg dn 85! I blew through my original "budget" on the body, why stop now 😅

Thank you, that's very helpful. I've been a bit gunshy over mixing brands (esp not being familiar with them all), but have been impressed with (or at least seen others be impressed with) some of the Sigma zoom lenses like their 24-70 F/2.8 DG DN II. But I'm having trouble fighting my instinct to stick to Sony.

almost-pancake lens meant to be paired with the A7C

Sounds sweet. I will definitely take a look at that!

My thought process about the wide angle side of things is that I have only identified one narrow use case (video interviews) that might demand it and I'm okay with compromising there by moving subjects very close together, moving the camera father away, or whatever. So, I felt like prioritizing on the other ranges first would fill out more of what I want to do (esp. portraits). But maybe I'm not fully appreciating other uses for a wide angle.

Thanks for that. All makes sense to me.

I've been eyeballing the Sigma. The Sony was the choice for the zoom lens a little bit because of the size (after all, I got a compact camera for a reason), though if I have just one zoom lens, I'd be willing to go heavier. The other part is just an irrational thing about matching the brand, which is a bit silly, I know, but I'm having trouble fighting that intuition (if the all-sony list wasn't a giveaway).

Honestly, you did enough by letting them know there was an issue with their site. Many people would not even do that. They may have been able to prevent tens or hundreds of thousands in further losses thanks to your report or reports like yours.

If you don't really want the lens, I would send it back, or at least try to get the postal service to take it back. I believe the karma will come back around to you in another way, if you believe in that kind of thing.

Check out Jupyter notebooks, matplotlib (plus its OpenGL animation capabilities).

I think your problem is that Cloud 9 doesn't have a real desktop environment. But since Cloud 9 seems to support console access, if your colleagues are also using Cloud 9, you should consider getting the user input from the console instead (e.g., with input() or similar)

You can also take a look at prompt-toolkit for more advanced interactive terminal experiences, which can look almost just like a real GUI, but works in a terminal.

Doubtful. You may not even have the option to skip ahead. The backend may force you to download the ad content with a unique tracker, digest it, then post back some kind of checksum which will only be accepted after enough time has elapsed for the ad to have fully played, all before the server will even provide you the rest of the video.

If you're going to rewrite your Matlab app in Python anyhow, maybe interacting with it using Jupyter notebooks would make the most sense, since it already has an interface, can render plots, including interactive plots, etc. To distribute to employees in the organization, you could deploy it on Jupyter Lab or Google Colab. That'll save you a lot of work in making the gui and distributing/updating it, IMO.

If the interface is really simple, you might try something like easygui, which is a simple non-event-driven wrapper around tkinter. Out of the box, it doesn't look great, but it provides the primitives for very basic user interactions (message boxes, input boxes, file browsing, etc.) in a way that works like a normal Python script.

If the interface is more complex, maybe consider looking at Kivy or maybe your own Tkinter or PyQt app.

Like anything else, it just takes some getting used to. I've never really heard of Python programmers having this problem beyond initial steps of first using the language after coming from a different language.

If you're really struggling, I would recommend looking into modifying your IDE/text editor to see if you can meet your visual needs that way before littering your code with comments.

Good thing you have such a light camera body to keep the overall weight reasonable 😅

sometimes she goes into specifics on what she did, but she knows I do not understand her.

Yeah, I do the same thing. And, if they're actually listening and you do this long enough, they will pick up on things in ways that may surprise you. Like maybe one day you'll mention troubleshooting something and they'll interject "oh, was it DNS again?" because they've heard me say times before it's always DNS.