3 ms·
The irony here is that programming languages and their native APIs are (apparently) not considered part of the stack™ and must be kept away as far as possible f
by masswerk 6y ago
The irony here is that programming languages and their native APIs are (apparently) not considered part of the stack™ and must be kept away as far as possible from the hands of developers, since this introduces the danger of injecting knowhow.
- jordache 6y agoProgramming languages are general purpose. When you build a specific solution, why opt for a general purpose raw language, when a framework provides a richer set of purpose specific tools? Why get al dogmatic about programming purity? When you don’t intent to use the language’s raw api to that an extend, then your stack is more represented by the framework, rather than language. Not discounting the necessity of mastering the language to be a strong engineer. However the framework being used is just as relevant, if not more so, than the underlying language
- ThrowawayR2 6y ago> "When you build a specific solution, why opt for a general purpose raw language, when a framework provides a richer set of purpose specific tools?" A web framework is often a one-size-fits-all solution designed to handle a variety of use cases, some of which conflict with each other. Like a swiss army knife, it does everything but none of them particularly well.
- deleted 6y ago[deleted]