although they are experimenting with it)
Do you have a source for this maybe? This is very exciting news but I don't wanna get my hopes up if it's not true
although they are experimenting with it)
Do you have a source for this maybe? This is very exciting news but I don't wanna get my hopes up if it's not true
I've only gone through the reddit thread and tbh most people seem to be bashing this method and pointing out flaws? It doesn't seem like a magic bullet solution and dual boot seems like the better option, at least for now.
Git Fork is amazing
Validation is usually the first step so I only start preloading after it's done of course, but you are right - you can easily end up loading more data than it necessary.
However, it can also result in fewer overall queries - if I load all relevant entities at the beginning then later I won't have to do 2+ separate calls to get relevant data perhaps. For example, if I'm processing weather for 3 users, I know to preload all 3 users and weather data for the 3 locations where they live in. The old implementation could end up loading 3 users, then go into a loop and eventually into a method that processes their weather data and do 3 separate weather db hits for each of the users (this is a simplified example but something that I've definitely seen happen in more subtle ways).
I guess I'm just trying to find a way to keep it a pure method with only "actual logic" in it, without depending on a database. Forcing developers to think ahead about what data they actually need in advance also seems like a good thing maybe.
Thanks, I'll give it a try! I'm really surprised this is the only suggestion here that's free / open source (at least the community edition), basically everything else is subscription based.
Python with Jupyter has always done well by me!
Hmm, having googled very superficially about django and flask, it seems to me like the state (at least today) is the opposite - flask is lightweight and django is more heavy duty, having a built in ORM layer, authentication service, admin interface, db migration framework, etc.
To be fair the article also says Django is known for its performance but when I googled that the other day, it looked like it was often near the bottom of the chart rather than top... I guess it really comes down to personal preference in the end 🤷♂️
Thanks for the book recommendation, I'll definitely check it out! The course sounds really helpful as well, I imagine there are many remote classes like that nowdays or as part of learning sites like pluralsight so that might be worth checking out. If there's one conclusion I got out of this thread so far is that it is pretty much something you have to learn and practice in advance and then hope to use appropriately, there's no sure-way or easy way of finding a pattern once you're already faced with a problem.
Seems like on one hand, programmers (online at least) are really against being questioned during interviews about whether they "live the code" and spend their free time on contributing to other projects or developing their own, but if this is really the only way to learn stuff like that then maybe they have a point. I was hoping there's a better way but I guess it's the same as always - work enough and hope the stuff you learn ends up being useful one day...
Maybe I'm using the word pattern wrong but I meant like builder, factory or visitor pattern, but on a more wide scale also stuff like dependency injection / IoC - basically "techniques" that are not bound to a specific language but rather provide a design by which some things can be accomplished better. Afaik those are not related to specific languages
This whole fediverse feels very shaky tbh, we have this issue now but as someone who is usually on kbin there's been issues like these from the start - posts not getting propagated to other instances, mod actions not being sent or updated, missing entire domains because of the bugs in the filter, etc. Add to that legitimate choices like defederation and domain blocking, it just feels fractured and nonfunctional because I still need a separate account on every instance to actually participate on it.
I know it's a FOSS project with no guarantees and everything these people do is in their free time but I really wish stability and basic functionality was the first thing they focused on, otherwise everything else is in vain since it's on top of an unstable foundation.
Thanks for the suggestion! I'm struggling a bit to incorporate that command into
podman compose
though, I'm reading through this issue and I'm a bit lost.Do I just add this to sonarr section in my yaml? I tried it and it doesn't seem to have done much
Should I try and switch everything to
podman kube play
as some user there recommended maybe?