#async
Some new features we recently shipped to @nozbe
🪟#Windows app with support for multiple windows
↗️ Converting task to project
📧 Assigning task to anyone in the world via their email address
🗓️ Drag and drop tasks between days in Calendar
🛟 New easy access to contact form so our best human customer support can help to make progress
I recorded a screencast for you showing it in my #HomeOffice
#Swift #actors #concurrency #Combine #async
I just encountered something I can’t quite figure out. When I annotate an actor property with Published, it starts to misbehave, and give me unexpected results and test failures? Why would that be?
Does Published property wrapper somehow break the actor isolation?
Just saw this on Twitter account of @donavon
Saw it, wanted to share also here 🤡
> I saw this code in the wild. It doesn't fail, but 🤦♀️
> Do you see it?
Have you ever tried using AsyncPublisher? I have. And some of its behavior has surprised me. I looked into it in-depth in my newest article, where I show how to use its behavior for your advantage, as well as how to get around its limitations. As you will see, some aspects can quite differ from observing publisher in Combine. #combine #swift #asyncpublisher #async
https://www.cleevio.com/blog/the-not-so-equivalent-code-demystifying-asyncpublisher
It's sad to see that this POC seems to be dead. :(
Here is the problem line of code:
https://git.luminescent-dreams.com/savanni/tools/src/branch/kifu/kifu/kifu-gtk/src/main.rs#L32
The compiler says "cannot move out of `response_rx`, a captured variable in an `Fn` closure".
My intention, though, really is to move it all the way into that process.
#MustRead for every #dotNET #developer:
How #Async/#Await Really Works in C# - .NET Blog
Note: took me 1.5 hours to go through it (and I probably will have to revisit)
https://devblogs.microsoft.com/dotnet/how-async-await-really-works/
How do you `#async` and `#await` in #Python? Let's take a look. "Async Python, Good it is" is up next at #PythonWebConf. Join us #online at https://2023.pythonwebconf.com/, slides at https://robrich.org/slides/async-python/, code at https://github.com/robrich/async-python.
https://swizec.com/blog/finding-unresolved-promises-in-javascript/ - techniques for finding and resolving uncaught #Promises in #JavaScript. Works great for #async code too. Nice article https://github.com/swizec.
How Async/Await Really Works in C# by Stephen Toub.
https://devblogs.microsoft.com/dotnet/how-async-await-really-works/
I'm kind of surprised, but the synchronization primitive wrappers I wrote for my keepcalm crate are pretty decent competitors for other primitives in both sync and async contexts, and you don't even need to use two different styles!
I don't fully trust these benchmarks yet and I'd rather see what sort of throughput I can get from a webserver instead of micro-benchmarking, but I'm happy that my one-size-fits-all works this well.
Me doing asynchronous code refactoring in dotnet
How do you test your #async streams in #swiftlang? I'm using #composablearchitecture from @pointfreeco and a little helper. Found it very convenient and comprehensive, not only for testing the reducers. Would love to learn how other developers are doing it. Here's my helper: https://gist.github.com/darrarski/6d4374835b17ff18da0378f18f18aaa9
"Transparently concurrent" knocks my socks off! I think I'm in love...🥰
Asynchrones Programmieren: async minus await
:python: https://www.heise.de/hintergrund/Asynchrones-Programmieren-async-minus-await-7527129.html?seite=all
#Async #Python Good it is. I'm teaching at #ConFoo. https://confoo.ca/en/2023 Slides: https://robrich.org/slides/async-python/, code: https://github.com/robrich/async-python
Rust async fundamentals initiative, https://rust-lang.github.io/async-fundamentals-initiative/.
A small website/book that tracks the work of the async fundamentals initiative, part of the wg-async-foundations vision process.
@billseipel Additional resources:
An Introduction to System.Threading.Channels:
https://devblogs.microsoft.com/dotnet/an-introduction-to-system-threading-channels/
Using Channels In C# .NET – Part 1 – Getting Started (this is part of a three-part-series):
https://dotnetcoretutorials.com/2020/11/24/using-channels-in-net-core-part-1-getting-started/
IAsyncEnumerable:
https://dotnetcoretutorials.com/2019/01/09/iasyncenumerable-in-c-8/
C# Channels - Publish / Subscribe Workflows:
https://deniskyashif.com/2019/12/08/csharp-channels-part-1/
2/2
An absolutely amazing workshop on #rust #async given by absolutely amazing @kookie!
I'm glad that I managed to do first two exercises with a very minor help from mentors.
I kind of slacked exercise 3, but I ended up learning about https://docs.irde.st/developer/technical/ratman/index.html
Which is a modular routing system that has a lot of properties that I was dreaming about while thinking about #selfhosting.
Check out my latest article on async void EventHandlers in C#!
https://www.devleader.ca/2023/02/14/async-eventhandlers-a-simple-safety-net-to-the-rescue/
#dotnet #dotnetcore #async #tutorial #programming #coding #code
TIL something in Swift which I hadn’t realized before. It makes sense, but was counterintuitive to me.
If you have an async protocol requirement, it can be satisfied by sync implementation. Makes sense because I can think of “sync” as “async that returns immediately”.
It was surprising to me that I don’t even have to annotate the sync implementation as “async” to match the protocol, the compiler figures it out for me.
#Swift #async #concurrency #actor
There isn’t a particularly clean, standard, high-level way to do this, is there? Queue up function calls to a long-running function on a Swift actor, so only one instance of the function is executing at any given time.
I see various lower-level/older ways to do it, like NSLock, serial dispatch queue, capturing the execution as a Task and waiting for it to finish, etc. But none are really satisfying.
How To Use Async/Await In Flutter | by Andrew Zuo | Better Programming https://betterprogramming.pub/how-to-use-async-await-in-flutter-the-flutter-event-loop-97c696caf912 #flutter #async #await #howto
#TIL that using `process.exit(0)` in a #Typescript / #JavaScript code will terminate your process even if there are pending #async operations 😳
Instead one is supposed to use `process.exitCode = 0`
https://stackoverflow.com/a/70117186/8607180
Not a smooth transition from #csharp land
How to write for the way your coworkers actually read
Steal these data-backed marketing tricks of the trade to improve your memos, emails, messages, and more.
https://async.twist.com/writing-at-work/
#async #asyncmindset #remotework
🔥 Passionate about hands-on content to help educate everyone about #DevSecOps #cloudnative #AI #observability ?
🤗 #DevRel #opensource and #community engagement makes you happy ?
🌐 You live and breath #remote #async #transparency #diversity ?
💥 YES to all of them? Apply now and join our amazing Developer Evangelism team at GitLab!
@Reil I would want our devs to take a jolly old time making coffee/tea, pick out some assam leaves, grind the beans, warm a china pot, wait for it to brew, stare out the window, smell the aroma, stretch, rummage through the timtams, be distracted for a bit. Because if they haven't fixed whatever they were working on by the time they get back then it might be time for a walk in the fresh air. Breaks are not brakes. If you want to destroy productivity limit breaks. #async
Just reading up on #async in #Rust -- and I have the impression that this just replaces the complexity of the classic select() loop approach with another, different, complex approach, with the drawback that you can't transfer the knowledge you gained from mastering it to another language (like I have when writing select loop code in C and Perl). Am I missing something?
Use Rust async functions and methods in Swift, Kotlin and Python, https://github.com/mozilla/uniffi-rs/pull/1409.
It's ready! Large PR, sorry for the reviewers.
#RustLang #kotlin #SwiftLang #future #async #uniffi #bindgen
The gotcha of unhandled promise rejections
https://jakearchibald.com/2023/unhandled-rejections/
#EsNextNews #EcmaScript #JavaScript #Promises #Async
Rust `Future` returning a `Result<T, E>` work in Swift and Kotlin, and throw an exception in Swift and Kotlin when it's an `Err` on the Rust side.
It makes me happy.
we're looking to build the first engineering team at Warp, working on the next generation of build systems, and I'm looking for #rust and #elixir programmers 🚀
we're a fully #distributed, #async #startup based in Europe / LatAm
who'd you recommend? 🤓
By far the most read tutorial I’ve written https://gill.net.in/posts/auth-microservice-rust-actix-web1.0-diesel-complete-tutorial/
The Packt $5 eBook and video sale is still going on! Through Jan 17th, get any eBook or video for just $5, including mine: Parallel Programming and Concurrency with .NET 6 and C# 10 (works great with .NET 7 and C# 11 too).
#csharp #dotnet #parallelprogramming #async #programming #concurrency #ebooks #books #learning #sale #deals
This is something I’ve been experimenting with and I think it has some interesting potential. Implementation is pretty simple also: https://tritarget.org/#EventIterator
#javascript #async
Today's discussion with @janriemer, @jgoerzen, @rust_discussions, and @monad_cat inspired me to write the microasync #rust crate. It's a *tiny* #async #runtime focused on making it possible to use an async function as if it was sync.
@r0bertmart1nez
My eBook is also $5 as part of the Packt sitewide video and eBook sale. 📙
https://www.packtpub.com/product/parallel-programming-and-concurrency-with-c-10-and-net-6/9781803243672
#dotnet #csharp #async #concurrency
Should have been #Yew in the previous post (I'll edit because I can)
#Axum looks cleaner than #Rocket_rs (less reliance on Macros which are a bit too "magic" for me), and close ties to #Tokio are good.
I'm finding the "Brooks Builds" channel on #YouTube very useful. Playlist: https://www.youtube.com/playlist?list=PLrmY5pVcnuE-_CP7XZ_44HN-mDrLQV4nS
Going to be a lot to learn about #Async as well as everything else. Wasn't really an issue when coding for 80486 processors which was about as far as we got when I was professionally coding ;-)
@janriemer @rust_discussions @monad_cat I'm with you, Jan. I really enjoy #Rust for the reasons you mention, and more. My main gripe is the #async system. It has led to a bifurcation in crates. Do I need a standard or an async one? And if async, will it work with the executor I'm using? There is something to be said for the #Haskell and #goLang "green threads use the same API as synchronous" approach. Yes I know it lacks some flexibility, but OTOH it is unified.
One of the ways I disagree with many of my esteemed fellow Rust people is that I think #async #RustLang is great. Switching #nextest over to #asynchronous Rust has yielded incredible dividends, including but not limited to what I described in https://sunshowers.io/posts/nextest-and-tokio/.
The ability to write cross-platform heterogenous selects provides an extraordinary amount of power.
BTW, now that I'm at @oxidecomputer, I've been trying out nextest on #illumos and it works with zero (0) code changes!
I guess I should properly introduce myself, since I failed to do that with my first post...
My name is Ricardo, and I'm from Porto, #Portugal 🇵🇹. I've been a computer and technology enthusiast ever since I saw my dad #coding in Visual FoxPro, almost 30 years ago. How time flies!
Nowadays, I'm a Frontend Engineer at #Doist, building #Todoist and #Twist, the future of #remote and #async work.
🧑💻 Doist Engineering: https://doist.dev/
📰 The Async Newsletter: https://async.twist.com/
Need to maintain a visually stable state while new data loads?
Try this keepLatest resource!