beaker VS beaker-ts

You didn't specify what framework you are using. There are different ones besides the native TEAL: pure PyTEAL, Beaker, Reach and Tealish. They abstract state management differently. Take a look if one better suits your style and needs.

MakerX is our technical partner on AlgoKit, and they've been doing a stellar job. Algokit's goal is to make development extremely easy, it was built with modularity in mind because all software (languages included) ages like milk, so whatever language there will be 30 years from now can still leverage our work. We are championing beaker, we're also trying to achieve vanilla python (this is the language) which is a huge engineering effort. Smart contracts programming will never go away, we can however give ever more building blocks that compose the most common parts of smart contracts. We're evaluating formal verification, have a few options (linked in other replies) let us know what you think!

Lastly if you still really want to get into smart contracts you'll want to use a framework, which you can find here (there's a tutorial on the algo dev docs too I think): https://github.com/algorand-devrel/beaker

For the initial release of AlgoKit we're focusing on back-end development and making sure we provide a great UX at that, we're developing a v2 roadmap and that will include a js front-end. React, Vue, Angular? Let me know which one you prefer! Whatever the outcome of the above is we want to provide a framework that generates as much as the front-end as possible and leverages tools and libraries to make that part of the development journey enjoyable