Earlier quoted context omitted.
The author started their post by defining what they mean by "framework" and it's pretty clear that your snark "do you have to write the HTTP server yourself" is way off from that definition. Also, if you don't have any experience with framework-free web applications - to the point where you can't imagine how one might exist - perhaps it would be a good idea to familiarize yourself with one? Yes, they exist. I've writ…
I don't accept the distinction between frameworks and libraries. Once past the most trivial stages, any codebase uses frameworks, often multiple of them. But they aren't all published or named as such. Often you create them yourself. I have myself written lots of things that work like a framework. Inversion of control is a powerful pattern. There really is no clear cut difference between a library and a framework. Al…
Using a framework will harm the maintenance of your software
491–500 of 550 posts
Re: Using a framework will harm the maintenance of your software
#492Earlier quoted context omitted.
If you were to write a program that relies on those aspects of the abstract C machine and don't provide those aspects, then you might have an argument, in that in that case the observable behaviour would be different, but if you choose not to make use of that functionality, its presence is entirely irrelevant. This is also massively shifting goal posts. You first wrote "At which point it is no longer C". By your argu…
Everyone knows Linux is actually written in GCC C, and Google has burned lots of dollars making it work with clang, if it was proper C, that wouldn't never been an issue.
Re: Using a framework will harm the maintenance of your software
#493Earlier quoted context omitted.
The whole point is that there won't be a mess or at least as much of it if you use a framework. How is this so lost on people here so often!
Perhaps because the framework is hiding the mess from you and you have no idea how it is accomplishing critical portions of your application. Out of sight out of mind.
User.add({})
I think you need to better examine what you consider critical and maybe try to further break down the word critical for a better understanding of where to focus your time and energy while coding.Re: Using a framework will harm the maintenance of your software
#494So frameworks try to manage this gap, and the only solution, IMO, is to invent language that integrate more advanced semantics to avoid the necessity of frameworks
Re: Using a framework will harm the maintenance of your software
#495>> A team that defines the standards, processes, practices, frameworks or architectures that other teams must follow..are amongst the lowest performers. It is a matter of degree. If teams responsible for this are legitimately trying to make things better (and not just trying to infallible high priests), it can be helpful. If there are established ways of doing things, it can sometimes alleviate the need to make the s…
At a minimum, Technology Standards Czar has to be earned. You can't just conjure up a spot on the org chart one day and staff it with some outside rando with a long, jargon-stuffed resume. The Technology Standards Czar should be an internal hire with a history of making good technology decisions for the org.
Re: Using a framework will harm the maintenance of your software
#496Re: Using a framework will harm the maintenance of your software
#497Re: Using a framework will harm the maintenance of your software
#498Earlier quoted context omitted.
Everyone knows Linux is actually written in GCC C, and Google has burned lots of dollars making it work with clang, if it was proper C, that wouldn't never been an issue.
And yet almost everyone would still agree that "GCC C" is also C, so this is entirely irrelevant to what was being discussed.
Re: Using a framework will harm the maintenance of your software
#499Earlier quoted context omitted.
> 1. Every sufficiently complex framework-free application contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of a framework. After 25 years of experience writing software I can honestly say I have encountered many people that agree with this, and perhaps all of them (every single one) have not actually experienced writing an application without a framework. This sentiment sounds correc…
Any time a piece of software abstracts a repeatable pattern, that’s a ‘framework’. All a framework means is that there is a coherent, repeatable model for implementing the building blocks out of which the application is built. Even a simple command line program with hardly any functionality soon runs into the issue of having more than one command-line argument or environment-variable based configs. And a sensible, ma…
Re: Using a framework will harm the maintenance of your software
#500Earlier quoted context omitted.
> Not all software has an implied framework within it. The definitions of "framework" are always a sticky issue. If you take "framework" at face value, it's minimally a set of idioms. "an essential supporting structure which other things are built on top of" - which necessarily includes a mental model of execution. This relates closely to why naming, in software development, is considered so difficult. All software h…
Well, I don't disagree, and we could almost label that "framework zero", and also hence the reference to Unix utilities and their assumptions regarding stdin/out, but I am also taking a contextual cue from the article linked at the top which is clearly taking aim at large pre-chewed boluses of code such as Rails, Django, Drupal and so forth. I am just about old enough to have even toggled in a program on the front pa…
Not saying that I could write code directly in octal... but I was pretty darn close. Of course, it helps when your assembly language consists of just eight instructions.