Ignore the people who tell you it’s pronounced “sequel”, they’re wrong and should be shunned (EDITOR'S NOTE: This opinion is incorrect). SQL is widely understood at this point by most techy people, but for those unaware, it stands for Structured Query Language. PostgreSQL (or Postgres, nobody can apparently decide how to refer to it) is the database we use. This way there’s a lot less Javascript involved, which means it’ll be easier on your computer and, if you’re one of those users who use mobile, your battery won’t drain as fast either. On top of this, there’s also a system called Livewire that we’re adding - this uses Blade as a basis, but adds some fancy dynamism on top so that you can have a similar experience to what you already have with dynamic elements. For the new version, Laravel gives us a set of tools called Blade that lets us write the frontend in PHP. It’s a Javascript framework created by Facebook. React is what you use right now to see the site. It gives us a lot of tools to work with, and so far, is making some things easier and some things harder. Personally, I prefer the older system (albeit with some major code touch ups needed), but that’s because I find MVC as a paradigm overly convoluted for what it does - but given Laravel is extremely widely used, and will make recruiting new devs easier in future, that’s what we’re going with. For new Cherp, we’re using Laravel, something most PHP developers reading this will be familiar with. On top of PHP, current Cherp uses a microframework called Slim to provide some API routing stuff. It’s quite likely that we’ll be able to upgrade through all the 8.x versions after this with little issue. Right now, we’re coding with 8.0 in mind, but by the time we release, we’ll be on 8.1. This is about to leave active support meaning it’ll be receiving security updates only, meaning that for this rewrite, we’re switching to PHP 8. Cherubplay was originally written in Python, but nobody really knew enough Python to fix that code up when it started breaking. On the frontend, we currently use React, an abominable monstrosity that we’re glad to be dropping. This interacts with PostgreSQL as our database engine, and Redis acts as a caching layer between the two for information that takes a little while to get but that’s accessed often things like your unread count, chat status, etc (Coincidentally, this is also the cause of the ghost unread bug - it caches your unread count for 24 hours unless it changes, but grace period and account deletes don’t decrement the counter. On both new and old Cherp, the core technologies are staying roughly the same - we use PHP as the backend language that handles all the server side logic. Last week we talked about user accounts and said that this week we’d talk about the new software stack, so let’s do that.
0 kommentar(er)
