Apache Thrift VS todomvc

There are various notable implementations of RPC like Apache Thrift and gRPC.

> "Most of the logic inside the form has to be written two times: in PHP and in vue"

That's just your choice of how to build your app, right?

For an internal-facing employee tool - you could've just gone with rendering templates on the server and sending static HTML to the client. Have the business logic and validations take place on the server-side too. I'm sure you have your reasons for doing things the way you did, but it's not like there's only one way to build something like this.

> "Most enum types are repeated"

Here's just one of ten-thousand other battle-tested options you can use: https://github.com/apache/thrift/

> That's just your choice of how to build your app, right? You could've avoided this by rendering templates on the server and sending static HTML to the client, keeping the business logic on the server.

No, that's a requirement on most business cases, my comment stated 'complex and dynamic web apps'. Re-rendering the whole page everytime the user checks a box or clicks a button is (a) terrible UX, (b) hard to track the state between page refresh, (c) wrong practice and (d) bad performance.

> Here's just one of ten-thousand other battle-tested options you can use: https://github.com/apache/thrift/

Sure, I should setup a complex and huge dependency for just one of the many problems I highlighted. What a great idea

Thus, we released Baseplate.py v2.1 with deadline propagation. Each request between Baseplate services has an associated THeader, which includes relevant information for Baseplate to fulfill its functionality, such as tracing request timings. We added a “Deadline-Budget” field to this header that propagates the remaining timeout so that information is available to the following request, and this timeout continues to get updated with every new request made. With this update, we save production costs by allowing resources to work on requests awaiting a response, and gain overall improved latency.

The biggest addition is native async reading via futures::AsyncRead and futures::AsyncSeek, which required a lot of (to be merged) changes upstream (changes to thrift rust compiler and parquet-format-rs). I placed those changes on a temporary crate until things are released there.

The odd thing is unison started purely as a language. Now there's a platform.

I often find the best way to understand complex things is to dig all the way back to when they were being thought up. In this case there's a blog post from 2017 that I still find useful when thinking about Unison:

https://pchiusano.github.io/2017-01-20/why-not-haskell.html

Key quote:

Composability is destroyed at program boundaries, therefore extend these boundaries outward, until all the computational resources of civilization are joined in a single planetary-scale computer

(With the open sourcing of the language I doubt it will be one computer anymore, but it's an interesting window into the original idea)

Personally I find there's a lot to this. It's interesting that we're really, really good at composing code within a program. I can map, filter, loop and do whatever I want to nested data structures with complete type safety to my heart's content. My editor's autocompleting, docs are showing up on hover, it's easy to test, all's well.

But as soon as I want cron involved, and maybe a little state-- this is all wrecked. Also deployment gets more annoying as they talk about a lot.

So I think Unison always had to have a platform to support bringing this stuff into the language, even though they built the language first.

I'd love to hear some opinions from outside Unison about how they like using this language, tooling and hosting.

I'd like to hear this too.

Also, it would be great if there was something like https://eugenkiss.github.io/7guis/ or https://todomvc.com/ for platforms that we could use to compare Unison, AWS, etc etc. Or is there already a 7GUIs for platforms that I don't know about?

How easy or hard to build Shopify without zero coding experience? Shopify is a big thing =) So that would be hard to build with zero coding experience. Start with a todo list, micro blog, or something small in scope that interests you. https://todomvc.com/ is interesting since it is the identical app, written in many different ways, different languages and frameworks - and you can use them as reference to see how others have built something.

This article will transform a classic demo example of TodoMVC into a decentralized TodoMVC using DB3.js. We will show how to use DB3.js to perform CRUD operations and demonstrate the process of writing, reading, modifying, and deleting data in decentralized applications. We will complete a to-do list application as shown below. You can click here to view the demo code.

Um, just thought of something. If all the whatevers are so great (IO monad, state monad, applicatives, etc.) they should be demonstrated in one of these examples.

I just had a quick glance but it looks like an example implementation from here and you can find plenty of react/angular,... implementations right on the side (probably even together with go ;) )

I built my own To Do website, custom domain, hosted on pi (but I have since moved it to digital ocean hosting).

It's basically a toy website that I used to try out web frameworks. In my case I tried out Python's Django and Flask. Other people have done the same in a variety of languages and frameworks - check out https://todomvc.com/

It has the colors, font, work-flow, features that I want.

Yep, there's this: https://todomvc.com/

You can compare (LOC, complexity and final bundle size) for example using the TodoMVC app:- Ralix version: https://github.com/ralixjs/ralix-todomvc- React version: https://github.com/tastejs/todomvc/tree/gh-pages/examples/react- Stimulus: https://github.com/chloerei/todomvc-stimulus- Vanilla version: https://github.com/tastejs/todomvc/tree/gh-pages/examples/vanilla-es6