Solid cable is quite a bit of setup though,compared to Liveview. The way LiveView manages the rendering for your is leaps ahead of how actual rails SolidCable development feels.
One of the arguments is how noisy the languages are. Elixir is without a doubt more powerful, more scalable and more sophisticated than Ruby.
What Ruby has though is ability to express what you are doing in a clear syntax. Elixir has a lot of ritual (albeit less than erlang) to set up your most used things like GenServer - you don't abstract away the concurrent flow (which is good, concurrency should be obvious), but you also wouldn't write elixir without it, so code inevitably becomes filled with technical concerns.
I'm biased, I write elixir for a living after a decade in Ruby, and I'm happy with that tradeoff. But there are times where you need to do an imperative thing and make it clear as day, and Ruby often does a better job here.
Rails is also somewhat more ergonomic for fast prototyping than phoenix. ActiveRecord is a blessing and curse, it's insanely productive for making things do things in minutes, but lacks composition later on.
In terms of competition it's really the same. Whether you fight with a team of 1 for 5 businesses or a team of 10 for 1 business that is 50x bigger, on average as long as you have equal competition in each segment you walk away with the same. But you get very different customers, for better or worse.
A segment of a customer base is hardly a buffer, if you underserve them they will leave, and you will have wasted effort making an inclusive sales and support process to them.
That makes not losing those customers more critical: if you lose one of the 50 smaller businesses, your revenue is barely affected; if you lose that 50x whale, you’re out of a job especially given how hard it is to find another one of that size.
This shows up especially in the context of hiring: for a generation, there have been a ton of people who learn VMware at businesses of all sizes and your large shop can reliably hire them. Shutting down smaller sales affects that directly and because the smaller places are going to do something else it means that the people who move up to a bigger place are going to have direct firsthand experience contradicting what the VMware sales people are saying about how risky it is not to use their software.
Granted, software engineering is a pretty ill-defined term, but I'm pretty sure most would agree that agile project management is not software engineering.
"Being able to be picky about what to learn" being programming is also a really confusing idea. Programming is writing programs, it's not some learning philosophy, and it's certainly not some liberated opposite to software engineering.
I guess you're confusing having a job with software engineering, and spare time coding with programming.
I feel developers get habits on the kinds of estimates they throw, but at least for anything that isn't straight duplication, I can't say that I've seen much reliability in them. But to be honest, I've also not tracked time to complete in a way that would rule out my bias, as I find that kind of creepy and besides the point.
In what way is postgres similar to cockroachdb? Except for being a database. Going by that standard you might as well say that Access is an alternative to postgres. Which it technically is but...
I guess that's true, I didn't think about that. But i think that you'd probably not be using cockroachdb if you were fine with what postgres offers. Cockroach might be compatible, but it really isn't "comparable" in terms of use cases and deployment imo. I might be totally wrong though, I have not been following it and Postgres closely since some time around 2021?
It's useful to use a Postgres-compatible syntax. The point of Cockroach was always to compete with globe-spanning DBs like Spanner, not with (possibly) sharded PG.
CockroachDB was already under the BSL. It's interesting that they're further restricting it... Perhaps the BSL isn't the panacea folks are making it out to be.
BSL code automatically converts to open source at a specified date. So probably several releases since then are now as open source as anything else in the world. And if not, then they will be soon - BSL allows a maximum 5 year delay.
i don't care that much because i don't use it, and evidently not much of anybody else does either, or there would have been a popular fork. i'm just saying that this is probably not a good time to expect one to pop up
I'm also waiting for longnow.org to start using long dates behind the scenes, like image urls, html metadata, http headers, etc. They need to eat their own dog food as far as software goes.
Counterpoint, monopolization is not a good thing, and as long as Apple doesn't allow alternative app stores, we can talk about how the value they provide is artificially gatekeeping the devices of over a billion people from running the software they would like. There's not only business in this equation, and historically attacking tech monopolies through legislative power has been more effective than suggestion that businesses exclude themselves from business to make a statement.
But they’re not stopping me from supporting creators. I can go to Patreon.com on my iPhone right now and subscribe to any creator without Apple’s fees. If they took their app off the App Store tomorrow I will continue to be able to have all of the functionality because they have a functioning mobile website that allows me to do everything I want to do. The web is a perfectly suitable alternative here and it’s working, so why exactly do they need to be on a store with rules they don’t agree with?
>If they took their app off the App Store tomorrow I will continue to be able to have all of the functionality because they have a functioning mobile website that allows me to do everything I want to do. The web is a perfectly suitable alternative here and it’s working, so why exactly do they need to be on a store with rules they don’t agree with?
Because majority of the people expect that app exists for everything and because Patreon.com is not just a website, it is a complex web app. And a complex web app usually works better on smartphones when it is in the form of native mobile app than just a website in the internet browser.
I think PWAs are the viable future. Native apps are too much problematic when it comes to developing and managing them; taking in consideration you need to wrestle with two monopolistic behemoths like Apple and Google on top of all the technical complexity behind like I said developing and managing them.
> because Patreon.com is not just a website, it is a complex web app
I don’t agree with this as someone who uses Patreon relatively frequently. It’s actually quite a simple website, and the main thing I care about is the ability to manage my subscriptions, which I can do on the mobile website today.
Maybe there’s an argument for the creator posts being a bit more complex, but nothing a non PWA shouldn’t be able to handle well.
Also with Patreon specifically, the creators tend to tell users how to support them, so it’s trivial to include “make sure to visit the website, it works on mobile too!” When they call out.
Why do you say that one needs to use Emacs? Like, I love using Emacs for the elisp and having the power of a full lisp machine, but for CL I didn't find sly-mode/slime to offer anything particular paradigm-shiftingly more powerful than the vim/nvim adaptions?
This very side is written in CL in vi, if I'm not mistaken?
