8

When someone writes a Flutter app like it's 1998 and blames Flutter for being "too hard" and "DIfficult"

First of all… WTF?

This guy wrote an entire Flutter app like it's HTML + CSS cosplay. No use of Flutter’s built-in Drawer, AppBar, or BottomNavigationBar. Instead? He manually built his own versions of all of them using Container, Row, and Column, all dumped inside the body. Literal pixel pushing. He made a fake AppBar inside the body. A fake Drawer inside the body. A fake BottomNav inside the body. It's like UI inception. Then he turns around and says “Flutter is hard.”

Bro… you made it hard. Flutter gave you prebuilt widgets. You chose pain.

Zero data structures. No architecture. No MVC.
The only MVC I found was: Multiple Voids in Class.

And the documentation? It's literally been around since 2018. Not even buried, just a Google search away.

Then came the excuses:
“Oh he’s from a Delphi / ASP.NET background, so Flutter is difficult for him.”

No. I’ve coded in Erlang and COBOL. You don’t see me turning Flutter into Erlang’s syntax disaster or WRITING DART IN ALL CAPS like COBOL.

Choose a paradigm. Functional? Procedural? OOP? Fine. Just don’t mix all three into some cursed hybrid mess.

What did I see in the code?

Recursion inside recursion for no reason

Functional programming patterns mixed with anti-OOP logic

500+ functions declared, zero referenced

Authentication by writing to file.txt. Like… bro, why?

And then there’s navigation. He stored route info in both SQLite AND SharedPreferences before pushing a new route. Why both? Why at all?

Honestly, Flutter has been one of the cleanest and most developer-friendly frameworks I’ve used. Dart is readable, fast, and predictable. But somehow this guy managed to turn a simple Flutter app into a twisted assembly simulator from hell.

Flutter didn’t fail him. He failed Flutter.

And yeah — the project folder was named Flutter_UI_Test_FINAL_v2_Rebuild_2023_OK and full of main_old.dart, main_old(copy).dart, main.dart.bak. I should’ve known from the start.

Really.......Some dev are idk what to describe

refer: https://devrant.com/rants/18897167/...

Comments
  • 4
    Keeping all those old versions-does he know people use version control these days?
  • 3
    60 % human rant / 40 % LLM
  • 2
    @TeachMeCode well, it's an app working since 1998. There is no flutter app lasting that long so far. That's how you write software! :D
  • 2
    @tamagotchi he said he’s been writing it as if it’s 1998 and not reaping the benefits of using flutter
  • 3
    @TeachMeCode I know, but I actually do not think it's that bad of an idea.
  • 4
    I want to mix all 3 paradigms now.

    Functional, Procedural, and OOP.

    FPOOP!

    I actually have a book somewhere that talks about mixing functional with OOP. It is kind of interesting.
  • 2
    @TeachMeCode the only version control I found here is Zip File
  • 2
    @YourMom FPOOP....hahahA
  • 1
    Yesterday I had some business with a KnockoutJS viewmodel that didn't use any asynchrony, callbacks, nor lexically captured anything besides the viewmodel instance. Instead, each event had an associated member function and those all decided what to do based on a bunch of boolean flags and enums on the component state. It was the kind of event handling logic you would only be forced to write in C nowadays.
  • 1
    There is one callback actually, sendRequest passes processResponse to fetch. processResponse then decides which request must've been sent and what to do next based on boolean flags in the component state.
  • 3
    flutter is worse than html/css in every single way. Next!
  • 1
  • 1
    @TeachMeCode @TeachMeCode I do not think that it's bad to write like it's 1998. Fun fact, I was writing html components like the real oldschool way - and @BordedDev was like 'what modern!' :P It became retro! :P Snek is soon HTML component based again, for a while it was function based because I lacked a very basic detail regarding extending HTMLElement. I used the shadow-dom just because... used to it? But it's the opposite of what i wanted. When I found out that it's not required, converting everything slowly back again. It's a problem, because I prefer just to leave working code for what it is and move on. I'm not in favor of refactor at all. You always throw hours of maturity away when rewriting something and it's ALWAYS underestimated. Snek looks like a simple app, but i have generated git logs based on changes of the application, It has 823 freaking commits now. While the development of the backend was a breeze, everything is self made. This kept the project fun and going.
  • 1
    @tamagotchi that’s cool, I posted “???” bc I didn’t get what you meant but yeah writing like its 1998 isn’t “bad” at all, I think his gripe was the other dev simply writing terrible code in general
  • 0
    @TeachMeCode that guy obviously did something wrong if a flutter dev thinks he's more than him. Ngl.
Add Comment