<@U0195MWDYES> I just found your project, and uh.....
# fun-adaptive
j
@Tóth István Zoltán I just found your project, and uh... we're doing almost exactly the same thing! I doubt with how far we both are along a merge could be in order, but at a minimum I'd like to trade notes. https://github.com/lightningkite/lightning-server https://kiteui.cs.lightningkite.com/ https://github.com/lightningkite/kiteui
t
Most interesting. I've checked your projects shortly, at first glance there are some conceptual differences. As I see, you are following a more conservative, enterprise-like approach, building on existing foundations while I mostly try to build from scratch to have full control and complete freedom. In result you can reach stable, production ready state much easier while I might face hard to crack or even unsurmountable challenges. You try to build on standard Kotlin + KSP with annotations while I put much logic into a compiler plugin. Both have cons and pros. The compiler plugin lets me create very clean, fully reactive code, while it is harder to maintain and even harder to support full Kotlin syntax. It might not be trivial at first glance, but I use this plugin for many other things besides the UI. For example, I have full metadata with constraints for data classes available at runtime, RPC implementation generated etc. You put much emphasis on small code size which is very reasonable. I do not optimise for this at the moment because I plan to use no-code for application level data classes and UI fragments. I will treat these as standard resources (just like images or such). I started from the concept that the client and the server side is one application. This has many consequences, For example, my server side is actually reactive (I do not use this at all at the moment), using the very same foundation as the UI. I can add adapters for PDF for example and then I can just use my standard UI fragments to write PDF output. Or I can build my server with the same graphical fragment designer I use to build my UI. I'm all up for a video call to share experiences and ideas (let's say middle next week if that's good for you). I see some points in your projects I would like to know a bit more about.
j
Yeah, after reviewing your stuff further it looks like I got a bit too excited by some surface reading of your repos - we definitely have some differing objectives, though we also share a surprising amount. We definitely have a lot we could share though, so I think we should have that chat! Looks like we're nearly on other sides of the world, but I think we can make it work. Middle of next week would work for me - it's the time that's gonna be tricky. Perhaps we should go for 8 AM my time? That would be 4PM your time.
t
4 PM (CET) is fine for me, may be even later if you are not a morning person. I typically work from 4 AM, anything in the afternoon is after my "official" work hours, so it doesn't really matter when exactly.
j
Let's stick with 4PM CET then. Wednesday the 26th?
👍 1