Clicking the Vercel logo at the top left of the page hard crashes my Chrome app. Like, immediate crash.

What an interesting bug.

Comments URL: https://news.ycombinator.com/item?id=46004625

Points: 4

# Comments: 1

Any suggestions?

As I've aged my preferences have moved away from dark themes to light themes.

I used to have everything in dark mode: terminal, IDE, sublime text, use Dark Reader Chrome extension.

But I can't see shit anymore. I need light!

Why aren’t you using feature flags to gate new behavior/functionality?

Did you think of us as living in a cave forced to connect to a BBS to share the latest on design patterns?

For large projects when you get down to it, slim frameworks are simply frameworks where you have to add in components yourself, vs shipping with sane defaults.

Symfony comes with Doctrine, Twig, etc, but you can choose not to use them or even include them.

With slim frameworks if they are built correctly they will have hooks to add these components but you have to choose them and import them and set them up.

I have not worked on a small project in years, and have not bothered looking at slim frameworks in as much time, so my knowledge might be out of date ... but a quick glance through Slim's documentation tells me I'm still fairly close.

I can (and have!) gone in-depth into my misgivings with Laravel, but it is fine for most projects and teams. It has elevated the average codebase quality throughout the PHP community and introduced many engineers to what PHP can do. Its creator and community have been a large net-positive to PHP as a whole.

I still prefer Symfony:

1) explicit 2) DataMapper ORM by default 3) What I am used to

``` /* @var array Variables stored in the context */ private $variables = []; ```

This should be typed as `array` (heck, I'd argue ArrayObject instead) and all your classes should have `declare(strict_types=1);` at the top.

Your `Dumbo\Helpers` classes are basically static mine traps that you are unable to mock in unit tests. Why does `BasicAuth` expose a single static method but then calls a bunch of other static methods? What ends up happening in any class that uses any of your `Dumbo\Helpers` classes will always run whatever code is defined in these helper classes.

I'm unsure where the bootstrapping process begins. What file does your webserver need to call to handle a new request? I am hoping it is within a root-level directory and not at the root level itself. In other words, `/public/index.php` vs `/index.php`. Your quickstart in README.MD makes it pretty clear that you expect the latter, which is highly unsafe. See any number of poorly configured webservers that stop processing PHP for any reason but now show your site's full contents to anyone passing by.

I would strongly argue against _any_ magic in your framework. Specifically, routes: they should be explicitly defined. I still work with a legacy Symfony 1 framework project and I can't tell you how much I detest magic routing. For a modern example see how Symfony 2+ requires explicit route definition. Heck, how it requires explicit everything because magic should be left to magicians.

Your framework seems like it can only handle `application/json` and `application/x-www-form-urlencoded` requests, but not `multipart/form-data`.

Take these as positive criticisms of your work. It's "fine". I wouldn't use it, I would actively recommend against using it, but I would actively recommend against using anything that's not Symfony (or Laravel if I were drunk). I do not think your project is at the "Show HN" level - it is still far too under-developed.

Thank you for your work, it was great while it lasted!

Someone needs to come up with a better name for this. “Quiet quitting” absolutely does not imply the above meaning… that’s simply work and nothing else.

From the POV of a software developer I’d consider quiet quitting as doing the bare minimum work to not be fired outright and instead placed on a PIP with no intention of surviving it.

You play your cards right and you would basically be paid 6 months for minimal effort, between when performance degradation is first noticed, PIP deployed, and your company Slack access is finally disabled.