Hello everyone. I want to tell you about the new, simple but very powerful, web development approach - JSDA Stack.

First, a couple of words about the concept. JSDA (JavaScript Distributed Assets) - is a architecture principle and the set of simple conventions. It brings PHP-like mental model into the JS world.

Do you remember why PHP become popular? It gave us possibility to put logics inside the HTML document. And it was very simple to use and to understand.

So, in JSDA we do almost the same - treating standard JS-modules (ESM) as a web-asset generation endpoints (text based). So, it's just like PHP but with all the power of modern JavaScript (Template Literals, top level await for async requests, flexible module composition, code CDN support for external modules, etc.).

Just make default module export string (export default /*html*/ '<div>Hello ${name}!</div>'), and name the file to map it to corresponding type - my-page.html.js. And JSDA Server will send to the browser resulting html with the text/html MIME type.

Obviously, you can do the same with CSS, SVG, JSON, MD and any other text-based asset. And that give us almost endless possibilities. Just imagine CSS with a full power of real programming language without any additional dependency such as pre- or post-processors and their own syntax.

Everything above is not just some odd idea — it works, and it works really well. To prove it, I've prepared a dedicated template repository that lets you spin up a full-featured JSDA project in seconds.

It's a project with a minimal dependency footprint and minimal configuration (easy to security-audit), yet it includes everything you need to be a legitimate competitor to things like, say, the popular Next.js.

https://github.com/rnd-pro/jsda-template

Somehow, I ended up creating my own micro-stack for web development. I've been in this industry for a very long time - I built my first paid website back in the late 90s. Since then, I've actively followed all the trends and technologies. I’ve worked with practically every popular framework and library out there (I mean JS ecosystem mostly, but not only). But in almost every single one of them, something just didn't sit right with me.

I think many of you will understand what I'm talking about. I'm not being original here. I don't like it when simple tasks require complex solutions, or when tools designed to eliminate our problems start creating new ones. There have been plenty of posts written about this. Often, instead of simply using a framework, we find ourselves fighting against it. Many experienced developers feel this. I was always curious if I could build something of my own, but better.

However, arguing that one technology is better than another requires criteria. And those criteria are different for everyone. For some, freedom and flexibility are paramount. For others, it's about minimizing the chance of shooting yourself in the foot. These are opposing concepts. By gaining freedom, you get a revolver pointed at your knee. By gaining safety and strict boundaries, you narrow the range of possible elegant solutions. It's a balancing act where everyone weighs things differently. It all comes down to engineering culture, and it's rarely black and white.

I spent years weighing the pros and cons, and eventually, I arrived at my own vision. I know my motivations resonate with many. It’s just that the solutions we ultimately arrive at can differ drastically.

In my case, it all started when I once again decided to build a personal website. Choosing a tech stack isn't just a reflection of personal preference; many factors are important, from what your available hosting supports, to how much you're willing to limit your future capabilities in some hypothetical, undefined future. And ideally, this task shouldn't drain all your energy, because there's always more important work to be done.

Ultimately, I arrived at my own framework that meets my requirements: minimal dependencies and restrictions with maximum capabilities. It includes both client and server sides, supports SSR, static site generation (SSG), and various hybrid approaches. It’s entirely built on web standards and native web platform capabilities, without trying to reinvent the wheel or replace fundamental concepts. All of this has already been thoroughly battle-tested in production on several non-trivial projects.

And this brings me to my main question: What next? I suddenly realized that it’s incredibly difficult to talk about these things nowadays. The information space is flooded with AI-slop, and the audience's attention is nearly 100% consumed by AI hype. On some platforms, your articles instantly drown in a sea of AI-generated content and jokes about it. How do you share your knowledge and genuinely working solutions? Nobody discusses substance anymore; everyone is fixated on the form. Nobody reads past the first few lines. I perfectly understand why this is happening. But does this mean it’s the end for any new idea?

I'm intentionally not posting any links here so no one accuses me of self-promotion, advertising, or anything like that. I just want to hear from people who have faced something similar. I also fully realize that not everything out there is worth attention. I've seen plenty of attempts by beginners trying to prove something to themselves or others without offering any real value to the world. But I would really love to have a space where such questions can be discussed without inherent negativity toward the authors and with solid technical argumentation. Even the discussion itself is useful; you can glean a lot of interesting ideas from it, even if you never intend to use someone else's work directly.

