Email or username:

Password:

Forgot your password?
Top-level
Natasha Nox πŸ‡ΊπŸ‡¦πŸ‡΅πŸ‡Έ

@blacklight @cybeej @lorq There are multiple bad developments I see at work here. One would be "dependency hell", another one the abundance of "jack of all trades" libraries and frameworks that can't be split up at all. Web development became quite monstrous in this regard, though some IDE's (or compilers?) are also quick in silently attaching 3 to 4 megs of libraries onto your hello world program unless told otherwise, just in case you need them.

3 comments
Lorq Von Ray

@Natanox @blacklight @cybeej You are not wrong. And that is also why I have to have "the talk" with devs before they put fresh code randomly into production. Then I attack it to see where it breaks. Then I give them hell if it's a large business entity I'm consulting with. Sometimes we learn by doing. Sometimes the dependencies teach us lessons we didn't know we needed.

Natasha Nox πŸ‡ΊπŸ‡¦πŸ‡΅πŸ‡Έ

@lorq @blacklight @cybeej I feel like we should get back to the UNIX / GNU style of toolboxes (not sure right now where the philosophy originated from). Make a tool that does *one* thing, and does it exceptionally well.
There might be an extended philosophy to be articulated for frameworks or very complex tools that require massive flexibility (simple example would be a Browser).

Fabio Manganiello

@Natanox @lorq @cybeej yes, this one πŸ‘†

The UNIX philosophy was born in the AT&T Bell labs in the first half of the 1970s - another example of good symbiosis between public funding and clever engineering that I often mention, probably on par with the Apollo and Voyager programs.

Founding fathers of our industry like Thompson, Kernighan and Ritchie were behind it, and they had the right level of "eagle view" on what they wanted achieve on a system level to be able to break it down into smaller and reusable components that communicated over simple messages (pipes and signals), and where everything was a file descriptor, so everything could leverage the same abstraction.

It's the textbook example of a good abstraction to me. It introduced something on top of the "bare metal", but it was lightweight enough to be conceptually easy to grasp, and easy to extend. And you could pick whichever component you needed, without being an all-or-none selection of a framework.

Do-it-all monolithic frameworks with dozens of abstractions like Spring, Django, React, Symfony or Blazor are exactly on the opposite side of the spectrum compared to the UNIX philosophy.

@Natanox @lorq @cybeej yes, this one πŸ‘†

The UNIX philosophy was born in the AT&T Bell labs in the first half of the 1970s - another example of good symbiosis between public funding and clever engineering that I often mention, probably on par with the Apollo and Voyager programs.

Founding fathers of our industry like Thompson, Kernighan and Ritchie were behind it, and they had the right level of "eagle view" on what they wanted achieve on a system level to be able to break it down into smaller and...

Go Up