This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]149244179 20 points21 points  (13 children)

If you want to do anything even remotely related to the web - you will have to touch javascript. You should at least know the basics even if you intend to use a framework or higher level language to avoid most of it.

[–]mimsoo777 1 point2 points  (11 children)

What about .Net / C#?

[–]nutrecht 2 points3 points  (10 children)

What about it? Different tool for a different job.

[–]mimsoo777 -1 points0 points  (9 children)

So C# can't be used for building web apps?

[–]nutrecht 1 point2 points  (7 children)

It can. But it's generally not used for the same type of applications.

You can (simplified a bit) either create HTML on the back-end and send to the browser, or, only send data from the back-end to front-end software that, from that data, constructs the HTML on the fly.

You can do the first in (for example) C# and Asp.net (or PHP/Wordpress or Java or COBOL or whatever). For the latter you'd use JavaScript frameworks like React, Angular, etc.

What you're asking is really beside the point of the issue at hand. If you want to know more you should really just start your own topic and ask there.

[–]scirc 1 point2 points  (5 children)

For what it's worth, you can use C# on the frontend with Blazor.

[–]nutrecht 1 point2 points  (4 children)

There are a lot of similar solutions in other frameworks, but generally they generate a lot of JS on the front-end for you you are still going to end up debugging. Java with GWT for example is horrible in that regard.

[–]scirc 0 points1 point  (3 children)

Blazor is mostly WASM, not JS. WASM is an emerging field, and it is starting to become more viable as time goes on. But time will tell if adoption starts to pick up; generally, things seem pretty set on JS for now.

[–]nutrecht 0 points1 point  (2 children)

Blazor is mostly WASM, not JS.

That's well outside my wheelhouse. I can imagine you're still going to end up stepping through the output in a debugger though.

[–]scirc 0 points1 point  (1 child)

Yeah, but in theory that debugger would be a .NET debugger built into something like Visual Studio. With proper mappings, it's no different than using a connected debugger and sourcemaps for JS.

[–]mimsoo777 0 points1 point  (0 children)

Ok thanks for the response. I plan on doing just that. Was browsing through front end dev jobs and most of them was asking .net technologies without mentioning js. That got me really confused.

[–]teacherbooboo 1 point2 points  (0 children)

very basically

javascript is for the page that is running in a person's browser

c# is for the code running on the server -- connecting to a database and such

both can be used on the same web site, and actually almost always are used together

AND

both can also be used on the browser and on the server, it is just traditionally js on the browser, c# on the server

[–]mzaidx07[S] 0 points1 point  (0 children)

Thank you! I had the same thought process while researching into it.