I worked on a team that did, and it was the second-worst application I've ever touched.
DeprecatedCompatV2
joined 2 years ago
How do you feel about line breaks?
I think they mean xcode.
I'm curious why you believe one needs to be a multimillionaire to enjoy Niagara Falls?
No you have it wrong, we just haven't implement clean architecture with usecases, it'll be different this time I swear, just wait until Google IO...
Flutter is pretty nice and the experiencd I've had has been pretty smooth. It also has a really awesome hot reload feature, and you can run your "mobile app" on your dev machine as long as you aren't using any mobile-only APIs in the particular feature.
I thought this as well.
I recall an issue that started with windows 8 and UEFI where the bootloader would get installed on any HDD instead of the SSD where the operating system would live.
I've worked in both android and spring boot and rewriting your security to use a filter chain is nothing* compared to the shenanigans google likes to pull. Keeping up with the deprecations and imaginary "best practices" is half the job. It's like someone combined the worst parts of react with the worst Java timeline and forced people to write inscutable spaghetti that's completely impractical/impossible to test.
*there are valid criticisms of spring security, but I think this particular change improved things, even if it felt pointless
Flutter will probably meet your needs.
I mean unit tests. I work on Spring Boot apps where there are distinct layers (controller -> service -> persistence), and you generally inject mocks into your object to isolate tests to the specific code you want under test. One benefit of this approach is that it's pretty easy to get 90% coverage.
How does it compare to Flutter?