Kotlin

Gotenks, Kid Trunks and Goten are annoying as hell, definitely not amusing and 100% cancer. They together with the whole majin boo arc, db gt, dbs, lolis and probably half of all other animes/mangas are prime examples for why two nukes weren't enough.

When it beats Node.js, so never.

lmao nodejs is shit

Vert.x makes it looks like the absolute toddler toy it is. I imagine any company pouring money into nodeJS will regret it in 3-5 years if they don't already.

Trunks (at least future Trunks) is one of the best characters in the whole franchise. He is the third strongest saiyan, he has a nice waifu and he is a seasoned veteran warrior.

>Kotlin
lol.. Kotlin is Scala for brainlets.

/thread

You can list the differences using your fingers.
It tries to copy C# features except with a shitty syntax and restrictions of the jvm.

Both are pretty shit and had to be reimplemented for the open source community when devs realized that walled gardens and proprietary security suck. If more brainlet programmers were responsible enough for C++, those languages would have died out long ago.

Attached: deadatcomputer.gif (400x267, 152K)

Majin Buu arc was amazing why do cucks insist it was bad?

I strongly disagree but

>They together with the whole majin boo arc, db gt, dbs, lolis and probably half of all other animes/mangas are prime examples for why two nukes weren't enough.

Holy shit, I laughed. I'll definitely going to drop that one to irritate weaboos if necessary.

Based nuke user

I bet his distaste comes from power level porn inserted into Majin Boo arc and so on. DBS took that to a whole other level -- to me even making Majin Boo arc acceptable.

C# hasn't been reimplemented in the open source community. Microsoft decided to let the C# and dotnet teams out of their cage and the result is roslyn, dotnet core, and vs code.

C++ is dangerous for all developers and should be reserved for performance critical code. Even extremely good developers let the occasional use after free or other boneheaded bug past them. In higher languages, bugs usually cause exceptions. In lower languages bugs usually cause security vulnerabilities.
And contrary to the circle jerk, using a language with no memory safety does not make you a more "real" developer. Knowing your shit, being a polyglot, and using the right tool for the job is what makes you a real developer.

Even though Kotlin is a better and has more modern features. The reason that Java (and its clone C#) will maintain dominance in enterprise programming is because forced classic OO is so easy to reason about when you are dealing with huge code bases being worked on by thousands of programmers. Kotlin (or Swift, or Go) would make large code bases unmanageable as it introduces more personalized imperative and functional code styles that wont mesh with other peoples code.

Java cannot be beaten it is in use by too many vital systems

>use a generic graph query language to replace an arbitrary resource specification schema based on HTTP
???

>static typing
>everything is auto
What the fuck is this?

>pleb doesn't understand type inference
Wait until you use F#, your puny mind will be blown away

Oh no I understand type inference you CIA nigger, I'm telling you that in a statically typed language forcing people to use it is fucking retarded.

>pleb claims to understand type inference
>actually doesn't
nothing new under the sun
enjoy overloading the same function for every type you can imagine

Oh buddy you sure are a fuckin stupid one aren't you. What I'm saying is that not allowing me to say "This is an unsigned char" or "This is a 64-bit int" means that, if certain functionality relies on the implementation details of a type, you essentially have to revert to fucking hungarian notation so that people will know what type a variable is supposed to be. All this auto meme shit is fine and good when you're working on a small codebase but in a corporate setting you're totally fucked. Try explaining to pajeet why he can't just re-use your Add function on his new class. It's a fucking exercise in frustration.

If you want to work in the nitty gritty of types and live in the world of bitmasks and shifts then go use C, you nigger. People who have deadlines and need to get shit done will live without worrying if their int is unsigned or 32/64 bits

Any feature worth using in C#, Kotlin can do better.

>He didn't know that /a/ and /b/ pioneered the two nukes joke in a raid, and thus can't be irritated by it.
It's still a good classic though.
>Either Mono didn't historically reimplement C# or the MIT license isn't open source.
>Fire is dangerous and should only be used in engines, not cooking.
There is a reason why I specifically criticized about responsibility user. Also the abuse of unsafe pointers and precompiler directives have been in decline for some time, due to the standard finally adapting features from other languages. Two such examples are the standard containers implementing functions to execute lambdas on each element, as well as monads. C++ is clawing it's way back from it's exile to vidya and microcontrollers, and the time to reeducate devs about not drinking and programming is running short.

Attached: 1477555148630.jpg (546x896, 82K)

Baka. Mono is an implementation of a C# compiler and the CLR. It was mostly developed by Xamarin which is now a subsidiary of Microsoft. It's the equivalent of openjdk and was only made because Microsoft took like 15 years to understand that maybe this Linux thing is going to take off.

Cooking on a grill or stove is fine. Lighting a fire on your kitchen floor is not. Analogies suck. You will make errors. C++ makes it trivial to accidentally fuck yourself over. Bolting more bullshit onto a language that was originally "C, but with a bunch of bullshit bolted on" won't make it better, it just makes it even more of a clusterfuck and makes long term maintenance of a C++ codebase that much more of a minefield. Want C++ but safer? Unironically use Rust. It has all the safety with none of the room for accidently invoking nasal demons. Want comfy development where the language gets out of your way but gives you 80% of what you need for a typical job? Use C#, Java, fucking golang, whatever. Not C++. You might as well be writing COBOL for how utterly deprecated it is.

C# and Java have proofable safety and that is the future.

i'm a java dev i hope it never dies
:^)

