- lijokOne of the best shitposts I have ever seen, by far. Absurdism taken to its finest form.
- PLEASE stop propping up the narrative that the GitHub Actions control plane was previously free. It never was. Pricing is not that simple. I see way too many people in this thread, and even GitHub Actions competitors promoting this nonsensical narrative.
- Ubicloud. Also faster than the analog runners github provide. Only problem is startup time is slower
- That’s 2.5x what my actual runners cost. For every $100 in compute, I will be paying $250 to github. They can fuck right off
- Like I said - you've clearly never been on Discord.
- Pretty sure you can install kali and have a hundred flags that have been legislated against in most countries, out of the box. Not a great argument.
- I'm not debating whether they should ban VPNs for minors with you. I'm providing a counter statement to your ill-conceived thought that this is "all manufactured fear by organized groups aiming to rip our rights to pieces".
- You've clearly never been on Discord
- If you have the expertise and restraint to not go off the rails, I agree, imperative is more powerful. That plan does not survive teams of sizes over 2 in the majority of cases.
- Getting too clever with an imperative language in what is inherently a declarative domain, is an idea bad enough that they invented a whole new language to avoid you doing it. But some lessons have to be learned the hard way I guess
- Amazing. Good work !
- How do you migrate from count/for_each to `enabled` ?
- Good move. They clearly didn't have the resources they needed. The design of the CDKs was atrocious.
- The lack of expressiveness of HCL is the point and what makes it so good
- It does. What are you looking for in a more advanced AWS provider?
- What features is it missing that you would like to see it implement?
- Why is gha just for short scripts, out of interest?
- I haven’t use depot but I’m pretty sure the setup is literally just switching out the runs-on value in your workflows
- Not trying to praise OOP at all here but notice a couple of things;
- You’re not dealing with persistence. No DB, no migration headaches, no downtime requirements, etc. Constraints entirely devoid of business requirements.
- You still arrived at the same level of indirection you belabored.
- You worked off of an established project that didn’t go off on any tangents. Building bottom up, depending on how much foresight you have, easily leads to the kind of mess that you cannot semantically compress without rewriting from scratch. In many cases, especially if working on projects with multiple people, those reusable patterns will be incredibly difficult to spot due to the mess surrounding the implementations.
You’re definitely on the right track, but for one it’s not an xor choice which approach you take (semantic compression or OOP), secondly, semantic compression is not as simple as it was made out here to be, and lastly, businesses do not build bottom up.
- God almighty. If you want to go in that direction, why not do all of this in a ticketing system with live collab features like Linear?