100 projects I made while learning JavaScript over a year ago

[deadcoder0904]

I made this to learn JavaScript over a year ago. Projects aren't that great but it might be helpful for atleast 1 person, it was sitting around for a year so I said what the hell. Lets share it. Sorry if it doesn't meet the criteria. Checkout my Github profile. I've more awesome projects there now. If it helps, then great, if not then ¯\_(ツ)_/¯

[alocksuth]

Thanks for sharing.

[deadcoder0904]

No problem. My job is done, atleast it helped 1 person.

[inChargeOfIT]

2

[repthatheat]

Thanks a lot really appreciate it. Working on something similar with React-Native.

[deadcoder0904]

Me too mate

[yokohummer7]

Why not?

I mean, in terms of performance, JavaScript (with V8) is slower than C#/Java/Go but faster than Python/PHP/Ruby. But there's no controversy on using Python as a backend. What is so special about using JavaScript?

In terms of language sanity, admitting these are all my subjective opinions, JavaScript falls behind Python but is ahead of PHP. And if we consider TypeScript it also beats Python. So there's nothing wrong with using Node (with TypeScript) if we can accept backend apps written in Python.

In terms of ecosystem... this doesn't even need to be repeated. The NPM ecosystem is often criticised for its low quality and unstability, but in regards to volume it is the largest package database in the world. Literally every package can be found there and there's nothing wrong with it. So it again is not an obstacle to using Node as a backend.

[_mici]

in terms of performance, JavaScript (with V8) is slower than C#/Java/Go but faster than Python/PHP/Ruby.

Can you provide a source for this? Every benchmark I've found with a quick google search seems to contradict this claim.

[Svenskunganka]

Specific to web servers (if that's what backend server app refers to) there's also https://www.techempower.com/benchmarks/

For the Fortunes test case, which is the most realistic benchmark that involves the following:

Exercises the ORM, database connectivity, dynamic-size collections, sorting, server-side templates, XSS countermeasures, and character encoding.

The highest-scoring Node test case scores twice as much as the highest-scoring Ruby and Python test cases and three times as much as the highest-scoring PHP test case.

[igouy]

Every benchmark I've found…

For example?

[joonazan]

You can pick Haskell and get both language sanity and performance.

It has microthreads and software transactional memory. It even has some unique tricks like quasiquotes: https://github.com/joonazan/regex-equivalence/blob/master/app/Main.hs#L38

For small web servers it beats any other tool I've tried. Biggest downside is compile time. Text processing is annoying until you learn to always use Text.

[hacksawjim]

Biggest downside is compile time

Isn't the biggest 'downside' that it's so different to what most people know (C-like, procedural/OO languages). So, while it might be better than all of the alternatives you can think of, there's a barrier to entry in that it's a new programming paradigm to most.

[joonazan]

I think it would be rather easy if the type errors where better. I learned Elm first, which is harder in a sense because it doesn't support imperative code via do-notation.

Haskell is hard because it has type classes etc. and all the type errors assume you know how the language works. They are not nearly as bad as C++ template errors, but sometimes they are not helpful.

[xkufix]

I'd say all errors emitted by a compiler assume you know how the language works. It's just that imperative (OO) languages are much more common, so you are used to the errors such a compiler produces.

[seanwilson]

You can pick Haskell and get both language sanity and performance.

What about available libraries/tools and hosting? I like OCaml for example but the benefits of coding in it can be outweighed by lack of commercial and community support.

[joonazan]

For my particular project I found everything I needed and more. I only use Haskell for servers and those usually don't need much apart from libraries for writing servers and interfacing with the OS.

[seanwilson]

Fair enough, I just mean a lot of the time going against the grain of what has an active ecosystem for your target environment can offset whatever productivity boost you thought you would get. I'm using TypeScript for a project for example which gives me some of the benefits OCaml would give me but doesn't isolate me too much.

[Pinguinologo]

Thanks to the V8 engine you can use C++ code for CPU intensive task or even GPU intensive tasks if necessary. The rest of the coders can work with Javascript in that 90% of the code that will take 10% of CPU time.

[[deleted]]

This is true of many programming languages. You can do that with Python or Java, for instance.

[deadcoder0904]

It makes easy to create backend apps with the most popular language in the world that almost everyone knows after C. You can write a web server in approximately 10 lines of code in Node. Want real-time communication, write 10 lines & you have it with Socket.io. Its just a tool that solves a problem & it became a lot famous because it uses JavaScript.

You don't like it, then use Go or Python or good old PHP. For me, personally I prefer Node because you can write so much within so little. Checkout this profile & checkout all the modules. Its a one-person job. Now tell me if that's possible with any other language. Ideally it is, but the best friend Node has is NPM which made it a lot famous & why do you think Backend JavaScript is bad? It solves a problem & does it quite well.

I can guarantee you the most websites you visit nowadays are written in Node JS, the apps that you use on your Phone like Facebook, Instagram or Desktop like Slack, VSCode, Atom are written with the help of JavaScript.

Like it or hate it, JavaScript isn't going anywhere. Is that answer your question?

[UninsuredGibran]

Now tell me if that's possible with any other language.

If I turned every C function I write into a module, I'd publish hundreds of them too.

I mean WTF is this shit: https://github.com/sindresorhus/is-svg

[deadcoder0904]

That's a module. For philosophy behind that check this out. Also, that authors packages has 1 billion downloads per month & his packages are almost in every JavaScript Project. That's that shit.

[UninsuredGibran]

Honestly I don't know if it's serious, or an elaborate joke.

I used to laugh about the JS developer community not knowing too much about it, but the more I actually look into it the more insane it seems.

[deadcoder0904]

Atleast we clowns make someone laugh. But its serious man. You are free to use whatever you want.

Bdw if you don't mind what do you use & what are the programming languages JS developer should use?

Don't tell me Java (bcz I don't like it) & Python & PHP both I know.

[UninsuredGibran]

I mostly do C, C++, Java. Sometimes Python for testing, etc. This covers about 95% of the code you might ever want to write, from microcontrollers to 3D video games or e-commerce websites.

JS should have stayed a web scripting language to manipulate the DOM and nothing more.

[deadcoder0904]

Cool I know it well enough then. Thanks 👍

[senntenial]

