It combines the "opinionated" aspects of ruby and rails and the power of erlang. The BEAM is like no other runtime and is incredibly fun to work with and powerful once you get how to use genservers and supervision trees.
We use Elixir for Mocha, and my one issue with it (I disagree with OP on this) is that live-view is not better than React for writing consumer grade frontends. I wish Phoenix took a much stronger integration with React approach, that would finalize it as the top choice for a web stack.
My current project is using React Native (for native and web) and getting GraphQL setup was initially a pain, but having React and GraphQL subscriptions gives me enough of the "live" functionality, but without having to worry about connection issues. With gql-tada, I get fully typed experience on the front-end too.
Yeah it’d be nice if they had a mix task to include your js frontend of choice and it “just worked”. Many have used inertia with success. I’m taking a different approach and pairing svelte with Phoenix channels.
Being precise with language and defining specifications based on domain knowledge is generally creative. The better analogy is product design rather than product management.
F2P creates this problem. If you're eating $20-60 per account every time your anti-cheat is burned it isn't much fun anymore. But if you can roll new accounts for free, there's nothing to lose.
This wouldn't work with CSGO either, as it's a play-to-earn game where you can win / gamble for items that some people are willing to spend a lot of money on. See also Diablo 3 when it first came out, there was a good story about a guy that would run two dozen bots just scanning the auction house, buying stuff for in-game money and selling it for real money. Every once in a while they did a round of bans, but the author just bought new copies of the game and continued.
This analysis is very much on point. I'm building a product in this space (https://getmocha.com), and can share a few more insider insights:
- The churn from companies like lovable is indeed very high, and user frustration is high also.
- There are sub-niches available. Building internal tools is not the same as landing pages is not the same as saas. In the previous website builder market, different players (webflow, squarespace, wix) found and dominated a sub-niche
- The market is way bigger than anyone realizes. Today hundreds of millions for basically early adopters and highly tech-savvy users. This tech can and will go mainstream
- A huge issue with lovable, solved by others like mocha and replit, is the app backend. Lovable took a shortcut and partnered with supabase but that deal will not last. Supabase is losing big on their free tier (had to raise 200M to support it) and both want to capture the margin from the customer. There will be a reckoning.
Even if what you said was true, it will be false within months or years.
What then?
This is the whole premise of the article. Just extrapolate and imagine that it can think and write poetry better than you (it will, and likely soon), what then?
.com is the best TLD by a long shot but it's really saturated, so as a startup you have no chance.
As you say, the hope is to make it and be able to buy the X in getX.com where hopefully you've checked that X belongs to a squatter and not an existing company (they're both bad the latter is worse).
> their interface is not nearly as bad as GCP / AWS
Underrated.
Until recently, all the features were grouped in a very clear manner within the dashboard. Now, even Cloudflare is complicating its management interface, but they still have a long way to go before reaching the level of confusion of AWS and GCP.
I managed to get R2 with their cdn in front of it up and working in under an hour. The same experience with s3 fronted by cloudfront was 2 very long days. Due to my misunderstanding, yes, but aws provided (1) incomprehensible docs, (2) an extremely complex UI; (3) stale help all over the internet; and (4) incredibly unclear error messages.
Honestly, I feel like Cloudflares interface is quite complicated for the number of features they have. All their stuff seems to be only slightly integrated.
I appreciate the fact its just connected enough to work. AWS does what feels like everything in their power to entrench you. I avoid AWS as much as possible but one example that comes to mind is the fact you basically need to use SQS for SES
It combines the "opinionated" aspects of ruby and rails and the power of erlang. The BEAM is like no other runtime and is incredibly fun to work with and powerful once you get how to use genservers and supervision trees.
We use Elixir for Mocha, and my one issue with it (I disagree with OP on this) is that live-view is not better than React for writing consumer grade frontends. I wish Phoenix took a much stronger integration with React approach, that would finalize it as the top choice for a web stack.