Hi fellow software engineers. Sorry for the long post in advance.

I'm offered a project for a website and E-commerce store for a medium-sized business.

There are thousands of E-commerce websites out there but I don't find it very straight forward to create one. I have mainly worked on enterprise software and don't have experience in E-commerce.

The website is going to be built with some SSG (probably Zola) az I really beleive in SSGs for websites. So we have that out of the way.

But for the E-commerce part, I'm confused.

Here are my requirements:

• least development cost (time and money)
• least maintenance cost
• robust (don't need constant babysitting. Can work for years)
• Simple both for developers and for admins
• Better if we can find people to maintain it easily

Things that I'm good with:

• JS/TS
• Clojure
• Python
• HTMX
• Vue / Nuxt
• HTML/CSS

options that I'm considering:

• Woocommerce

The layman's choice. I find wordpress horrible for websites but I think (not sure) that woocommerce has the least hassel and cost for an E-commerce website.

• Django

Tried and tested. It has more cost of development but I think tge cost of maintenance is less. Creating with it's own MVVM architecture, it's basically server side rendering.

Also, python and django are very popular and it's very easy to find other people to work on the project.

• Clojure + pedestal

It's similar to Django but for Clojure. Straight forward, scalable. I like Clojure MUCH more than python and am much more productive with it. The performance of this stack is also MUCH better than python and django and the technologies are more stable and need less maintenance.

The downside is, I probably cannot find anyone that knows Clojure.

• Clojure + kit-clj + HTMX

This is a more "custom" approach, unlike frameworks like django, laravel, pedestal who take care of lots of things for you and do a lot of magic behind the scenes, we will be rolling everything ourselves here.

Render html server side with selmer and hiccup, and use HTMX for client side interactivity. Obeying HATEOAS and REST architectures.

I think this will be the most robust way but development cost will be higher and again, I will not find anybody else to work on it.

• Server Client architecture

Server works with the database and handles business logic (Clojure/python/TS/JS) . can use graphQL to cut much cost and time from server side development, Client probably uses Nuxt.

Classic architecture, all young and old people are familiar with it, server and logic is decoupled from client.

Downside is the complexity of the front end stack rises. Horrible DX, horrible debugging, and costly.

• Medusa.js

Never used it, it is a full e-commerce framework, seems cool to be honest.

What do you guys suggest I should do? What's your experience? If there are better options that I'm missing out on, please tell.

Explaining why we need "apocalypse-proof software" and some actual software tools for the mentioned situation.

cross-posted from: https://lemmy.world/post/41155034

cross-posted from: https://lemmy.bestiver.se/post/841355

Comments

Good (but scary) overview of state of AI in the og article, some points:

• The transformation of work by AI is already underway, not a distant future event. The NBER model quantifies this as a potential 366% productivity boost coupled with a 23% employment reduction, with half the job displacement happening within five years. This underscores the urgency of being intentional about how AI reshapes work environments.

• The future of AI in the workplace favors augmentation over replacement. Most workers prefer AI to automate repetitive tasks and to act as partners or coaches rather than substitutes. Enterprise AI strategies should therefore focus on complementing human skills, freeing teams to concentrate on creative and interpersonal value-driving activities.

• AI adoption and impact are highly role-specific. While some jobs like logistics management face high automation risks, others like hands-on mechanics remain largely unaffected. Similarly, AI is democratizing expertise by leveling the playing field for freelancers, which challenges traditional premium skill valuations. Effective AI strategies require granular, nuanced understanding of these variations to maximize benefits and mitigate harms.

cross-posted from: https://lemmy.ml/post/32333121

This article isn’t about convincing you to choose Scheme over other languages. Instead, if you’ve already recognized the growing trend of functional programming and are curious about powerful, well-established functional languages, this piece will illuminate Scheme’s often-overlooked strengths in a production setting.

Find the full article here:

https://jointhefreeworld.org/blog/articles/lisps/scheme-and-lisps-are-great-for-production/index.html