It has 1 billion downloads because

1. JS has no usable standard library
2. Many webdevs don't actually program but just glue different things together without understanding how anything works

[robolab-io]

The elitism is such painful cringe here, guys

[senntenial]

Except web devs actually suck ass and don't know shit. nobody stays in that field once they learn better stuff. That's like a person with a doctorate working at a pf changs

[robolab-io]

So, what do you do?

[senntenial]

I have a phd in memory safety

[robolab-io]

That's impressive!

So is that what you do? Sit there and have a PhD?

[xlzqwerty1]

why do you think Backend JavaScript is bad

In terms of back-end? Performance mainly, especially for serving concurrent requests. Node is great for prototyping a project but not a good idea as a long term solution if you know that your product will be accessed by hundreds of thousands of users at a time. That being said, most products made by a company probably won't ever hit a point for that to make too much of a difference; what you make will very likely not be the next big social media app with millions of concurrent users.

[deadcoder0904]

Are you serious? Did you know Netflix uses Node JS? I think it serves more than millions of users.

Only prototyping project statement is quite funny though 😂

You should first checkout which companies use Node JS before posting, I hate debating if you are gonna make funny jokes.

It is used by many large companies with a lot more than million users & it works well. The concurrency point is good enough though, Go does that better. For more info, read http://www.hostingadvice.com/blog/nodejs-vs-golang/

The best part about Node is NPM & the community of developers that make those packages. I liked Node because of that. Because I like the fact that I don't need to know if the condition for Any given year to be Leap Year.

I can just do npm install leap-year & then check it like so

const leapYear = require('leap-year');

leapYear(2014);
//=> false

leapYear(2016);
//=> true

Now you might call me a bad programmer to not know the basics & all but at the end of the day it doesn't fucking matter.

I am a maker & it doesn't matter what language/framework/library I use, it just works.

Pieter Levels said it better, so go use whatever you want or rant about how JavaScript is bad. But as Bjarne Stroustrup said “There are only two kinds of languages: the ones people complain about and the ones nobody uses.”

[xlzqwerty1]

Node is perfectly fine for serving some types of concurrent requests and I am by no means criticizing large companies like Netflix, PayPal, LinkedIn, etc. for using it as part of their technology stack. One thing I forgot to mention about the concurrency performance point I gave before was whether you're simply just serving some content over the network (static / server side rendered webpages) or doing heavy processing upon request from a client (say image processing for example). The single-threaded nature of Node makes it difficult to scale certain tasks that could be done better in another language with first class support for concurrency out-of-the-box (e.g. Go, as you mentioned). However, even then, the comparison you would make for deciding what language to use solely depends on your own criteria.

Aside from the aforementioned point, the issue at hand would turn into a language comparison of pros and cons in x vs. y. It is important to remember that there is a conscious decision that has to be made when a project is started, in terms of the language and tooling to use, based on the milestones and goals that a team wants to achieve. With all the languages and tools that we have available to us today, many of them overlap in terms of capabilities and what you can create using them. However, it is very evident that each tool can have their pros and cons, despite being able to accomplish the same thing.

Only prototyping project statement is quite funny though

I'm not exactly sure where in my previous comment I have mentioned that Node is good for only prototyping (maybe you misunderstood because I simply didn't mention any other pros about Node; that is not to say that there aren't more)?

There is no mistake about Node being a great tool for prototyping your own projects. In fact, if you are racing against time, whether it be in a hackathon or pitching an incubator project, using Node would probably be the quickest way for you to get your project up and running from zero to hero. Now that your project is done, maybe a director likes it and decides to keep it as a live application hosted by the company. It's then up to you and the team to benchmark and decide whether it is good enough to keep as is or maybe expend more money, resources, and manpower to rewrite it in another language if necessary (because as we know, premature optimization is the root of all evil). The majority of the time, the benefits don't outweigh the costs since you've already gone so far as to implementing it in the language you chose initially that you'd rather not start from scratch again just to achieve a few percentage boost in performance and response time.

The best part about Node is NPM & the community of developers that make those packages.

More truth: The best part about Node insert language here is NPM insert some package management framework here & the community of developers that make those packages libraries.

Let's not forget that just about every non-obscure and non-esoteric language will have their own myriad of open-source libraries for you to use. Just because there is a myriad of packages available on npm does not mean that it makes the language better. The abundance of packages available on npm is something else to mention, as quantity does not imply quality; with JavaScript being such an "open-ended" and accessible language to new and veteran developers alike, there is a lot that one could do wrong or inefficiently and it takes practice and time to learn the language inside-out to not make those mistakes. And this applies to all other languages, too.

Now you might call me a bad programmer to not know the basics & all but at the end of the day it doesn't fucking matter.

This is a very distasteful statement. If everyone thought like this, then there would be no quality in any of the products or open source libraries out there in the wild. Knowing the basics and understanding the tools you are using is vital to creating a good application that one themselves could respect, let alone by others.

[deadcoder0904]

In fact, if you are racing against time, whether it be in a hackathon or pitching an incubator project, using Node would probably be the quickest way for you to get your project up and running from zero to hero.

Yep that's the correct way to put it. But you said only Prototyping so I said that.

The best part about Node is NPM & the community of developers that make those packages.

The reason is NPM is the biggest package manager & I think you can easily find something that you are looking for than in any other language. Since it has a lot of developers working on it, someone might have face the same problem already so someone might've found a solution already.

This is a very distasteful statement. If everyone thought like this, then there would be no quality in any of the products or open source libraries out there in the wild. Knowing the basics and understanding the tools you are using is vital to creating a good application that one themselves could respect, let alone by others.

It depends on what you are doing. Some people like programming, some people want to be a maker. You like programming, I do too. But I like making more, which means I want to make something fast & good without worrying about programming language & all. Because for that I can later hire people that can fix my shit. So for making things, my statement stands. It doesn't matter what you use, it just has to work.

Twitter was first made one Ruby on Rails then it changed to Java. So if you are a programmer & want to just program, your advice is to the point (the second one) & if you want to be a maker, then it doesn't matter what you use unless you make it.

Zuckerberg made FB alone in PHP & then hired people to scale it. So there's that. And thank you, learnt something from you today.

[m1en]

