It might correlate to design level thinking but it also might not.
1,562 karma · joined November 23, 2016
It might correlate to design level thinking but it also might not.
Free, open source, and has worked perfectly for me so far. (I think I briefly ran into issues with an Elastic Search container? so ymmv a bit)
I think the community tends to overestimate the ecosystem’s maturity which is one of the big things holding it back, both because it blinds the community to areas that need improvement and leads to bigger shocks when newcomers do unexpectedly run into the rough edges.
Phoenix has significantly faster templates than Rails by compiling templates and leveraging Erlang's IO Lists. So you will basically never think about caching a template in Phoenix.
Most of the Phoenix “magic” is just code/configuration in your app and gets resolved at compile time, unlike Rails with layers and layers of objects to resolve at every call.
Generally Phoenix requires way less RAM than Rails and can serve like orders of magnitude more users on the same hardware compared to rails.
The core Elixir and Phoenix libraries are polished and quite good, but the ecosystem overall is pretty far behind Rails in terms of maturity. It’s manageable but you’ll end up doing more things yourself. For things like API wrappers that can actually be an advantage but others it’s just annoying.
ASP.NET and Springboot seem to only have theoretical performance, I’m not sure I’ve ever seen it in practice. Rust and Go are better contenders IMO.
My general experience is Phoenix is way faster than Rails and most similar backends and has good to great developer experience. (But not quite excellent yet)
Go might be another option worth considering if you’re open to Java and C#
You’re not entirely wrong but you’re exaggerating the difficulty.
18mb vs 180mb is probably the difference between an instant download and ~30 seconds. 1.8gb is gonna make someone stop and think about what they’re doing.
But 18mb vs 9mb is not significant in most cases.
It does seem weird to complain about the file size of a debug build not a release build.
Once they solve that it will really take off beyond just a better Twitter.
Is it soulless when a sculptor doesn’t source their own clay and marble directly from the earth?
Or when a musician uses an instrument made by someone else, or a composer uses digital sounds recorded by someone else?
There are many different forms of artistic expression and many rely on relatively mechanical and “soulless” work being done for us by someone or something else.
Tools like this can open up new and creative world building options to people who previously didn’t have access to 3D models. It increases the opportunities for creative expression rather than diminishing them.
I'd be happy to help if you need anything! Whether hosting or just backend related questions!
Also depending on how hard coded your architecture is, maybe you can separate out the Magic specific data from the app itself? So the MTG specific data could just be loaded as a datapack?
How do other languages, like Python, scale better to more devs, besides more devs available? All that comes to mind immediately is modules in Elixir being globally available, but I’m genuinely curios about your experiences.
Elixir is extremely overhyped, not because it’s not great but because most of the discourse is about how much better it is than other languages.
With Python, Rust, Go, and JavaScript I can find a ton of interesting projects and tools; tons and tons of examples of people doing interesting things, easily outweighing the language hype.
Elixir has a handful of core tools, tons of hype posting, and a smattering of introductory blog posts to those tools.
The community really has the appearance of lacking depth. (Granted I think partly that’s because the depth exists inside companies that don’t really talk about it)
18.04 is an LTS release which according to Ubuntu's website ended standard support in April 2023 and still has "Expanded Security Maintenance" until April 2028.
From the article it seems like the real problem is Microsoft didn't adequately communicate the change in advance or provide safety checks when upgrading. It seems like an easy oversight to make though.
Also I'm sympathetic to the numerous situations in which developers have no ability to upgrade old Linux boxes but it seems like Microsoft's not entirely to blame for not supporting a 6 year old Ubuntu release a year after its standard support timeframe.
TL;DR: Situation sucks, seems like a typical Linux dependency issue, hopefully they consider and communicate better in the future.
For example https://news.ycombinator.com/item?id=39219568 was just a dupe. Maybe that's the case for some of the more technical stories that are removed.
But anything remotely technical with code snippets, diagrams, screenshots, tables, etc, PDF is going to be infinitely better.
So you now have the option of a $400 cheaper 8GB version or a $200 cheaper 16GB version.
Instead of discussing the merits of 8GB vs 16GB commenters are incredulous that Apple would even offer an 8GB laptop in 2023.
You know Apple's base models have a history of being insufficient for your use-case and that upgrades are pricier than you'd like.
You see the cost of the base model and are upset when you find that you will need to spend more than that base cost to get the model you want.
Apple devices and upgrades are costly, without a doubt. But there is clearly a market for whom the price and capabilities of the base model is more than enough.
Zoom isn’t great but Teams is worse.
Once you get away from those things get sparse. Several really common libraries have glaring omissions (or entirely missing) module docs, and others just barely cover the common web use case.
It’s not uncommon for me to have to open the source code to try and understand what some function actually does.
Elixir is still my language of choice and has a better docs ecosystem than most languages but the community demonstrates a bit of a blind spot also.