111–115 of 115 posts
Earlier quoted context omitted.
The price is fine, I'm more so talking about not having a pricing section on the main website and instead being on another website domain.
Well, yeah, there is no good reason tbh, I kind of haven’t just thought about this
Earlier quoted context omitted.
> I wonder what makes Sidekiq special? Time, know-how, and long term dedication are the key ingredients from my perspective. Maybe he's working 10-20 hours now, but there's support and development every day for the past 11 years. > I don't imagine any equivalent product (background job processing) in the other languages is raking in that much, if making any revenue in the first place. I guarantee, there are backgroun…
https://getoban.pro/ would like to have a word... It's apparently making good money
Earlier quoted context omitted.
> It costs nothing to actually put down a reason for being upset, versus having totally generic downputs Actually, it does cost something- time and effort- but thanks to the latest AI, I can cut some of that out right now: As an Elixir enthusiast, I'd like to point out some technical criticisms of JavaScript and its ecosystem, particularly in comparison to Elixir's approach to dependency management and community. A)…
Works for me! Very much matches the MO I've been using as "JS is wild, ain't it great!," so I tend to agree with the shown perspective. I also think a huge amount of these tend to be pretty typical conservative-developer overconcern (see Yegge's Notes From The Mystery Machine Bus https://gist.github.com/cornchz/3313150 ), governing yourself on fear, that is probably not really as fully warranted or deserved. But I'm…
I don't actually hate JS. It's possible to write great JS. (And honestly, things like Elm do exist, and Svelte looks pretty amazing, but these also have their cost.) The failing for me is that there's nothing stopping anyone, especially a library I might decide to depend on, from writing bad JS. This was the same problem I had with Ruby. We spent all this time aiming for thread safety in our app (a whole team spent a lot of time on it) and it turns out the 2 culprits were 2 libs we depended on, because Ruby simply makes no guarantees about thread safety (and cannot, because it's mutable, thus making forking either expensive or dangerous). That and probably a few other things burned me enough to make me say "no more" and I suddenly loved the idea of a language where "thread safety" is completely a given and impossible to violate and you don't have to mutex-lock everything.
I don't think FP will ever get popular, unfortunately, unless we NEVER teach ANYONE ANYTHING but FP, because the people that pay the cost of learning the FP way are paying it because of all the ways they got burned by the non-FP (OOP, imperative, mutable) ways...
If you ever get there yourself, you have my hat-tip. And truly, it is worth the journey.
Earlier quoted context omitted.
https://getoban.pro/ would like to have a word... It's apparently making good money
Funny enough, you replied to the creator of Oban.
He was so understated that I missed it lol