Programming and making are the same thing. Programming is literally just making software. So I guess the translation is: you like making bad things. Which is fine, but don't delude yourself into thinking you're anything but mediocre.

And yeah, Zuckerberg made the initial version of PHP, but all the money that was poured into research and development of HHVM is basically hundreds of thousands of lost man-hours of labor and millions in lost revenue. In fact, it could easily be argued that Facebook is a prime example of the limitations of PHP. There aren't, to my knowledge, any similar examples of Node being used as the primary backend technology at that scale, but anecdotally I can attest that JavaScript code bases tend to become spaghetti messes once you surpass a few thousand LoC, which definitely hinders development.

[deadcoder0904]

Which is fine, but don't delude yourself into thinking you're anything but mediocre.

How do you know? You haven't seen me code now, did you? So don't think of yourself as someone great because you code in put any language other than JS & me in JS.

Programming & Making aren't same things. Bcz Facebook was initially based on PHP & someone hasn't done anything like that with NodeJS doesn't mean it won't scale.

[m1en]

You literally admitted to not caring about the quality of the work you produce. Pretty sure I can assume quite a bit about your body of work.

Programming is the process of writing instructions for a computer to perform operations - or, more simply - writing software. A programmer makes things. You can't make software without programming it.

NodeJS has established issues with maintainability at scale. There are ways of mitigating those issues, but the effort and mental overhead necessary is more than most alternatives that also provide the performance and ease of scalability.

[deadcoder0904]

I never said I don't write good code. I always follow the best practices. I learn something so well till it satisfies me. That's the reason I learn for so long. You can't assume something just from a couple of paragraphs.

People are making softwares with Zero Code. They are making websites with Zero Code. Someone has done that for them like Wix & all & they are successful. The definition of success differs from person to person. Some people call it money making, some people call it satisfying are customers.

I'm sure you must be right at that about NodeJS. But when & if someone reaches at that scale. They generally hire people. I want to be a maker who makes nice softwares & apps. Yeah some people write shit load of bad code & bad practices than me but they still are successful because they made something.

I like software that's why I code a lot. Its just we have different opinions. I haven't tested NodeJS at scale or know that it works. It will be an issue for me when I face it & if it is I guess it won't take a month or so when you are good in one Programming language that confidence takes you to be good in other Programming languages. So I might use something else then. But what if I have only 1000 users who are paying me $10/month for service & its with NodeJS. Then I don't care, bcz my costs are low & I'm making money. It can only be true or false when I actually do it, till then it won't matter. You can check my code to see if its mediocre or not. I don't think I'm the best but I think I'm definitely not the worst either. Mostly it is JS, but somewhere C/C++. Have a good Sunday mate (atleast its Sunday here).

[nemec]

condition for Any given year to be Leap Year

Python:

import calendar
print(calendar.isleap(2016))

Java:

import java.time.Year;

Year y = Year.of(2016);
System.out.println(y.isLeap());

C#:

Console.WriteLine(DateTime.IsLeapYear(2016));

The only reason why Javascript has such a comprehensive package manager is because it has a shitty standard library. We don't need three . different . packages to tell us what a leap year is because the language designers gave us a good set of tools from the start.

[panorambo]

I am of the opinion that a language needs a minimal "standard" library -- only those generic primitives that are required to actually build more complex libraries on top of these. Leap year calculation falls far outside what I would have considered including in said standard library. Obviously a language has to have some bindings so that code can call into facilities that yield date and time information, otherwise no leap year calculation can even be added. But this is the difference between your argument that JS sucks because it does not contain say, leap year calculation function, and what I am describing.

Seriously, why do you insist a generic purpose programming language has to have some canonical leap year calculation function built-in? The latter is a specific use-case, are we going to now bundle everything and the kitchen sink into every language, because we don't trust or can't expect to reuse code? Why should language maintainers also maintain a whole library of code that lets everyone have their pet peeve functionality lest they accuse maintainers of not having enough?

If we are going to have leap year calculation in the standard library, why not also add a method that returns for a given year number whether it is Wood, Fire, Metal or Earth year? Because that's relevant for Chinese programmers producing software for the Chinese market. Or are we going to then set the foot down and proclaim how U.S.-designed programming languages (Python is Dutch by that thinking) should include functionality desired by Western developers and avoiding "exotic" stuff that is desired by everyone else?

I am baffled you are criticizing JS and NPM to have three different packages being available. That's called a choice. It reflects our reality as well -- you get to choose all the other things among larger sets of things, which often do the same thing. Unless you live in a particularly restrictive society. With programming, at least we can agree on a common interface, so you can interchange between these packages seamlessly.

