81–90 of 90 posts
jQuery is ok for super simple sites, but modern interfaces becomes more and more interactive and complex. Attempts to organise some logic via imperative jQuery way usually turns into hell. So, first of all it isn't scalable.
Btw, I wrote an article how Vue.js can replace jQuery for "websites", not only for "web applications": https://medium.com/@borisadimov/vue-js-the-second-breath-of-...
Earlier quoted context omitted.
I'd never heard of this library and I spend a couple hours a day reading developer news so I wouldn't call this popular. I'd also argue that this as a current generation framework. I only did a brief skim but the patterns remind me of a Knockout or Enyo codebase with data binding between components doing explicit dom manipulation. The contributors tab shows a 2014 start but I'd have guessed a 2010-2011 start from loo…
You'd be surprised. UI5 is made by SAP as their go-to UI technology. SAP's profit last year was over 6B euro and it's used in almost every large enterprise out there. It's just hard to see as a tech company because it's not consumer facing. I'm an SAP and UI5 developer.
Earlier quoted context omitted.
PHP is some tool that was never really good, but had some compelling features that no other tools provided. Except that now there are better tools for any task it solved, excluding the task of "maintaining a PHP codebase". If you are starting a new project on it, you should indeed feel silly.
Have you looked at the PHP landscape over the past few years? You may still not love the syntax, but PHP as a language, an ecosystem, and a developer community is extremely strong. It's a fantastic choice for a web app in 2016.
Also honestly, I don't think I should look now. The PHP applications I see around are still the ones getting serious vulnerabilities found every week, the same ones that other communities found ways to pack the solutions into tools and conventions that are easier to use than not to. I also don't see anybody claiming PHP has any new template system to replace the dated original one.
I've seen some progress on the language, but not nearly enough to make it compelling. I have plenty of stuff already on my ToTry list, PHP would have to say something better than "I'm not a complete mess anymore" to enter it.
Earlier quoted context omitted.
Have you looked at the PHP landscape over the past few years? You may still not love the syntax, but PHP as a language, an ecosystem, and a developer community is extremely strong. It's a fantastic choice for a web app in 2016.
Honestly, no, I haven't look at it in the last 7 years. (It's being that great! Thanks for lighting-up my day.) Also honestly, I don't think I should look now. The PHP applications I see around are still the ones getting serious vulnerabilities found every week, the same ones that other communities found ways to pack the solutions into tools and conventions that are easier to use than not to. I also don't see anybody…
Earlier quoted context omitted.
I disagree. jQuery was the tool that acts as a "polyfill" for cross-browser compatibility. Nowadays jQuery is dying, not because of React, Angular or TypeScript, Elm. It's dying because of browser-support of `querySelectorAll`, unified event handlers, unified AJAX request API and others. jQuery had it's time. Now you just use "vanilla" JS and it is enough. No external dependencies for your landing-page / non-web-app…
Here's what I tell my devs: Yes, "you might not need jQuery". But, the first time you have to log real hours fixing a cross-browser bug that the jQuery team already took care of, I'm fucking firing you. Choose wisely.
Earlier quoted context omitted.
Honestly, no, I haven't look at it in the last 7 years. (It's being that great! Thanks for lighting-up my day.) Also honestly, I don't think I should look now. The PHP applications I see around are still the ones getting serious vulnerabilities found every week, the same ones that other communities found ways to pack the solutions into tools and conventions that are easier to use than not to. I also don't see anybody…
You can of course choose to still avoid it - but your advice to other devs to do the same makes little sense. It's a completely different beast than it was 7 years ago.
Because the language is a bit archaic (has maintainability problems for large codebases, has the "too little power" problem for small codebases); as far as I have looked, the ecosystem still does not include a good templating system (although it does include most of the tools available on other web ecosystems); and the community is still heavy on applications with the same kinds of security bugs they always had, and many, many "X-only" developers.
And, anyway, fixing those outstanding problems can only make it an ordinary language. And there's no reason to look at any language that the best claim is "it's not worse than any other random language".
Of course jQuery is still a thing.
Can I ask how old you are, linkula? This seems like a question a 13 year old would ask.
Earlier quoted context omitted.
I disagree. jQuery was the tool that acts as a "polyfill" for cross-browser compatibility. Nowadays jQuery is dying, not because of React, Angular or TypeScript, Elm. It's dying because of browser-support of `querySelectorAll`, unified event handlers, unified AJAX request API and others. jQuery had it's time. Now you just use "vanilla" JS and it is enough. No external dependencies for your landing-page / non-web-app…
Here's what I tell my devs: Yes, "you might not need jQuery". But, the first time you have to log real hours fixing a cross-browser bug that the jQuery team already took care of, I'm fucking firing you. Choose wisely.
Very simple and as always it depends on what you want. You want to do the cool new thing? Then use one of the younger frameworks but expect things to be slow, buggy, and ungooglable. If you want to make money wiht little effort then use the older frameworks that survived (e.g. jquery).
How does one make money? Help please
2. Profit