Even if Java dies, there's going to be a ton of old Java software that needs to be maintained. Java would probably be like the new Cobol.

Fuck off to /a/. This is technology board.

>even nodejs shits all over...
HAHAHAHAHAHAHAHAHAHA

This is an anime website, faggot.

oh btw netflix is migrating 1/2 of the infrastructure to node.js, but yeah what do they know

sorry, got to go back to earn my $8k/month remotely writing JS fulltime

This is an alt-right website. Anime is for losers.

Fuck off Piccolo

heh

Attached: Untitled.png (402x301, 28K)

alt-right is full of pedos so they LOVE anime

also haskelljava

Attached: ss-2018-05-10-11-02-48.png (471x150, 6K)

Never, it literally can't exist without Java

Prove it. Anything in C# kotlin does much worse
Example: nullable types in C# are followed by one ! whereas in kotlin they put two !!.
The naming is inconsistent and type erasure is not going anywhere. pjeets know nothing about designing a language. Stick to lagdroid

Oops I mean ? for C# and lots of different garbage for kotlin including the !! operator.
The JVM sepples going functional-ish

but Kotlin was designed by russians

>Example: nullable types in C# are followed by one ! whereas in kotlin they put two !!.
Non-nullable reference types (e.g. the types you're actually going to be using 90% of the time) do not exist in C#

Can't you do like val stuff : type = ... ?

>This is an incel website
No, sorry, that's just Jow Forums

It is supposed to be added in C# 8
I am against it because it is exactly the same bullshit as checked exceptions.
It is supposed to give warning though in C# and not errors unless you decide to enforce it in some setting.
Also, the syntax for non nullable is ! and for nullable ?
! for NOT nullable
? for maybe null?

Imagine being this gay lmao

Checked exceptions are a good thing, you lazy slob.
>Also, the syntax for non nullable is ! and for nullable ?
>! for NOT nullable
>? for maybe null?
And people say C# isn't a C++-tier mess.

As opposed to what? Java? Where Integer can be null by default and cucks you out of simple types like unsigned because 'not kosher'? Or kotlin where you have to write !!!!!!!
Enjoy your memes. C# design team always picks the sane way to enable the dev to write code that expresses his intent.

>Foo is a nullable class
>Foo! is a non-nullable class
>Bar? is a nullable struct
>Bar is a non-nullable struct
If you can't see the problem here there's no saving you.

Also, checked exception are shit just like your PL
>artima.com/intv/handcuffs.html

>Foo is always nullable le Null(((Pointer)))Exception
>There is no Bar struct
If you don't see the problem, there is no saving you.

An API which doesn't document the exceptions it may throw is a shitty API. The only difference with checked exceptions is that it enforces the correctness of that documentation.

Being simple and gimped is better than being complicated and inconsistent.

It ensures absolutely nothing useful at all.
It is just handcuffs.
>simple and gimped
Java is neither. Kotlin is a just suitable java for android needs.
Java is the epitome of inconsistent standard library and half baked features.
All this non nullable and nullable mess doesn't even matter most of the times.
Its use is only where makes sense.
Java Boolean can either be true, false or null which makes no sense at all!
bool is either true or false. A nullable bool is a tristate which should be only used when needed like opening a dialog box and getting a bool? result indicating what happened (true, false, undefined).
But you are out of luck because you got your baby duck syndrome on java. Poor user.

>It is just handcuffs.
You might as well claim that returning a value which isn't Object is "just handcuffs" because it limits the evolution of your API. Knowing what your method throws is exactly as reasonable an expectation as knowing what your method returns.

Have some discipline you fucking code monkey.

Isn't kotlin kill, arent they ditching it for flutter

Kotlin wont replace c#, but I can wish it to replace Java, its a step in the right direction for it.
But with the amount of legacy Java code around, its here for good. It will be the new COBOL.

ITT: No one has a clue what they're talking about. At least be informed about upcoming features before starting arguments about them

blogs.msdn.microsoft.com/dotnet/2017/11/15/nullable-reference-types-in-csharp/

string firstName; // Not null
string? middleName; // May be null

You clearly haven't used anything other than guava and apache.
The real world java is not your perfect useful readable documentation you pretentious faggot.
Stick to you inconsistent libraries, useless over makeup and kosher that you don't get to decide.
Most of SO java questions are literally NPE because your 'simple design' is all shitty objects. Nothing is what it means. List is an interface, interface is not a contract, Integer can point to null, strings operators are magically overloaded, == compares references for strings, Boolean is not only true or false, and generics but with type erasure! Nice meme.

Nice cherry picking. Those are discussions about the future of it and are not implemented or finally decided yet.

I seriously doubt they'd go to all the effort of implementing and releasing official previews of it without things being pretty much decided already.

github.com/dotnet/csharplang/wiki/Nullable-Reference-Types-Preview

Then you have no idea what you are talking about.
Proposals of many F# features reached high in the design list and they had it almost working with prototypes but knocked it off because it was inconsistent.

>Kotlin
>take off
pick one

always funny to see science degree cucks afraid of stuff like php or node.

>List is an interface
Which makes perfect sense. List is an ADT, not any particular kind of list. Why it this a problem?
>Integer can point to null
>Boolean is not only true or false
All reference types have the same behaviour. Making exceptions is the stupid thing to do.
>strings operators are magically overloaded
This is actually bullshit.
> == compares references for strings
Once again, consistency is the goal here. What does == do for two objects in C#? You can't know unless you check their definition of the type. Operator overloading is questionable but it's especially bad with reference types and no referential transparency.
> generics but with type erasure
This is bullshit.

Hmm this actually might be a better idea than using !
It still isn't decided though.

>being this mad
>unironically defending misfeatures
Stop being a tubro lang babby. Your PL is objectively shit and you have to swallow it.

>unironically defending misfeatures
That's the domain of Csharts with inconsistent operator overloads, inconsistent reference/value semantics and inconsistent nullability though.

What ever makes you sleep at night when looking at those sour grapes

I use Racket, I don't care what you OOPeasants have to deal with. I'm simply stating the truth that Java is consistent and readable where C# is bloated and intractable.

>(((Kotlin)))

>animeme website
>butthurt when people talk about anime

woah, what a fag!

contrarians and nostalgia fags

>claims she uses FPL
>says java is more readable and consistent
youtu.be/qlOTNtUvhe8
No further proof needed. You don't have a programming job. You have never touched racket. You have never used java in production for job. You never used or read about C#.
You are just a silly underage who asked dpt/sqt for easiest PL to learn and book resources who thinks effective java is a good read.

Once android 8 and 9 are on majority of devices. So, 3 years from now.

>Android 9
Fuchsia and dart.

fuck off weebs

How is it nostalgia when it came out immediately after the cell games? It was just shit, buu was an okay villain but they didn't do any good by having all the other new support hero characters that were God awful

GraphQL obsoleted REST

>Historically was used as a clear modifier for the point.
>Point out that Microsoft panicked and bought up an upstart company in order to not eventually have to compete with them on their own platform in the future.
>Still doesn't negate the fact that mono is MIT licensed.
Have you no shame in sucking a company's anticompetitive cock? High quality compilers for feverishly protected enterprise languages don't just come from nowhere, they require someone footing the bill to hire dedicated, competent, and experienced developers. The fact that a company was bought out in order to control it and to protect microbucks is an indictment of C#.
>He thinks lethal house fires don't happen from stove mishaps already.
Saying that most people should prefer (by default) using their microwave does a disservice to the microwave itself just as much as it does for chefs and cooks. People need to learn that danger inherently comes with power, and be acclimated to it in order to use the lion's share of libraries in the broader ecosystem. The fact that a massive amount of websites were crippled by a popular library not meshing well with a bug fix is an indication of the danger faced by centralizing toolchains. Running away from the upper foundation of software development is impossible if you actually care about your comfy languages.
>Well known and respected features from other languages that incentivise safer development by being more approachable or adaptable is somehow not inherently good.
So this is the power of enterprise programming.
>Unironically engaging with Jow Forums
>A population that is a subset of two other populations implys that the majority of the other two populations are subsets of each other
>Insulting both in an ambiguous defense of one of them.
wew. It's no wonder why Jow Forums has a bad reputation.

Attached: HyperCincinnatusPressiotism.png (2414x648, 17K)

Jesus christ take your pills

no u

The nukes don't prevent anime
Because the nukes CAUSED anime.

>> generics but with type erasure
>This is bullshit.
Did they change how generics work in java? Last time I've checked, you couldn't do something like
class Factory {
T create() {
return new T();
}
}
because of type erasure.

>i'm a java dev i hope it never dies
I hope Pajeets programmers die painfully

Attached: She.gif (656x288, 69K)

> SOME MEDIUM POST TOLD ME THAT REST IS DEPRECATED BECAUSE ITS AND GRAPHQL IS THE NEW TRENDY TECH XDDDD I'M SO MODERN

KILL YOURSELF

Attached: raf,750x1000,075,t,fafafa_ca443f4786.u1.jpg (750x1000, 49K)

Attached: 1516486590564.jpg (602x709, 103K)

Flutter is a toolkit
The language is Dart
Kotlin can be natively compiled and might actually be Flutter-compatible
It's up to JetBrains to figure that out though

async

No, I'm agreeing with you. What you described doesn't work, and that's one of the few criticisms I think actually holds.

>He doesn't know programming is a woman's job and not a man's.
user should not be wrong in assuming we're all little girls here.

Attached: 30261598_p0.jpg (1200x848, 691K)