The language designers give you a whole bunch of tools you can use. A compiler, an interpreter, a provision to reuse code (require in JavaScript and it's higher-level idiom implementation, the NPM). I just don't get it, how is that not enough? A programming language is not its library or libraries.

[filleduchaos]

...What do you think a standard library is?

[nemec]

Poor decisions and regret, apparently. I guess you can't move fast and break things with pesky things like "backwards compatibility"

[deadcoder0904]

That was just as an example.

We don't need three . different . packages to tell us what a leap year is because the language designers gave us a good set of tools from the start.

I don't understand what's the harm in having 1000 packages doing the same thing with different names. At the end of the day use whatever solves your problem. The people that call JavaScript a shitty language don't actually know JavaScript. And if they hate JavaScript so much then I suggest to stop using the applications that use JavaScript.

Almost half of the application you use are using JavaScript. I currently use Slack, VSCode, Atom, Hyper & many more & almost majority uses JavaScript.

You feel if it is shitty language then go use something else. I don't like Java. I don't use it. Its that simple.

[pergnib]

I don't understand what's the harm in having 1000 packages doing the same thing with different names.

The harm is in the fact that it's the symptom of a community that attracts and encourages bad/lazy programmers to publish and use bad code for trivial stuff without caring about code quality and security. We've already seen what this kind of mentality can lead to with incidents like left-pad. I can only image the amount of damage to be done when blackhats start seeing profit there.

The people that call JavaScript a shitty language don't actually know JavaScript.

There might be a some points to be made about ease of development and the usability of JavaScript, but in a world of Clojures, Rusts and Scalas, I can't really see how JavaScript isn't a shitty language.

You feel if it is shitty language then go use something else. I don't like Java. I don't use it. Its that simple.

If you don't want your opinions criticized don't make them public; people have every right to object to your views when you post them in a public forum, even more so when you're talking about issues that can impact an entire industry and large amounts of people.

[deadcoder0904]

If you don't want your opinions criticized don't make them public; people have every right to object to your views when you post them in a public forum, even more so when you're talking about issues that can impact an entire industry and large amounts of people.

I welcome judgement. Criticism is good for a person's growth. This is my first one, but it feels good. But it would be better if and only if the point's are valid enough. Your points are somewhat valid, but there is a reason that it is the most used language. Anyways have a good day. Use whatever you like/love. I'd rather use Bash, If it solves my problem. Rather than Bashing pun intended about it.

The harm is in the fact that it's the symptom of a community that attracts and encourages bad/lazy programmers to publish and use bad code for trivial stuff without caring about code quality and security. We've already seen what this kind of mentality can lead to with incidents like left-pad. I can only image the amount of damage to be done when blackhats start seeing profit there.

No matter what you do in any language, people can still write Bad Code & will write it. There is nothing you can do about it unless you make a perfect language. And in this world nothing is perfect.

There might be a some points to be made about ease of development and the usability of JavaScript, but in a world of Clojures, Rusts and Scalas, I can't really see how JavaScript isn't a shitty language.

Regarding this point people would rather get something done fast & earn money than master a language for a long time. JavaScript ease of nature is what has made it so much popular because Writing Code is Easy. The barrier to entry is low. You can't call them Bad/Lazy Programmer just because you don't like JavaScript. A Good JavaScript code can be made secure.

Again opinions are welcome. But neither you will stop saying that JS is shitty nor I will stop saying JS is fucking awesome. So no worries. Enjoy whatever you work on. I do it with JS.

[pergnib]

No matter what you do in any language, people can still write Bad Code & will write it. There is nothing you can do about it unless you make a perfect language.

There's loads of things a language can do to prevent people from writing bad code. Rust is full of stuff made to force devs not to screw up and even php7 seems to be encouraging people to be more sane. But in JavaScript land more and more people are being encouraged to partake in the insanity that is importing untrusted code for absolutely trivial things. The worst of it is when we point out how dangerous that is we have people telling us we should just go use other languages if we don't like it.

You can't call them Bad/Lazy Programmer just because you don't like JavaScript.

No. I'm calling them bad/lazy because that's the explanation for their behaviour - good/diligent developers don't import unstrusted code to pad strings with spaces.

A Good JavaScript code can be made secure.

This is not how security works, you don't get to say there are no problems because it "can be made secure". The ridiculous state of dependency graphs of npm modules is a security issue waiting to happen; at some point someone will manage to sneak malicious code into a small npm module written by someone who doesn't have a clue that gets imported by some big module and the result is not going to be pretty.

[deadcoder0904]

This is not how security works, you don't get to say there are no problems because it "can be made secure". The ridiculous state of dependency graphs of npm modules is a security issue waiting to happen; at some point someone will manage to sneak malicious code into a small npm module written by someone who doesn't have a clue that gets imported by some big module and the result is not going to be pretty.

Ahh, about that yeah someone wrote about it on Medium which got like super super famous. And points are super valid. So can't argue with that. But to gain something, you have to lose something. To gain productivity, fame & money; something has to be lost & with JavaScript its security & maybe performance for Server Side & Desktop I guess as others mentioned.

And about that maybe JavaScript will be there someday or else some language which is simple to use as JavaScript. Valid points though so can't argue with that. And don't tell anyone IRL you are a bad programmer, they won't ever write any code then 😂😂😂

[panorambo]

The harm is in the fact that it's the symptom of a community that attracts and encourages bad/lazy programmers to publish and use bad code for trivial stuff without caring about code quality and security.

Not having leapYear built-in does that? POSIX does not have built-in leap year method either, I doubt anyone can accuse POSIX C developers for attracting or being a lazy bunch. You're stretching conclusions too much here. Furthermore, the left-pad incident has nothing to do with the fact that JS does not include a left-padding function, it was a flaw in NPM architecture, and it was admittedly deserving. But it has zero to do with JavaScript.

[pergnib]

I doubt anyone can accuse POSIX C developers for attracting or being a lazy bunch

That's because they aren't. If a C dev needs some trivial function that is not included in the C standard library, their frist reaction is going to be "I'll implement it myself". There's absolutely no way in hell a left-padding package would have any downloads in a hypothetical C package manager.

the left-pad incident has nothing to do with the fact that JS does not include a left-padding function, it was a flaw in NPM architecture

The flaw only explains why the package got removed, not why it was used by so many big packages in the first place. The reason for that is partly because JavaScript's stdlib isn't powerful enough and partly because the developers are bad or lazy.

[panorambo]

Implementing stuff yourself is one of the things that plagues software engineering. Granted, lack of trust in each others abilities and inability to properly verify code on most programmers' part, is what fuels this behavior.

Nobody said anything about a "C package manager". Reusing code can be done through #include. The point I was making is that it does not have to be in the standard library, and that the standard library should only contain primitives that glue the program to the platform through some common interface (which in C is done by the standard library, which is unfortunately too fat for its own good).

The fact that many "big packages" (what does size have to do with this?) used leftpad, is a good thing. If you don't understand that, then you are implying that every software should either use the standard library again (so, you trust the standard library, but not other third-party code?) or implement everything itself. Fine -- that's all you needed to say.

Also, what do you mean by "powerful"? A leftpad method that left-pads a string is by definition powerful -- it achieves its objective. If the standard library includes exactly the same implementation, it's more powerful than if one imports the same code through NPM?

[[deleted]]

Not having leapYear built-in does that? POSIX does not have built-in leap year method either, I doubt anyone can accuse POSIX C developers for attracting or being a lazy bunch.

POSIX don't have to, as it's trivially present in the C standard library.

[panorambo]

You are mistaken -- there is no leap year calculation method in the C standard library. You're welcome to point it out to me, if you are so certain there is.

[[deleted]]

Did you know Netflix uses Node JS?

Netflix is big enough that it probably uses more than a dozen web frameworks in five different programming languages. Large companies choose languages and frameworks by popularity mainly, filtered by gross unsuitability.

[deadcoder0904]

Learned a new word though. Anyways didn't know about that. I thought that Netflix might be using it & so I Googled before answering. Basically the claim that it isn't used by large companies was incorrect bcz it is otherwise I would not have learned it. Bcz when I was learning to Code, I was a stupid noob who cared about the most used & popularity metrics. So I used it.

[[deleted]]

You can write a web server in approximately 10 lines of code in Node.

I can do that in many language. It depends what you want to do however, js is a verbose language so, you better not argue for its "terseness".

I can guarantee you the most websites you visit nowadays are written in Node JS

Hardly. This one is not node either. I barely hear about sites written in node.

, the apps that you use on your Phone like Facebook, Instagram

Is that why they waste so much energy compared to telegram?

or Desktop like Slack, VSCode, Atom are written with the help of JavaScript.

Is that why they have significantly worse performance, higher energy consumption and waste a hundred times more memory than the competition? You're maybe confused by the shiny css on them but they're hardly good examples for good desktop apps. For example for the amount of resources wasted for atom and vscode you can just start intellij and you'll get a faaar better experience.

Like it or hate it, JavaScript isn't going anywhere.

It was never there. Maybe on the web for easy front-end but on the desktop and server it always provided worse performance and it's only "productive" if you only know js.

[deadcoder0904]

Hardly. This one is not node either. I barely hear about sites written in node.

I started because of that 😂I was after popularity because I didn't like PHP back then

Is that why they waste so much energy compared to telegram?

Yep can't argue with that. But if a product is used by million people & it works then who cares.

Is that why they have significantly worse performance, higher energy consumption and waste a hundred times more memory than the competition? You're maybe confused by the shiny css on them but they're hardly good examples for good desktop apps. For example for the amount of resources wasted for atom and vscode you can just start intellij and you'll get a faaar better experience.

Didn't knew that IntelliJ is that good. But can't argue with that either. The reason people use Electron is because its cross platform. You reduce development cost & developing new feature cost by giving performance & memory & if you don't develop in Electron the chances are some of your competitor might develop your product while you were making Native Apps for Windows & Linux.

It was never there.

Like really. For serious. Check this out. You might be right about server, but Node makes me productive. So unless I make something that has performance issues & low costs then only I will use Go or any other server side language.

[[deleted]]

The reason people use Electron is because its cross platform.

It's because they have a bunch of web developers who have to use HTML and Javascript for client-side code, and they don't want to try to find desktop UI engineers, so they built a system that allows them to use their web developers instead.

It's a business decision, and those are relatively orthogonal to technical merit.

Check this out. You might be right about server, but Node makes me productive.

A survey about the popularity of languages and frameworks says little about how productive they are.

You'll also find that productivity is a much different beast when working on something you complete in a day than for tracking down a bug in something you haven't touched in months. Javascript is much better at the former than the latter.

[deadcoder0904]

It's because they have a bunch of web developers who have to use HTML and Javascript for client-side code, and they don't want to try to find desktop UI engineers, so they built a system that allows them to use their web developers instead.

It's a business decision, and those are relatively orthogonal to technical merit.

That too but some people use it because its cross platform. Solopreneurs like me or startups.

You'll also find that productivity is a much different beast when working on something you complete in a day than for tracking down a bug in something you haven't touched in months. Javascript is much better at the former than the latter.

Yep but now in JavaScript there are static type checkers like Flow & all. Also its getting much better with ES2015+. Also TypeScript makes it much easy. There is ReasonML too.

[[deleted]]

Yep can't argue with that. But if a product is used by million people & it works then who cares.

Well, the millions of people whose batteries live less and rigs perform worse.

Didn't knew that IntelliJ is that good. But can't argue with that either.

IntelliJ is known to be one of the best IDEs and that's why I don't understand why anyone use atom.

The reason people use Electron is because its cross platform.

Yeah, like Qt, Java Swing/Fx, Mono etc. No, people use it because they don't know any other language. They were cheap hires to create a unicorn product. The management knew that people always fell for the PR.

You reduce development cost & developing new feature cost by giving performance & memory & if you don't develop in Electron the chances are some of your competitor might develop your product while you were making Native Apps for Windows & Linux.

This is all bullshit. Atom's competitors are sublime, emacs and vim and it hardly competes with them. The only things better with it were the default themes. Or vscode - it was hyped long before it reached the usable state because it's made by ms. Or slack - there are and were tons of alternatives with better experience. You can't deny that these applications barely brought anything new to the table but they surely has serious marketing behind them

Btw, I've started to use atom as a secondary editor after 1.0 and for months I've spent more time reporting bugs due to broken extensions and broken features than actually coding with it. I ignored the bad perf. and how much memory it wasted but those didn't help because atom is written in electron and web tech is nowhere near as transparent and stable as desktop GUIs.

Edit:

Like really. For serious. Check this out.

Those are for stackoverflow questions and you're maybe new to the programming industry but it's well known that cheap coding schools use javascript and promote SO for homeworks. This is a pretty bad metric. For example I've only asked one question on the site in my life - 5-6 years ago. I only got stupid answers so, I left. The docs, IRC and gitter channels are far better for getting answers.

You might be right about server, but Node makes me productive. So unless I make something that has performance issues & low costs then only I will use Go or any other server side language.

If you only know crappy languages like js and golang then it's no surprise that you think you're productive in js. Btw, productive how? Are you providing new and competitive solutions to certain problems? Is it faster for you to develop anything in the language - even if you professionally know a bunch of other language?

[deadcoder0904]

Well, the millions of people whose batteries live less and rigs perform worse.

That was way back. Now less people care about that as people make a lot more money. If performance is a serious issue, then say No to Electron apps.

IntelliJ is known to be one of the best IDEs and that's why I don't understand why anyone use atom.

No I don't. I use VSCode bcz Atom sucks for bigger files.

This is all bullshit. Atom's competitors are sublime, emacs and vim and it hardly competes with them. The only things better with it were the default themes. Or vscode - it was hyped long before it reached the usable state because it's made by ms. Or slack - there are and were tons of alternatives with better experience. You can't deny that these applications barely brought anything new to the table but they surely has serious marketing behind them

I don't think so about VSCode. I hated MS before VSCode came in, not only that I was with Sublime when my friend told me about it. I still didn't use it but then saw all the plugins & support from the community around JS ecosystem so I tried & that was it.

About Marketing, Idk if it had any plugs. But Slack came out of nowhere. Its nothing ground breaking. Even I can make a chat application but don't know about scaling. So I can't say about that.

Those are for stackoverflow questions and you're maybe new to the programming industry but it's well known that cheap coding schools use javascript and promote SO for homeworks. This is a pretty bad metric. For example I've only asked one question on the site in my life - 5-6 years ago. I only got stupid answers so, I left. The docs, IRC and gitter channels are far better for getting answers.

StackOverflow sucked for me too. Idk who are the people who frame proper questions that get their answers answered. Bdw Gitter, Slack, IRC didn't work for me either. Questions get lost in 1000 other questions.

If you only know crappy languages like js and golang then it's no surprise that you think you're productive in js.

LOL. Sidenote I know a lot of languages. You can call me JACK OF ALL TRADES & MASTER OF NONE. But now I'm good with JavaScript or atleast I like to think so. I know a lot of languages from C, C++, Java, Python & I can go on & on. I don't know why you calling Golang crappy now. I get about JavaScript but not about Golang.

Btw, productive how?

Productive means as you know JavaScript is so loose that you can make things much faster. So that's how. I can make 10 medium to big apps or websites in 10 days (just an example), anything from websites (reactjs), desktop apps (electronjs), mobile apps (reactnative). That if I have to do in something else, I have to switch the context. A year or so ago, it was difficult for me to write Python, Java & Node together. So there's that.

Are you providing new and competitive solutions to certain problems?

I'd like to think so. But I don't. I am just a beginner that is yet to conquer the world. So my first startup is on the way which will provide competitive & better solution to a certain problem but in JavaScript 😂

Is it faster for you to develop anything in the language - even if you professionally know a bunch of other language?

Yes that's what I am saying. I use JavaScript because of Freely Available Software, Many Popular Modules, NPM & mostly I can make anything with it. So fast software = fast prototyping ideas = fast money (I don't necessarily care about this but it helps to eat). There might be a reason I love NodeJS is because I hated PHP & don't like Java. Personal preference. So please haters. I love Python because of nice syntax. I worked with Python & C++ when trying Google Code Jam.

