C# looks like an alright language but I'm wary about the idea of selling my soul to Microsoft. What if they make shitty changes that you basically have to adopt?
I guess you'd hope at that point that some people would fork it and maintain a version without shitty changes, but who knows if that would happen.
>people would fork it and maintain a version without shitty changes, but who knows if that would happen.
I would eat my hat if that happened and nobody forked it, the question is whether anybody used it, which you could somewhat affect if you were determined enough
C# is mature enough that I wouldn't expect already established things to change too much, at the very least you'll get backwards compatibility, just don't jump on features while they're still in the trial phase, I got burnt with that once and spent a month migrating a project.
That's true. But I think the JS ecosystem is probably a bit more open in general. You could use JS doc instead of TS if you wanted (some people do).
But anyway the main alternative to C# would obviously be Java, and yes Java is another corporate language, but it's probably less tightly controlled by Oracle, than C# is by Microsoft.
This. I went to a react conference the past week on a whim and they are 1-2 years behind Microsoft and .NET (which uses mostly C#).
The entire panel was trying to get the point across that server side rendered react components are here, but it will take 1-2 years for the community to adopt. Only Next.js has it baked in.
Meanwhile, .NET has everything ready with blazor and its all united now, most libraries/frameworks are going this route where you have one set of development tools for any case (static/PWA/SPA/server)
reacts done a lot more because of their community participation compared to .NET, even though .NET is ahead in terms of the tech and cohesion in their offerings (crazy coming from microsoft I know)
The only question is if microsoft is willing to stick it out long enough to build and support a community, or whether blazor will end up webforms 2.0.
>makes more money than you will ever have by using PHP
Yes that's PHP not JS, but obviously JS on the server didn't exist when he made Facebook, and some things I've seen show JS as being faster than PHP these days.
If he can make billions from a site written in a scripting language then maybe others can too.
Faceburg hasn't been written in PHP for a long, long time at this point. It was at the beginning, then they encountered a lot of performance problems so spent a lot of time and a lot of money re-writing from PHP in various other languages. >JS as being faster than PHP these days.
Speed is only a single metric, NodeJS is an awful language to develop in. The end result is almost always buggy and littered with .then().then().catch().then().finally(). And don't even get me started on the ABSOLUTE STATE of Nodes ecosystem.
>literally called Hack
they also have developed the abomination that is called React, a software that went through major revamps multiple times. Facebook is leaving their devs a lot of leeway to experiment, but that is not an argument for them making good decision in good software development. They should have scrapped PHP in the beginning and would have saved a lot of money and dev time.
>Faceburg hasn't been written in PHP for a long, long time at this point.
hmm? looks like they are still using PHP
https://engineering.fb.com/2020/05/08/web/facebook-redesign/
>should i use browser technology on the server?
the nodemonkeys are already on the rust and zig train to reinvent all their tooling, because those ignoramus finally realized the problems
These are the only relevant and good languages for backend dev:
>Java
If you want "it just werks" >Kotlin
If you want "it just werks" and don't hate yourself >Go
If you want "it just works" but also be le hip and modern >Scala
If you develop advanced stuff instead of just crudshit
>Kotlin, Go, Scala
Nobody actually uses these. Not to mention that you bring up muh masochism an an argument when backend work in languages like Java, C# , JS and php even has far more documentation and established projects (meaning more job opportunities too).
>Nobody actually uses these
Thanks for proving you have literally zero experience writing anything other than basic crudshit >C# >Js >PHP >For backend
See point regarding masochism
Scala is the only usable language combining true FP with OOP, that actually has a huge ecosystem
2 weeks ago
Anonymous
OCaml has a decently sized ecosystem, I would say it's enough for the vast majority of use cases.
Secondly, you shouldn't use OCaml or Scala for anything. There is no good reason to combine "true FP" with OOP. These languages try to combine everything to make everyone happy but end up butchering both approaches. Every half decent OCaml programmer ends up just never using the OOP features, so what's the point of having a slightly broken syntax with extra bloat? Should have just used sml and not split the ecosystem. And Scala is JVM shit so out the window it goes anyway.
2 weeks ago
Anonymous
>Should have just used sml
What and not have to spend two decades trying to add multicore support? What's the fun in that?
2 weeks ago
Anonymous
>Seethe seethe seethe >Cope cope cope
Meanwhile in reality: scala is the ONLY option if you want to do anything relevant regarding high availability, distributed processing/computing, high throughput/big data or similar
2 weeks ago
Anonymous
Ask me how I know you've never designed a high availability, distributed processing/computing, high throughput protocol.
2 weeks ago
Anonymous
>Protocol
Completely different thing you brainlet
>scala is the ONLY option
LMAO
Name another then?
2 weeks ago
Anonymous
>Name another then? >Distributed computing
Anything with OpenCL bindings >High availability
Anything that can run on k8s >Big data/High throughput
Anything with CUDA bindings. But I'll give you this one, there's a lot in the Apache ecosystem that's good for big data.
It's like you learned about Akka, Spark and Haddop and think that's the be all and end all. But these are just tools to make you life a little easier. Ultimately you can do this any language.
2 weeks ago
Anonymous
>OpenCL >For distributed computing
Stopped reading right there lmfao you don't even know what you're talking about
2 weeks ago
Anonymous
>OpenCL >Literally built for heterogeneous distributed computing
Brainlet
2 weeks ago
Anonymous
>Literally built for heterogeneous
Correct >distributed computing
Incorrect
You don't really know what distributed computing is, do you?
2 weeks ago
Anonymous
Distributed computing is distributing computations over multiple compute units. It's literally what OpenCL was made for.
2 weeks ago
Anonymous
Not him but distributed computing usually refers to cases where communication is unreliable, so across the internet for example. But you don't use Scala to do it of course, you use erlang.
2 weeks ago
Anonymous
Might just be a difference in terminology then, I work mostly on numerical projects and spreading a computation of multiple compute units is called "distributed computation" for obvious reasons.
2 weeks ago
Anonymous
Yea that's a field specific term then, in general it refers to multi-agent message passing scenarios.
2 weeks ago
Anonymous
I'm willing to admit that I'm wrong on this.
2 weeks ago
Anonymous
>Distributed computing is distributing computations over multiple compute units
Thanks for confirming. Brainlet doesn't even know the difference between parallel and distributed computing kek
2 weeks ago
Anonymous
>Completely different thing you brainlet
Ask me how I know you're ESL
2 weeks ago
Anonymous
>Unironically thinks a protocol is the same thing as applications >Calls others ESL when he's called out for his stupidity
2 weeks ago
Anonymous
>Unironically thinks a protocol is the same thing as applications
Except I never said that anywhere.
2 weeks ago
Anonymous
>scala is the ONLY option
LMAO
2 weeks ago
Anonymous
Niggas who lick musk's pole all day be like
2 weeks ago
Anonymous
>Musk
Only because Twitter also uses scala doesn't mean it owns scala kek
Also musk is a pseud btw
2 weeks ago
Anonymous
>Twitter also uses scala
Oh I was wondering why twitter is so broken all the time, makes sense
2 weeks ago
Anonymous
Scala is the only reason why Twitter as a concept is able to work at all. Blame the frontend devs for why the UX is shit
2 weeks ago
Anonymous
I'm talking about backend things, not receiving the correct notifications, receiving them weeks later, tweets randomly not loading and downtime etc.
I refuse to use either of those languages, so you presume wrong. The only time I touched C# was because I was importing a database from a C# application, it contained a lot of `?` characters in the password hashes because whoever wrote the C# code was too retarded to properly encode the hashes, probably not unexpected of C# users.
Probably erlang, lua or haskell, depends on what it is. Maybe nim is recommendable but I haven't used it. I want to say Pony as well but unfortunately it seems to be dying.
>Should have just used sml
What and not have to spend two decades trying to add multicore support? What's the fun in that?
It's so tiring actually. And of course it's the french. Imagine if all that effort went into sml or at least half of it, things could have been so good.
Python
C# if you're white. Nodejs if you're not.
C# looks like an alright language but I'm wary about the idea of selling my soul to Microsoft. What if they make shitty changes that you basically have to adopt?
I guess you'd hope at that point that some people would fork it and maintain a version without shitty changes, but who knows if that would happen.
>people would fork it and maintain a version without shitty changes, but who knows if that would happen.
I would eat my hat if that happened and nobody forked it, the question is whether anybody used it, which you could somewhat affect if you were determined enough
C# is mature enough that I wouldn't expect already established things to change too much, at the very least you'll get backwards compatibility, just don't jump on features while they're still in the trial phase, I got burnt with that once and spent a month migrating a project.
Mono already happened once. And older version of .net are still available so if you don't want to use the newest version, you don't have to.
>selling my soul to Microsoft
Node development would most likely happen with Typescript, which is also a Microsoft project
That's true. But I think the JS ecosystem is probably a bit more open in general. You could use JS doc instead of TS if you wanted (some people do).
But anyway the main alternative to C# would obviously be Java, and yes Java is another corporate language, but it's probably less tightly controlled by Oracle, than C# is by Microsoft.
C# is primarily non white, specially pajeet, all the post si see on LinkedIn regarding c# are almost exclusively done by pajeets
They love the corpo feeling, nodejs is widely used by all races which is in fact more inclusive and it's cross platform, c# isn't fully cross platform
Also
>Microsoft java
It's a pajeet language by default
PHP
C
It's significantly faster and simpler to do it in NodeJS.
Go + HTMX
>backend
C++ or you're not a real programmer.
Sorry anons, them's the breaks.
>makes more money than you will ever have by using PHP
A CIA company stooge is not a good example.
Of course it's a good example. Does he care if the NSA collects data from Facebook? No. He still has all his money so I doubt he cares.
Kotlin
Neither of those wtf use something decent like elixir or haskell
Who the fuck writes their backend in Haskell
scotty and warp chads
C# is the better tech, but you'll get more fun and interesting projects in node.
This. I went to a react conference the past week on a whim and they are 1-2 years behind Microsoft and .NET (which uses mostly C#).
The entire panel was trying to get the point across that server side rendered react components are here, but it will take 1-2 years for the community to adopt. Only Next.js has it baked in.
Meanwhile, .NET has everything ready with blazor and its all united now, most libraries/frameworks are going this route where you have one set of development tools for any case (static/PWA/SPA/server)
reacts done a lot more because of their community participation compared to .NET, even though .NET is ahead in terms of the tech and cohesion in their offerings (crazy coming from microsoft I know)
The only question is if microsoft is willing to stick it out long enough to build and support a community, or whether blazor will end up webforms 2.0.
Golang
Anyone using JavaShit on the server needs to be tortured to death.
Let me refer you to this example:
Yes that's PHP not JS, but obviously JS on the server didn't exist when he made Facebook, and some things I've seen show JS as being faster than PHP these days.
If he can make billions from a site written in a scripting language then maybe others can too.
Faceburg hasn't been written in PHP for a long, long time at this point. It was at the beginning, then they encountered a lot of performance problems so spent a lot of time and a lot of money re-writing from PHP in various other languages.
>JS as being faster than PHP these days.
Speed is only a single metric, NodeJS is an awful language to develop in. The end result is almost always buggy and littered with .then().then().catch().then().finally(). And don't even get me started on the ABSOLUTE STATE of Nodes ecosystem.
>re-writing from PHP in various other languages
no they didnt, they made their own PHP dialect and compiler
Sure Hack was one of the things they did, but I think they migrated to JVM based languages.
>literally called Hack
they also have developed the abomination that is called React, a software that went through major revamps multiple times. Facebook is leaving their devs a lot of leeway to experiment, but that is not an argument for them making good decision in good software development. They should have scrapped PHP in the beginning and would have saved a lot of money and dev time.
>Faceburg hasn't been written in PHP for a long, long time at this point.
hmm? looks like they are still using PHP
https://engineering.fb.com/2020/05/08/web/facebook-redesign/
>should i use browser technology on the server?
the nodemonkeys are already on the rust and zig train to reinvent all their tooling, because those ignoramus finally realized the problems
These are the only relevant and good languages for backend dev:
>Java
If you want "it just werks"
>Kotlin
If you want "it just werks" and don't hate yourself
>Go
If you want "it just works" but also be le hip and modern
>Scala
If you develop advanced stuff instead of just crudshit
The rest are only if you're into masochism
pretty much this
only other option would be python since it's pretty much everywhere, but for web dev it's trash
Worst post ITT and that's saying something
I know reality hurts your feefees, but sure indulge us and show literally one (1) thing wrong with the post
>Kotlin, Go, Scala
Nobody actually uses these. Not to mention that you bring up muh masochism an an argument when backend work in languages like Java, C# , JS and php even has far more documentation and established projects (meaning more job opportunities too).
>Nobody actually uses these
not him but you've just shown that you're a complete retard
>Nobody actually uses these
Thanks for proving you have literally zero experience writing anything other than basic crudshit
>C#
>Js
>PHP
>For backend
See point regarding masochism
>No body uses Go
Posts discarded.
people use them.
they shouldn't of course
but they do.
Scala is the only usable language combining true FP with OOP, that actually has a huge ecosystem
OCaml has a decently sized ecosystem, I would say it's enough for the vast majority of use cases.
Secondly, you shouldn't use OCaml or Scala for anything. There is no good reason to combine "true FP" with OOP. These languages try to combine everything to make everyone happy but end up butchering both approaches. Every half decent OCaml programmer ends up just never using the OOP features, so what's the point of having a slightly broken syntax with extra bloat? Should have just used sml and not split the ecosystem. And Scala is JVM shit so out the window it goes anyway.
>Should have just used sml
What and not have to spend two decades trying to add multicore support? What's the fun in that?
>Seethe seethe seethe
>Cope cope cope
Meanwhile in reality: scala is the ONLY option if you want to do anything relevant regarding high availability, distributed processing/computing, high throughput/big data or similar
Ask me how I know you've never designed a high availability, distributed processing/computing, high throughput protocol.
>Protocol
Completely different thing you brainlet
Name another then?
>Name another then?
>Distributed computing
Anything with OpenCL bindings
>High availability
Anything that can run on k8s
>Big data/High throughput
Anything with CUDA bindings. But I'll give you this one, there's a lot in the Apache ecosystem that's good for big data.
It's like you learned about Akka, Spark and Haddop and think that's the be all and end all. But these are just tools to make you life a little easier. Ultimately you can do this any language.
>OpenCL
>For distributed computing
Stopped reading right there lmfao you don't even know what you're talking about
>OpenCL
>Literally built for heterogeneous distributed computing
Brainlet
>Literally built for heterogeneous
Correct
>distributed computing
Incorrect
You don't really know what distributed computing is, do you?
Distributed computing is distributing computations over multiple compute units. It's literally what OpenCL was made for.
Not him but distributed computing usually refers to cases where communication is unreliable, so across the internet for example. But you don't use Scala to do it of course, you use erlang.
Might just be a difference in terminology then, I work mostly on numerical projects and spreading a computation of multiple compute units is called "distributed computation" for obvious reasons.
Yea that's a field specific term then, in general it refers to multi-agent message passing scenarios.
I'm willing to admit that I'm wrong on this.
>Distributed computing is distributing computations over multiple compute units
Thanks for confirming. Brainlet doesn't even know the difference between parallel and distributed computing kek
>Completely different thing you brainlet
Ask me how I know you're ESL
>Unironically thinks a protocol is the same thing as applications
>Calls others ESL when he's called out for his stupidity
>Unironically thinks a protocol is the same thing as applications
Except I never said that anywhere.
>scala is the ONLY option
LMAO
Niggas who lick musk's pole all day be like
>Musk
Only because Twitter also uses scala doesn't mean it owns scala kek
Also musk is a pseud btw
>Twitter also uses scala
Oh I was wondering why twitter is so broken all the time, makes sense
Scala is the only reason why Twitter as a concept is able to work at all. Blame the frontend devs for why the UX is shit
I'm talking about backend things, not receiving the correct notifications, receiving them weeks later, tweets randomly not loading and downtime etc.
ahaha, the absolute state of LULZ
Seething c#let I presume? Or even worse, and nodejstard?
I refuse to use either of those languages, so you presume wrong. The only time I touched C# was because I was importing a database from a C# application, it contained a lot of `?` characters in the password hashes because whoever wrote the C# code was too retarded to properly encode the hashes, probably not unexpected of C# users.
So enlighten us, what do you use for backend then
Probably erlang, lua or haskell, depends on what it is. Maybe nim is recommendable but I haven't used it. I want to say Pony as well but unfortunately it seems to be dying.
It's so tiring actually. And of course it's the french. Imagine if all that effort went into sml or at least half of it, things could have been so good.
Golang
Node.js is uncontested, and everything else is a contrarian sperg meme, if you are going to use the same code and datatypes on clientside and on BE.
>public static class Program
>public static void main string args
I thought C# was supposed to be better than java
Verbosity isn't a problem, boilerplate is. You've never used java if you are complaining about such dumb things.
>doing webshit
neither
Golang