91–100 of 241 posts
Earlier quoted context omitted.
Yep. IE went so far as to add support for VBScript (a language based on visual basic) to compete.
I now wish there'd be actual Python on the web.
The same applies with other languages too (e.g. Perl, Ruby, etc).
Earlier quoted context omitted.
Well, if by 'for years', you mean 25 years, you're right. ECMAScript is still hot garbage that clogs up computers and the internet, ballooning requirements on browsers and nearly forcing the monoculture we have in terms of browsers and rendering. If you want a website, you should write a website. If you want a program, you should write a program. Don't write programs to run in the same space as websites.
> Don't write programs to run in the same space as websites. Who do you imagine is going to find this advice compelling?
Earlier quoted context omitted.
Complex javascript apps just weren't a thing...hell, it took google writing Gmail (2004) to really show everyone that a large SPA using javascript was even possible. After Gmail...things really started to move in the javascript world...people started to put effort into both the runtimes and the libraries.
They really weren't a thing, but they also weren't unheard of. Personally speaking, I started working on a complex JavaScript application (web-based ERP/CRM system) in 2000. While it wasn't an SPA, we designed our pages so you didn't have to leave them to do what you needed to do. For example, a user might stay on one page for a few hours because they're speccing out a project. Updates were often committed live using…
This obviously lends the question, given it's criticism back in the day, which PL is the next javascript?
Go, maybe? Or is it not flawed enough and not criticized enough? Or is it already used too heavily?
The release of JavaScript was deeply confusing to me as a developer back then. Java applets and Macromedia Flash were already touted by their vendors as the one true way forward for interactivity. The scripting language released at about the same time seemed like an oddball. It's easy to forget, but for years after its introduction JavaScript didn't work well. It was extremely slow, limiting the complexity of what co…
Complex javascript apps just weren't a thing...hell, it took google writing Gmail (2004) to really show everyone that a large SPA using javascript was even possible. After Gmail...things really started to move in the javascript world...people started to put effort into both the runtimes and the libraries.
https://en.wikipedia.org/wiki/Oddpost
It also felt more like an app than gmail ever has given it had the "standard" 3 panel look of most desktop email apps (same as most of them do today like Thunderbird/Outlook/Apple's Mail)
And before that Outlook had a browser version that acted like a SPA since 1997.
https://en.wikipedia.org/wiki/Outlook_on_the_web
In fact I'm pretty sure that's why Microsoft introduced XMLHttpRequest
Earlier quoted context omitted.
Complex javascript apps just weren't a thing...hell, it took google writing Gmail (2004) to really show everyone that a large SPA using javascript was even possible. After Gmail...things really started to move in the javascript world...people started to put effort into both the runtimes and the libraries.
They really weren't a thing, but they also weren't unheard of. Personally speaking, I started working on a complex JavaScript application (web-based ERP/CRM system) in 2000. While it wasn't an SPA, we designed our pages so you didn't have to leave them to do what you needed to do. For example, a user might stay on one page for a few hours because they're speccing out a project. Updates were often committed live using…
Earlier quoted context omitted.
Complex javascript apps just weren't a thing...hell, it took google writing Gmail (2004) to really show everyone that a large SPA using javascript was even possible. After Gmail...things really started to move in the javascript world...people started to put effort into both the runtimes and the libraries.
They really weren't a thing, but they also weren't unheard of. Personally speaking, I started working on a complex JavaScript application (web-based ERP/CRM system) in 2000. While it wasn't an SPA, we designed our pages so you didn't have to leave them to do what you needed to do. For example, a user might stay on one page for a few hours because they're speccing out a project. Updates were often committed live using…
That was a fun, well-paid project with lots of (non-exempt) overtime. Then the .com bubble popped.
The release of JavaScript was deeply confusing to me as a developer back then. Java applets and Macromedia Flash were already touted by their vendors as the one true way forward for interactivity. The scripting language released at about the same time seemed like an oddball. It's easy to forget, but for years after its introduction JavaScript didn't work well. It was extremely slow, limiting the complexity of what co…
I wonder how history would have looked like if Scheme had been used instead, as was the original intention.
Or perhaps, Lua.
The release of JavaScript was deeply confusing to me as a developer back then. Java applets and Macromedia Flash were already touted by their vendors as the one true way forward for interactivity. The scripting language released at about the same time seemed like an oddball. It's easy to forget, but for years after its introduction JavaScript didn't work well. It was extremely slow, limiting the complexity of what co…
Well, if by 'for years', you mean 25 years, you're right. ECMAScript is still hot garbage that clogs up computers and the internet, ballooning requirements on browsers and nearly forcing the monoculture we have in terms of browsers and rendering. If you want a website, you should write a website. If you want a program, you should write a program. Don't write programs to run in the same space as websites.
Earlier quoted context omitted.
Complex javascript apps just weren't a thing...hell, it took google writing Gmail (2004) to really show everyone that a large SPA using javascript was even possible. After Gmail...things really started to move in the javascript world...people started to put effort into both the runtimes and the libraries.
Please don't repeat this non-fact. There were plenty of large SPAs before GMail. Oddpost existed 2 years before Gmail https://en.wikipedia.org/wiki/Oddpost It also felt more like an app than gmail ever has given it had the "standard" 3 panel look of most desktop email apps (same as most of them do today like Thunderbird/Outlook/Apple's Mail) And before that Outlook had a browser version that acted like a SPA since 19…