whats wrong with authjs or lucia. your reason is so stupid, php doesn't have any auth package, laravel has. this is not the question for first party or third party package. adonis has auth built it. talking about hot things, those are still heavily being used. you see the downloads and you would know. drizzle for me is an upgrade as how it handles things, unlike elequent which is the same for all these years, sometimes changes also mean improvement. there are currently 8 vulnerabilities reported in php itself. php developers usually get pride in saying a big portion of website on the internet runs on php and php isn't the same as it used to be, but they fail to say the percentage of those php website that uses wordpress and how 15% and 54% of php websites still in v5 and v7 respectively according to w3techs. I myself started from php and I know how the language is, how the architecture is so inefficient. But it bothers me when people trash on nodejs for such silly reasons like there is no auth package and they ignore things like lucia. having everything built in where you don't have to write at least minimal code is not good, I know a lot of "laravel" developers that doesn't know how auth even works, they only know to run a command.
Where to start? The ecosystem is a mess. Even when you limit it to the frontend where it belongs, the latest garbage fails in the least graceful way. NextJS: "A client-side application error occurred" Give me something sane. Prefer Java or Rust on the backend. Typescript is just more duct tape over a bad design. You have to use some JS in the browser, but it shouldn't break your project. Most of the functionality you need is provided by the browser API. Rely upon that instead of some insane SPA framework. We're at a point where jr. webdevs don't know basic HTML.
Perfectly articulated man!!! This is the reason why I am moving to something more stable like SpringBoot or Go. I started working with Express a month ago and found out every single tutorial is either outdated or in fact I could not find any latest express tutorials that solved some problems, rather youtube/medium is filled with Next.js, Nextjs doesnt have as many openings as Express. Then comes typescript integration, every single module has to be in types and few middleware do not compile as the type is not recognized. Javascript was better than Typescript in Express. In fact, people now are saying Express and Passport.js are kinda outdated and suggest to pick something else. There is not a single architecture or approach or in fact a library for auth or a library for REST API at this point, every day something is brought new and the old ones are constantly marked outdated.
As a data scientist, I am looking for ACCURACY comparisons on how FUZZY the nearest neighbors match is to the correct answer, or inaccurate some indexes may be.
Love this video - i'm a junior in the programming world, and your videos are like listening to a senior dev advise on what to be aware of ahead! So what I get from this video, I have a vanilla JS proficiency, where enough to help me build interactions on my website. I should learn Node.js for small projects or microservices, but If I'm thinking long term to create a product that do not depend much on outdated dependecies, I should look for more mature ecosystem like Laravel for example. But that would require me to learn PHP (which I know a little). Did I get this right?
Thank you! And yes, that’s a good summary of my views. Broadly speaking, if your goal is to build a successful business, you will be much better served by a mature full-stack framework than a ragtag collection of v0.x node libraries where the burden of integration is effectively all on you. Laravel is my personal favorite but Rails is a close second. People have done great things with Django as well, although I feel it’s gone a bit stagnant the last few years. Thanks for watching!
I view that 2050 claim with some skepticism. From what I understand the SQLite team(or is it one person?) does not accept contributions from outside the team and given that, will the committers still be around to maintain SQLite 26 years from now?
Glad you liked it! Haven't tried, but I think you could make them work together by configuring Filament tenancy to read/write on the same tenant columns (which is something like `team_id` and `user`.`current_team_id` for Jetstream).
I don’t blame planetscale for the decision. I used the free tier as basically a testing remote db. I might actually use the regular plan at 30+.. in the future for a bigger project if they become stable and reliable into the future.
This move made me stop and think about what I was doing. I think I was learning on these services for a convenient developer experience because I do not really need global/infinite scale capabilities. I ended up dropping PlanetScale and Vercel completely and moved everything to a single Linode 4GB Dedicated VPS. I built my own multi-environment CI/CD with GitHub Actions and Docker. I use Cloudflare's "Zero Trust Access" product to protect access to the dev/staging deployments and the database is now running locally on the same host as the app. My application is now faster for my customers and it is cheaper for me!
Yup! All my apps start life as single node deployments as well. It’s crazy how performant everything is when it’s all on the same server. People also forget that you can scale to billions of records in a modern relational DB before you need to shard.
Most applications don't need those assumed scale on expensive cloud providers. I have been saying this for years and have been leading migrations from expensive cloud to VPSes and CEOs get amazed at the cost saved. When the economic downturn started, reality struck for some CEOs who didn't buy the idea of migration.
Jet Stream looks awesome, but I I'm a little confused for SaaS, as those core features are not included. Maybe show us how you could easily adapt this for Saas. There are just a handful of other packages that already have the multi-tenacny and payments, having the frontend would be nice though.
Just add Laravel cashier (another first-party open source package) and along with the teams, MFA, API tokens, etc. with Jetstream I think you're set up pretty well for most SaaS scenarios.
Really nice content, I learned a lot with this video! But man, just don't chew like that while recording, please(or edit that before you post). I lost my focus a lot of times because of that. Anyway, success to the channel, you got a new subscriber.
The biggest difference is the licensing models. If you distribute MySQL in a commercial product, you have to either make your entire project open source or purchase a a commercial license.
Sure, but I don’t think it’s a super important distinction in practice. In cases where you use MySQL as your database for a web app, you won’t be distributing the binary and the licensing provision won’t apply. And in cases where you would distribute a binary (eg embedded environments) SQLite is almost always the go to option anyway, for reasons unrelated to licensing.
@@GringoDotDev General consumer B2C websites - yes. B2B has numerous cases where they want an on-premise enterprise installs. ( eg. medical, large corps, finance, enterprise software) such as examples are Jira or Salesforce. In such cases, commercial license of MySQL would be required if its used. That''s often why other DBs are chosen in these cases because they have a more lenient distribution model.
Feature wise both would work for me. I was testing the free tiers tonight and planetscale took about times to return results to me +100ms. Mostly 150ms+) compared to 30-40ms for the other two contenders: neon & cockroachdb. I’m in the Midwest & setup all services in the Midwest. Would you base your decision on that or do u think it might or screwed since it’s the free tier?
I'm not aware of any latency differences by plan for Planetscale. One thing to double-check would be that your region is on AWS if you're using AWS or GCP if on GCP. Crossing data centers could definitely add some lag even in the same region. Not sure if you've seen it but they have some docs on it here: planetscale.com/docs/concepts/network-latency Since the options are functionally equivalent for you, I would next assemble a price curve for each based on some reasonable assumptions and map out how I expected each option to scale over the next couple of years. If that too is a draw, then yeah, latency is a perfectly valid basis to make a decision. Closing thought (which applies to all options) is that you can get pretty far with putting most of your reads behind a short-term Redis cache for really low latency. For a lot of use cases, fast reads and slower writes is perfectly fine.
For sure! I got tired of creators shilling for sponsors / courses / etc. and started the channel to just get (my view) of the unbiased truth out there. I hope it's helpful!
@@GringoDotDev I have started learning about web development from past 3 months. I watched your other video about why nodejs should not be used. That was an eye opener for me. I have gone through dozens of videos and courses and no one has talked about it in the way you said. I started with nodejs and expressjs as framework, and believe me from past 1 month I am just setting up the environment, framework and libraries. Sometimes it is a compatibility issue, version issues, libraries get deprecated. The problem is most of the front end developers are creating the courses and tutorials, they know javascript and typescript and they push for it in the backend as well.
@@streetboyback you're not alone! I agree that junior frontend devs moving to backend is driving a *lot* of the conversation and churn around node.js. Which is fine, I just really hope they keep an open mind to other ecosystems as they mature. I also think there's a really corrosive influence from channel / creator sponsorships, especially Vercel. Keep with it though! As bad as the current job market and learning materials are, I think it's the perfect time to continue upgrading your skills so you're ready for the next boom. I'll do my best to guide you along the way. Thanks for watching!
Great video! I especially appreciated the way you clearly distinguished between what was a cold hard fact (e.g. supported data types) and what was a professional opinion that others might disagree with (e.g. NoSQL will burn you enough to mostly disregard it and focus on relational DBs). That's such a helpful way to share your experience and earned wisdom without creating confusion.
📝 Summary of Key Points: 📌 Continuous integration involves running automated tests continuously as part of the software development process. GitHub Actions allows tests to be run whenever code is checked in or a pull request is opened. If all tests pass, the code can be deployed to the production environment. 🧐 Continuous integration allows for faster development and better quality assurance compared to the traditional approach of having a separate QA team and a complex release process. 🚀 Tests are essential for ensuring the functionality and stability of the application. Developers are encouraged to have at least a basic test suite to verify the core features of the application. 📌 The video demonstrates a GitHub Action created for a Laravel project called "The Stoic Developer." The job definition in the YAML file includes setting up the environment, installing dependencies, running tests, and deploying the code. 🧐 The speaker mentions the use of a tool called "act" to run GitHub Actions locally for easier development and testing. 🚀 Railway, a deployment platform, can be configured to gate the release of code based on the successful passing of tests. Railway will only deploy the code if all the actions defined in the GitHub workflow pass. 💡 Additional Insights and Observations: 💬 "Continuous integration allows for faster development and better quality assurance." 📊 No specific data or statistics were mentioned in the video. 🌐 GitHub Actions and Railway are valuable tools for implementing continuous integration and deployment in a Laravel project. 📣 Concluding Remarks: The video highlights the importance of continuous integration and demonstrates how to implement it using GitHub Actions in a Laravel context. It emphasizes the benefits of continuous integration, such as faster development and better quality assurance. The speaker also emphasizes the importance of testing and provides a practical example of setting up a GitHub Action for a Laravel project. Overall, the video provides valuable insights and guidance for developers looking to implement continuous integration and deployment in their projects. Made with Talkbud
thank you for this video. it was really helpful. but i ve been having this error: ERROR: failed to solve: process "/bin/bash -ol pipefail -c ./deploy.sh" did not complete successfully: exit code: 126 Error: Docker build failed
I don’t use prisma but just did a quick check and it doesn’t seem to have first class support for geospatial queries. I imagine you could just write a raw query along the lines of what you see in the video however.
Great analysis. Thank you. I've been evaluating both (Neon, PlanetScale). I like that Neon is based on Postgres, but really dislike the coldstart times (even as of Nov 2023, seeing at bad as 10 sec). Neon keeps blogging about how they're addressing and are now sub second, but I'm just not seeing it (and running out of Ohio, which is supposedly their best control plane), so this has become trust issue for me. A solution is to just not let the instance suspend, but then quite a bit more expensive and, again, the trust thing. PlanetScale on the other hand just works and performs flawlessly. For these reasons, I'm leaning towards PlanetScale.
Planetscale is a great option indeed! Having used them in production for a while I have nothing but good things to say. Fingers crossed they're able to navigate the current funk with Oracle and grow into a bigger stewardship role for MySQL.
