sowhatquestion

As a Laravel dev who almost went down the Rails path, I’m curious: what advantages do you think Rails has over Laravel at this point?

This is the Soylent hypothesis. "Processed food" as such is not the problem—it's processed food used as a delivery vehicle for as many addictive sugars, fats, and simple carbs as possible. I would guess that the bad kind of processed food is much more common because it's both easier to make and more profitable (flour is cheap; oil is cheap; protein is expensive).

The same hypothesis (that we can reclaim the idea of processed food for nutritionally complete foods) is also on display in a product like Vite Ramen which explicitly patterns itself after a nutritionally dubious staple food (i.e., instant ramen). I would expect to see more startups in this space in the next few years.

I would recommend Kafka's short story "The Great Wall of China"

> It's so easy in the vacuum of a single developer with a single application to think everyone should keep up to date, but the reality is most of the PHP sites on the internet are owned by non-technical people

"Non-technical" people who don't plan for maintenance costs to their software (including maintenance to keep up with dependencies like PHP) don't get a ton of sympathy from me ¯\_(ツ)_/¯

I've heard this criticism of Laravel a couple times and never understood it. I've been using the framework for years and have never had an issue with upgrades. There is a clear and comprehensive upgrade guide with each release, as well as a third-party package called Laravel Shift that can inspect your code and perform automatic upgrades in many cases. I've found there are only one or two breaking changes per minor version release (which seems reasonable to me), and they are always well-documented.

Aside from that, I'm glad you've highlighted Laravel, which—despite being the most popular server-side Web framework on GitHub—gets virtually no attention from HN. It's typical to use Laravel in the old server-side rendered Rails paradigm (which is still probably best for some applications), but I've had success using it to develop APIs as well. Core features like the ORM, job queues, dependency injection, email templating, etc, are very solid, and the ecosystem of packages around it is phenomenal. I would recommend it to any Web developer.

> How do you compose two base classes into a subclass?

In most other OOP languages besides JS, the obvious answer would be to use traits.

Honest question: what's so bad about the reddit redesign?

It would be far from the first HN article (or comment) that failed to make a distinction between "poorly designed object-oriented systems" and the very idea of OOP, design patterns, etc

I was glad to see this posted here. Reading it again, I thought, "I can't be the only one who works in ad tech yet broadly agrees with this proposal."

Very impressive. Does the federal government have anything comparable to this?

I'm a (primarily backend/API) web developer, with 5 years of experience at this point, and I've been planning to apply to Georgia Tech OMSCS in order to branch out into different specializations like ML and data science. A better foundation in algorithms etc. wouldn't hurt either--my bachelor's is not CS-related.

This article gave me pause, since I've never heard much skepticism expressed about a Comp Sci MS before. Is it really so overrated?

They've addressed this many times. There are different "grades" of maltodextrin with different glycemic indexes. Soylent uses a higher grade with a low glycemic index. Google "low DE maltodextrin." Soylent also uses other low-glycemic carbs such as isomaltulose.