Oh man, this must just be subjective because I find Ecto to be beautiful compared to the absolute trainwreck of Activerecord. Having compile time guarantees through Ecto is wonderful.
I agree with this sentiment, though in practice it doesn't seem to be much of an issue the vast majority of the time. Sometimes you do need that niche library though, and end up forking and updating for your needs.
Given how rarely this comes up it feels like a tolerable problem that will only diminish as Elixir adoption continues to increase; I am aware of many rail shops that are slowly and quietly switching everything to Elixir, and it feels like that snowball continues to pick up pace as Elixir improves and those libraries are created.
Very true it is actually designed for telecoms, but like you mentioned the distinction is so small it's not really even a stretch to say it is purpose built with at least the general architecture of web in mind.
> Add in problems finding developers skilled in Elixir and Phoenix and the small available libraries.
Is this actually a problem you see? I'm going on 15 years in the industry and haven't seen any issues training people up on a new language in just a couple months.
If you need an expert in some library or language to make meaningful business progress I feel like that says more about whatever tool or language you're using, and I simply don't see that with phoenix or elixir in the years I've worked with it.
After programming with elixir and phoenix for a few years (with many prior years of rails experience) I have a hard time seeing why one would choose rails.
Elixir is more performant, has compiler safety guarantees that are only getting better as types are introduced, is actually designed from the ground up for web dev (being based on the Erlang VM), and... it's just way more fun (subjective I know). Elixir is what I always wished Ruby was, and I couldn't be more excited about the coming type inference.
Programming with Elixir makes me feel like Ruby is a previous generation language, much like Ruby made me feel that way about Cobol or Fortran, it really is that stark.
To expand on this, many states have a large white pine lumber industry. The white pine is highly susceptible to a type of fungus harbored by currants.
The fungus does not spread from white pine to white pine, only from currants to currant, or currant to white pine, so eliminating the nearby currants protects the white pine industry.
One of the most powerful features of vscode is extensions. Until zed has a comparable extension set to rival all the things I use in vscode, I couldn't care less about 50ms vs 70ms lag on keystroke renders.
Typescript takes away a significant amount of the pain for me; the only hold up after that was getting an environment set up to compile it. Deno supporting typescript without any configuration is incredible.
I've done freelancing before at 4 days a week and loved it, and have generally negotiated into 4 day workweeks at various startups. Give a shout-out to your company if they're hiring ;)
As someone currently growing more cucumbers than I can handle (gardener problems), I've been eating at least 2 a day of a few different varieties, including a somewhat bitter pickling variety.
That said, I've never experienced the burping side effect many report. Makes me very curious what's going on metabolically to cause some to burp but not others. Can gas produced by the microbiome of the upper tracts of the intensities make it back up into ones stomach?? All very fascinating regardless.
Because the FDA exists?? Because that would be fraud to claim otherwise, and fruit/veg sources are easily traceable back to their source, particularly at quantity?
Do you have evidence to back up this claim? I'm aware CA puts many warning stickers on various products... but isn't it possible that profit-seeking corporations are, in fact, using cancer-causing materials simply because they're cheaper?
Lots of comments here opposed to Martin Fowler's advice. I'm curious if anyone who is anti-Fowler has software design books they _do_ recommend? (Asking because I'd love to read them)
I have a hard time calling immense wastes of resources "wonderful". Think of how many man-hours of at least better-than-average engineers have been wasted developing something like 5 separate chat apps... it's absurd.
Given that this is Google, my money is on them either abandoning it, or making a new version every 2-3 years (for no discernable reason) making no actual progress as a result.
I would LOVE to be proven wrong, but Google's track record with bringing products to market, and actually keeping them for longer than a media boost, is downright depressing.
At some point it feels like every Google side project is just a media buy for their real business: hiring engineers to drive more ad revenue, engineers who are enticed by shiny projects like these.
This feels like saying no because of one very specific use case. I use a flat bottom wok on my electric stove almost every day. Adapt and you'll be fine.
My honest take is that it's rare to name your tables and columns with all caps, whereas there are various cases where people do so with camelCase and snake_case.
In the end this makes spotting SQL-specific functions much clearer. I find it much easier to read SQL with this convention since my brain immediately knows when it's looking at context/project-specific data or a FUNCTION.