https://preview.redd.it/kjjotrleryxg1.png?width=2800&format=png&auto=webp&s=d65de35fae76d6c0163d82726c22ee98a52e223a

Learn how to build a 360-degree interactive product widget using Cloud Images Toolkit (CIT) and Immersive Media Spots (IMS) Web Components. 

https://rnd-pro.hashnode.dev/how-to-build-an-interactive-360-product-viewer

Learn how to build a 360-degree interactive product viewer using free and open-source tools: Cloud Images Toolkit (CIT) and Immersive Media Spots (IMS).

Hey everyone! I recently saw a post here from someone looking for web studios to implement projects. I’d like to make a related offer, but from a different angle.

We are a small team of experienced R&D engineers looking for a partner to help us acquire clients.

We manage our own workflows and excel at operating in highly ambiguous environments to solve complex problems. This is a rare combination of skills on the market, so I want to emphasize it right away.

What we do:

• End-to-End R&D: Analytics, hypothesis testing, competitive analysis, architecture, design, development, and operational maintenance.
• New Products: Building MVPs and startups from scratch.
• Existing Products: Architecture audits, legacy modernization, optimization, refactoring, and scaling.
• Beyond the Standard: We don't just use modern tools; we build them. We solve problems that AI cannot handle, while effectively using AI to automate the routine stuff.

We work exclusively with senior tech specialists for whom engineering is a passion, not just a paycheck. We know exactly how to manage the inevitable chaos of R&D-heavy projects.

While our core team is based in Argentina, we are fully distributed across multiple time zones (including Eastern Europe) and can scale our processes to assemble highly professional, motivated teams for specific projects.

How we work

Our model is simple and transparent:

• We allocate one or more engineers to a project at a single fixed monthly rate.
• Work is divided into monthly iterations.
• At the end of each iteration, we review progress, make strategic decisions, and adjust processes.
• The project can be paused, resumed, or pivoted at any time.

The client bears no additional liability for our team. This makes it easy to forecast costs for companies that need R&D capabilities but aren't ready to build an in-house department.

We are flexible and open to various arrangements, supporting traditional payments as well as cryptocurrency (fully legal in Argentina) and blockchain-based smart contracts to manage agreements.

Who are we looking for?

We are looking for a Lead Generator / Business Developer - someone who can find clients and negotiate the initial steps of collaboration.

You can also choose to take on some operational load (our side focuses purely on engineering). In return, you essentially build a stream of passive income: you receive a percentage of the fixed rate for every developer involved, for every month the client pays.

We handle almost everything else. We have a baseline commission structure ready, but we are fully open to discussing your proposals.

If there is mutual interest, we’ll happily share more details.

If this sounds like a fit, please send me a DM. Briefly introduce yourself and let me know how you see us collaborating!

Welcome to r/web_engineering! 🚀

Hey everyone! I'm u/sheveli_lapkami, a founding moderator of r/web_engineering.

This community was created specifically for experienced web engineers. We welcome deep dives into complex technical topics, architectural concepts, and innovative ideas.

This is a space for those who are tired of their voices drowning in a sea of AI-generated content, and who want a sanctuary for genuine, high-level engineering discussions.

🛠 What to Post & Open Source Rules

You are ENCOURAGED to share links to your Open Source projects on GitHub here! However, we have some IMPORTANT rules designed to combat AI-slop, spam, and low-quality content.

To share a project, it must meet ONE OR MORE of the following criteria:

• It contains git commits that are at least 2 years old.
• The main contributor has a GitHub profile older than 5 years with an active contribution history.
• The project has a clear, comprehensive README.md and a stated open-source license.
• The project already has over 100 stars on GitHub.

🚫 What is Highly Discouraged

To maintain the quality of our discussions, please avoid:

• Baseless Criticism: Do not criticize someone else's work WITHOUT providing sound technical arguments.
• Personal Attacks: No ad hominem attacks. Keep it professional.
• AI-Generated Content: Publishing raw AI-generated text is not allowed (using AI for translation is fine).
• Beginner Questions: Please avoid asking basic questions that can be easily Googled or resolved by asking an LLM.

👋 How to Get Started

In the comments below, please introduce yourself! Tell us about your experience, your current tech stack, and share any ideas you have for growing and improving this community.

Thanks for being part of the very first wave. Let's build a space where high-level engineering thrives!