Karax steps forward

Nexus can be isomorphic, everything can be written in Nim if you use Karax. However if you choose to use Nimja (only or with Karax) then you are probably going to introduce some HTML and JS. So it's up to you, but I'm planning to take the framework in the direction of "the developer decides", wh

Karax steps forward

@jasonfi With , do you have "isomorphic" in mind? (One language. One model. One set of tests. The same business logic and domain Models are running on the clients and the server. See: )

Karax steps forward

Karax is awesome , but what we really need is documentation not just examples. I have been on my spare time creating javascript apps and converting them to karax ones. Karax could be a replacement for html, javascript but it lacks docs. I would be willing to "donate" to a karax cause especially

Karax steps forward

> "core" support to build read: a _much-simplified_ , productive way to build... (as in the latter example).

Karax steps forward

Svelte is a great framework. I'm working on a Nim frontend framework combining mutable tracking based on es6 Proxy with direct dom generation. I'm also experimenting some hacks to make components easier. For example support the implicit children function. proc buildText*(name: Reac

Karax steps forward

> what i think i want, is sapper/sveltekit (SSR) but in all nim, where the > backend, routing etc is in nim compiled to c, and the bare minimum required > for the front end features, is nim compiled to js. Exactly. Are there actually any "full stack" single-language and single-codebase solutio

Karax steps forward

I haven't used a lot of js (just sprinkled here and there) and i've never used a full fledged js framework in production, but from my somewhat exhaustive (albeit high level) investigations over the years, what i _think_ i want, is sapper/sveltekit (SSR) but in all nim, where the backend, routing

Karax steps forward

Not sure how Karax does it, in React components also used for the performance optimisation. When React calculates the DIFF, it uses components to quickly find changed components (using fast == reference/address comparison for component models, that's the reason why React models have to be immuta

Karax steps forward

I dont think so , "component" is good for reuse code, I can write statefull component in karax but the problem is use of this component is depends on my own implementation, also when coming in nested components I have to mark all nested component dirty , I think I only need karax if I decide wri

Karax steps forward

> I started with React and was able to apply a lot of its concepts in Karax Likewise, I moved from `React -> Vue.js -> Karax` and a lot of the approach carries over. And I prefer Karax to the others.

Karax steps forward

@bung components can be easily emulated and I have done so for the implementation of this forum. We can certainly add some syntax sugar if really wanted, but then this should be implemented in a library that users can use together with Karax. If you're really after having components then impleme

Karax steps forward

Yes, if you think in "components" you're already using the wrong mental model and Karax won't help you. And yeah, maybe Svelte can be an inspiration as a virtual DOM is fundamentally at odds with the _stateful_ DOM.

Karax steps forward

I've tried use karax build a movie site / after demo stage I give up, online preview here :/ , compare to react and vue, it lack of component implementation , the experimental component not like others framework nowadays.

Karax steps forward

People have already used server side [karax with tmx](https://forum.nim-lang.org/t/4051#48026). Whats your opinion about it, how it compares with Svelte?

Karax steps forward

I usually just do a folder for a component if it gets to big, but I posted those links because the Svelte version uses the exact same structure: and thus it's a bit more of apples-to-apples example. I personally wouldn't d

Karax steps forward

My good, do you really think [this is good](https://github.com/vuesomedev/todomvc-react/tree/master/src/components)? Not even just a file, but the whole folder, for every single UI element? (by the way, I saw once a React project where every component had its own NPM module). And the event flow

Karax steps forward

There is also a tool called [html2karax](https://github.com/nim-lang-cn/html2karax) that converts static html to Karax.

Karax steps forward

Not only is the code last updated in 2018, that code is so unreadable that I think the person who wrote that would even overengineer a Svelte solution like that. It even still uses `React.createClass` in places, haha. Contrast that with the Svelte code written by the maker himself, of course tha

Karax steps forward

> As far as Svelte being simpler and more productive than React, I'd say that > depends on person and what they like. But what Svelte does really right is > that interactive guide which is amazing. We can measure it, there's [TodoMVC](https://todomvc.com/) an UI showcase app, implemented in all

Karax steps forward

I've recently heard about Knete through : which is an experiment of using Nim without using a VDOM: In non-Nim world: which is also Sv

Karax steps forward

Existing experiment by @mildred of using svelte’s ideas in Nim:

Karax steps forward

I would like to mention Svelte specifically. It's a different approach than React/Karax. But it's well worth to watch [talk of Rich Harris](https://www.youtube.com/watch?v=AdNJ3fydeao) creator of Svelte why it created it and how it works. And maybe go through [Svelte Tutorial](https://svelte.d

Karax steps forward

I would be really interested to see your new approach. Even a small sample would be great.

Karax steps forward

This is not a debate. I think they are completely different projects and both are awesome.

Karax steps forward

@ajusa Great work, this will certainly help attract more users and get them up and running with Karax. @moigagoo I'd be interested in hearing more about your new approach to state management. I found your [blog post](https://moigagoo.svbtle.com/exploring-karax) very informative and nicely writ

Karax steps forward

Already seen?

Karax steps forward

I've used jQuery Dom builder before and also used React, Svelte and Typescript recently. For me, Karax is more similar to jQuery Dom than it is to more "modern" techniques as jsx / tsx. I also miss a node integration. I couldn't find examples for this. Even if this might not be necessary as nim

Karax steps forward

Oh this is so good! Karax could use some love like having its one landing page with tutorials and stuff. I’ve recently discovered a simpler state management model than the one I’ve described in the old Exploring Karax article, looking forward to write about it too. Alas, the time is always shor

Karax steps forward

Hello everyone, As many of you probably already know, [Karax](https://github.com/karaxnim/karax) is a core Nim web framework. It can be used as a DSL to generate HTML (good for templating on the backend) and to create Single Page Applications in Nim. Karax was mostly written back in 2017, and