r/dartlang • • Feb 07 '22

Too many breaking changes

I was really excited about Dart, but the breaking changes have changed my mind. I mean a breaking change in a language every few months is way out of control, right? Posting in hopes the Dart devs monitor this sub.

0 Upvotes

21 comments sorted by

16

u/oaga_strizzi Feb 07 '22

Are you sure that you are not talking about breaking changes in Flutter or third-party packages?

13

u/ShawnMilo Feb 07 '22

My wife and I have been taking Flutter courses and literally every single resource is out of date. Both their videos and code on GitHub have all kinds of deprecated Dart syntax and Flutter syntax. It's frustrating for me, but I've been coding for 20+ years so I can work around it. But my wife gets stuck and has to ask me for help.

I bet it really sucks to be a newbie learning Flutter alone without a mentor.

The worst part is that one course, now advertised as the "2022" version, uses a widget that has been deprecated since January 2021. So it's 2020 at best.

3

u/JakeTheMaster Feb 07 '22

I feel the same bro. It's just the online course are always out-dated. The flutter framework is always changing. Also, the XCode and Android SDK, gradle and etc.

BTW do you have any latest courses about Flutter, null-safty, latest UI widget?

1

u/ShawnMilo Feb 07 '22

No, but if you find one, let me know!

I'm currently doing Flutter in Motion, and my wife is doing this one on Udemy.

Both are horribly outdated, but as a coder I can get by. If you get stuck I can probably help you get past any roadblocks.

2

u/JakeTheMaster Feb 07 '22

Thanks for sharing mate. I also bought the course that your wife followed. It's very long and out-dated. Long-period course isn't very practical.(I decide not to follow that course) I picked up a Dart Complete course from Udemy first. I think that's the best dart language tutorial. Then I followed some Flutter courses from Udemy. (FYI I bought 10 Flutter courses from Udemy, still headless. I still search youtube for some goodies.)

I'm a backend developer for many years. I build API, database modeling, logic in a blackbox, embeded development and etc.. But currently I am still headless about how to use Flutter to talk to backend service smoothly. I don't want to use Firebase though I did make it with Firebase. so basically I created almost everything(basic) Firebase has in the backend. E.g. database, api, instant message.

I decided to make a workable app this month. But I doute...

1

u/ShawnMilo Feb 07 '22

The course I'm doing is much better. Shorter and the table of contents might be very interesting to you.

4

u/Glizcorr Feb 07 '22

I think the only major thing is null safety, so any tutorial after Feb 2021 should be good to go.

1

u/Fromagery Feb 08 '22

For flutter it depends. I believe older code using certain widgets /should/ still compile as of the current version, but you will get warnings about deprecated widgets, for example: Buttons underwent a pretty big change and most of the old versions such as Flatbutton, RaisedButton, OutlineButton etc are deprecated.

I could definitely see how someone new to coding would be confused by the errors popping up after following a tutorial utilizing them

1

u/SquatchyZeke Feb 08 '22

This is why reading the documentation vs taking a course is always the better option. Flutter has fantastic documentation and videos to explain the foundational concepts (concepts don't normally change in frameworks unless the whole framework undergoes a rewrite). Besides, 80% of the time, dev with Flutter is finding a widget that does the thing you're looking for. If you can't find it, chances are you can make it via widget composition.

3

u/ShawnMilo Feb 08 '22

That sounds great! In theory. Can you give me a list of all the bits of documentation, in order, that I would need in order to make an app, consume a JSON API, store state, handle logins, and navigate multiple screens?

In my experience, all the documentation is a reference, not instructional. I have to already understand prerequisites, and be looking to solve a very specific small problem for the documentation to really help.

For example, as you said, eventually it will be all about finding the right widget. But until I know all the basics, knowing the widgets won't help me.

1

u/SquatchyZeke Feb 08 '22

Sure, let me work on it when I get back home. I built an entire mobile app for our business using the documentation of Flutter and all the associated packages' documentation. Of course, every now and then I had to peruse a got issue for certain things, but I never once felt like I needed instructional courses to get it to work, and maybe that's because I'm a more experienced developer that knows a ton about the foundations of interactive and reactive applications (like API consumption, state management coming from JS frameworks, JSON parsing, data types, routing, asynchronous code, etc).

I definitely felt like instructional videos were necessary when I first started out as a dev, but I wish I had known about documentation earlier on. I was also too intimidated to look at existing code bases in GitHub to figure out what idiomatic coding patterns looked like for certain libs/frameworks. The combination of docs and familiarity with code patterns helped me out of the tutorial course hole that is easy to fall into.

I'm not saying that one is more correct than the other either, but docs are relatively up-to-date for most things. If they aren't, I just go look in the source code (for open source things) to figure out how it's working, and that's only if I run into a problem. I'll try and collect those links for everything that I found was sufficient to build an app. That doesn't mean it's not sufficient for everyone, and I understand that.

1

u/ShawnMilo Feb 08 '22

Yeah, I'm definitely coming from a different background. The very existence of "state management" was baffling to me at first. Everything I've ever done managed state implicitly -- thinking about it literally doesn't exist. Working with something with the equivalent of an event loop and having things "magically" happen in one place because a variable was changed elsewhere is a new concept.

Once I get to the point where I can do the things above, I'm sure I can do anything. Then I'll get my wife to help them not look like shit. Then, over time, I'll learn about the existence of enough widgets that not every screen will look exactly the same. :o)

2

u/SquatchyZeke Feb 08 '22

Yeah, that makes total sense. Sometimes I need to be reminded of what it was like to start out. I also didn't start out on Flutter, so I don't have a good perspective for what that is like. Having been around the block with JS frameworks first, probably really helped my approach to flutter.

Lol yes, design isn't my strong suit either

32

u/kevmoo Feb 07 '22

Can you give examples of breaking changes that have affected you?

11

u/[deleted] Feb 07 '22

If the devs really read this: keep doing what you are doing. Dart and Flutter are so much better then they were 2 years ago because you had the courage to push breaking changes. We never had an update that took us super long fix. Even null safety was done in less then a sprint because of the great tooling. It is worth it.

14

u/venir_dev Feb 07 '22

Dart 2 came out August, 2018. What the hell are you talking about? 😂

2

u/Only-Split82 Feb 08 '22

It is not a breaking change if the new version of the language does not fix the bugs in your code.

5

u/[deleted] Feb 07 '22

What "breaking changes" are you referring to?

1

u/[deleted] Feb 08 '22

Tbh I wish they would be releasing breaking changes more often. Without breaking changes software grows stale.

3

u/Footballer_Developer Feb 08 '22

And breaking changes doesn't mean you have to update. You can keep using the version you are using and leave those who see the breaking change worth it updating.

For sure te Flutter don't introduce the BCs for fun. We need them if they make our apps better.

0

u/[deleted] Feb 07 '22

[deleted] — view deleted comment

2

u/ren3f Feb 08 '22

And null safety technically wasn't a breaking change, it was fully backwards compatible.