85 karma · joined September 29, 2013
But it depends on the complexity and size of a project and how many developers are involved. I prefer frameworks too, but for a small WebApp, it is overkill to use frameworks like angular/backbone/whatever.
"Get the job done" got replaced with "its cool to use xyz".
I created http://apidocjs.com and had the problem that i needed some "simple" logic in the templates (handlebars). For such things i must implement a separate view with configuration/data modelling/... and Helper function, but that makes the project-output complex, because i want that the people can change the template as easy as possible. Quick & dirty developed i create many duplicate code in the template to avoid a separate view. It was a silly idea, it makes the template more complex ;-) And only because of some missing logic.
Or is an add-on planed for permanent shares (e.g. for companies)?
And Performance? Which Performance? They call tasks that do something, and the task need performance.
I dont see the problem, you get what you pay for.
And you can enable Swap space, so where is the problem? We talk about 5 bucks in a month !
Sorry, but it is correct that google kick you out.
And i cant believe that app users understand what they installed in background. I think many users complained about the ads and thats why google react.
Casandra post a nice article about that: http://blog.teamspir.it/productivity/journaling-is-productiv...
For a small test system ok / or hobby project, but not for a productive usage.
What would you do with links if the new Web-Designers change all URLs (because of a "fancy cool" new SEO style)?
Which problem did you solve with your kind of view of an API ?
If the companies grow you are absolutely right, but what did this companies do that they grow ?
That is the crucial question. I think there are many services like Dropbox before Dropbox exist, but nobody now them.
Hope to find it soon on some CDNs.
But this is in case you have a bigger JS-File (e.g. for a Web-App) and your customer visit again, so you only have to transfer a small peace of data.
But iam not sure if the performance / traffic advantage is so high, that dyno justify the effort. And you have one more source of possible error, so i did not think many developer will use it.
The idea is good, but the solution should work automatically in background on the transportation layer, between browser and server, not for app developer.
@Jason Anderson: Call google - chrome developer if they implement it in their Browser and write an apache Plugin ! :-)
The problem for the mass of developers is, that they "fall in love" with their CMS and that make them blind for obvious things.
We shift away from CMS as central point for web and web-application. CMS is only a tool to maintain simple static data in various languages for many people. For everything else (like shops) we use other systems, that are NOT a integrated part of a CMS.
If interaction between CMS and ohter systems is needed, implement a separate and clean API.
Is it a perfect Engine, that need no support, or did nobody use it.