aper VS bicep

The relevance here is that this post mentions their new Rust library Aper (https://aper.dev/). In addition, CRDTs are a favorite topic of Raph Levien, AKA the Rust GUI guy, and featured in the Xi editor, his first major Rust project (retrospective here: https://raphlinus.github.io/xi/2020/06/27/xi-retrospective.html).

It's also super refreshing to see the work on Aper [1] [2] (a Rust library implementing state machine synchronization across a trusted network). Looking forward next series of articles here!

[1]: https://aper.dev/

[2]: https://github.com/drifting-in-space/aper

Our Aper (https://aper.dev) implements a number of similar concepts (state machine replication with optimistic local transitions + rollback). I 100% agree that it’s an easier model to reason about.

Your approach with cursors is clever, that part I haven’t seen elsewhere.

Drifting in Space | Full-time | NYC | https://driftingin.space

We make Jamsocket (https://jamsocket.com/), which allows application developers to spin up and connect to server-side compute. This allows browser-based applications to do computationally-intensive things that are otherwise impossible in the browser.

We went through YC and just raised a seed round and are looking to build up our team. We are based in NYC but are open to remote for experience candidates.

Our tech stack includes Rust, NATS, Docker, Postgres, TypeScript.

We have lots of fun technical problems that get into the nitty-gritty of networking and operating systems, plus fun open-source stuff like Aper (https://aper.dev/). We are excited to build a diverse team and encourage non-traditional candidates to apply.

Email [email protected] or see more details here: https://www.ycombinator.com/companies/drifting-in-space/jobs...

I thought it was a good idea, but Bicep did not agree. I have submitted a proposal to the Bicep team for how this can be allowed. Vote for this issue if you agree!

Bicep has limitations which makes it non-declarative even though it is marketed as declarative: https://learn.microsoft.com/en-us/azure/azure-resource-manag...

MSFT is trying to add features to make this better, but it is not in production yet: https://github.com/Azure/bicep/issues/10460

Additionally, Bicep does not support interacting with Azure Active Directory: https://github.com/Azure/bicep/issues/7724

So it really is not very useful. Terraform is better in almost every single conceivable way.

Github: https://github.com/Azure/bicep/issues/9569

Since its launch Bicep has become popular within the IT community. You can find blog posts, tweets, conference sessions, and plenty of interaction on the official Bicep GitHub space. Bicep became production ready at v0.3. It is supported by Microsoft Support Plans.

Please give Azure Bicep a try. You get a really simple experience with all the benefits of using the platform native capabilities https://github.com/Azure/bicep

I was on the bicep call last month but that doesn't mean I didn't miss the announcement, it looks like they are getting close though - https://github.com/Azure/bicep/issues/8598

Bicep, the open source project used by Visual Studio Code to extend its capabilities, has finally arrived in Visual Studio, enabling users of Microsoft’s flagship IDE to use some of Bicep’s most popular features in the same program they have been using since they were introduced to it — in other words, Visual Studio itself.

In addition, check the similar issue on GitHub.

There is an ongoing thread here https://github.com/Azure/bicep/issues/1853