u/KerrickLong

Was the talk recorded? I'd love to listen to it.

You should read this: https://maevyn.codes/decoherence

Since y'all are having trouble, here's how I see each of your positions. Perhaps this will help one or both of you understand each other.

Erem_in posted a yes-or-no question, asking the community if they share a given opinion about Ruby.

sshaw_ ignored the yes-or-no question , suggesting Erem_in use a different programming language than the one this post (and this subreddit is about).

Erem_in clarified they were looking for discussion about the yes-or-no question about Ruby, not for advice about using other languages.

sshaw_ suggested that asking a yes-or-no question is the same as asking for advice outside of the scope of the question.

This is why (and how) I wrought RatatuiRuby and Rooibos, and why I tinkered with Tokra. I need to do it again, and more.

Unfortunately I can't answer that because I hadn't heard of Rutie until your post. My question was genuine, as I used Magnus to make RatatuiRuby but am not married to it. If there was a reason that was worth the effort, I'd consider switching.

Do you make money from the code you no longer read?

Do you do it as a member of a team of other folks who also point their agents at the same software product?

Why would I choose this over, say, Magnus (which uses rb-sys)?

- a catalog case

The web-dev-specific chapters from the 1st edition (database design, web app security, framework design) were dropped in favor of tightening the focus on core language/design principles

Interesting, I guess this will be another book where both editions keep a permanent place on my bookshelf.

https://www.vanishingincmagic.com/magic-books/the-business-card-compendium/ is the most complete resource on business card magic I've seen. I was lucky enough to buy one of the limited hardcover copies.

Also on DVD - https://store.ammarmagic.com/easy-to-master-business-card-miracles.html

I enjoyed watching it, and learned a few things.

but for people to be able to take up arms against this they need proof other than "I don't like it."

No they don't. Taking up arms (metaphorically) because they don't like it is how those laws get written at all.

Can I introduce you to my lord and savior Domain Modeling? As it turns out, object-orientation, modeling, layered architectures keeping all your logic untangled are really handy, lead to better human and AI understanding, and cost less context.

Domain-Driven Design: Tackling Complexity in the Heart of Software by Eric Evans, 2003. Aged like a fine wine... except the cover design. ;-)

The revolution is that slop is becoming normalized and accepted by business decision makers in exchange for visible (but temporary) speed boosts. This turns into a mandate via engineering leadership, which turns into the new normal with programmers who want to keep their jobs. A bad economy keeps employees compliant while also making business decision makers desperate for quick action. Thus, the old regime of thoughtfully designed systems built for adaptability and change falls. The revolution is complete at some companies, and impending at others.

We cannot remove this time element from the inquiry. It is possible that the SKYBLOCK mark was inherently distinctive for some services when Mr. Chaney selected and began using the term in 2012 but that is not the issue before us. We are concerned with the environment in which prospective purchasers find themselves today. A mark cannot be inherently distinctive if it is deemed to be merely descriptive of the services within the meaning of Section 2(e)(1). And whether the term is descriptive is determined by evidence of purchasers’ understanding of the term now, such as third-party Internet evidence.

From the USPTO final decision.

Any chance you sell a print version? Or if I buy the ebook version, could I print a single copy of it at home?

How do you do, fellow programmers. Don't you agree it's terrible how much we pay you? I mean, how much we (programmers, which I am also) get paid? We should work until we die!

I recommend that you read Nonviolent Communication by Dr. Marshall Rosenberg. Truly internalize what it says, introspect to figure out what needs you're trying to get met with your strategy, and then have another conversation with your wife about it. (The rest of this comment will make sense once you've read the book...) Put on your giraffe ears, and hear the needs behind what she says. Ask whether your guess is correct, then give her emergency empathy. Then work together to find what will likely meet both of your needs, whatever that may be.

The risk that I'm reducing is the risk of being cyber-bullied for being "deceitful" by not disclosing the use of an LLM.

Sort of reminds me of the “sent by iphone” email footers.

I started using these git trailers, even without tooling that automatically adds it, because I was bullied/harassed for not doing so. Whether or not I think it's silly (like "Sent from my iPhone"), it's a risk reduction technique.

Native AOT may let ruby compete better in the CLI/TUI space than Java AOT, because a self-contained binary with no dependencies is otherwise a huge reason to choose Go/Rust.

When you added, "and robots," you significantly moved the goalposts.

I live outside of any city limits on 27 acres in MO, and the nearest town has a population of 3,000. The nearest hospital is in a futher town 20 miles away. The nearest airport isn't international and never gets jetliners, and is still a 50 minute drive away.

And yet, I still found community. My wife and I posted "Adventurers Wanted" signs around the various businesses in town and on the local Facebook groups, and found about two dozen folks who wanted to play D&D. We did short starter campaign sessions and chose our favorite eight people. We've now got two long-term D&D groups (2 years and counting), and have become close friends with a number of them.

Community is where you make it.

No, you configured a test environment that HR also used for production. :)

I have no affiliation with Ruby Central or RubyGems.org (except one PR I made to scratch my own itch), but I think I understand why.

I made RatatuiRuby this winter. Yes, it's great that it helps rubyists make a TUI. But really, I made it because I want more rubyists to exist. People learn languages like Rust and Go for libraries like Ratatui and Charm. Perhaps they'll learn Ruby for libraries like RatatuiRuby and Rooibos instead. But for that to be feasible, they need to be discovered by people new to programming (or at least, that area of programming).

Twenty-five years ago, that meant a high-quality beginner-oriented book with good presence in bookstores. Fifteen years ago, that meant a strong website and documentation with good SEO. Five years ago, that meant a strong social media presence with good engagement. Today, that means a strong presence in coding assistants and chatbots with good representation in the statistical weights.

That's the how. As for the why...because it's existential. There's no reason for RatatuiRuby or Rooibos to exist unless people use them. People won't use them unless they know about them. So, their existence is conditional upon their discoverability. Similarly, RubyCentral's raison d'être is to run rubygems.org and RubyConf. People won't use/attend them unless they use Ruby. So, their existence is conditional upon Ruby's use--and thus its discoverability (and growth, to fight natural attrition). Thus, Ruby Central has every reason to fight for Ruby to be discoverable and its community to grow.