Posts tagged with history
A fascinating deep dive into the very first commit of Laravel, made by Taylor Otwell on June 9, 2011. The article explores the original directory structure, the early Eloquent ORM, the session system with its clever flash data prefixing, and the authentication basics that are still recognizable in today's framework.
Read more [laravelnepal.com]
This is an amazing documentary that shows the origins of Laravel, and it's 12 year journey. I'm honoured being a part of this.
Join 9,500+ smart developers
Get my monthly newsletter with what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
"Always fresh, useful tips and articles. Carefully selected community content. My favorite newsletter, which I look forward to every time."
No spam. Unsubscribe anytime. You can also follow me on X.
– stitcher.io - submitted by Brent
There are one or two parallels with the history of braille that Brent thinks we can learn valuable lessons from.
Read more [stitcher.io]
To celebrate PHP's 25th birthday, JetBrains published a nice timeline that shows PHP's rich history.
Read more [www.jetbrains.com]
Joe Watkins compares the execution speed of PHP 4 against PHP 8. It's amazing how far PHP has come.
Read more [blog.krakjoe.ninja]
Laurie Voss, co-founder of npm, explains how databases work, what the difference is between MySQL and something like Redis, why MySQL is popular and much more!
My twitter-friend Simon had a simple question that contained much complexity: how do databases work? The result was an absurdly long thread of 70+ tweets, in which I expounded on the workings and history of databases as used by modern web developers, and Simon chimed in on each tweet with further questions and requests for clarification. The result of this collaboration was a super fun tiny explanation of databases which many people said they liked, so here it is, lightly edited for clarity.
Read more [seldo.com]
Here's an amazing talk by "Uncle" Bob Martin where he gives an amazing overview of the history of programming and where he thinks it's headed.
How did our industry start, what paths did it take to get to where we are, and where is it going. What big problems did programmers encounter in the past? How were they solved? And how do those solutions impact our future? What mistakes have we made as a profession; and how are we going to correct them. In this talk, Uncle Bob describes the history of software, from it’s beginnings in 1948 up through the current day; and then beyond. By looking at our past trajectory, we try to plot out where our profession is headed, and what challenges we’ll face along the way.
Can't wait for his talk at this year's Laracon US.
Bram Van Damme explains the origin of the word "patch" in context of software.
A common misconception is that a software bug is called a bug because of an actual bug – a moth – that got stuck in Harvard University’s Mark II calculator in 1947, and Grace Hopper finding it + taping it inside a logbook. ... What seems to be legit however is the history of the term software patch.
https://www.bram.us/2017/01/24/why-a-software-patch-is-called-a-patch/
So I'd like to stress that while it really came together in just about ten days or so, it wasn't like it was some kind of mad dash of coding. The actual amount of that early code is actually fairly small, it all depended on getting the basic ideas right. And that I had been mulling over for a while before the whole project started. I'd seen the problems others had. I'd seen what I wanted to avoid doing.http://www.linux.com/news/featured-blogs/185-jennifer-cloer/821541-10-years-of-git-an-interview-with-git-creator-linus-torvalds
The source code manager to build git was... git.
