GETProtocolCoreV1.0-DEPRECIATED VS psarm

I'm gonna go with the GET Protocol website: https://get-protocol.io/

Also check out GET https://get-protocol.io/

Not shilling - really this is just for info - but "GET Protocol " are trying to do exactly that.... https://get-protocol.io/

Anyway, here is GET main website and then the blog is here.

It'll depend on the pandemic, but my money is on GET Protocol (https://get-protocol.io/).

If you go with the "pay 20mln for a rock jpeg" NFTs then no, I doubt those would get more value over time. However, there are other, better, usecases with NFTs where I could see the value rising over time. GET Protocol for example (protocol for selling scalp free ticketsz, see https://get-protocol.io/) makes every ticket an NFT. Imagine buying the first Rammstein VIP NFT ticket for the normal sell price, let's say 500 euros. Now imagine Rammstein says "if you have a VIP NFT from us, we'll half the price of every ticket/merch you buy afterwards!".

It did a x30 in about 2 weeks I believe, from 0.30 euros to 9 euros. Retraced back afterwards (but still x10), but is growing once again. I got a feeling it'll grow waaay more in the near as I believe it's massively undervalued. It's still a nano cap, but it's got an actual working (and used by multiple companies) product that keeps growing. Basically it provides a scalp free solution of selling tickets (right of entry). Highly recommend looking into it: https://get-protocol.io/

I think that's something different, I'm thinking of this: https://get-protocol.io/

Thanks for the thoughtful response! Many of these are totally legitimate: in particular, we're making steady progress to centralize module design, release, documentation, and modernization, or at least to bring many teams closer together. In many cases, we're at a transition point between moving from traditional PS remoting modules and filling out PS coverage for newer OAuth / REST API flows.

I don't know how recently you've tried PS7, but the back-compat (particularly on Windows) is much, much better[1]. And for those places where compatibility isn't there yet, if you're running on Windows, you can just `Import-Module -UseWindowsPowerShell FooModule` and it'll secretly load out-of-proc in Windows PS.

Unfortunately, the .NET problems are outside my area. I'm definitely not the expert, but I believe many of the decisions around the default assembly load context are integral to the refactoring of .NET Core/5+. We are looking into building a generalized assembly load context that allows for "module isolation", and I'd love to get a sense in the issue tracking that[2] whether or not fixing that would help solve some of the difficulties you're having in building modules.

For Azure, you should check out the PSArm[3] module that we just started shipping experimentally. It's basically a PS DSL around ARM templates, as someone who uses PS and writes the Azure JSON, you sound like the ideal target for it.

As for the help content, that's a very funny story for another time :D

[1]: https://aka.ms/psmodulecompat

[2]: https://github.com/PowerShell/PowerShell/issues/2083

[3]: https://github.com/powershell/psarm