Coryodaniel

Staying on my 13 mini until someone makes a dumb phone that doesn’t suck.

Trust em or not … had that happen to someone else using Cursor a few weeks back. I ran a prompt for refactoring a function and all of a sudden it started dumping someone else’s directory structure and file contents into my text file. Like hundreds of files. Not exactly sure what happened but I immediately uninstalled Cursor.

Im on team tofu.

Come to the webinar tmrw, not quite a scripting engine but multilang no-custom-provider custom function support

https://www.linkedin.com/posts/opentofuorg_native-lua-more-i...

Apologies for the LI link I’m a startup CEO

This is tight!

Least cool thing I’ve ever seen.

Staying with my mini! These phones are too damn big!

Citizen is great. Definitely recommend it. Really easy to get up and running locally for PoC w/ ngrok.

I love these new words that just entered my vocab

I don’t recall the payload size, but these were all POSTs w/ decent sized bodies, it took about 60 Kinesis shards to avoid writethroughputexceeded.

Yep. Massdriver [0] is built on elixir and golang.

All user facing APIs and cloud provisioning state is written in elixir and runs on pretty much just fumes. Cloud systems interaction is written in golang because cloud stuff.

Email is in profile if you’d like to chat. Always happy to talk elixir and golang

0: https://massdriver.cloud

I wrote the lambda piece, you could say re-arch saved us the money (although we could only re-arch cheaply because we already had other massive scale serverful systems in place), but I don’t believe I could have made it as efficient and dependency free in any other language.

i had been developing in ruby for over a decade and about 5 years of Node exp at the time.

im not a language enthusiast and mostly write in go today.

Author of the “Lambda” piece [0], all of the cost savings I discussed came from API Gateway alone. The lambdas were negligible.

That being said, I don’t think we could have processed the traffic more efficiently in another language.

We were processing 12M requests per hour. You could run the entire thing on 2 vCPU we “over provisioned the crap out of it” by running it on 4 pods w 2 vCPU as the upper request limit.

Our service didn’t quite grow exponentially in use, but it did hockey stick. It went from free, to a few hundred bucks, to around $12,000 just for API Gateway. No Kinesis. No Lambda. Just API Gateway.

A good part of this entire system still runs in Lambda, although it will be moving into Elixir over time to make it easier to reason about and develop on locally.

What everyone should do is think about where your service is going, and can you afford those costs when you get there. If you don’t have a team of ops people and you aren’t familiar with serverful stuff, spending $30k/mo on HTTP requests might be cheaper than an ops team.

[0] https://medium.com/coryodaniel/from-erverless-to-elixir-4875...

waves

Thank you, we appreciate your words! We’ll do our best to make sure if you have to migrate, it’s just a binary change.

This is correct. TFCDK is also MPL (for now?).

You will be able to generate tfjson w tfcdk and execute it with opentf

I am very curious about the future of Nomad. It definitely has its place for some orgs and was exciting to see an alternative to k8s gaining traction.

I think this license change will hamper adoption and contribution when teams compare a foundation supported k8s vs a source available Nomad. I haven’t heard of anyone taking this on, but I’d love to keep my eyes on it if/when it happens.

Disclaimer: early supporter of opentf, cofounder of massdriver

We plan to maintain backward compatibility with the legacy version of terraform. You should be able to just start developing and swap the CLI.

Depending on when you start, the first release mag already be out!

Responded on a similar Q above.

https://news.ycombinator.com/item?id=37264675

We’d love to know what issues / PRs are important to your team to help us prioritize

Our first two issue templates on github are for exactly this! Please add any that are particularly important to you or your team!

https://github.com/opentffoundation/roadmap/issues/new/choos...

Thanks for having us!

I’m talking more along the lines of the 300 HashiCorp partners

https://registry.terraform.io/browse/providers?tier=partner

Massdriver co-founder here.

We are super excited to be supporting this initiative. The community around Terraform has been pushed aside for too long.

Terraform is the most widely adopted tool for managing cloud infrastructure. Putting it in the hands of a foundation that can ensure it remains open-source, community-driven, and impartial is crucial to so many infrastructure and operations teams around the globe.

HashiCorp manages a handful (~4 [0]) of the providers, while over 2,000 are managed by the community. I suspect breaking the interface would be further damaging to their reputation. The clouds will also have some influence around their provider.

[0] https://registry.terraform.io/browse/providers?tier=official

I said

open-source _community_

Listen to the Hashi CEO talk about community @18m

https://youtu.be/59rEiAyYEVk?t=18m

Note, they are tracking "updated at" on every one of the 27 FAQs ... it changes frequently.

HashiCorp hasn't been committed to open-source community in years, particularly with Terraform.

Their own words https://github.com/hashicorp/terraform/blob/ad634f60a5acbaad...

Yours or theirs? Elaborate.

If the point is they want more revenue, I understand that point - I think the decision will have the opposite impact.

If the point is they care about community, I can’t find a single through line that makes that true.

They are being given the opportunity to work in the spirit of the open-source and get the community support they claim to want.

The OpenTF manifesto has been signed by 84 companies, 8 OSS projects, and over 270 individual contributors.

The community that HashiCorp claims to have wanted is willing and able to contribute.

HashiCorp's actions are having a much broader impact on the open-source community from Kubernetes to containerd to flux and many others[1].

If you are 'just an end-user' of a HashiCorp BUSL tool, you will be impacted as the CNCF pulls away from using and contributing to those tools.

[1] https://blog.massdriver.cloud/posts/the-changing-face-of-ope...

Disclaimer: cofounded Massdriver

One of the authors here. Disclaimer: Massdriver, YC W22

First, this is Dave & I's personally opinion, not the view of OpenTF.

This isn't an attack on Hashi's founders. We don't know them, we've just watched a ton of videos over the past few days trying to understand them.

This is three things:

1. an uncomfortable feeling for my co-founders & I, realizing that the even the most passionate founders' image will eventually fade from a for-profit company

2. that we, as a community, may be at a point that we have to seriously look at any open source tool we use at work that is not a part of a foundation

3. calling out some of hashi's bullshit about their commitment, their change has far reaching impacts on the broader open-source community.