raitucarp

Now, we can delegate such tasks, comment every functions, classes and variables to GPT-3 davinci or Codex with clever prompt as clear as possible, (ELI5, reasoning, anecdote, storytelling, metaphors, etc). I think that would definitely useful AI use case.

Wow, the dream of decentralized web comes true, soon. With encryption and wasm, we are gonna conquer the goals toward true decentralized web.

Context:

https://p2pfoundation.ning.com/forum/topic/listForContributo...

When Al-Khwarizmi explain Al-Jabr, he was using Islamic family inheritance analogy. In world of number, Imaginary and negative also were poorly understood at the beginning. Imaginary number was a derogatory term and regarded as fictitious or useless. However, in the journey of Math, new concept of number usually unlock new knowledge even useful for other field of science. IMO surreal numbers in the video somehow will unlock another new fields.

I mostly agree with @antirez's hypothesis points, because I am also writing novel these days, I think on my journey I need to make strict structure, perhaps if any, something like writing software that has feature to make functional novel writing works because in programming I am fan of FP, not imperative nor OOP.

btw, Congratulations.. Looking forward to your sci-fi novel @antirez

Anyway, I love how redis evolved, and its design from the beginning from @antirez. That's why I am eagerly to read his another craft.

Cool project. If this project become stable it probably will replaces Disqus and friends with decentralized features.

I agree with you. And we also need technology like dApps that don't cost when running it by opcodes -with its vm, but use hourly pricing like cloud based hosting, so it will run your software deliberately without throw decentralized capabilities and it will enable decentralized economy to the mass.

- Next.js (react)

- Chakra-UI (for ui + ux)

- Hasura (graphql + postgresql)

- Express.js (for custom actions, event hooks etc)

- Kafka for message brokers

Previously, I was fullstack javascript developer using raw html with only express js and its renderer. Later I discovered ui and ux, react with dsl also graphql as data layer overwhelmed me. So I found simple stack for faster shipping. Learning curve is not that difficult I think.

Somehow remind me of Software 2.0[1]

[1] https://medium.com/@karpathy/software-2-0-a64152b37c35

Ebook from APIGee is pretty good, at least for me.

https://pages.apigee.com/web-api-design-register.html

Maybe you interested combine QT with react?

- https://docs.nodegui.org/

- https://react.nodegui.org/

Why someone bump this again?

Because dx (developer experience) is also important, I suggest you to considering use Expo

Yes, I wonder why they down-vote my comment

Awesome. But, I suggest Haiku people need hire ui/ux for their default theme/window. It will sure attract more user to try this OS as alternative.

"parasitic business model."

Can you elaborate more?

Man, looks great. I also build something similar in node.js. I implement everything what documentation said (complete implementation). ICYMI:

https://github.com/Ribhnux/piranhax

this!

also this: https://twitter.com/tangleblog/status/967513038374031360

I'm curious, is the date header important or not? OMG, Is this a real conversation? Even this tweet from the tangleblog who leak this document is hilarious: https://twitter.com/tangleblog/status/966286394636296192

I just copy paste from CfB's response, in case you missed it:

Thank you. This article was useful for me, it showed what details of IOTA haven’t been highlighted yet. Below I list incorrect things from the article, if you find time it would be great if you paid more attention to them and shared your thoughts:

“IOTA has no limit on transactions and therefore, it has no limit on bandwidth requirements or disk space.” — In the future the majority of the nodes will be swarm nodes forming clusters and using Swarm Intelligence. A swarm can process more transactions than a single full node.

“This means, if you run a full IOTA node, anyone on the IOTA network can write data to your hard drive with just a small, extremely low cost proof-of-work.” — IOTA was created for the Internet-of-Things with network-bound PoW in mind, the current state of things is temporary.

“Over time, the IOTA transaction set size can grow unbounded, leaving only storage farms with the resources required to host the data.” — This is incorrect even for Bitcoin because of pruning techniques.

“My past experience working at companies that develop hardware products tells me this does not make sense in any other way but a marketing bullet.” — While this thing is likely correct I decided to list it here. IOTA team has experience working at companies developing hardware products too. Even more, I bet your smartphone contains a chip developed by one of our advisors.

“IOTA claims their Ternary-based Proof-of-Work function will work with IOT because it uses minimal power, but I contend that any power usage more significant than signing a transaction is too much because there is another alternative approach.” — As I already said, IOTA will be using network-bound PoW, which will be consuming less energy than required for a transaction signing.

“Contacting a central server run by the company that built the IOT device, announcing the need to submit a transaction at which point the centralized server will submit the transaction on the device’s behalf.” — You described the Internet, not the IoT. Please, refer to “Connectivity” section of https://iot.ieee.org/newsletter/march-2017/three-major-chall..., it explains why you are very wrong.

“In the case of IOTA the client software design intends to kick nodes off the network that do not participate enough, so being even just a passive listener is not an option.” — And again you talk about the Internet, not about the IoT. Googling for reasons of not using IP(v4/v6) should show you the mistake.

I don’t mention insignificant mistakes in your reasoning, all those seem to be caused by the lack of information about IOTA. This is an issue that the IOTA team is working on.