25 ms·
I feel like I made a mistake investing professionally into Flutter
- keyle 3y agoThe mistake is believing that you can ever stop learning. 20 years I'm doing this professionally, 20 years I'm learning.
- 0x445442 3y agoThe mistake OP is referring to is spending too much time learning the wrong thing which is easy to do in the Cargo Cult that is modern Software Development.
- Barrin92 3y agoThere isn't really anything to Flutter that stands out as so unique it wouldn't translate. Dart is not opinionated, sort of as if you threw every Algol family language into a blender, and the component/reactive style is just like any other modern framework. it's arguably one of the strengths of Flutter, regardless of where you come from there's nothing esoteric to it, so it's not like you learn the wrong thing. Learning Programming isn't about memorizing APIs or libraries, it's about concepts. If you've done Flutter for several years your experience translates just fine to say React native, you just gotta learn Javascript
- the_only_law 3y ago> Learning Programming isn't about memorizing APIs or libraries Maybe not, but interviewing often is.
- edem 3y agoI wonder why anyone thinks that learning a library that's written in a dead language is a good idea.
- thowrasdf23 3y agoRight? The community has been quite honest on its wants/desires for dart with little progress in 10+ years. Thankfully Skia+React metaphors are being actively developed in more mature and healthy language ecosystems.
- cageface 3y agoDart has been evolving rapidly. It remains to be seen if Google will stay committed to it but you can hardly call it dead today. https://medium.com/dartlang/announcing-dart-3-53f065a10635 https://medium.com/dartlang/announcing-dart-3-53f065a10635
- sgammon 3y agoYou did — blame Google for breaking their promise to you and to users.
- Aulig 3y agoAs the comments on the post say - it's most likely due to the generally slow job market. 3.5 years later I'm still glad that I chose to use Flutter in my business.
- deleted 3y ago[deleted]
- merrvk 3y agoYou could say this about any Google technology.
- rvz 3y agoI know right? Just like Golang, Kubernetes, Chrome APIs, etc /s
- sgt 3y agoThey're even keeping GWT alive somehow. That was a major mistake, though. I remember building a large GWT project and the compile times just started getting into multiple minutes. Debugging was hard.
- invalidname 3y agoThey are not. It's a third party fork that's keeping it alive. It's dead because Google didn't put any resources into it and just threw it out to see if it sticks. Then didn't keep up with the capabilities of JavaScript frameworks and didn't release any proper templates.
- nailer 3y agoDid gmail migrate off GWT?
- invalidname 3y agoIt never used GWT. They claimed GWT can be used to build apps like gmail and that was misleading. They didn't write it using GWT since it predated the existence of GWT.
- sgt 3y agoWhen I checked 2-3 years ago, Google Cloud portal was based on GWT.
- 3y ago
- nprateem 3y agoWell that's why you should always keep tabs on what's in demand and switch stacks if necessary.
- zigzag312 3y agoDart is my biggest issue with Flutter. It's still missing ergonomic features like data classes and lower level things like unsigned 64-bit integers. There is no runtime reflection, which I think is a good thing for end user apps, but it's also missing static metaprogramming. And code generation is not integrated into a complier. Since, there is no runtime reflection, metaprogramming & integrated code-gen are sorely needed. Flutter itself is slowly reaching maturity on mobile and is already quite good, if you can live with a few compromises.
- sgt 3y agoIt may lack things - true. But it's a pleasure to work in. I code quite a bit of Dart these days and the language never really holds you back. It flows quite easily. I use some code generation by having a build runner in the background.
- skybrian 3y agoI'm wondering how you deal with the pile of constructor calls needed to construct views in Flutter? Deeply nested expressions remind me of Lisp. JSX is conceptually the same but somehow seems easier to read. Maybe it's the close tags?
- satvikpendem 3y agoI use the packages flutter_hooks and functional_widget. They remove most of the boilerplate required for Flutter.
- pzo 3y agoI'm wondering about this as well, actually this weekend been doing Flutter 'Test Drive' of their tutorial and experience was not that great. I'm still forcing my brain to parse this complex structure with very simple widget structure from their samples. Its Flutter: ``` class MyHomePage extends StatelessWidget { @override Widget build(BuildContext context) { var appState = context.watch<MyAppState>(); var pair = appState.current; return Scaffold( body: Center( child: Column( mainAxisAlignment: MainAxisAlignment.center, children: [ BigCard(pair: pair), SizedBox(height: 10), ElevatedButton( onPressed: () => appState.getNext(), child: Text('Next'), ), ], ), ), ); } } ``` versus SwiftUI: ``` struct MyHomePage: View { @StateObject private var appState = MyAppState() var body: some View { VStack { BigCard(pair: appState.current) .padding(.bottom, 10) Button("Next") { appState.getNext() } .padding() .background(Color.blue) .foregroundColor(.white) .cornerRadius(8) } .frame(maxWidth: .infinity, maxHeight: .infinity) .padding() } } ``` versus React Native: ``` const MyHomePage = () => { const [pair, setPair] = useState(/* initial pair /); const getNext = () => { // Logic to get the next pair // You'll need to implement this function }; return ( <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}> {/* Replace BigCard with appropriate React Native components */} <BigCard pair={pair} /> <View style={{ marginVertical: 10 }}> <Button title="Next" onPress={getNext} /> </View> </View> ); }; ```
- bibabaloo 3y agoAre mobile stacks so specialised that it's difficult to switch between them? Out of curiosity, how long would it take a flutter dev to become productive in some other stack?
- nikanj 3y agoThey are not, but HR / hiring managers are keyword based and won’t entertain the idea of hiring someone with the wrong experience. See also: https://versastudio.com/blog/if-carpenters-were-hired-like-programmers https://versastudio.com/blog/if-carpenters-were-hired-like-p...
- FirmwareBurner 3y agoIt's the same in every other stack/programing language/technology when you go through the default channels of HR/recruiters. It's not that competent engineers can't become quickly productive in a new/stack language, it's that business don't understand that and/or don't want to risk it with switchers, and so prioritize hiring only those already experienced in that stack, creating employment bottlenecks where there's simultaneously a shortage and enough people willing to switch. Same when talking to recruiters: "oh you only have experience in X (which is similar to Y), sorry but the hiring manager said (s)he wants someone with at least 3 years experience in Y". Your only escape is having a solid network so you can push your resume directly to hiring managers who understand technology and your adaptability, and this way bypass the hiring shit-show.
- tkiolp4 3y agoC’mon. HR doesn’t have a clue of what they’re asking for. Anyone with a little of experience in the IT industry knows that: 1. You’ll need to put whatever is needed in your CV to pass through HR 2. You can explain yourself to the actual tech people who interview you in the next stage. For example, if you know Ruby and RoR, but there’s an excellent opportunity to work in a cool product for a company that does Python and Django, well, apply! Obviously you’ll spend a couple of days with Python and Django and notice the similarities and differences with Ruby and RoR. You will add to your CV the keywords Python and Django and you’ll get pass HR (if HR asks you about your experience with such tech stack you can always say that, indeed, I have plenty of experience with MVC web frameworks and blah blah blah). When you pass to the next stage of the interview and get to talk to real engineers, then you can explain that you have many years of experience working with RoR and that learning Django will be a pleasure.
- PedroBatista 3y agoObviously I feel the pain of the OP but I think he blames the wrong thing. Flutter is a ( viable ) technology that’s being growing for the last few years. A very significant percentage of new mobile apps are programmed with it these days. It seems his problems have everything to do with the local job market and not the technology. With the added bonus that you can be a single man operation and release your own apps for both iOS, Android and the desktops. I’m not a fanboy and even less of Google but Flutter really offers the ability to make lemonade if the job market gives you lemons.
- candiddevmike 3y agoFlutter is pretty old if you think about it and still has too many rough edges and not a lot of big name adoption. The project is too ambitious, and the features seem more like PoCs than something you can rely on in production, IMO.
- bmitc 3y agoThis is what has prevented me from diving into Flutter for a personal project. Although it supports desktop and web, it is first and foremost a tool for building mobile applications. For desktop, too much of the API is built around the assumption that you are on a mobile device with a single window and a finger as the pointing device. Feature requests for desktop, such as proper support for mouse-based drag and drop and multiple windows, are either ignored or take forever to develop. Any platform that tries to support web, mobile, and desktop all at once, of which there are many, are destined to this fate of being spread too broadly and thinly.
- pohuing 3y agoWhat do you mean by mouse based drag and drop? As far as I can tell Draggable and DragTarget work fine on windows and macos at least.
- bmitc 3y agoThe API assumes you are on a relatively small screen and using a finger to drag and drop. Thus, it doesn't provide functionality that you would expect if you were on a desktop or laptop monitor with more space and using a mouse and keyboard where there is a wider variety of things that you would like to happen with a drag and drop interface. The API is primarily assuming you're taking a widget and dragging it with a finger to somewhere just an inch or two away on a phone or tablet screen. Yes, drag and drop "works" on desktop as it is, but the API is not well-designed for desktop-based usage. A lot of ad-hoc type of behavior using global state has to be used.
- tenpies 3y ago[flagged]
- FirmwareBurner 3y agoIt's the same in most of Europe too. Employers are picky with who they hire.
- tommica 3y agoWhat does this have to do with the original post?
- monsieurgaufre 3y agoNot much, imo. But this discourse is rather frequent from people/doomers who hate Trudeau for $reasons. Source: am canadian.
- anonyfox 3y agoI don't get it. Whats wrong over there?
- tkiolp4 3y agoI don’t buy it. As software developers we learn technologies for breakfast. We learn them, and then we forget them. We recollect the wisdom gained and apply it in our next gig using a different technology. It works for mobile development, for frontend, for backend, for infra, for almost anything. I have worked for years with PHP, Apache, Ansible and MySQL. Nowadays not anymore. And in 7 years I’ll be using something else. Learn the fundamentals (which is not a one-time job, btw) and you’ll be fine. If someone asks for technology X in their job offers when you know Y, but you know you won’t have difficulty in learning X, just take a few days in learning X and then put it in your CV. You’ll get pass HR screening and then you’ll have a chance to explain in tech interview that your are more of a technology-agnostic dev. You’ll do fine.
- littlecranky67 3y agoI agree, but unfortunately hiring managers, recruiter etc. don't think like this. If you happen to find a person that is tech-savy, they can asses your true skillsets and capabilitiy of solving problems. Hiring managers and recruiter match buzzwords in your CV. I recently got rejected for a project from an agency (am a contractor) because I did not have provable skills or knowledge in "CI/CD". Stupid me, made the mistake of putting extensive details about creating build and deployment pipelines with Travis, GitLab, GitHub Actions, Azure Pipelines for each past project going back to 2012, but did not specify the right buzzword "CI/CD" for the recruiter...
- tkiolp4 3y ago> Hiring managers and recruiter match buzzwords in your CV So? You put those buzzwords in your CV. What’s difficult about that? You feel like being dishonest? If so, again, just explain in the next stage of the interview (with real engineers) that you do have real world experience in similar but not exactly the same technologies listed in your CV. You just did so to pass through HR. Not a big deal (as long as you’re confident and believe you can learn technologies easily)
- dwattttt 3y ago
- ThinkBeat 3y agoId say that its the wrong way to think about it. As long as you are working in the software engineering field change is a near certainty. You will not hit on a technology / framework / product that will keep you going for 40 years. [1] Working with Flutter you have learned a lot that is valuable going forward. Learning to adopt new tools is part of the job.
- nailer 3y agoTime is a limited resource. Choosing to invest in the right technologies at the right time is the important part of a career in tech.
- mgkimsal 3y agoC, Java, PHP, SQL, Python, Ruby have kept a lot of people going for more than 20 years, and will likely continue to be relevant in some capacity for at least another decade (if only maintenance, not even including new projects started with those tech stacks). I've been working with PHP and some variation of SQL for the past 28 years, and it will go on for a while longer. I've also worked in the Java world, and have done a smattering of other tech along the way as well. Not everything lasts 40 years, but many things last more than 3-5.
- ThinkBeat 3y agotrue. But Java 2023 is quite different from Java1. The tools you use now are different (unless vi) You have had to learn a lot of new technologies, frameworks, syntax to keep up. PHP has also gone through so many changes that it is near a different beast these days than when it first appeared. So if you had relied on your skills you learn as PHP 1.0 and Java 1.0 today you would not be very productive.
- mgkimsal 3y agoMuch/most of Java 1 will still compile, at least (FWIR). The evolutionary progress of java 1... to whatever it is now (current one I'm using is 17, but I know there's more past that) has largely been adding of new libraries/methods, etc, and the majority of your java skills from 10-15 years ago are still valid (although might not be the most efficient any more). I've watched people go through Flash/Silverlight/Actionscript, multiple MS tech stacks, and many many other promising tech. Many have had to large scale reinventions of themselves and cram 'new to them' tech as the old stuff has gone away. It's definitely easier to evolve with a tech stack over the years. You get a better sense of idioms, best practices, etc. that is hard to replicate overnight. And yeah, some tooling is different over the years too, but yeah, vi still works :) Shiny new 'hey look at this' ideas can pop up in newish langs, but diving deep in to them isn't often the best path for most people. The truly good and impactful ideas tend to get recognized and adopted in the more mainstream ecosystems over time, giving you most of the benefits without needing to throw out much of your experience.
- shipscode 3y agoFlutter and svelte have clearly been astroturfed as part of their marketing strategy. I wouldn’t touch them with a 10 foot pole.
- esafak 3y agowhy not svelte?
- deleted 3y ago[deleted]
- nailer 3y agoOf course they did. Dash/dart was obviously dead about three months into it’s existence. Google cancelled their plans to replace JavaScript after nobody expressed interest and Dash/dart will never be more than a curiosity.
- glimshe 3y agoI only invest in company-sponsored tech after the market share grows to a ver significant number. A lot of what is sold as "the future of X" is just marketing. Flutter and Dart in particular failed to thrive, as many of these technologies do, and are evolutionary dead ends (despite the remaining die-hard users).
- cageface 3y agoI recently started building my first Flutter app and overall I've found it to be surprisingly pleasant. I've had no trouble finding good packages for features I need and even though I'm learning the language and APIs as I go I've made rapid progress. I've done many apps in Electron, React Native & native iOS and at least on a technological level I prefer the devx of Flutter.
- nicechianti 3y ago[dead]
- synergy20 3y agoI spent quite some cycles into flutter|dart, ended up with React Native for mobile and wxWidgets for cross platform desktop GUI(electron.js is too fat for me and wxWidgets 3.2 looks decent). RN(javascript) and wxWidgets(c++) are both job friendly, unlike Dart, which is a language I actually enjoy, but there are not a lot jobs for it anywhere.
- PKop 3y agoAny particular reason you chose wxWidgets over QT ?
- synergy20 3y agoI don't want to get into the complexity of Qt licenses ever, and wxWidgets does everything I need so far, plus it's 100% open source and free to use. the new release 3.2 is pretty good and it's also smaller than Qt ecosystem, which means much easier for me to learn and start to make releases.
- faitswulff 3y agoThe job market is pretty rough regardless of tech stack right now.
- 5cott0 3y agoparsing JSON in Flutter seems like A LOT https://codewithandrea.com/articles/parse-json-dart/ https://codewithandrea.com/articles/parse-json-dart/
- throwoutway 3y agoJust holding down the spacebar to scroll that page made me never want to use Flutter to parse JSON
- mhoad 3y agoIt’s less dramatic in real life https://dart.dev/guides/json https://dart.dev/guides/json even more so in Dart 3 https://dart.dev/language/records https://dart.dev/language/records
- mattdmrs 3y agoLet’s not forget about how the new Dart 3’s patterns can help with parsing and validating JSON: https://dart.dev/language/patterns#validating-incoming-json https://dart.dev/language/patterns#validating-incoming-json
- mtizim 3y agoIf you really want to write it yourself, sure. This code is very easily automatically generated. https://pub.dev/packages/json_serializable https://pub.dev/packages/json_serializable
- suyash 3y agoFor anyone reading this and if you want to develop mobile apps, just first learn native iOS/Android platforms, they are not going anywhere before you get tempted by other flashy technologies like Flutter or React Native. Most companies including the ones that created these cross platform frameworks, build thier core apps using native stack for a reason.
- zukzuk 3y agoI'd argue the opposite. For a lot of people, getting quick results is absolutely needed for motivation. Focusing on learning "the fundamentals" before getting to the enjoyable parts is bad advice for most, as it often leads to people dropping out before they get hooked. I agree that you probably can't be a decent mobile dev in the long term without learning basic iOS/Swift or Android/Java(/probably Kotlin nowadays) but that is not a good place to start for people who are just getting started.
- m_fayer 3y agoI used to say just this. And I did native Android dev for many years, but I gave it up around 2019. When I finally checked out, native Android was a teetering mess of compatibility libraries, half-baked never-finished “new ways of doing things”, lacking docs, forever-bugs, and overall neglect. Simple ui would take you 5x as long as equivalent css and have you dropping down to low level drawing in frustration. Back then, I felt native Android didn’t deserve my time or patience. Has this picture improved?
- tarkin2 3y agoJetpack Compose, and Kotlin coroutines, mixed with kotlin multiplatform code, came and made many things nicer, especially UI. With so many libraries and so many ways of doing things with so many opinions it’s still hard to digest of course. It’s better than non native for performance and experience but many companies will of course care more about the money saved from a sub native experience with fewer developers.
- flutas 3y ago
- pjmlp 3y agoFlutter and Dart future are tied together, both rescued by AdWords business unit. It is never going to be beyond a niche thing, unless Google does indeed ship Fuchsia in large scale.
- deleted 3y ago[deleted]
- amelius 3y agoSo what would be the best mobile development setup for someone who: - prefers to work in a Unix-like environment (e.g. Linux); - prefers to code in Vim; - prefers to have a single unified codebase for different mobile platforms; - prefers to test applications on a Linux machine running an X server.
- rcme 3y agoMacOS is Unix, and it’s pretty much the only option if you want to target iOS.
- izacus 3y agoThe one that changes your listed points to something that's compatible with modern mobile development. Your questions sound like a plumber asking how can he repair computers with a wrench and a saw. Don't get emotionally invested in tools.
- amelius 3y agoOk, then I guess I'll wait for the day when WASM runs on these mobile platforms so I can bring my dev environment to them instead of the other way around.
- rapsey 3y agoWhy are you hamstringing yourself?
- allarm 3y ago(not op) This is not hamstringing. It’s a matter of preference. I prefer jeans to a tie and a costume. I prefer Emacs and Vim to Vscode. I choose jobs that allow me to wear jeans and code in Emacs.
- saagarjha 3y agoThere are plenty of jobs that will let you do that. Most of them will not be writing software that is built on X.
- jstx1 3y agoThe mistake isn't investing time into Flutter; it's being "the Flutter guy", only knowing Flutter and only searching for Flutter jobs.
- willio58 3y agoSame could be said about “the react guy”, which I definitely have been in the past. Of course react has buy-in 10x what flutter ever had but still.
- MrDresden 3y agoIt has been interesting seeing how many interviewees coming in for a mobile app developer positions in the last 4-5 years have made bold claims about native development (Obj-C/Swift/Kotlin/Java) being dead due to Flutter, then fumbling completely when asked to solve problems that would require them to drop 'down' into the native environment. Having Flutter in the toolbox is quite a good thing, unless there is nothing else in there. Then you are in trouble.
- anon7331 3y agoIt isn’t clear why the discussion is around flutter. The problem is when you define yourself by the technology you know. You’re an app developer or an engineer, not a flutter developer. Focus on showing your ability to make apps or whatever the target company does.
- pshc 3y agoAnd yet the company where I work can't find enough Flutter talent.
- kebsup 3y agoI have worked as an Android developer for about two years, then had to do project in Flutter. Learnt it over a weekend and getting the UI right took me less time then if I were to do it in native Android (before compose).
- sirsinsalot 3y agoIt mistake misses the point of the investment. The pay-off is experience in new patterns, new tooling, new approaches. The dividend is in the job where you use the tool but the capital gain is in experience. When I hire for my team, I never mention the stack. I don't care. I am hiring software engineers, and what I value is mindset and ability. I'll throw you in at the deep end. Learn the language, libs, tooling, infra on the job and the team will support you. Because you're awesome. That's why I hired you. edit: Sound _less_ unintionally arrogant.
- gettodachoppa 3y agoThat sounds crazy to me. If you throw me at a new language, sure learning the language might only take a couple of weeks (if it doesn't radically depart from what I already know), but learning the libraries/ecosystem is at least 6 months. Probably more for something yuge like Java or .NET. I'll be referencing the doc and tinkering every little thing for many many months, which is sure to affect my productivity. Append to a file? Make an HTTP connection? Serialize a data structure? Have to look it up. Then come all the 3rd party libraries a seasoned developer will already know. How do I talk to Postgres? Which of these five 3rd party libraries should I use? Which library do I need to help generate my SQL statements? It's like you're looking for a journalist for an American newspaper, and you decide "oh, you don't have to speak english, you can learn that later". Sure, you can do this for an exceptional talent, but on average you're better off finding people who already speak english.
- mattdmrs 3y agoAt our company, out of the 8 engineers I hired, only 2 had specific experience with our backend (Elixir) or frontend (Flutter) stack. I hired for apparence of talent, experience in some other equivalent stack and the right attitude towards learning. All of them got productive rather quickly and had PRs shipping to prod in the same week, if not within a couple days. I’m not saying it _will_ go as smoothly for anyone else, but if you have the right environment and pick the right people, as an employer you’re better off being flexible with experience.
- nologic01 3y agoDevelopers have a finite useful lifespan and they need to pick their portfolio of techologies wisely if their journey is not going to be an anxious random walk chasing the latest fad. You cant only pick "winners" but you almost need to develop a sixth sense for what will be a valuable and long term addition to your finite toolbox. Looking at tech attributes is just the start. business and community context, complementarity with other pieces etc are all the subtle factors that may help avoid wasting energy in short lived pursuits.
- somsak2 3y agoI don't think it's subtle at all. Pick existing popular technologies / frameworks. If you like to gamble a bit, pick those that you see growing quickly. Invest time in learning new stuff (ideally, on an employer's dime) throughout your career. If you don't care about being on the 'bleeding edge', you really don't have to think about it too hard and you'll have plenty of job opportunities.
- nologic01 3y agoHmm, lets put that approach to the test? Is flutter 'popular'? There are other popular alternatives for mobile apps. Is one or two years being "the most loved" on surveys sufficient to decide its "growing quickly"?
- dcchambers 3y agoWhy are people so obsessed with hyper specializing in software development? Labeling yourself a react dev or rails dev or flutter dev or whatever is only going to limit your growth and options. Your career will outlive many tech stacks. Tech changes quickly. Never stop learning.
- deleted 3y ago[deleted]
- pragmatic 3y agoBecause recruiters. The person with one year of experience selling cellphones who now does the phone screen needs to see the exact tech listed on a resume or they pass.
- the_only_law 3y agoOr they just edit your resume without your consent and confuse everyone in the interview. I’ve had that happen a few times.
- sph 3y agoIt is frightening to internalise that the entire job hunting circus depends on failed salespeople with no actual knowledge of the matter at hand.
- pjmlp 3y agoMany recruiters are good at their job, however there are those that want to maximize their sales and don't really understand any tech, so if the customer is looking for XYZ Developer that is what they filter on.
- lucasyvas 3y agoSome companies hire this way which always seemed stupid to me, but I agree with you.
- the_only_law 3y ago
- jimmychoozyx 3y agoPersonally, my goal is to buy an expensive item (property/house). house <- resource accumulation <- in-demand skills <- study I learn what is in-demand. And then I acquire those in-demand skills. Then I practice those skills to earn the money I need to attain my goal. But that's just me-- my goal is to earn money quickly. This is why I focus on in-demand, popular, low-barrier languages & frameworks: python, javascript, SQL related ones.
- Gud 3y agoLearn multiple stacks, all the way down from JavaScript down to the circuit breakers. It will make you an overall better technician.
- harel 3y agoThe market is so weird right now, that I find it hard accepting this. A lot of jobs that would have been otherwise open are paused. Having said that, I have just recently got into Flutter/Dart and I found the experience quite enjoyable and the resulting app very polished. From the tooling to the language itself and the Flutter framework - it's a joy.
- akmarinov 3y agoYeah, I don’t understand why anyone jumps on Flutter. There’s barely any Flutters devs out there, definitely few with Dart experience. You’re dooming your project to die based on churn, so definitely a bad business decision. There’s thousands of Reacts devs out there that picking RN will guarantee that you have your “one codebase” and will be able to support it long term. What’s the benefits of Flutter? A nicer dev experience? No customer cares about that. And you obviously don’t care about the best possible user experience or you would’ve gone native. And that’s even before the whole “one day Google will wake up and kill it off on a whim”.
- johnnyanmac 3y agoIt's a a good enough language (Dart is kind of odd, but when comparing to Javascript it's tolerable), and the API itself IME (as someone who's done hobbyist web development) had the least amount of "CSS jank". I put a button in the middle and by god, it seemed to know what "center" meant for once. But the real magic comes from the tooling. I've also done some Android development, but Flutter's iteration times were incredibly fast. This combined with the lack of aforementioned CSS Jank made it feel like I could actually be productive without getting bogged down in all sorts of weird layout edge cases. Also, Google support in theory means that there's (relatively) little risk of abandonment. >What’s the benefits of Flutter? A nicer dev experience? No customer cares about that. You're asking a dev why they like flutter, not a businessman. Why should I take into account customer care when determining my tooling? As we both agree, they don't care anyway. If I made a usable website in Microsoft Word, then mission accomplished as far as the customer knows. Dev marketability is important as a professional, but TBH you couldn't pay me to be a web dev to begin with. So that's not a factor in my answer. The only reason I'm using React right now for some current hobby projects is due to the lack of maturity for Flutter Web (at least, 2 years ago. But nothing in the current docs make me think it's better today". >you obviously don’t care about the best possible user experience or you would’ve gone native. native doesn't guarantee the best UX. Even RN's maintainers break their own established rules on their websites. don't take my context menus and navigation away from me without a very sensible, intuitive reason (e.g. Google Sheets)
- 3y ago
- deleted 3y ago[deleted]
- pipes 3y agoMaybe I'm thick, but becoming competent in a new framework takes me a lot longer than a few days. For example, angular, ploughing through courses on plural sight slowly to properly absorb the lessons. Even after that I'm flailing about trying to do anything useful.
- Alifatisk 3y agoThe problem is OP going by the role Flutter dev and not just Mobile app developer, why limit yourself by a single tech? Your experience cuts through multiple fields!