Despite being down on all the extras, I wanna reiterate - I do think this is a cool project and I dig that HTAs are still around.
WelsonJS: Build a Windows app on the Windows built-in JavaScript engine
11–20 of 57 posts
Re: WelsonJS: Build a Windows app on the Windows built-in JavaScript engine
#12Quite amazing solution. From the .hta file you can see it was inspired by VBScript (whose most popular software is ILOVEYOU I guess). It looks like the ultimate hack, but why not ? It's very creative and the intention is good as well: TypeScript/JavaScript is a very popular language. Though C#.NET is great as well. It could make sense in the very long-term that Microsoft themselves explore this possibility. Ultimatel…
Look up WinJS sometime! It was a really neat idea that MS sadly abandoned.
Re: WelsonJS: Build a Windows app on the Windows built-in JavaScript engine
#13Quite amazing solution. From the .hta file you can see it was inspired by VBScript (whose most popular software is ILOVEYOU I guess). It looks like the ultimate hack, but why not ? It's very creative and the intention is good as well: TypeScript/JavaScript is a very popular language. Though C#.NET is great as well. It could make sense in the very long-term that Microsoft themselves explore this possibility. Ultimatel…
Look up WinJS sometime! It was a really neat idea that MS sadly abandoned.
+1 - that was a really cool idea that I really was hopeful would take off.
Re: WelsonJS: Build a Windows app on the Windows built-in JavaScript engine
#14Earlier quoted context omitted.
> using native JavaScript without all the BS that comes with TypeScript do you think javascript was just too easy and people had to invent some bs to make it more interesting for no reason? You don't even know what you're talking about when you make the connection from ts to oop. My experience comming into javascript is that it's a garbage language and the web stack was a joke, everything was hard for the wrong reaso…
I think, based on many battles, a lot of folks in the early days that came from Java/C++ absolutely struggled with the key concepts of JavaScript, couldn’t find “features” (like strong typing) they claimed were critical for writing good software and invented ways to make the language fit their paradigm, rather than really deep dive into the language and embrace it. There were constant battles back then - and I’m sure…
I hear you, but am also interested in some JS libraries or techniques that fall in the elegant category.
An elegant typed one would be Structurae [0].
I imagine/would love to see a bunch of elegant non-typed ones as well.
Re: WelsonJS: Build a Windows app on the Windows built-in JavaScript engine
#15Earlier quoted context omitted.
> using native JavaScript without all the BS that comes with TypeScript do you think javascript was just too easy and people had to invent some bs to make it more interesting for no reason? You don't even know what you're talking about when you make the connection from ts to oop. My experience comming into javascript is that it's a garbage language and the web stack was a joke, everything was hard for the wrong reaso…
I think, based on many battles, a lot of folks in the early days that came from Java/C++ absolutely struggled with the key concepts of JavaScript, couldn’t find “features” (like strong typing) they claimed were critical for writing good software and invented ways to make the language fit their paradigm, rather than really deep dive into the language and embrace it. There were constant battles back then - and I’m sure…
I love functional languages but I'm not sure how JavaScript could be considered as a functional language (at least if functional means something like haskell, or elm). Functions-as-values isn't enough, otherwise Python could be called a functional language.
Re: WelsonJS: Build a Windows app on the Windows built-in JavaScript engine
#16I saw a partial example, but not clear instructions on how to bootstrap a project. Did I miss it in the README? Or should it be obvious to me if I have some XYZ experience?
Re: WelsonJS: Build a Windows app on the Windows built-in JavaScript engine
#17Earlier quoted context omitted.
> using native JavaScript without all the BS that comes with TypeScript do you think javascript was just too easy and people had to invent some bs to make it more interesting for no reason? You don't even know what you're talking about when you make the connection from ts to oop. My experience comming into javascript is that it's a garbage language and the web stack was a joke, everything was hard for the wrong reaso…
I think, based on many battles, a lot of folks in the early days that came from Java/C++ absolutely struggled with the key concepts of JavaScript, couldn’t find “features” (like strong typing) they claimed were critical for writing good software and invented ways to make the language fit their paradigm, rather than really deep dive into the language and embrace it. There were constant battles back then - and I’m sure…
I've enjoyed vanilla JS since forever, and currently work in a TS shop, and FWIW I think you're waaaay off base. There may have been times and places where TS was heavily OO, but all the TS I come into contact with is heavily functional, class-averse, immutable by default, etc.
(In face, the Java/C++/OO-types I know strongly dislike TS because it's structurally typed. TS doesn't care a jot who extends what - as long as they have the same properties it's happy. Hard to get more un-java than that.)
The real reason that TS won is simply that large teams (e.g. hundreds) cannot effectively work together on untyped JS. If you're doing a solo project, fill your boots - use JSDoc comments, sprinkle asserts around, whatever. But the webdev world at large doesn't care about Java or OO concepts, it settled on TS because huge teams can work effectively with it.
Re: WelsonJS: Build a Windows app on the Windows built-in JavaScript engine
#18Earlier quoted context omitted.
I think, based on many battles, a lot of folks in the early days that came from Java/C++ absolutely struggled with the key concepts of JavaScript, couldn’t find “features” (like strong typing) they claimed were critical for writing good software and invented ways to make the language fit their paradigm, rather than really deep dive into the language and embrace it. There were constant battles back then - and I’m sure…
I love functional languages but I'm not sure how JavaScript could be considered as a functional language (at least if functional means something like haskell, or elm). Functions-as-values isn't enough, otherwise Python could be called a functional language.
Classic example of comments I've heard since the 90s.
I’d strongly encourage doing a deeper dive here. Functions in JS are objects and can have their own methods/props + scope. They’re a first class citizen.
Re: WelsonJS: Build a Windows app on the Windows built-in JavaScript engine
#19Earlier quoted context omitted.
I think, based on many battles, a lot of folks in the early days that came from Java/C++ absolutely struggled with the key concepts of JavaScript, couldn’t find “features” (like strong typing) they claimed were critical for writing good software and invented ways to make the language fit their paradigm, rather than really deep dive into the language and embrace it. There were constant battles back then - and I’m sure…
I've enjoyed vanilla JS since forever, and currently work in a TS shop, and FWIW I think you're waaaay off base. There may have been times and places where TS was heavily OO, but all the TS I come into contact with is heavily functional, class-averse, immutable by default, etc. (In face, the Java/C++/OO-types I know strongly dislike TS because it's structurally typed. TS doesn't care a jot who extends what - as long…
There it is… that’s the classic argument. Large teams/codebase. I totally get the appeal, but the idea this can’t be done effectively without it is nonsense. Long before TS, we had JS apps with teams of 50-100+ working across hundreds of not up to a couple thousand files - in CVS/SVN repos (ugh). I will concede that TS does help in the larger teams/codebases but - I will contend it is not necessary if your team is composed of folks that have depth of experience working without.
Re: WelsonJS: Build a Windows app on the Windows built-in JavaScript engine
#20Earlier quoted context omitted.
I think you are conflating ES6 classes with TypeScript.
Static/strong typing is not necessary in JS. Yes, ES6 brings the OOPiness
That’s just like your opinion, man.
Just because you think that doesn’t mean it’s true. The sheer fact that TS has overtaken JS for the majority of web development says enough.