BIG ISSUE - Defaulting to Javascript

[davidjeba]

z.ai is so powerful using im building a massive programming language itself for the future web.
gomazing/goscript
But when im trying to create a demo capability website for goscript using goscript itself
z.ai is forcing/defaulting itself to use Javascript frameworks.

Can you help me to build this goscript language further restricting javascript altogether?

[Gaurang98]

I think this is happening because almost every coding AI today has been trained mostly on JavaScript-based web projects.

So the moment it sees words like:

• frontend
• website
• UI
• web app

it automatically assumes:

• React
• Next.js
• TypeScript
• npm ecosystem

Even if you clearly want to build everything using Goscript itself.

So honestly, I don’t think the real problem is GLM-5 specifically — it’s the overall training bias of modern coding models.

A few things that might help a lot while building Goscript further:

1. Give Goscript its own strong identity

Instead of presenting it as a “JavaScript alternative”, try defining it as:

• its own runtime
• its own rendering system
• its own UI framework
• its own package ecosystem

The more independent it feels, the less the model tries to fallback to JS frameworks.

---

2. Add very strict generation rules

Something like this helps a lot:

NEVER use:
- JavaScript
- React
- Vue
- TypeScript
- JSX
- npm packages

ONLY use:
- Goscript syntax
- Goscript-native APIs
- Goscript renderer/runtime

---

3. Create More Goscript Examples

Right now the internet is flooded with JavaScript examples, but the model probably has very few Goscript references to learn from.

If you create examples for:

• routing
• state management
• components
• animations
• websockets
• SSR

then the AI starts understanding the “Goscript way” of building applications instead of defaulting to React patterns.

---

4. Maybe Target WASM Long-Term

Instead of:

Goscript → JavaScript → Browser

a future direction could be:

Goscript → WASM → Browser

That would make Goscript feel much more independent from the JavaScript ecosystem and help establish it as its own web platform.

---

5. Even Repo Structure Matters

LLMs also learn from:

• filenames
• folder structure
• architecture
• naming conventions
• documentation

So even small things can influence generation behavior.

For example, instead of:

src/components/App.jsx

using something like:

src/ui/app.gs
src/runtime/dom.gs
src/core/reactivity.gs

can help the model think in a Goscript-native way instead of automatically assuming a React/JavaScript ecosystem.

[davidjeba]

@Gaurang98 Thanks a lot, you helped me to rethink gomazing/goscript in a proper way (as it should be)