tealang VS flow-nft

The Algorand Foundation has a grant for developer tools if you are interested in making tools. https://github.com/pzbitskiy/tealang maybe could use some help (although in the past the development has sometimes been stalled).

Jason W: @Orageux101 I am not in the research team but from my point of view: When smart contracts were first launched we supported a very limited set of opcodes. This was mainly for performance reasons. There would have been no way we could have supported full solidity. Since then that list of opcodes has grown and we made TEAL (not the AVM) turing complete. This was possible because we have also been improving our performance (which is still ongoing). Because TEAL is basically an assembler language we thought anyone could create an interpreter to it if they desired. In fact we built PyTeal to do just that. The team is also actively updating https://github.com/pzbitskiy/tealang to write contracts in JavaScript as well. Our layer 2 contracts will also use Clarity->TEAL. With the next release we will also get the ability to create payment and asset xfer transactions in the AVM similar to way you can do in Solidity contracts. After that i could easily see some converters being built.

Now, open the link named NonFungibleToken which contains the NFT standard. Copy all the content from that file and paste it into the new file you just created ("NonFungibleToken.cdc"). That's it! You've successfully set up the standards for your project.

In this example, we use the ExampleNFT contract to create a basic functionality where any account that wants to receive an ExampleNFT must have a collection.

This usually refers to code or data that lives on the blockchain. It can be stateful or not. When minting an NFT, for instance, there is usually a variable on the smart contract that is incremented to record the total supply. The incrementing of the variable is happening 'on-chain'. In the case of Flow, we can easily store data in smart contracts or even within digital assets like NFTs. It works kind of like this – all NFTs on Flow implement the Flow Non-Fungible Token standard. The NFT itself is just a block of code that conforms to that standard. In addition to the requirements of the NFT standard you can store other data inside as well. So if the NFT represents something like a ticket to an event, then that block of code is where you have an opportunity to store things like an image of the ticket or other metadata like the event name, performers, and so on. It's up to the developer to implement what else goes there in addition to the Flow NFT standard requirements. Adding these 'extra' things to the NFT or a smart contract – things that are meaningful to the experience you're trying to build – are also part of what we colloquially refer to as 'on-chain'.

I thought that was still in ideation phase[1].

[1]https://github.com/onflow/flow-nft/issues/9

AngelHack is proud to announce that we're partnering with Tribe to host this online 6-week hackathon is designed to bring together the brightest creators and innovators from around the globe to challenge boundaries in the world of blockchain technology. Join us from September 20 - October 31, 2021, together with the experts from Filecoin, IPFS & Flow for Developer Hour sessions, technical workshops, and a whole lot of adventure and fun.

check onflow.org

http://howtobuyflow.com is porked on the bun but there's no content. https://onflow.org doesn't mention it