@joaoao yeah, just created one, whale-compose

@mohammed *grabs 🍿 while waiting for them*

I would say the same if guys wore high heels!!

@gitpush this did it for me

VBoxManage setextradata "vm name" "VBoxInternal2/EfiGraphicsResolution" "1920x1080"

@gitpush I was able to change the resolution to 1920x1080 in VirtualBox by using the VBoxManage command

@magicMirror I use fastlane as well. The problem is in compiling an app. If i change a freaking background color, I need to wait 4 mins to see it

@gitpush i'll probably do that. The same happens with gradle. Takes so much time..

I'm thinking of buying a good laptop (something between 1k - 1.5k) and use mac on a VM.

@gitpush the problem is not in uploading the app but in building/compiling it. Need to wait around 4-6 min each time.

@gitpush well since my VM runs faster than my macbook it would be cool if it was possible. I wouldn't need to spend 2 month salary on a laptop

@obritoluis can we introduce the concept of Decentralized food?

No problem.. At last some notifications on my phone #sad #foreveralone

Probably they're trying to tell you that flutter is not for web dev

@Nino9612 At least for me, while coding, any type of music that doesnt have lyrics its good

Don't get me wrong, I'm a native mobile developer and I would love to keep doing that. But, at least where I live, clients are not willing to pay the price of native app for both platforms

Frameworks like Flutter and React Native (and probably some other framework that will show up in the near future) can do what native do. Not yet with the same performance but I'm guessing someone eventually will solve that.

As happened with web development, the cost of it decreased with time and I think the same will happen with mobile development. Companies are not willing to pay for two engineers when they can have the same job done with one.

Yes, it does not support data binding out of the box but you can always use something like ReactiveKit. I used MVVM for some projects but started noticing, at least for ios, the view model have too many responsabilities ( api requests, business logic, saving persistent data, table views data source, etc..). Because of that I've started to use a more clean approach and decided to start using VIPER pattern. Its the swift clean architecture and it's only architecture that takes navigation into account (correct me if I'm wrong pls).

Also because of that I've began to use it in server-side as well.

Things like type-Safety, type-inference, property observers, etc.. Also, because it is protocol-oriented you can easily write reusable and more modular code. And then it is a very readable language. You can easily understand what's going on.

Definitely not Xcode. It is still optimized for Objective-C. Those compile times are a joke.

Well the issue was not the presentation itself but what they were talking about.

It's very difficult, if not impossible, to prepare a good presentation with such an abstract subject.

Don't be shamed m8.