Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing Flutter Release Preview 1

medium.com

Post reply on HN
Print view View original

41–50 of 86 posts

Re: Announcing Flutter Release Preview 1

#41

Post by rchrch »

k__ wrote: post #39
mehblahwhatevs wrote: post #36

Earlier quoted context omitted.

Cool - how is the WebView support? I have a project that will require a WebView in the app. Also I downloaded Flutter a while back and noticed a lot of buggy / unintuitive behavior with their TextViews (multi-line specifically) such as with copying and pasting, selecting text, etc. Do you know whether these components have matured?

I found this: https://github.com/dart-flitter/flutter_webview_plugin Looks rather hacky.

I've used this for pop-up dialogs. Works fine and I've had no issues on various sites which certainly have gross amounts of js. It shouldn't be long before the Flutter team provides a WebView widget.

Re: Announcing Flutter Release Preview 1

#42

Post by eksemplar »

mixedCase wrote: post #18
eksemplar wrote: post #6

Earlier quoted context omitted.

I have a different view on it, I actually like Dart. I like the strong types and how the language is more suited for enterprise development than both typescript and JavaScript. There is the added benefit of being able to reuse assets from your mobile app in AngularDart, which I suspect may see an increase in use along with flutter. I’m not coming from Kotlin or rust though, but a .net core backend with JavaScript on…

>is more suited for enterprise development than both typescript and JavaScript. What makes you think this given the library and tooling situation? Is this strictly a "worse is better" thing where lacking modern language features is a plus (at which point I'd argue for Java) or is there a Dart feature that makes you think it's actually an improvement over TypeScript, Kotlin, .NET Core (both C# and F#) or Rust (just to…

I think you misunderstood me. I don’t think it’s an improvement over c# (or Kotlin, but I have no experience with Kotlin so I wasn’t commenting on that).

I think it’s an improvement over JavaScript, Typescript and the Xamarin experience + tooling, with the added advantage of letting you share language in your clients.

I don’t think dart is great though, it’s just better than the terrible alternatives.

Re: Announcing Flutter Release Preview 1

#43

Post by LegNeato »

munificent wrote: post #24
greenhouse_gas wrote: post #5

Unfortunately, I kind of feel torn: On one hand, I love flutter as a concept[1]. It removes a lot of the baroque from mobile development (no need for the whole RecyclerViewer construction for every list! No Fragments! Doesn't require Android Studio to start working!) but I hate the language (dart). After using Kotlin (let alone Rust), It feels like moving back to Java (no non-nullable types) and in some ways it's act…

I'm on the Dart team (though I wouldn't necessarily take my comment to be an official statement of the entire team). > (no non-nullable types) I really wanted [1] to get those into Dart 1 (way back before Swift and TypeScript even existed), but I couldn't convince language team at the time that it was worthwhile. When we moved to a stricter, sound type system with strong mode, we hoped to get non-nullable types into…

> (I'm not aware of any cases where it's been done at this scale.)

Facebook has done it twice at this scale: PHP -> Hack, plain JS -> Flow JS.

Re: Announcing Flutter Release Preview 1

#44

Post by greenhouse_gas »

k__ wrote: post #35
greenhouse_gas wrote: post #28

Earlier quoted context omitted.

The thing is that the longer you wait, the harder it will be to migrate, as the codebase size grows (and once you leave beta, people assume that the language is finalized and won't be too happy being forced to refactor their code when Dart 3 comes out). But as it is, I doubt that the nice parts of Kotlin will ever make it to Dart.

Yes, it's really sad that a language as young as Dart already has such problems :/

It's because the language was made to compile to JS, and competition to JS, so appropriate tradeoffs were made.

For example:

1. JS is single-threaded, with extremely heavy threads only recently made available. So Dart is single threaded, with extremely heavy threads available.

2. JS is weak-typed, so Dart was made optional typed. Remember, it was made before typescript, so they probably didn't expect that such type-heavy features as ADT would interest people.

Kotlin does the same (for example, internal immutability would be much nicer, but since the JVM doesn't support that, neither does Kotlin).

Re: Announcing Flutter Release Preview 1

#45

Post by felideon »

k__ wrote: post #13
pplante wrote: post #4

I've been using Flutter for a few months now, and have not felt this productive in years. Being able to iterate so quickly on real or virtual devices has changed how I design and development a UI. I can set out with a mock-up and almost immediately start to feel why it isn't perfect and just use it until the feel is right. The productivity bonuses are sometimes hard to explain to people who haven't yet tried Flutter…

Sounds like Expo to me. How does it handle native APIs? Like React-Native (you have to write bridges in ObjC/Java) or like NativeScript (you can simply access all native APIs via JS)

See this blog post from last year: https://hackernoon.com/whats-revolutionary-about-flutter-946...

Re: Announcing Flutter Release Preview 1

#46

Post by zerr »

munificent wrote: post #24
greenhouse_gas wrote: post #5

Unfortunately, I kind of feel torn: On one hand, I love flutter as a concept[1]. It removes a lot of the baroque from mobile development (no need for the whole RecyclerViewer construction for every list! No Fragments! Doesn't require Android Studio to start working!) but I hate the language (dart). After using Kotlin (let alone Rust), It feels like moving back to Java (no non-nullable types) and in some ways it's act…

I'm on the Dart team (though I wouldn't necessarily take my comment to be an official statement of the entire team). > (no non-nullable types) I really wanted [1] to get those into Dart 1 (way back before Swift and TypeScript even existed), but I couldn't convince language team at the time that it was worthwhile. When we moved to a stricter, sound type system with strong mode, we hoped to get non-nullable types into…

How did you end up in that team, and how one should apply (in case you have any open positions)?

Re: Announcing Flutter Release Preview 1

#49

Post by frollpin »

pplante wrote: post #4

I've been using Flutter for a few months now, and have not felt this productive in years. Being able to iterate so quickly on real or virtual devices has changed how I design and development a UI. I can set out with a mock-up and almost immediately start to feel why it isn't perfect and just use it until the feel is right. The productivity bonuses are sometimes hard to explain to people who haven't yet tried Flutter…

Dart is by far the most productive cross-platform web technology I've ever worked with. We got the same (quite complex due to the domain requirements) core codebase for web client, IOS, Android, and on the server side is well. Had we chosen to go with the more traditional combination, the effort to keep everything in sync would rise exponentially with the complexity of the project.

Re: Announcing Flutter Release Preview 1

#50

Post by Apocryphon »

frollpin wrote: post #49
pplante wrote: post #4

I've been using Flutter for a few months now, and have not felt this productive in years. Being able to iterate so quickly on real or virtual devices has changed how I design and development a UI. I can set out with a mock-up and almost immediately start to feel why it isn't perfect and just use it until the feel is right. The productivity bonuses are sometimes hard to explain to people who haven't yet tried Flutter…

Dart is by far the most productive cross-platform web technology I've ever worked with. We got the same (quite complex due to the domain requirements) core codebase for web client, IOS, Android, and on the server side is well. Had we chosen to go with the more traditional combination, the effort to keep everything in sync would rise exponentially with the complexity of the project.

What frameworks are you using for the web client and the server?
Post reply on HN