Okay, TIL: noj! https://scicloj.github.io/noj/

They appear to be doing this very thing, but for the data + science 
ecosystem!

I wonder if the web ecosystem can steal their playbook.

On Thursday, October 31, 2024 at 11:47:09 PM UTC+5:30 aditya....@gmail.com 
wrote:

> X-linking to some chatter over at r/Clojure, where I X-posted this email.
>
>
> https://www.reddit.com/r/Clojure/comments/1gfjkiy/a_web_stack_special_interest_group/
>  
> On Thursday, October 24, 2024 at 6:50:40 PM UTC+5:30 Fabio Dias Francisco 
> wrote:
>
>> I know what you mean, in terms of web framework, idk, but I had to go 
>> just that route and build myself my own data processing framework. There 
>> was nothing for that purpose that was truly native, so I used my knowledge 
>> of many frameworks like that, and built my own.
>>
>> On Thursday, October 24, 2024 at 9:47:03 AM UTC+1 aditya....@gmail.com 
>> wrote:
>>
>>> Hello, thoughts about the Clojurish web stack have been bouncing around 
>>> in my head for a while now. In recent months, I've noticed an uptick in 
>>> conversations about the same. Maybe it's recency bias. Maybe not. The 
>>> "boring business web app" is where the money is, after all.
>>>
>>> I wonder if people would like to put heads together to come up with 
>>> *something* general-purpose that helps people understand + construct + 
>>> apply web things built by community members over the years.
>>>
>>> Personally, I'm not convinced that a One True Framework is the solution. 
>>> However there might be opportunity to out-framework all the framework-heavy 
>>> communities by making a way to construct one's own framework.
>>>
>>> The "constructor" might spit out a "standard recipe" that could be: 
>>> "Ring + Compojure" or "Ring + Reitit" or "Kit" or "Duct" or "Sitefox" or 
>>> "Donut" or "Pedestal" if the user feeds in well-specified requirements that 
>>> match one or more of said framework/library collection. Or, it might run us 
>>> through a decision tree to incrementally expand requirements into a project 
>>> on disk (a clj-new template, but created incrementally).
>>>
>>> AND, as m'colleague Kapil insists (and I agree) it should be a "full 
>>> system" system... have us covered from parts assembly to production 
>>> deployments.
>>>
>>> /Explanations/ would be a key feature of such a constructor; Why this 
>>> and not that? How to wire X and Y together? What are some example use 
>>> cases? The explanations would be sourced from source repos.
>>>
>>> Basically, this thing would respect and support the diversity and 
>>> inventiveness of the Clojure web ecosystem /while making it accessible/ to 
>>> the masses. The innovation is distributed, but the composition is 
>>> centralised. This sort of thing is definitely in userspace and not language 
>>> maintainerspace. IMHO, SciCloj is a great example of a special interest 
>>> group that's doing yeoman service.
>>>
>>> I'm not sure if I'm making any sense, but I'm sure smarter people that I 
>>> have struggled enough to have had ideas of their own and if they come 
>>> together, they might conjure up a very creative solution. What I *am* 
>>> confident about, is that this is a *complicated* task, but not a 
>>> complex one.
>>>
>>> Anyway, I just wanted to put this out into the clojureverse and see what 
>>> happens.
>>>
>>> May The Source be with us,
>>> - Adi
>>>
>>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/clojure/e0ef4a5d-fa26-4646-afc2-e16fe1dbd5adn%40googlegroups.com.

Reply via email to