dham

> Wow. At what point do we get Generative Web Apps or Site, full backend and front end.

Well GameMaker came out in 1999. So maybe like 2002?

1. Rails has had direct upload since it introduced Active Storage. No one has uploaded files through their servers in a decade

2. What do you mean? Point whatever CDN you want at your origin

3. Maybe

3a. Yes

3b. Metadata or a new table

4. GraphQL is the single worst technology that has ever been adopted. We adopted at my company...twice. Twice we made the same mistake now we're stuck with it for mobile clients. In fact we're stuck on the old Graqphl RB gem that used a DSL instead of classes, which also blocks our Rails upgrade. We've been able to revert everything back to good ole Rest for another part of the app. Be cautious adopting technologies of large companies.

I understand there are hereditary cancers, but isn't cancer a metabolic disease in a lot of cases?

I agree to a certain extent but a tool charging money just seems odd. Like what if Ableton starts charging for every stream someone gets on Spotify, or Apple with Final Cut for every minute someone watches a video. Or probably, not so far fetched, Adobe charging for every view you get on Twitter of an image.

Like, just charge someone a fee for your tool and be done. If you think your tool is worth more just charge more.

I've been enjoying Construct 3. Not the visual scripting but the Javascript portion. It's a really good Javascript engine at its core. For some reason people don't know this? DragonRuby has also been pretty fun and hot reload is nice. Godot is the main answer for Unity but web support is just better with Construct, obviously since it's built on web technologies.

My main issue with Unity and why I never picked it up is, I have poor vision and the editor doesn't scale on Mac. You basically have to have perfect vision to see anything that's going on. A scalable editor is a must. Godot / Construct fit these. Game Maker looks so poor on 4k that it hurts my eyes.

Too much sugar in Apples, not enough fiber.

Meat isn't bad, meat with carbs is bad.

Low in fruits: What kind of fruits? Not all fruits are created equal and it's important how we consume them. Drinking fruits in smoothies doesn't mean you're healthy. Eating Blackberries, Rasberries, Strawberries, Avocados, yea. Eating grapes, raisins, apples, no

Diet high in red meat: Nope. Only if your diet is also high in carbs (the American diet). Eating a grass fed steak with some broccoli and walnuts on the side. Ok. Eating a steak with baked potato and chocolate brownie for dessert, na.

High in sodium: Nope. Only if your diet is also high in carbs

Low in milk: Lol

Alcohol consumption: Yes

Tobacco use: Yes

Developers didn't understand event delegation, so entire codebases were filled with $.live, on and off events. If you componentized behaviors with jQuery it wasn't all that bad, although I'll admit it could get somewhat gnarly.

The problem, from what I saw was nested forms and trying to hold state on the client when the server should have been asked for the state. This lead to template duplication and trying to hold too much state on the client.

CSS? In all seriousness though Tailwind or SCSS.

Well, we existed for 10's of thousands of years before we ate bread, so yea not 30 years, but like a long time.

I know what it is. It's sitting on the toilet with a phone for long periods of time. Also sugar. Red meat / nitrates are out as our grandparents / great grandparents all ate this stuff like crazy.

Everyone made fun of people that said, "I did my own research" during Covid, but if you've been failed by the medical system once, you're used to this.

There's a physical aspect as well as a mental aspect to it. Media is constantly feeding you information about loss of smell (even though I've lost it at least a few times before with viruses).

We have to stop putting sugar in dumb things first, like ketchup and bacon. We have to get a grip.

I was just explaining this to my wife while we've been on keto. Yes, artificial sweeteners are bad, let's try to avoid them if possible, but if consuming some aspartame in jello helps us stay on keto and lose belly fat, then the benefits outweigh the risk.

> If you are only re-rendering what is required, it's just a webpage at rest.