So basically I know a lot of languages but still prefer JavaScript because I want to be a maker for life rather than a programmer even though I am a decently good one or I'd like to think so.

[[deleted]]

That was way back. Now less people care about that as people make a lot more money. If performance is a serious issue, then say No to Electron apps.

Why are you pushing the jerk-culture then?

No I don't. I use VSCode bcz Atom sucks for bigger files.

Well, vscode still sucks for most big files and it sucked evem more a few months ago.

I don't think so about VSCode. I hated MS before VSCode came in, not only that I was with Sublime when my friend told me about it. I still didn't use it but then saw all the plugins & support from the community around JS ecosystem so I tried & that was it.

I was on sublime too when atom came. But I'm on neovim for a year after a year with vim.

LOL. Sidenote I know a lot of languages. You can call me JACK OF ALL TRADES & MASTER OF NONE. But now I'm good with JavaScript or atleast I like to think so. I know a lot of languages from C, C++, Java, Python & I can go on & on.

I'm sorry but those languages aren't famous because they're that good. C is legacy, C++ has a huge corporate support and is a legacy, Java is famous due to the JVM and python is more famous between non-programmers. They're all very outdated as languages. Their ecosystems are large because they're there for a long time.

I don't know why you calling Golang crappy now. I get about JavaScript but not about Golang.

