Filter
Exclude
Time range
-
Near
You folks make it SO easy for me to take my ideas, however silly, live in literally a matter of minutes. I couldn’t imagine doing that even just 4 years ago. Not only did it rekindle my love for building side projects but helped me recover from a bad burnout. Thank _you_!
1
1
1
4
Taking a web based idea to fruition hasn’t been easier thanks to the awesome folks at @zeithq @begin and @darklang. All very different approaches with different trade-offs but all very rewarding. Thanks for all the hard work folks!
2
2
0
8
Agreed! This is awesome! What made up the session?
0
0
0
0
Replying to @rauchg @zeithq
Wait, what?! What led to it? How does it work? This is brilliant! mental health is key!
1
0
0
2
Idk about your name bruv
0
0
0
0
Building a mood tracker powered by @fauna and running in @zeithq. Software development has never been easier.
2
4
1
29
And the response was around complexity. The marketing talking points you allude to were not stated as an argument against AWS anywhere here. They were stated as a response to a question where the OP was unsure if an infra provider indeed used AWS under the hood. :)
0
0
0
1
I know they are. And, to your surprise probably, I have already experienced them :) To re-iterate, the thread is about dealing with complexity (UX, DX, billing, etc) that current providers have. Not about migrations and multi-cloud that you seem to be stuck on.
1
0
0
0
The line of thinking in this thread is about the OP finding AWS complex and companies solving for that. Not about cloud lock-in or the multi-cloud silver bullet (which, we know isn’t a silver bullet, just a different set of trade-offs).
1
0
0
0
FYI I didn’t mention it as a talking point or any such thing. Someone wasn’t sure about a piece of information, I linked to it. Simple.
1
0
0
0
What’s the fourth? (Also, doc update? 🙃)
1
0
0
0
It (@zeithq) is multi-cloud. It currently uses AWS and GCP under the hood. zeit.co/docs/v2/network/regi…
2
0
0
2
It’ll be featuring the wonderful Next.js project from @zeithq, @contentful, my own browser based graphql solution, the awesome graphql-code-generator from @dotansimha, my fork of @intercom’s awesome contentful-typescript-codegen and the sweet apollo-server for quick local dev
0
0
0
7
Show this thread
My reason for suggesting the gql way with @fauna is because FQL is finicky and hard to hand code and not very readable. And on bringing this up in the past, folks from fauna recommended the gql route which I now default to. ^_^
1
0
0
0
Replying to @rauschma
I’d say @begin with @begin/data (DynamoDB wrapper) if you want built in persistence. If you don’t mind using a db over gql, I’d say @zeithq + @fauna. Fwiw, it takes about 5min to get a gql api in Fauna. Upload your schema and you’re good to go!
1
0
0
2
Brilliant! Looking forward to giving it a spin! Thanks for the clarifications and info as always!
1
0
0
2
So there will be a non-deprecated way in the near future to setup — 1. Methods allowed to access a fn 2. A rewrite & headers mechanism that allows matching qs 3. Custom build setup & other usual escape hatches? A lot less is good but good config powers a quick migration to zeit.
1
0
0
1
now.json basically. Hatches for custom folder structures, non-deprecated ways to have custom build setups & to declaratively manage routes (`methods`, `continue`), the problem this thread is about, etc. These worked perfectly before but are now deprecated w/o equivalents.
1
0
0
0