Web Applications with Pascal

[zamronypj]

it is true that pas2js can target node.js to create server side web application, but what is the point if FPC can create it directly? If you need to write server-side application in JS, you will mostly write that in JS.

If you look at pas2js demo, most of it are applications that runs on browser. that is pas2js is for

https://gitlab.com/freepascal.org/fpc/pas2js/-/tree/main/demo?ref_type=heads

[Leledumbo]

it is true that pas2js can target node.js to create server side web application, but what is the point if FPC can create it directly? If you need to write server-side application in JS, you will mostly write that in JS.

The point of Pas2JS is NOT to write JS at all. Pas2JS can be considered as a separate Pascal dialect just like $mode directive, so when you work with Pas2JS for both backend and frontend you're working with a single dialect, which could be an attraction point for those who don't want to think in different POV everytime they switch side. At the very least, consider it an option for those who need it. I do prefer ObjFPC on the backend and Pas2JS on the frontend, but my preference doesn't have to be other people's.

[Thaddy]

it is true that pas2js can target node.js to create server side web application, but what is the point if FPC can create it directly? If

Yes, that s true.
You can target it with pas2js cde only, no need to write JS, if necessary you can even write the js in an inline assembler block.
The earliest demo's that came available have examples for node.js. I use it both for KIOSK mode applications that can run locally or remote and plain GUI-less server modules.
[/quote]
The point is, you don't need js, you can write everything in object pascal. Serverside and clientside.

[zamronypj]

on server side ObjectPascal -> Pas2Js -> JS is optional

on client-side (browser) ObjectPascal -> Pas2JS -> JS is neccesity

[oliverhbailey]

I just read this thread and go back to the days before Turbo Pascal.  I would like to point out some important historical facts.  The author of Turbo Pascal was eventually recruited by Microsoft.  He is the Architect of C# and .NET framework.  As a forner user of UCSD Pascal, Turbo Pascal was one of the major contributions to the success of the IBM PC and commercial software development in general.  It combined a strongly typed language with a super fast assembler and small footpeint executable before there was any native code generator for C++.  Borland grew from this single product quickly and growth was fueled by new internal development and acquisitions.  But at that time, Turbo Pascal was the fastest wat to develop IBM PC prigrams.  I was one of the Alpha testers and developers using Turbo Pascal, Object Pascal, and Delphi. 

[VisualLab]

I just read this thread and go back to the days before Turbo Pascal.  I would like to point out some important historical facts.  The author of Turbo Pascal was eventually recruited by Microsoft.  He is the Architect of C# and .NET framework.  As a forner user of UCSD Pascal, Turbo Pascal was one of the major contributions to the success of the IBM PC and commercial software development in general.  It combined a strongly typed language with a super fast assembler and small footpeint executable before there was any native code generator for C++.  Borland grew from this single product quickly and growth was fueled by new internal development and acquisitions.  But at that time, Turbo Pascal was the fastest wat to develop IBM PC prigrams.  I was one of the Alpha testers and developers using Turbo Pascal, Object Pascal, and Delphi.

There were more programmers who went from Borland to MS.

As for C#, in my opinion it was "chopped" C++ and Object Pascal served in a "Java brewing cup" (and .NET was for a long time a kind of black pudding created from WinAPI, VCL and loose ideas, which MS gradually improved). It has been better for some time. But it still needs a "chassis on wheels" (VM).