I wonder what's the oldest and/or most maligned language that you can use to make a similar comparison that's still somewhat valid...
Kotlin is like TypeScript
31–40 of 49 posts
Re: Kotlin is like TypeScript
#32Earlier quoted context omitted.
Still waiting for web developers to rediscover 90's RAD tooling.
I don't think we're ever going to go back to that. Those UIs were pretty static, i.e. you only created the "initial state" in the UI designer, and then modified it during the application run-time (sometimes even creating new widgets in code), or attached some kind of data-binding models to it. With the popularity of things like React, you now have a powerful way to express how the UI looks in every state, not just th…
Now we just need something which would take care of the 'R'.
The time you needed to develop an app with those 90's RAD tools wouldn't even be sufficient to setup the build pipeline for those trendy JS frameworks.
Re: Kotlin is like TypeScript
#33Earlier quoted context omitted.
Still waiting for web developers to rediscover 90's RAD tooling.
I don't think we're ever going to go back to that. Those UIs were pretty static, i.e. you only created the "initial state" in the UI designer, and then modified it during the application run-time (sometimes even creating new widgets in code), or attached some kind of data-binding models to it. With the popularity of things like React, you now have a powerful way to express how the UI looks in every state, not just th…
I will only agree, the day someone makes a RAD based React WYSIWYG editor that can at very least compete with Microsoft Blend, Android Studio or XCode just to give a few examples.
Re: Kotlin is like TypeScript
#34Earlier quoted context omitted.
Still waiting for web developers to rediscover 90's RAD tooling.
I don't think we're ever going to go back to that. Those UIs were pretty static, i.e. you only created the "initial state" in the UI designer, and then modified it during the application run-time (sometimes even creating new widgets in code), or attached some kind of data-binding models to it. With the popularity of things like React, you now have a powerful way to express how the UI looks in every state, not just th…
I'm 100% we are.
Step 1: People realise that Electron apps look different and do not fit the OS.
Step 2: Big company invests and creates a library that supports Win/OSX looks.
Step 3: Same big company creates a RAD type tooling for it.
We present you a revolution - Big Corp. RAD Tooling 2020 a la Borland Delphi 2007.
Re: Kotlin is like TypeScript
#35derived from Swift is like Kotlin: https://github.com/Nilhcem/swift-is-like-kotlin
let x = 1
const x = 1
val x = 1
var x = 2
It's unfortunate each language has a different keyword for constants and variables.
Re: Kotlin is like TypeScript
#36name: string; constructor(name: string) { this.name = name } You don't have to do this in TypeScript either, you can just do constructor(public name: string) { } Also, the "Empty collections" section doesn't do the same thing, the collections you created in Kotlin are immutable. And the TypeScript ones have the value `undefined` (unfortunate that strictNullChecks doesn't catch things like that https://github.com/Micr…
Some of the TS examples also include an external library (lodash) to compare features; not sure if that's an apt comparison.
Re: Kotlin is like TypeScript
#37This is getting ridiculous
Kotlin getting love, this is nice, although in a very peculiar, syntax-comparison type of way.
Re: Kotlin is like TypeScript
#38Earlier quoted context omitted.
I don't think we're ever going to go back to that. Those UIs were pretty static, i.e. you only created the "initial state" in the UI designer, and then modified it during the application run-time (sometimes even creating new widgets in code), or attached some kind of data-binding models to it. With the popularity of things like React, you now have a powerful way to express how the UI looks in every state, not just th…
I'm 100% we are. Step 1: People realise that Electron apps look different and do not fit the OS. Step 2: Big company invests and creates a library that supports Win/OSX looks. Step 3: Same big company creates a RAD type tooling for it. We present you a revolution - Big Corp. RAD Tooling 2020 a la Borland Delphi 2007.
>Step 1: People realise that Electron apps look different and do not fit the OS.
This is not an issue for most people. I like to use Spotify (the desktop app) as an example - it's a pretty good looking app, works nicely, and yet it uses an HTML-based UI.
Microsoft's own UWP also looks vastly different than native Win32-based apps.
The resource usage and slowness of Electron apps is a problem, but that is caused by using the entire browser runtime. When it comes to the capabilities of a UI framework, one of the questions I ask is "Could you build something like Spotify's UI with this? How difficult would it be?".
Re: Kotlin is like TypeScript
#39[deleted]
Re: Kotlin is like TypeScript
#40TypeScript has structural typing, that is a HUGE difference.
Yes, that would be its biggest differentiator. Scala has it too indeed, but it's not the default mode and feels awkward, also has known limitations. The nice thing with typescript is that structural typing makes sense for 90% of the use cases, and for the remaining 10%, you can very easily simulate nominal typing by adding a field like so: interface Robot { __Robot: true }
>interface Robot { __Robot: true }
I would much prefer if they just added a new keyword to the language, instead of hacks like this.