GETProtocolCoreV1.0-DEPRECIATED VS PowerShell

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/

msiexec.exe /package https://github.com/PowerShell/PowerShell/releases/download/v7.2.6/PowerShell-7.2.6-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1

This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments.

https://github.com/PowerShell/PowerShell/pull/1901

PowerShell is available on macOS and Linux as well (source on Github: https://github.com/PowerShell/PowerShell). It may not be as well-integrated with things like system services management, but the language still works well. You can still use all the command line tools you're used to on Linux, of course.

nushell does look interesting, though the lack of a .deb repository does put it pretty low on my to-do list.

Issue #7940 discusses potential improvements to array slicing.

Note: This can be problematic as it prevents upstream commands from running their end {} block. See here. The new clean {} block introduced in PowerShell v7.3 does not suffer from this issue.

Can you give an example of something that PS can do that is built-in for text processing, instead of a proprietary symbolic query language?

[1] https://github.com/PowerShell/PowerShell

https://github.com/PowerShell/PowerShell/blob/master/LICENSE... is the MIT license. (Microsoft supplies debs directly which may reduce the motivation for Debian to do so.)

Oh, heh, also https://github.com/PowerShell/PowerShell/blob/master/docs/bu... the build script is written in PowerShell, so there's a bootstrapping problem :-) (Debian has solved those before of course, but with community sentiment like the above maybe noone is motivated to bother.)

According to https://github.com/PowerShell/PowerShell/issues/19628, the default behaviour is invoked whenever the completion script returns no output. To attempt to do so, I tried exiting the script via returning an empty string, or using the return keyword to exit the script completely, unfortunately with no avail. Is there a technique to achieve what I want, and is there any documentation about it other than the official one? Thank you in advance.