As someone who has used React since 2015, and has worked on tons of React apps, with a wide range of team members and skill level, this is easier said than done. First of all, some developers just don't "get" React. The framework has a lot of foot guns, especially around performance. The most productive I've ever seen a team is with Mobx, which does fine-grain updates out of the box if you model your state correctly.

Getting great performance in vanilla React requires constantly thinking about where state lives, lifting, lowering state, composition, and memoization. It's not exactly fun, requires a ton of diligence, and most developers can't architect a simple table that has interactivity that just re-renders a single row instead of the entire table.

It's not the fault of the developers, it's the framework that has poor performance, has a team that doubles down on awful architecture, and doesn't have the empathy of what it's actually like working in React day to day with just normal developers.

Compare this with Solid or Svelte, which have fine-grain interactivity, and you don't have to refactor your components changing where state lives constantly. You can actually describe your UI with components based on where they should live, not how they should update. Contrast that with React, which requires you to describe your UI and state by how it's updated, not where it makes sense.

In a world with advancing AI and great new frontend frameworks, why are we specifying memoization dependencies manually? It's a joke. The model of a component executing top-down every change has to go. The react-forget compiler has been in the works for years at this point. I've moved on, so should you.

I could rant on this for hours, but that's the gist.

With 6x CPU slowdown (although not enough anymore) or a "normal" computer? React isn't exactly fast, in fact it's pretty slow. Developers just think it's fast because they have $4000 Mac Book Pro's.

Yea devs just don't understand that Ruby is strongly typed. In fact, it's the most strongly typed language out there besides Scala. It's just not statically typed.

We just looked at our options at work and landed back on Rails. The problem is the Javascript ecosystem is just bad for any project that needs to live for more than a year. The database libraries changes every 6 months, stuff is just constantly rewritten over and over. I agree that Typescript is nice but the eco system is awful. If you want a batteries included framework, that is used at scale, has a lot of history behind it, and doesn't churn every 6 months, there are only a few that you can use. Rails is one.

> If you're having to poke around in running code to find out WTF some symbol even is and where it comes from

I see this people complain about this but I don't understand why. First of all I've seen highly competent engineers complain about methods in Rails that exist from basic inheritance in Ruby. A concept that they probably learned when they were 10 years old. This is how object-oriented code is written. Pretty much every game is written the same way. Yes the dynamic methods that are generated can be annoying, but not what I see people complain about.

Second, they're trying to code a language like Ruby in a text editor and complain. If you tried to write Java or Scala in a text editor you would also have a bad time. So, yea I don't get it to be honest.

That's what I thought this was. Brackets coming back and becoming a web-only editor or something. Even though it was already a web-based editor.

Is an enterprise product sitting around and watching "movies" by yourself?

We use Algolia, and we have an index of that is 10 million records, 1 that is 5 million and 1 that is 4 million. Performance and reliability have never been an issue. In fact, it's the only thing in our stack that we never have issues with. (knock on wood)

I still use old.reddit.com. Anytime I can opt out of "next gen" React interfaces I'm going to do it, so my M1 Pro processor doesn't melt.

> Measles alone meant you likely lost kids in that age range.

I get what you're saying, but Measles is definitely the wrong thing to put here. Most people over the age of 35 aren't going to get what you're saying.

I'm right with you. This stuff was exciting like ~5 years ago. I did several projects with Firebase functions as well as Lambda. Randomly on a few of my projects, the functions don't work anymore. Although I haven't touched it in like 4 years.

Either way, I'm back on the monolith train and probably won't look back for a while.

Yea it's funny how it worked out. I felt similar. I was chasing the latest trends, frontend frameworks, databases. They weren't, and now we're back where we started with sending data from the server and submitting forms.

I'm less likely in my career to stray away from whatever the old heads came up with. For instance the new thing is putting server/database calls in server side React components. But something tells me MVC was invented for a reason by people way smarter than me.

Yea, React is moving to the server. Check out Remix, which pushes the more "old school" approach of doing forms. I think Next is coming soon with something for that.