Josh Mountain⚡️ @JoshMountain - Twitter Profile

@laravelphp "ensure that every environment they're employed in runs Vapor Core ≥ 2.33.1" - just confirming, this means each site/environment that connects to the database needs to be running Vapor Core ≥ 2.33.1 correct?

0

239

JoshMountain retweeted

Robby Doyle @rmdoyledesign

almost 3 years ago

Week 2 update for Taxie - your personal tax assistant with the help of AI 🤖 CC: @_nightsweekends // @_buildspace - flushing out UI/UX - pages of site - Storing test conversations in DB - working on Rating Answers

1

2

1

0

252

JoshMountain retweeted

Taylor Otwell

@taylorotwell

almost 3 years ago

It's come up a few times lately so I want to clarify something regarding Livewire "vs." Inertia - and a few things about Inertia in general. Comparing Livewire to Inertia doesn't make sense. You should compare Livewire to Vue or React. Why? Inertia isn't a frontend framework. It is a JSON protocol specification (https://t.co/L3oksXtKBi) that allows backends (not just Laravel!) to communicate to a React / Vue / Svelte frontend what page to load and with what data. The various Inertia backend and frontend libraries essentially just provide helpers for working with that protocol. When viewed with that understanding, Inertia is "complete software". At heart, it is a wire protocol specification to allow you to build Laravel + React / Vue / Svelte apps monolithically - and it does that well. It is 100% complete in that regard. It solves the problem it set out to solve. That means it is stable. You should not expect it to get loads of new features. Why? You are using Inertia in order to use Vue or React as your frontend framework. Remember, Inertia is primarily a wire protocol. Instead, you should be keeping up with what new features Vue or React are getting. Thank you. 😅

50

1K

171

169

231K

Josh Mountain⚡️ @JoshMountain

almost 3 years ago

@JackEllis Would definitely be interested in reading this. We are planning a full rework of our semi-existing teams structure.

0

27

JoshMountain retweeted

Taylor Otwell

@taylorotwell

almost 3 years ago

We said @LaraconUS videos would be available quickly - we weren't kidding. My keynote is up now: https://t.co/v6fKGjTzla I'll be trickling out the other speaker videos over the course of this week. 🔥

17

657

89

62

80K

JoshMountain retweeted

Taylor Otwell

@taylorotwell

about 3 years ago

New things I know you will see at @LaraconUS … New Pest 2 Features Livewire 3 Early Laravel 11 Preview Laravel Herd Laravel Folio Laravel Volt Laravel Prompts 🥵

34

761

91

21

102K

Josh Mountain⚡️ @JoshMountain

about 3 years ago

@taylorotwell Amazing! This will be very useful, especially in our vapor environments.

0

1K

JoshMountain retweeted

Mohamed Said

@themsaid

about 3 years ago

Part 1 of "PHP to Go" is 1h 27m. I focused on comparing the concepts to ones in PHP so it's easier to relate to. Go gives us more control when it comes to memory management. For these parts, I found it easier to compare the concepts to those found in databases and ORMs.

themsaid's tweet photo. Part 1 of "PHP to Go" is 1h 27m. I focused on comparing the concepts to ones in PHP so it's easier to relate to.

Go gives us more control when it comes to memory management. For these parts, I found it easier to compare the concepts to those found in databases and ORMs. https://t.co/mOqMCSuewB

13

327

18

69

38K

Josh Mountain⚡️ @JoshMountain

about 3 years ago

@themsaid Thanks Mohamed, I've been going through the course preview and enjoying it so far, very high quality content. Do you have any examples (inside or outside the course) or real life scenarios where Go would be used instead of (or along with) Laravel?

0

49