No need to swap wallets. Create a single 2of2 multisig wallet where each party holds a key. Send your funds two to different addresses of that wallet. Then you just sign a transaction transferring from both addresses to designated other ones (outside the multisig wallet). Since a "single" signed transaction in bitcoin can have multiple input and output addresses, each party can review the full transaction for correctness (50/50 split to right addresses) before signing.
The only challenge is "filling" the wallet, but doable: one party starts sending small amount to the multisig wallet, then the other party evens out. Increase amount by the amount the other party paid in total, until the preagreed amount is in.
Having VS2022 crash is certainly not expected or normal. I appreciate it must be pretty frustrating. If there’s any way you can submit a VS Feedback item when that happens, or post repro steps to the dotnet/aspnetcore GitHub repo, we’d definitely want to investigate.
Having myself sent VS Feedback in the past with video and other references and gotten no positive response except a bot closing for lack of evidence it's hard to care about reporting issues anymore. Much like other MS feedback hubs they feel more like spots to absorb issues rather than address anything meaningful.
This is great. Can the new razor syntax - that can finally have nested child content - also be used server-side, i.e for amp components? Will it be possible to build universal apps, and re-hydrate server-rendered content on the client like with react?
The CoreRT and Mono folks certainly do talk to each other.
As I understand, Mono is going to be moving forwards with WebAssembly much faster than CoreRT will do. Mono has officially committed to it already, whereas for CoreRT it was more of an exploratory spike.
Also it makes much more sense for Mono to be the .NET runtime for WebAssembly. Mono is already Microsoft's preferred production-grade .NET runtime for most client scenarios (iOS/Android native apps, Unity games) and is designed for that kind of portability. WebAssembly is another client platform like those.
The version of the specs published to knockoutjs.com didn't match the final release. I've just updated them. Please let us know if anything is still failing, preferably at https://github.com/knockout/knockout/issues
I wish this were true, but unfortunately not. Object.observe doesn't provide any 'read' notifications, so you wouldn't be able to detect dependencies like this does.
Would that be considered negative? In any case, KO is not a Microsoft project, and only one of the core team members (me) works for MS.
Anyway, many projects are built with KO, and its 3500+ watchers on GitHub suggests it's something like 7 times as widely used as one of the libraries in the article, so it's perhaps inaccurate to say that nobody considers it!
I don't think it is, but others might. I've often sung KO's praises but it always seems fall to the wayside.
Personally I think KO would greatly benefit from more architectural guidance (as i mentioned above). You're left on your own architecturally and structurally, with little guidance or higher level constructs to assist. This is much like backbone, but with backbone there is a lot of guidance out there, and even frameworks built atop of it (e.g. Marionette) which aim to instil best practices.
Things I'd like to see, which might quell other's trepidation:
* A large-scale demo app, with a detailed run-through of the how's and why's
* A guide to unit testing ko apps
* Drop IE6 (maybe even IE7?!) support to make it super lightweight. It's never going to be backbone lightweight, but imagine being able to say the tiniest front-end framework with no dependencies - that's a powerful message
Best practices and a large-scale app would be awesome!
The people in the IRC channel are very helpful (and will happily tell a cleaner way to do it than the KO examples on their website), but to have all this written up would be excellent.
Thanks for the tip about the IRC channel, didn't realise there was one out there. I assume it's on freenode?
But for most, hitting up an IRC channel is a barrier to entry they just won't have the enthusiasm to overcome. Such advice should be front and center, easy to access, up to date and canonical.
I agree. The documenation is awesome. Concise, accurate and not confusing (i'm looking at you angular). And the interactive online tutorial is the icing on the cake. I posit that a complete beginner could get up and running with KO within a few hours.
But again, for non-beginners, I'd like to see more in-depth stuff.
For example, I have spent most of my career using Microsoft developer tools building LOB applications. I think the MS dev toolset is great.
At one point I was involved in building a consumer web app and attended various "startup" community events. I would start chatting to people (generally Rails/PHP devs) and as soon as I mentioned I was building a web app using MS tech they would look at me as if I was mad. Sometimes they would even make excuses to stop chatting and find somebody else to talk to - I concluded from this that there is definitely some anti MS feeling within the startup community.
Anyway, this has gone off topic, but thought it was worth mentioning. BTW, one of my colleagues has just started using Knockout and thinks it is great!
How would you prove to me that you don’t still have the key for your old wallet?