sisve

Completely prohibited is not what they say is it? Is it not wait until 8'th grade to get your own. Meaning you can borrow your parents or similar.

Seems like the value proposition is quite similar to windmill.dev

Could you explain a bit more about the differences and similarities between you and windmill

Seems like a good idea. It would have been revolutionary 10-15 years ago. But the db-space has gotten really crowed the last couple of years. And all have the focus on doing it simpler.

You should try to find your target audience and see how you can make nodb better then what ever db/solution that audience is using instead of nodb

Good luck!

Yeah i guess i kind of did., I should have asked the parent comment. I'm not a java/kotlin developer but for me it looks like kotlin is thriving. Is that not how it looks for insider's?

Thanks. That explains it. See that it was added to deno in jan. I guess the last version on deno made it ready to be used on deno deploy.

I agree so much with the article about cloud being to complicated and fast feedback being import. I wish them the best of luck.

PaaS solutions and not IaaS is also a solution for many.

No code / low cose beeing a solution for someone else.

It's not to many days since my solution was on HN. Windmill.dev is really something special.

And by mine i do not mean that i has any affiliation with windmill, just that it solves my problem. quick iterations including ui building.

But it's not a low code plaform either. I would call it a code platform for developers

Am I the only one reading this right or am I the only one reading it wrong.

Deno is not supporting node.js built-ins. It's deno deploy. Meaning that this will not work on other hosting platforms, right... or?

What do you mean by "same fate as kotlin"? I would say Kotlin is doing great. Anything I missed?

yes you can sync the scripts, the json for the flows and the app UI. Including variables, secrets, resource types etc.

See https://github.com/windmill-labs/windmill-sync-example

it should be trivial to push that to a self-hosted setup if you need it.

I have not tried to take my entire workspace from self-hosted to cloud. But I have been exporting and importing individual scripts/flows/apps from self-hosted to cloud.

(no affiliation, just a happy user)

Currently the only support shell is Bash

I actually got codeium to work on windmill today trough their chrome extension. the extension lets you whitelist sites to work on. They do not offer a chat interface yet for the chrome extensions but they do have it on other integrations they provide. So I would not be surprised if they got it on the chrome extension also, at least if it turns out to be popular.

You should def check out windmill.dev.

They center more around code, and then builds app and flows based on the code/scripts you create. It's been a really pleasant experience for me. The first time I looked at the product I did not quite get it. But when I tried it I was hooked. It was not what I expected but what I needed.

You can have your code in git and use vscode and push scripts up to windmill if you like, I do and like it. You CAN also edit flows and apps from vscode. But I'm quite sure you do not want to - meaning it's JSON you will change and not the underlying svelte scripts.

I actually started using windmill after I described my pref. low-code solution on HN and what I felt was missing and got a response back saying that I was describing windmill.

You should check out windmill.dev For me it was a breath of fresh air.

It's opensource - so you can self-host. The UI is quick and responsive.

But my favorite part of it is that it centers around code. Other tools like zapier and retool (my experience) and budibase (your experience) are so much many clicks and if you drop down to code (aka the off-ramp) you need to program in a input field. With windmill you have an LSP and the Monaco editor (the code editor that powers VS Code) and you can have sync to git. So if you like you can sit and program in vscode, but are you doing small changes you can do it in the web gui. So code is "native" to windmill and it feels so nice.

(no affiliation, just a happy user)

If someone needs something between zapier and trigger, check out windmill.dev. been using it for a few days. And I'm really impressed. I think Activepieces is targeting the same user as zapier. Trigger is targeting developers. Windmill seems to be able to give github sync and + you start of with writing code not in the GUI. And then you add a GUI on top of the script or connect scripts together into workflows. As a developer i found it amazing. But it's for people who can ( ow would like to) program. I think they found some kind of magical middle ground. (No affiliation, just a happy user.)

