Live data from Hacker News

Ask HN: What are you working on (August 2024)?

news.ycombinator.com

391–400 of 1001 posts

Re: Ask HN: What are you working on (August 2024)?

#391
I am working on a new type of NFTs.

I found a way to add code to NFTs. The simplest way to understand it is that it is similar to Adobe flash.

I know that NFTs are down, but I have invented a way to add actual utility. I call them xNFTS - executable non fungible tokens. Imagine the famous Ape or Penguin NFTs - by adding my technology, the NFTs can change images, play music, or play games without installing anything.

I got a patent on the process and they work on any blockchain- or even off. the market is down, but I am very excited about tying web2 with web3.

If anyone wants to join or learn more, let me know

Re: Ask HN: What are you working on (August 2024)?

#394
A Jenkins replacement in Python (I hate Jenkins with the fire of a thousand suns, and it will never die as long as nothing appears to take its place). I've dropped it for the moment while I'm building a custom truck camper (which will also go on GitHub once my FreeCAD plans are done)

Re: Ask HN: What are you working on (August 2024)?

#397
I'm writing a programming language. https://github.com/coreyp1/CTang (probably will be moved eventually).

It's meant to be a scripting language to be embedded in another program, generating HTML. Eventually I hope to make a CMS and this be my solution for easy templating.

Technical details: Written in C, the language has an x86_64 JIT compiler, but falls back to a bytecode VM so it should work on any architecture. The language itself is dynamically typed and garbage collected. Currently at 20K LOC (not counting blank lines or comments), with good test coverage and checking for memory leaks. It's been quite enjoyable!

Re: Ask HN: What are you working on (August 2024)?

#400
I'm building an open source implementation of the Firebase RTDB server, that will be wire-compatible with Google's. This means that all the (already open sourced) SDKs will work pretty much as is, over REST or websockets. Security rules will also be fully supported. (The only meaningful caveat is that it's just the RTDB, so you need to deal with authentication yourself, and kinda shoehorn it into the existing APIs.)
Post reply on HN