Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
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/...10 -
In Kotlin, I love sealed classes. They're beautiful. The compiler knows every possible subtype. When you use a when expression, it forces you to handle every single case. It's a closed, predictable, and exhaustive world. You can't have a random, unexpected state popping up at runtime.Then I look at my career. My path isn't a neat set of predefined subclasses like JuniorDev, SeniorDev, TeamLead. It's a chaotic mess of SideProjectThatBecameCritical, AccidentalSysAdmin, TemporaryScrumMaster, and ThatTimeIFixedThePrinter.The "when" expression of my professional life has a million unhandled branches and the compiler is screaming at me that there's no else block.
I just want a way to document all these weird, unexpected states so they look less like a series of runtime errors and more like a feature set.6 -
Getting predictable... Deadline day and developer takes day off sick. Or day before deadline developer takes day off sick. Leaving it all to everyone else to clean up their mess... Same people every time...1
Top Tags
Weekly Rant
View