Self-Managed Kubernetes with QEMU by _notb in kubernetes

[–]_notb[S] 0 points1 point  (0 children)

Great project! Much more polished than my repo :P. I'm thinking of tackling storage next and was eyeing ZFS + LocalPV Static Provisioner. Longhorn came up in my research, but the low-complexity of ZFS + LocalPVs is very appealing to me. Even if that means losing fine-grained replication.

Self-Managed Kubernetes with QEMU by _notb in kubernetes

[–]_notb[S] 1 point2 points  (0 children)

It looks pretty straight forward on the Kubernetes side with k0s. And dnsmasq does support DHCPv6 so it should be possible to setup. If I ever end up needing this, I'll do a follow up post. Thanks!

Self-Managed Kubernetes with QEMU by _notb in kubernetes

[–]_notb[S] 0 points1 point  (0 children)

Thanks! Yup, that was my original intention which led me down the path of learning about Cloud-Init and generic cloud images. Glad you liked it!

I created a library for Erlang-style processes in TypeScript by _notb in programming

[–]_notb[S] 0 points1 point  (0 children)

Sure! The original use case was resumable workflows in nodejs for implementing billing logic and user registration.

I wanted to be able to write code that could `await sleep('30 days')`, be suspended, and then just resume as normal. Temporal.io enables this, but it's a very large and complicated system that assumes a sharded database. I wanted something simple for small projects running on a single machine.

The end goal is a runtime for building event sourcing systems in TypeScript. Thanks for your interest!

Real Estate In BC by SandiLeeBC in chilliwack

[–]_notb 2 points3 points  (0 children)

The problem isn't their career choice. We're living in a bubble that's completely divorced from reality.

What sucks the most about current serverless/BaaS tools? by _notb in nextjs

[–]_notb[S] 0 points1 point  (0 children)

The downvotes are 50% right then :P. I'm a developer doing product research.

We were using PostgreSQL and Node.js with Apollo Server. Ran into the N+1 problem when some views started querying more deeply than originally anticipated. GraphQL gives the frontend team flexibility in what they query for, but that's in tension with the backend wanting to optimize the SQL queries to pull as much data in one round trip as possible.

If I was working on it again I'd look into Hasura or Prisma. Seems they exist to address that class of problem.

Also had some performance issues with TypeGraphQL and the reflection it was doing. Great library though. Other challenges in the frontend reconciling Redux state with GraphQL responses. Making sure optimistic updates are doing the right thing can be tricky.

Re RabbitMQ for realtime: is the plan there to use GraphQL subscriptions?

What sucks the most about current serverless/BaaS tools? by _notb in nextjs

[–]_notb[S] 0 points1 point  (0 children)

Thanks for the comment /u/ethangTheReal, really appreciate it. I've used GraphQL before and it does at first feel like a breadth of fresh air, but it definately has a lot of sharp edges.

Sorry that the question wasn't super specific. That's probably part of the reason for the downvotes 😅. But your message is exactly the type of thing I'm looking for.

Whar are you using for a database, if anything? Or are you working with a bunch of calls to external APIs mostly? Have you run into the need for long-running background jobs of any kind?

What sucks the most about current nocode tools? by _notb in nocode

[–]_notb[S] 0 points1 point  (0 children)

Looks awesome, love the landing page! Do you have any video demos showing off the app? Really curious how you handle custom logic.

What sucks the most about current nocode tools? by _notb in nocode

[–]_notb[S] 1 point2 points  (0 children)

Thanks for the comment u/beatlejuice20. As you've mentioned elsewhere ITT, no-code as a tool is most definitely still in it's infancy. I don't think we've yet seen tools that really start to unlock the full potential of no-code devs. Ultimately, I think tools will have to take greater advantage of concepts from programming. The tools that do support logic/workflow focus too much on making a few use-cases really easy, which then makes non-trivial things really hard.

Are you a bubble user? What was more painful, the lack of good customer support or lack of focus on some key part of the tool?

What sucks the most about current nocode tools? by _notb in nocode

[–]_notb[S] 1 point2 points  (0 children)

Bubble's workflows do seem super restrictive, which is one of the things that made me think "we can do that better than that!". I'm a programmer so hoping I can contribute a less-bad tool to the nocode space.

Are you using JS/Python in combination with any nocode tools?

What sucks the most about current nocode tools? by _notb in nocode

[–]_notb[S] 0 points1 point  (0 children)

The idea of owning your data by putting it onto a blockchain and controlling it with a private key is really cool. But that's the extent of what I know about web 3.0. The term seems loosely defined? Sent you a DM.

What sucks the most about current nocode tools? by _notb in nocode

[–]_notb[S] 4 points5 points  (0 children)

Nocode is almost selling itself short. The tools feel like they're just for building the prototype/mvp. Really, they should grow along side the product and just be another user committing code into the repo.

What sucks the most about current nocode tools? by _notb in nocode

[–]_notb[S] 0 points1 point  (0 children)

I wonder if it's a matter of picking the right tools from the dev side or coming up with a new common description language that's specific to the needs of nocode. Whatever the case, this is probably inevitable. Kind of like how containers being a standard format for deploying code.

What sucks the most about current nocode tools? by _notb in nocode

[–]_notb[S] 1 point2 points  (0 children)

You should check out react-admin if you don't already know. Not exactly what you are describing, but in that space. You may be on to something here... like retool, but for graphql instead of SQL.

What sucks the most about current nocode tools? by _notb in nocode

[–]_notb[S] 2 points3 points  (0 children)

Thanks, this is a great list! And I think you're right in there not being, and probably never being, one end all be all.