4 ms·
Yeah, same here. This framework development frenzy seems to me like procrastination from doing actual work. 'Gee, I finally have time to do this web site I alwa
by mszcz 6y ago
Yeah, same here. This framework development frenzy seems to me like procrastination from doing actual work. 'Gee, I finally have time to do this web site I always wanted! Well, let's start with the OS my custom browser will run on!'.
Please note, that this is not a dig at this particular project. I'm sure it's nice and all but I'm never going to use it because 1) what's the chance this'll be around and maintained in 6 months time? 2) no community support, probably no way to ask questions or see other people's questions, 3) what's the chance that 1 & 2 will change in a couple of months? This line of reasoning can be applied to most of the new frameworks out there I think.
- majkinetor 6y agoIts not exactly procrastination because while creating framework you are deep into topic and amassed knowledge helps you in general, no ? You can't understand anything until you build it.
- javajosh 6y agoIn general you shouldn't be creating a framework, you should be making an application.
- majkinetor 6y agoIn general, any non-trivial application uses micro-frameworks (that you write) and macro-frameworks (that you use or write).
- deleted 6y ago[deleted]
- mszcz 6y agoHey, I didn't say procrastination's not useful-ish. I once learned, among other things, the difference between sleet and hail but that critical knowledge was of no use to the client or the project I was supposed to be working on ;)