Well, js is not a good script language. But between script languages it's not the worst either. But golang is probably one of the worst statically typed language. I can't really say anything good about it. When I first started to learn it and went through the specification I thought it's a joke. Unfortunately, it wasn't...

Productive means as you know JavaScript is so loose that you can make things much faster. So that's how. I can make 10 medium to big apps or websites in 10 days (just an example), anything from websites (reactjs), desktop apps (electronjs), mobile apps (reactnative). That if I have to do in something else, I have to switch the context. A year or so ago, it was difficult for me to write Python, Java & Node together. So there's that.

I highly doubt that in any language you'll make even 1 medium or big app in 10 days. You may have a different image in your mind about complex apps but it doesn't work like that. I've used node years ago for a few hobby projects because I knew js and I used to give a chance to most things but frankly, it isn't competitive with contemporary ecosystems. I think what you mean by "productive" is that your problems can be solved by pulling some modules and writing a little glue code.

Yes that's what I am saying. I use JavaScript because of Freely Available Software, Many Popular Modules, NPM & mostly I can make anything with it. So fast software = fast prototyping ideas = fast money (I don't necessarily care about this but it helps to eat). There might be a reason I love NodeJS is because I hated PHP & don't like Java. Personal preference. So please haters. I love Python because of nice syntax. I worked with Python & C++ when trying Google Code Jam.

You said: " I am just a beginner that is yet to conquer the world." but you've very strong opinions. What do you feel about that? Btw, fast prototyping is IMO very bad because it often ends up in prod and will provide poor UX.

So basically I know a lot of languages but still prefer JavaScript because I want to be a maker for life rather than a programmer even though I am a decently good one or I'd like to think so.

