为什么在开发中使用框架？ [英] Why use Frameworks in Development?
问题描述
我曾经拒绝使用我自己没有构建的框架。我总觉得它会像其他人发展的大多数事情一样令我失望，或者让我沮丧。我的意思是，严肃地说，有些人不知道如何使用JavaScript，如果你要从它们那里拿走jQuery。
但是当你开始为底线公司工作时（你的举止表明你还没有，这没关系）并且被迫使用框架，你可能会发现自己很惊讶。 WordPress是功能齐全且可扩展的，CodeIgniter功能强大，对开发人员友好，jQuery非常接近JavaScript的替代品。
好的框架只是为了加速你的生产过程。你宁愿使用PHP而不是汇编，对吗？框架只是另一层抽象。 ：）
我绝对得到你所说的，谢谢你的回复！
我实际上不想使用汇编 - 虽然我还是想学习它，但那是另一个故事;也许PHP只是我在工作流程中习惯接受的一个框架，但我从来没有真正把它看作一个框架，更多的是作为一个基础开始（虽然它实际上基于C，但是来吧）。 />
我认为不使用框架的主要原因并不是我不相信第三方代码，这只是一个小问题;使用这些的真正问题可能只是使用服务器端脚本，其中安全性是一个问题 - 当您使用开源框架时，您总是需要了解特定于框架的漏洞，这是我宁愿的时间花了更多令人兴奋的事情。
我自己做这些事情的主要原因是我只是使用简单易用的东西而感到无聊。你知道，第一次验证表单并将所有内容写入数据库 - 这是一种很棒的感觉。但是现在我只是觉得残障再做一遍（你需要这些东西）。
使用JavaScript框架可以简化我作为Web开发人员的工作，但这需要我工作中的每一个快乐，因为我唯一的乐趣就是尝试新事物，并试图了解他们的工作方式。我发现让它变得有趣，最终让它发挥作用。
所以我想这是我现在的生活方式。但你是否适合在公司中使用框架;我在这些方面运气不错;我工作的公司从零的网页开始，所以我从头开始构建它，现在我有了自己的框架（当然有自己的bug）;好的部分是每次我需要改变一些我确切知道在哪里搜索它的东西。
哦，在我忘记它之前 - 我可能有一天会考虑使用jQuery及其竞争对手，但在我这样做之前，我希望能够 - 至少在理论上 - 建立我自己的。因为我不想使用任何我无法看到的东西。 ：）
哈哈。倾听你就像是在倾听自己。 :)
在我创建自己的JavaScript框架之前，我绝对拒绝尝试jQuery。在开发我自己的MVC框架之前使用CodeIgniter也一样。在我开发自己的博客软件之前，我从未使用过Wordpress。在尝试比赛之前，我重新制作了自己的每个应用程序两次。
但是现在，经过几十个未完成或被遗弃的项目，我发现在阐述基础知识后，我专注于功能。虽然，我已经发誓最终恢复我的旧项目并用我自己的东西替换CodeIgniter + jQuery。 ：3
无论如何，这样做会更好。我可以花费其余的开发过程进行重构。网站维护并不好玩。开发后端是。 :)
至于能够读取代码，CodeIgniter和jQuery是非常易读的，只是不容易理解在哪里发生的事情。但它们很容易扩展，因此它很少成为问题。你可以覆盖他们的大部分功能。
我还能说些什么。你确定了它。
我相信我们都将走向光明的未来 - 至少在所有的电源都消失之后我们生活在世界中心，躲避机器。 ：）
I used to refuse to use frameworks that I didn''t build myself. I always felt like it''d either disappoint me like most things that other people develop or that it''d dumb me down. I mean, seriously, there are people that wouldn''t know how to use JavaScript if you were to take jQuery away from them.
But when you start working for bottom-line companies (which your demeanor suggests that you haven''t yet, which is okay) and are pressured into using a framework, you may find yourself surprised. Wordpress is full-featured and extensible, CodeIgniter is powerful and developer-friendly, and jQuery is damn near a replacement for JavaScript.
Good frameworks are only here to speed up your production process. You''d rather use PHP than Assembly, right? Frameworks are just another layer of abstraction. :)
I absolutely get what you′re saying, thanks for your reply!
I actually don′t want to use assembly - though I′d like to learn it anyways, but thats another story; maybe PHP is just a framework I am used to accept in my workflow, but I never really saw it as a framework, more as a base to start with (though it′s in fact based on C, but come on).
I think the main reason for not using frameworks for me is not that I don′t trust third party code, that′s just one little side; the real problem in using these might be only with using server-side scripts, where security is an issue - when you use open source frameworks, you always need to be up to date about framework-specific vulnerabilities, which is time I′d rather spent doing more exciting things.
The main reason I do these things on my own is that I got pretty bored by just using things which are easy. You know, the first time validating a form and writing everything into the database - that was a great feeling. But now I just feel stump doing it all over again (you need these things all the time).
Using a JavaScript framework would simplify my work as a web developer, but it would take every joy out of my work since the only fun I have is trying out new things and trying to understand the way they work. I find it exciting to fiddle around with it to make it work in the end.
So I guess it′s my way of life by now. But you are right about being constrained to use frameworks in companies; I′ve had good luck in these terms; the company I work for started with it′s webpage at zero, so I built it from scratch and now I have sort of my own framework now (with its own bugs of course); the nice part is that every time I need to change something I know exactly where to search for it.
Oh and before I forget it - I might someday consider using jQuery and its competitors, but before I do that, I want to be able to - at least theoretically - build my own. Because I don′t want to use anything I can′t look behind. :)
Haha. Listening you is like listening to myself. :)
I absolutely refused to even TRY jQuery until I made my own JavaScript framework. The same with using CodeIgniter before developing my own MVC framework. And I never used Wordpress until after I developed my own blog software. And I re-made each of my own applications twice before even trying out the competition.
But now, after dozens of unfinished or abandoned projects, I find myself focusing on the functionality after laying out the basics. Though, I''ve sworn to eventually revive my old projects and replace CodeIgniter + jQuery with my own stuff. :3
It''s better that way anyway. I can spend the rest of the development process refactoring. Website maintenance isn''t fun. Developing the back-end is. :)
As for being able to read the code, CodeIgniter and jQuery are quite readable, just not exactly easy to follow in terms of what happens where. But they are easily extensible, so it''s rarely an issue. You can overwrite most of their functionality.
What more can I say. You pinpointed it.
I believe we are both heading towards a bright future - at least until all of the power supplies are gone and we live in the middle of the world hiding from machines. :)
这篇关于为什么在开发中使用框架？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
