News for hackers. Stuff that matters.
Re:CommonJS Is Hurting JavaScript by yafbum on Friday June 30, 2023 @01:05PM (#36538498)
> I really think that the needs of server side code are different enough than the needs of client side code that we’re better off drawing from Python and Ruby than from Dojo and jQuery.

This sentence sounds ok until Python and Ruby are held as the apparent gold standard of server development. That's not really the case, I think?

Re:CommonJS Is Hurting JavaScript by AmpsterMan on Friday June 30, 2023 @01:29PM (#36538890)
I think the historical context is necessary. At the time, Rails was a thing and python was taking server space from Java, PHP, etc. They weren't looking to those languages as standards, but rather as languages that were likely to have similar problems.
Re:CommonJS Is Hurting JavaScript by bdcravens on Friday June 30, 2023 @01:13PM (#36538618)
Thinking back to when CommonJS was implemented, absolutely. I don't think you'd want to call Spring or ASP the gold standards.
Re:CommonJS Is Hurting JavaScript by meepmorp on Friday June 30, 2023 @01:44PM (#36539152)
You know, now that I think about it, ASP might actually be the first example of a server side JS programming environment, kinda sorta. Nobody really did it, but you could use JScript instead of VBScript.
Re:CommonJS Is Hurting JavaScript by tracker1 on Friday June 30, 2023 @02:11PM (#36539582)
There was the Netscape JS stuff, but I don't think it was nearly as popular as Classic ASP by 2000. I wrote a lot of ASP in JScript, was able to reuse validation libraries, etc for common inputs/forms which was nice at the time. I think the difficult points, were COM iterators were kind of alien feeling in JScript, and developing COM controls at the time were awkward and a real pain to debug/diagnose even in VS at the time.

Not to mention, very little in the space of Classic ASP was open-source, free or even anything not insanely expensive from what I recall at the time. What was in the box was pretty much just JS and VBS, and most of what you could piece together was sluggish as all hell. Cool, you can use the spell checker from MS-Word... damn, three users tried to use it at the same time on the server. etc.

I have some fond and nightmare memories from those days. I think in terms of before jQuery (though scriptaculous, prototype and others were cool), after jQuery and after Browserify and 6to5/Babel. The ESM transition is much, much slower going.

Re:CommonJS Is Hurting JavaScript by freedomben on Friday June 30, 2023 @01:13PM (#36538628)
Remember this was 10+ years ago. Many of the contemporary gold standards weren't fully a thing yet.
Re:CommonJS Is Hurting JavaScript by groggo on Friday June 30, 2023 @01:40PM (#36539072)
what are the contemporary gold standards?
Re:CommonJS Is Hurting JavaScript by ilyt on Friday June 30, 2023 @01:11PM (#36538594)
Compared to JS it's hard to throw a rock and not hit something better than it...

But I can confirm deploying Python or Ruby apps is generally bigger PITA.