Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Technology Choices for My SaaS in Retrospect

thomasbandt.com

Post reply on HN
Print view View original

41–50 of 74 posts

Re: Technology Choices for My SaaS in Retrospect

#41

Post by excsn »

scarface74 wrote: post #15
ofrzeta wrote: post #10

I'd say this is quite biased, which is fine I guess, we all have our biases. Seems his choice of F# is set in stone, so you either go with Bolero or you have 1+1 languages in your stack. This is also reflected in his choice of Xamarin: he "doesn't like" Dart as a language, so he's forced to choose "dotnet MAUI as a platform [which] might not be as mature and capable as Flutter even today". Flutter as well "suffers fr…

I would never choose a Google specific cross platform environment. A cross platform mobile environment constantly needs updating to stay consistent with the vendor’s platform. I wouldn’t trust Google to give that much attention to Flutter especially seeing they are moving away from it internally for iOS development. https://9to5google.com/2021/10/10/google-ios-apps-native/

You don't need to trust Google, but it certainly don't mean making general statements about what Google is doing. The article says nothing about discouraging Flutter use and given Flutter 3 came out this year, Google is still supporting and using it. Flutter has iOS UI replication of look and feel, which is what that article says Google is encouraging. Fuschia hasn't come out yet, but it still uses Dart and Flutter is used to create apps on it.

I'll take a bet, use and choose Flutter for a long time.

Re: Technology Choices for My SaaS in Retrospect

#42

Post by excsn »

ofrzeta wrote: post #10

I'd say this is quite biased, which is fine I guess, we all have our biases. Seems his choice of F# is set in stone, so you either go with Bolero or you have 1+1 languages in your stack. This is also reflected in his choice of Xamarin: he "doesn't like" Dart as a language, so he's forced to choose "dotnet MAUI as a platform [which] might not be as mature and capable as Flutter even today". Flutter as well "suffers fr…

Given he gives no examples of "Flutter as well "suffers from many bugs and problems" and given one is bound to use third party libraries, maybe he refers to third party libraries he chose being buggy. It is too general and very unclear what this means. Dart/Flutter has been a wonderful experience by far when it comes to cross platform libraries.

Re: Technology Choices for My SaaS in Retrospect

#44

Post by gnz11 »

scarface74 wrote: post #14

First for context, I’m far from a Microsoft hater. I spent 22 years exclusively in the MS ecosystem. I love C# and even now I’m the go to person when it comes to implementing MS solutions on AWS for my department. That being said, when I was a dev lead, the first things I thought about when choosing a technology were the ecosystem and the how hard it would be to find competent devs. You can throw a rock and find a go…

Where in that article does it say they are moving away from Flutter?

Re: Technology Choices for My SaaS in Retrospect

#45

Post by scarface74 »

excsn wrote: post #41
scarface74 wrote: post #15

Earlier quoted context omitted.

I would never choose a Google specific cross platform environment. A cross platform mobile environment constantly needs updating to stay consistent with the vendor’s platform. I wouldn’t trust Google to give that much attention to Flutter especially seeing they are moving away from it internally for iOS development. https://9to5google.com/2021/10/10/google-ios-apps-native/

You don't need to trust Google, but it certainly don't mean making general statements about what Google is doing. The article says nothing about discouraging Flutter use and given Flutter 3 came out this year, Google is still supporting and using it. Flutter has iOS UI replication of look and feel, which is what that article says Google is encouraging. Fuschia hasn't come out yet, but it still uses Dart and Flutter i…

You have to trust Google not to abandon support for it and to keep up with iOS latest changes.

Anytime that you emulate a platforms UI, if the vendor makes changes, a native widget will take advantage of it a replicated one won’t.

The fact that Google is working on a third operating system (Fuscia) is not exactly a vote of confidence on Google’s ability to focus.

Re: Technology Choices for My SaaS in Retrospect

#46

Post by vikramkr »

herodoturtle wrote: post #25
thraxil wrote: post #24

Earlier quoted context omitted.

React and Docker are both almost a decade old (both released in 2013). TypeScript is from 2012. Functional programming is very, very far from being a modern concept even if it's (maybe, finally?) getting a bit more attention.

So interesting seeing these perspectives on here. I’m in the same boat as previous commenter - React et al feels like new tech to me. But that’s because I’m an old fart who’s been using php for over 20 years.

So react's existed for almost half the time you've been using php. I think yhr distinction here is between tech that's new, and tech that's new for you

Re: Technology Choices for My SaaS in Retrospect

#47

Post by scarface74 »

gnz11 wrote: post #44
scarface74 wrote: post #14

First for context, I’m far from a Microsoft hater. I spent 22 years exclusively in the MS ecosystem. I love C# and even now I’m the go to person when it comes to implementing MS solutions on AWS for my department. That being said, when I was a dev lead, the first things I thought about when choosing a technology were the ecosystem and the how hard it would be to find competent devs. You can throw a rock and find a go…

Where in that article does it say they are moving away from Flutter?

If they are using UIKit, they aren’t using Flutter for cross platform development. They aren’t eating their own dog food.

> Google concluded that it was time for the latter route, and that Apple’s UIKit had matured enough for internal needs. The company no longer had to maintain most of the custom components that it built out over the years, including app (top) bars, lists, and menus.

Re: Technology Choices for My SaaS in Retrospect

#48

Post by monlockandkey »

lmarcos wrote: post #39

As someone who's working on something similar (one-man project), what I struggle the most is with the infra details. Author mentions that there's a single machine for the api, db and nginx; this means the machine is publicly accesible to everyone, and so is the db (although the port the db is running could be only accessible to localhost). I don't really feel comfortable doing that (so I force myself to out the db wi…

Check out https://dokku.com/

Dokku is basically open source Heroku. Put it on a server, and then just push your application to it.

Re: Technology Choices for My SaaS in Retrospect

#50

Post by excsn »

scarface74 wrote: post #45
excsn wrote: post #41

Earlier quoted context omitted.

You don't need to trust Google, but it certainly don't mean making general statements about what Google is doing. The article says nothing about discouraging Flutter use and given Flutter 3 came out this year, Google is still supporting and using it. Flutter has iOS UI replication of look and feel, which is what that article says Google is encouraging. Fuschia hasn't come out yet, but it still uses Dart and Flutter i…

You have to trust Google not to abandon support for it and to keep up with iOS latest changes. Anytime that you emulate a platforms UI, if the vendor makes changes, a native widget will take advantage of it a replicated one won’t. The fact that Google is working on a third operating system (Fuscia) is not exactly a vote of confidence on Google’s ability to focus.

Google has a lot of trust in its infrastructure projects. You assert they don't therefore don't use it and you have many Google front-end platform projects that serve as counter examples to your assertion. Angular being the most popular open source Google front-end project.

Like I said, you are welcome to distrust Google, but your general assertions are far fetched and stems from Google's product engineering that has to expand and contract its offerings as they are expected to make money unlike its open source projects.

Post reply on HN