3 ms·

Am I the only Luddite who Deploys Go app containers. Pick a cloud. Use whatever they offer. Deploys static JS to cdn Calls it a day. I really do not underst

Am I the only Luddite who Deploys Go app containers. Pick a cloud. Use whatever they offer. Deploys static JS to cdn Calls it a day. I really do not understand these tools. Who is using them? I’ve built and worked on apps used by millions of people. Really don’t understand where the benefit is or if people are just over complicating basic things to extract money from chump developers?

creakingstairs 4y ago
Yes their DX is technically “over complicating basic things to extract money from chump developers” but it lets users just write code and automate away everything else with couple of click. It limiting your options can be a good thing, people can just ship instead of being stuck in analysis paralysis forever. I also found it quite nice entry point for newbie developers. I’ve been donating my time to help out new developers, and learning deployment (it isn’t ”basic” for complete newbies) on top of everything can be daunting. Vercel lets them deploy for free and effortlessly so that they can show off what they’ve learned. That being said, I personally wouldn’t touch Vercel for any serious work either.
- pjmlp 4y ago
  Problem is that how things go, many SaaS products are now making partnerships with Vercel for their webhooks and hosting of frontends and middleware configurations, with SDKs that are Vercel ready and DIY for anyone else.
overbytecode 4y ago
Do you deploy just the JS to a CDN or a whole website? I wanted to do something similar, throw a static website on a CDN and use a Go API as its backend. But unsure how to get around CORS in a reliable way.
- fireant 4y ago
  You setup CORS on your backend, it does not matter where or how you frontend works. IMO biggest problem is that if your website is public facing, then just having an SPA is bad for crawlers and not great for UX.
- moomoo11 4y ago
  You whitelist domains that can access your server (in my case I have env vars with whitelisted domains list that the Go code picks up) and that should be all you need to do.
ilrwbwrkhv 4y ago
This whole new dx based industry is because sub par JavaScript developers who write bloated electron apps have flooded the market. Nobody wants to come out and say this but that's the truth. Measuring costs are not part of their mindset when it comes to either memory usage or billing. So they can be charged overpriced rates as long as there is a big button which says deploy.
vlakreeh 4y ago
With frontend a lot of what engineers are tasked to make (highly interactive websites that still have decent SEO and time to FMP), you need to add some complexity to achieve that. SSR + hydration for web apps has been common for years because it's great for SEO and getting a fast paint and because of that we now have these super established hybrid (as in client side and server side rendered) frameworks. Sure you can implement these sites with an html file and some JS to populate it with data, but it's hardly a nice and *easily maintainable* experience when dealing with non-trivial applications. And now that your app is using one of these frameworks, you probably need some sort of API for whatever. There's a lot to be said about designing a REST api just being exporting an JS function in a file in a /api folder or whatever. If you are already using a hosted option for these frameworks it's an incredibly simple solution that doesn't require to you mess around creating a new project, making a docker image, going to a different cloud provider and giving them your credit card, etc. And depending on your scale that might genuinely be cheaper than running a container 24/7 on a public cloud.

creakingstairs 4y ago

Yes their DX is technically “over complicating basic things to extract money from chump developers” but it lets users just write code and automate away everything else with couple of click. It limiting your options can be a good thing, people can just ship instead of being stuck in analysis paralysis forever. I also found it quite nice entry point for newbie developers. I’ve been donating my time to help out new developers, and learning deployment (it isn’t ”basic” for complete newbies) on top of everything can be daunting. Vercel lets them deploy for free and effortlessly so that they can show off what they’ve learned. That being said, I personally wouldn’t touch Vercel for any serious work either.

pjmlp 4y ago
Problem is that how things go, many SaaS products are now making partnerships with Vercel for their webhooks and hosting of frontends and middleware configurations, with SDKs that are Vercel ready and DIY for anyone else.

overbytecode 4y ago

Do you deploy just the JS to a CDN or a whole website? I wanted to do something similar, throw a static website on a CDN and use a Go API as its backend. But unsure how to get around CORS in a reliable way.

fireant 4y ago
You setup CORS on your backend, it does not matter where or how you frontend works. IMO biggest problem is that if your website is public facing, then just having an SPA is bad for crawlers and not great for UX.
moomoo11 4y ago
You whitelist domains that can access your server (in my case I have env vars with whitelisted domains list that the Go code picks up) and that should be all you need to do.

ilrwbwrkhv 4y ago

This whole new dx based industry is because sub par JavaScript developers who write bloated electron apps have flooded the market. Nobody wants to come out and say this but that's the truth. Measuring costs are not part of their mindset when it comes to either memory usage or billing. So they can be charged overpriced rates as long as there is a big button which says deploy.

vlakreeh 4y ago

With frontend a lot of what engineers are tasked to make (highly interactive websites that still have decent SEO and time to FMP), you need to add some complexity to achieve that. SSR + hydration for web apps has been common for years because it's great for SEO and getting a fast paint and because of that we now have these super established hybrid (as in client side and server side rendered) frameworks. Sure you can implement these sites with an html file and some JS to populate it with data, but it's hardly a nice and *easily maintainable* experience when dealing with non-trivial applications. And now that your app is using one of these frameworks, you probably need some sort of API for whatever. There's a lot to be said about designing a REST api just being exporting an JS function in a file in a /api folder or whatever. If you are already using a hosted option for these frameworks it's an incredibly simple solution that doesn't require to you mess around creating a new project, making a docker image, going to a different cloud provider and giving them your credit card, etc. And depending on your scale that might genuinely be cheaper than running a container 24/7 on a public cloud.