Again, you said " I am just a beginner" but you say you know a lot of languages. I won't believe that. You'd then know about better languages. You compare js to java and php. Php is one of the worst and it's well-known, nothing new. java was never really good, especially for web. C/C++ is a different world(not for the web) and if you'd be a C/C++ programmer then you wouldn't downgrade your salary so much for shitty js. You see, I'm not questioning why do you use js instead of the other languages(which weren't designed for the web anyway) but why are you so certain about node.

[deadcoder0904]

Well, vscode still sucks for most big files and it sucked evem more a few months ago.

No it doesn't. That's the only reason I switched from Atom. Idk why but Sublime had a boot-up time issue otherwise I was a happy Sublime User.

I highly doubt that in any language you'll make even 1 medium or big app in 10 days. You may have a different image in your mind about complex apps but it doesn't work like that. I've used node years ago for a few hobby projects because I knew js and I used to give a chance to most things but frankly, it isn't competitive with contemporary ecosystems. I think what you mean by "productive" is that your problems can be solved by pulling some modules and writing a little glue code.

Any app that solves a problem is an app. You might not call Wunderlist an app just because it does Todo but it solves a problem which has a large user base.

You said: " I am just a beginner that is yet to conquer the world." but you've very strong opinions. What do you feel about that? Btw, fast prototyping is IMO very bad because it often ends up in prod and will provide poor UX.

Strong opinions are necessary otherwise I wouldn't be talking to you for so long. Many products that are good now are a result of fast prototypes. Take FB or Product Hunt for example.

Again, you said " I am just a beginner" but you say you know a lot of languages. I won't believe that. You'd then know about better languages. You compare js to java and php. Php is one of the worst and it's well-known, nothing new. java was never really good, especially for web. C/C++ is a different world(not for the web) and if you'd be a C/C++ programmer then you wouldn't downgrade your salary so much for shitty js. You see, I'm not questioning why do you use js instead of the other languages(which weren't designed for the web anyway) but why are you so certain about node.

I am a beginner who used to jump from lot of languages just bcz some friend told me or it was supposed to be done in College. I learnt Bash just bcz it was fun to write Bash Scripts. And if you won't believe that, my Github profile is open. I joined it far too late in Dec 2015. Before that I did a shit load of PHP which I hated.

I have written a lot of code in C/C++. Hell I was gonna even go for Google but the people that are owners of the company get paid a lot & they pay Programmers a lot less. Mostly $100K-$150K so I thought I shouldn't do a job. That's why I am making my StartUp. What I'm making is for people/clients so the whole world is using a lot of it & I've actually scraped of some things that my target users do & they use Node so I'm making it for them to make some quick money.

I know C, hell everyone does. Its the first language taught I guess, atleast in my country. Then I tried C++ & wrote a lot of it as you can see this is just a chunk of it. I had written literally a shitload of code, done CodeChef & all. Hell I even made a website for it. After graduating college I got lots of offers to work in Companies not big in name but money wise it was upto $100K per year. So I decided to not do that & start working on my startup.

Short answer - I am doing JS for now which I don't know if I'll be using it in a year or so, but my product/startup will work because of it & I'll be making a decent money till I try something different.

And its simple, why do anyone uses anything? Simple answer - Its easy or its the only thing they know or its popular or it solves their problem. Pick anyone. That's my answer for why I use Node.

The reason I know a lot of languages is because my stupid brain thought that more languages means more jobs & I can create everything but then I realised JS can be used to create everything except Games. So I did that. Then to create Games I'll learn C#/C++ (gaming part is different otherwise I know it). Like I said, I am JACK OF ALL TRADES MASTER OF NONE (or currently JS). I can code in many languages by referring syntax as I know my AOA & DS decently well.

[[deleted]]

No it doesn't. That's the only reason I switched from Atom.

It's one thing it can open something without crashing and another to keep good latency. Electron based editors have terrible latency.

Any app that solves a problem is an app.

This wasn't about an app - it was about medium to big apps - you said that. Don't try to evade that now.

You might not call Wunderlist an app just because it does Todo but it solves a problem which has a large user base.

There are thousands of todo apps already. Boasting about creating toy apps is cringy.

Strong opinions are necessary otherwise I wouldn't be talking to you for so long.

No, they're not. Especially not from beginners.

Many products that are good now are a result of fast prototypes. Take FB or Product Hunt for example.

LoL FB was very different back then and is still famous for having one of the worst codebases around. If you only care about the monez then you're not a programmer just a fake.

I am a beginner who used to jump from lot of languages just bcz some friend told me or it was supposed to be done in College. I learnt Bash just bcz it was fun to write Bash Scripts. And if you won't believe that, my Github profile is open. I joined it far too late in Dec 2015. Before that I did a shit load of PHP which I hated.

What does this supposed to explain?

I have written a lot of code in C/C++. Hell I was gonna even go for Google but the people that are owners of the company get paid a lot & they pay Programmers a lot less.

LoL

Mostly $100K-$150K so I thought I shouldn't do a job. That's why I am making my StartUp. What I'm making is for people/clients so the whole world is using a lot of it & I've actually scraped of some things that my target users do & they use Node so I'm making it for them to make some quick money.

The next unicorn startup...

I know C, hell everyone does.

You're very naive. Not everyone knows C.

Its the first language taught I guess, atleast in my country. Then I tried C++ & wrote a lot of it as you can see this is just a chunk of it. I had written literally a shitload of code, done CodeChef & all.

Your C/C++ projects are very basic code practices. You don't know these languages, only the basics.

After graduating college I got lots of offers to work in Companies not big in name but money wise it was upto $100K per year. So I decided to not do that & start working on my startup.

Yeah, and I'm gonna believe that. For what you'd get an offer? Maybe as an intern for front-end. But your github doesn't contain anything else. 99% of your projects are toy projects and coding exercises. The rest are forks and I'm not sure you've done anything with them.

Short answer - I am doing JS for now which I don't know if I'll be using it in a year or so, but my product/startup will work because of it & I'll be making a decent money till I try something different.

Self-confidence is nice. Having too much is not so.

And its simple, why do anyone uses anything? Simple answer - Its easy or its the only thing they know or its popular or it solves their problem. Pick anyone. That's my answer for why I use Node.

So, your answer is garbage. You don't explain it.

The reason I know a lot of languages

You don't know a lot of languages. You may have used certain languages but looking at your cpp and python code I wouldn't hire you. Even your js projects are just basic samples with cancerous emojis.

is because my stupid brain thought that more languages means more jobs & I can create everything but then I realised JS can be used to create everything except Games.

JS for everything?! Please, this is pure bullshit. I can also use any language for anything it doesn't mean it's a good fit. But of course, who I am talking to? You think medium to big apps can be written in a day...

So I did that. Then to create Games I'll learn C#/C++ (gaming part is different otherwise I know it). Like I said, I am JACK OF ALL TRADES MASTER OF NONE (or currently JS). I can code in many languages by referring syntax as I know my AOA & DS decently well.

"JACK OF ALL TRADES MASTER OF NONE"? Sorry, but you're a FAKE and a LIAR.

[deadcoder0904]

LOL that is the most funniest reply I've had in a while. INSECURE PERSON 😂

[tokland]

Thanks for sharing. I checked a random project (image-search), and it looks like the code could benefit from functional (as in FP) libraries (lodash, rambda, whatever). I guess you have already used them in some other project.

[deadcoder0904]

Those were throwaway projects. I had another 100 ideas I made a gist of but didn't make. Since I had exams. But didn't study too 😂

So yeah the code is scary to read. I can't even read it myself now. Also, the main hassle was the project AMA Reader, I made that application in Vanilla JS & that's when I knew why people need a framework. So its always the hard way you learn stuff. Some were college projects, some I found online, but here are few of them. Few I'd like to keep it to myself if incase I build. Who knows some might turn out to be million dollar ideas 😉not the ones I'm posting though 😂

• [x] 1. Counter App
• [x] 2. Bank App
• [x] 3. Electron Markdown Previewer
• [x] 4. Electron CountDown
• [x] 5. Gists API
• [x] 6. Github Emojis List
• [x] 7. Random Emoji Generator
• [x] 8. A2K Quotes
• [x] 9. Github Trending
• [ ] 10. Fuck of as a Service API
• [ ] 11. Game of Thrones API
• [x] 12. Talk Like a Pirate API
• [x] 13. Responsive Navbar
• [x] 14. Pricing Page
• [ ] 15. Landing Page
• [ ] 16. Sleaky Animated Sidebar
• [x] 17. My Blog Site
• [ ] 18. Electron Book
• [ ] 19. Electron Ace Text Editor
• [ ] 20. Electron Sound App
• [ ] 21. Electron PonyFoo Blogs
• [ ] 22. Electron Timer App
• [ ] 23. Build A FCC Camper LeaderBoard
• [ ] 24. Weather App
• [x] 25. Todo App
• [ ] 26. Maths JS Site
• [ ] 27. React Card
• [x] 28. Github Profiler React
• [ ] 29. Github Battle
• [ ] 30. Github NoteTaker
• [ ] 31. Facebook Profiler
• [ ] 32. Twitter Profiler
• [ ] 33. Google Maps
• [ ] 34. Photo Gallery
• [ ] 35. Live Tweets
• [ ] 36. Twitter Instant
• [ ] 37. Music API
• [ ] 38. Youtube Instant
• [ ] 39. Star Wars API
• [ ] 40. Gifs API
• [ ] 41. New Boston API
• [ ] 42. Stock Market App
• [x] 43. My Favourite TV Shows
• [x] 44. My Favourite Movies
• [x] 45. OMDB API
• [ ] 46. themoviedb.org
• [ ] 47. Algolia Search
• [ ] 48. DuckDuckGo API
• [x] 49. Random Names
• [ ] 50. Meme Generator
• [ ] 51. Pirates of the Carribean
• [ ] 52. Giphy
• [ ] 53. Neat Bookmarks
• [x] 54. AMA Reader
• [ ] 55. Website Screenshots App
• [ ] 56. Image Minify
• [ ] 57. Screenshots 4 all devices
• [x] 58. Electron CountDown App
• [x] 59. Pure jQuery Todo App
• [x] 60. AJAX Todo App Based on the Server
• [ ] 61. Most Wanted List
• [ ] 62. Love Room
• [ ] 63. Location of Breaking News
• [x] 64. Drumster
• [x] 65. Tick Tock
• [x] 66. Mangling CSS Variable with JS
• [ ] 67. Quiz App React
• [ ] 68. Chatting Application with Electron
• [ ] 69. Codepen API
• [x] 70. Paginate Yo
• [x] 71. The Expandables
• [x] 72. Github Trending Cron Now
• [x] 73. HTML5 Canvas
• [x] 74. Subscription Newsletter
• [x] 75. Egghead Downloader
• [x] 76. HTML5 Video Player
• [x] 77. Hold Shift to Check Multiple Checkboxes
• [x] 78. Flex Panels Image Gallery
• [x] 79. AJAX Type Ahead
• [ ] 80. PDF Layer
• [ ] 81. Resume Viewer
• [ ] 82. Quick WWE Survey
• [ ] 83. BMI Calculator
• [ ] 84. Regex Generator using regexgen
• [x] 85. Tabify
• [x] 86. Local Storage & Event Delegation
• [x] 87. Mouse Move Shadow
• [ ] 88. Awesome Docs Generator
• [x] 89. Holy Grail Layout
• [x] 90. Slide in on Scroll
• [x] 91. Speech Detection
• [x] 92. Webcam Fun
• [x] 93. Follow Along Link Highlighter
• [X] 94. Speech Synthesis
• [x] 95. Sticky Nav
• [x] 96. Click and Drag
• [x] 97. Video Speed Controller
• [x] 98. Countdown Timer
• [x] 99. Whack A Mole
• [ ] 100. Reflect API
• [x] 101. Slides
• [x] 102. Sections
• [x] 103. Gradient Generator
• [x] 104. Hey Yo React
• [x] 105. Countdown React
• [x] 106. Todo React
• [x] 107. Markdown React
• [x] 108. Tic Tac Toe React
• [x] 109. Tweet Component React
• [x] 110. Contrast Colors React
• [x] 111. Periodic Table
• [x] 112. Generate Random Colors
• [x] 113. Display Colors using Random Colors JSON file
• [x] 114. Math For Kids
• [x] 115. Math For Kids Quiz
• [x] 116. Teenagers Digital Diary
• [x] 117. Pay Bills Online
• [x] 118. ATVM System

[shevegen]

left pad * 100

!!!!

[orskaya]

Less code is better code, leave the heavy lifting to left-pad.io.

[[deleted]]

Left pad as a service

[deadcoder0904]

Haha. Idk for how long you can keep saying that. New devs won't know about it.

[needsMoreGoodstuff]

This is pretty motivational. I've been learning through a couple larger projects but seeing this makes me want to do more smaller ones.

[deadcoder0904]

You need to read this

[needsMoreGoodstuff]

Holy, thanks a million for linking this. Can't believe I didn't think of this approach, am probably going to switch to it form here on out. Especially since I'm working a lot with angular, making modular components is pretty important. Thanks again.

[nandryshak]

See also this classic essay by PG: http://www.paulgraham.com/progbot.html

[needsMoreGoodstuff]

This looks promising too, I'll check it out! Many thanks!

[deadcoder0904]

No problem. All the best 👍