As a zapier alternativ this looks great. Congratulations with the launch and good luck. A lot of things is happening in this space now.

WOW. I have been looking into this at work today, and windmill is def. what I was looking for, a low-code solution that do not hate code (as text). Thank you so much for creating this. The value prop. that you have in the intro[1] is perfect. The first paragraph on github is maybe correct. But I'm still not sold on what it actually does. Marketing is hard. Hope you will succeeded, the product looks great!

[1] https://docs.windmill.dev/docs/intro/

Does windmill have any way of going into code, without it basically becoming "code in a input box". The developer first solution trigger.dev have here is really scratching a real problem. But as they say they are not for the easiest workflows. I'm really looking for something that is gui first but as a drop down to code when you want. But inline code editor, let me save it to a git repo or similar. And don't have globals aka zapiers inputData and output.

I really in favor of being able to deploy on Friday's. I do think that they make a good point in mastering it.

But there is one important point I'm think they have learned but they do not explicit say in this blog post.

It's what you deploy. Context matters. Deploy most things as normal on Friday's.

But you do hold off the release that is bigger than normal and involves some new infra on the backend side or is known to more memory heavy etc.

But for bug fixes etc. Deploy. Works great here at least. And I am, or at least for most of my career, was the person that fix the problem.

You ship it you fix it. Then it's up to the person that has the PR. A judgment call

A great example on that context matters. Seems very reasonable to do.

I agree that I took it "a bit" far to make a point… that just ruined my case.

I do think that in a monolith you try to do most things yourself.

Take Auth for example. It's huge. And I think we more and more are excepting that even for a monolith we do not want to do that ourself.

If you start from scratch and your spec say that they want OIDC and SAML then most ppl will look for a saas service to get help.

Same with storing files, we would make use of S3 or similar.

But if we go to pre 2010. I think most people would try to both of these themself.

Im not saying that this is microservice at all, but I'm saying we are moving stuff that are commodity's out from the monolith compare to what we did 10-15 years ago. Because there are services that does a much better job for us.

And that was part of my point with the original comment. That trying to keep everything in one place is probably not the right choices.

Sorry for not being more precise on my previous reply.

For your core service. I think you are right most of the time.

But you are probably not talking about the website marketing wants to build.

And you are maybe using S3 or similar for documents storage?

And your logging system are probably not on the same machine?

But if by "system" you mean the main API + SaaS website or similar yeah. Sounds reasonable.

in reality we do so much more now. That I think some part of what was the monolith years ago is now just SaaS the company use. That the development department do not even need to know about.

I really do not understand the debate on monoliths and microservice anymore.

Context matters so much. Should you have absolutely everything in 1 system. No. And I think no one thinks that anymore.

Should you spilt your system into as many pieces as possible?

No, of course not.

You are prop. storing files one place and have a data in a database another place. And most likely none are on the webserver receiving request. Or maybe you are, because context matters and I'm wrong in your particular case. Could be.

My advice would be to split your application up into enough pices so that;

1.your engineers feels like they have control over the code and are not afraid of doing changes.

2. if you get uptime issues. Get the heavy / unrealiable services over to new node. Don't let one service/endpoint take down other endpoints.

Think and act according to the problems you have in front of you. Don't go extreme in any direction. Context context context

So much great postgres stuff comming out from supabase. I'm really impressed with how much focus and direction the team have. So many companies would try to broaden their product/feature suite, but fail at understanding what made the core sucsessful and stretch the company in many directions. It really seems like they are just making them self better and better experts at postgres. And how to use it well. Really looking forward to see where this is going.

On a sidenote, is not the wrappers for Airtable, BigQuery and ClickHouse opensourced? Or why did they skip that column in the second table?

Is all of supabase opensourced now? I'm meaning I heard something about function not being opensourced but I can be remembering wrong. Most stuff is on GitHub I see

Yes, been using devbox for a while now. It's great. This seems like a direct competitor or? Have anyone compared them?