phaedryx

If you're in the Salt Lake County/Utah County area, we're having Ruby meetups: https://www.meetup.com/utah-ruby-users-group/

I helped run a website selling tickets for a venue that had a Garth Brooks concert. I can confirm that they did the same thing in the 2010's.

This is my understanding:

1. Ruby Central hosts, maintains, and sponsors Rubygems and Bundler

2. Based on recent events, it was possible that credentials were stolen (https://www.bleepingcomputer.com/news/security/60-malicious-...)

3. They decided to lock everyone out until security issues could be resolved

It makes sense to me from a security standpoint, but their communication has been terrible which has led to a lot of speculation.

It sounds like the judge works for Anthropic

The first programs I ever wrote were from one of these books.

Hypercard was inspired by an LSD trip.

I've made it a point to always ask beforehand: "what is the dress code expectation? I've seen everything from t-shirts to suits in the tech industry and I'd like show up dressed appropriately."

I always get a positive response.

Same. When the game started I was looking for a black circle to use against the "bubbles"; none showed up, and suddenly I had lost.

This looks interesting. I think I'll try it out over the weekend. Thanks for sharing.

Why not create a word/name? e.g. Clojure

I work for a company that uses Rails. We don't have any Python code, but we use a lot of AI.

Yes. It does a lot for you and you can add features and explore ideas quickly. The batteries are included.

I do know Ruby well though.

I remember when Backbone first came on the scene and “get your truth out of the DOM” was the rallying cry.

I'm going to cheat and get a list from AI:

1. Difficulty in maintaining and debugging: When state is scattered throughout the DOM, it becomes challenging to track and manage, leading to code that is hard to maintain and debug.

2. Performance issues: Frequently querying the DOM for state information can be more expensive and slower compared to accessing data stored in JavaScript objects or dedicated state management solutions.

3. Lack of a single source of truth: Storing state in the DOM makes it difficult to establish a centralized, authoritative source for application data, which can lead to inconsistencies and errors.

4. Synchronization problems: Keeping DOM elements in sync with a mutable list of data can quickly become complex, especially when dealing with dynamic lists or elements without unique identifiers.

5. State persistence issues: DOM-based state is vulnerable to loss during page refreshes or navigation, which can lead to poor user experiences, especially in single-page applications.

6. Scalability challenges: As applications grow, managing state in the DOM becomes increasingly cumbersome and can result in performance bottlenecks.

7. Difficulty in implementing advanced features: Techniques like time-travel debugging, state snapshots, and easy hydration become more challenging or impossible when state is primarily stored in the DOM.

8. Increased complexity in component communication: Relying on DOM for state can complicate the process of sharing data between components, potentially leading to prop drilling or other anti-patterns.

I think the idea of "sprinkling" JavaScript into your server-rendered HTML is a good one. However, I think that Stimulus is terrible.

1. There isn't a good way to test it. There is nothing in the docs about how to test it.

2. Keeping state in the DOM is dangerous

3. Messaging between Stimulus controllers is painful

4. They disconnect parameters from functions. The functions have to scan through the DOM to find what they need which I think is fundamentally weird

5. Reusability is rare

6. It doesn't try to play nice with the larger JavaScript ecosystem.

I personally prefer Vue.

Would that make them sick?

Looks really nice.

Some very minor feedback: the animations are a bit too busy for my tastes

Will no one rid me of this turbulent priest?

Collaboration is much easier in the office, but I find home much easier to go heads down, headphones on and work on something; hybrid is the sweet spot for me.

The thing is when people around me are "ruining their lives" it does affect me.

Crime goes up, bankruptcy goes up, corruption in sports goes up, etc.

I agree that people should be given freedoms, but we live in societies and people aren't independent, disconnected, autonomous units.

Found an answer to my question: Milford, UT

https://kslnewsradio.com/2113554/largest-geothermal-energy-d...

Does anyone know exactly where this is supposed to be? I'm from "southwest Utah" so I'm curious.

Here's what Claude gave me:

A real-life example of three events A, B, and C where A and B are correlated, B and C are correlated, but A and C are uncorrelated could be:

A: Ice cream sales B: Temperature C: Energy consumption for air conditioning

Let's break this down:

A and B correlation:

Ice cream sales (A) and temperature (B) are positively correlated. As temperature rises, people tend to buy more ice cream.

B and C correlation:

Temperature (B) and energy consumption for air conditioning (C) are positively correlated. As temperature increases, people use more air conditioning, leading to higher energy consumption.

A and C uncorrelated:

Ice cream sales (A) and energy consumption for air conditioning (C) are not directly correlated. While both increase with temperature, there's no direct causal relationship between them.

Our definitions of vandalism are different. I would count graffiti as vandalism. I would also count racial slurs written on private property using sidewalk chalk as vandalism.

If you like react/mobx, why not Vue? That's the combo that eventually got me on Vue 3.

I'd go with "Climate Protesters Vandalize Stonehenge"

What would you call it when AI doesn't have the answer so it makes stuff up (sometimes in a dangerous way)?

I worked on a GraphQL API a few years ago and we solved these problems at the beginning and then forgot about them. We generated the schema for a user from their CanCan abilities (CanCan can handle attribute-level access, I wrote the PR). Shopify has support gems for the N+1 stuff, if I remember correctly. You can limit how many levels deep your query can go. We added some rate limiting.

Basically, these are all solved problems.

This is a blast from the past. What a crazy place the early internet was. I remember just striking up random conversations with random people with ICQ. My friends and I used it a lot. AOL's acquisition and changes killed it for us. It pushed us all over to IRC.

How many "Amber"'s do we need?

e.g. https://github.com/amberframework/amber

https://amber-lang.net/

https://ambermd.org/tutorials/

https://openjdk.org/projects/amber/

I'm probably grumpy, but I like unique names.

Yeah, I grew up in the 80's.

I also have a lot of fond memories of getting on my bike and going pretty much anywhere I wanted to.