GETProtocolCoreV1.0-DEPRECIATED VS additive-guis

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/

Start from an empty file and write to an imaginary API what you actually want to do and coding is easy!

But when you start from an existing codebase, existing infrastructure, it slows to molasses.

I'm an advocate and trying to design what I call "commutative programming", which is another way of saying that the behaviour is the product of every statement about the behaviour that is desired, not an explicit instruction of what to do next which is what modern programming is and it is slow and tedious and doesn't compose.

We need query engines for behaviour.

I started work on a commutative GUI https://github.com/samsquire/additive-guis but I'm also thinking from time to time about commutative code where we define refinements to desired behaviour and the computer query engine or rule engine generates the code that exhibits this behaviour.

For me desktop software feels extremely difficult to change and rearchitect to change swiftly.

A request/response server side application can be changed by adding endpoints, or redesigning or adding layers or database schemas but GUIs are hard to update easily by comparison because everything is so brittle and linked together so thoroughly.

I wrote toy proof of idea that GUIs could be additively defined declaratively. You define the layout by describing things in relationship to eachother rather than collection classes arranged in a tree. Behind the scenes, it IS a tree but in additive-guis in attempt to create GUIs that were responsive *to change of descriptions rather than declared positions*. you should be capable of describing the GUI with declarative description of how it should look *and* its behaviour.

https://github.com/samsquire/additive-guis

Writing code to manually maintain widgets in a hierarchy is error prone and slow to develop and adapt and change.

I worked on an Android mobile banking application and I wouldn't want to rearchitect the application.

I would love to understand Qt better but I find it very hard to understand to architect good software as a GUI.

I have looked into immediate mode GUIs.

I started writing a layout engine based on ORC Solver paper but it's very early days

https://github.com/samsquire/browser for a simple screenshot. It can arrange things without overlapping them, similar to a flow layout. But I need to handle text properly.

In some ways Mozilla achieved the impossible: a truly cross platform, compatible desktop application infrastructure that is powerful and rich. It can play video, show images and play sound and do 3D graphics. Unfortunately the market doesn't value those things, it thinks of them as dated. Firefox market share where it is.

Everyone said they wanted independent implementations of standards but when Google Chrome came out, everyone including web developers and engineers were happy to move to it.

There's just too much technical complexity and knowledge required to know how to do things on each platform. Writing a cross platform desktop application is LOTS of fiddly effort.

I've wanted to create a GUI similar to IntelliJ Community Edition but I worry that the code shall be outside my reach in understandability.

I wrote a GUI framework that uses React API directly.

It's more proof of concept than useable, the idea is that we don't actually have to write layouts, we can just describe the layout with code or a template language and let the computer work it out.

https://github.com/samsquire/additive-guis

https://github.com/samsquire/additive-guis