Oh, I can tell you about INext. I ran that shit for about 5 months. I hate it so much. Josh may have had his best intentions when creating it, but the software made me want to neck myself.
PHP
First off, the language choice was a mistake. Josh thought that by using a common language like PHP, he could attract contributors. Well, Josh, that only fucking works if you're using raw HTML and not a framework that only some people use.
The PHP system is also a horrible mess. The config file (a config file for a programming language environment!) is versioned and it is separated for fpm, cli, and mod-php. There's so much shit you need to tweak in order to make PHP run like how $modern_lang runs OOTB.
Laravel
Laravel is the most ass-backwards framework I ever used.
>some caching methods shown as available but explodes when used because it doesn't support something
>caches the entire codebase into a cache/compiled.php file, making stack traces absolutely useless
>this cache will also occasionally not be cleaned if edit something just right, causing you to pull your hair out trying to understand why it doesn't work
>the routes offer you to use closures for routes instead of controllers, but then route caching explodes if you used a closure. why offer it if it doesn't work well?
>models do not auto-generate migrations because PHP lacks reflection
>models need you to define getter/setters for everything, because see above
>the caching system, by default, stores keys indefinitely. more on this later
>every minor version breaks shit instead of deprecating them, which is fucking absurd. you cannot use a laravel app designed for 5.2 on 5.3
>routes can overwrite each other and no detection is in place.
etc. etc.
The caching system will store keys indefinitely by default. What this means is that eventually your cache will be full, and it will start evicting other apps' cached keys.
The Blade template system has fucking dumb quirks. For instance, sections will not get overwritten by for loops, which caused a bug where all action menus for attachments pointed to the first attachment's actions. This cost me 2 days and half my hair.
The routes don't check for overlap. There was a bug where the route for files overlapped those for file actions. When you visited an attachment moderation page it just gave you the attachment file.
Joshcode
Josh is not an adequate programmer. There're a lot of nonsensical stuff in INext.
>permissions
The permissions system is a broken mess. There are some which you can't override, permissions get denied because it's Tuesday, and the roles page sometimes likes to explode. I could not fix it during our use of the software.
>files through php
Fucking Josh. This made our server load go to 30 when Librechan first died. Every single file has to go through PHP to get the correct path. We mitigated it back then by using an nginx proxy cache which is a god-awful hack.
>captcha
The captcha was bad. It also didn't have high entropy and didn't mangle/warp text (because enabling sine would get the server load up to quadratic tire fire levels), so we had lots of botspam.
There's a fuckton of stuff I don't remember that's in my IRC logs. I could try going through them and find the stupid shit in INext. Now, I do realize this comes off a bit hypocritical as Blazechan has problems of its own, but at least I listen to criticism instead of doing /ignore in IRC. Fuck.