351–360 of 404 posts
Earlier quoted context omitted.
I remember switching from mootools to jQuery back in 2006ish. Thought it was fantastic. Awesome it’s still around. We still use it from Time to time.
Don't forget Prototype ( http://prototypejs.org/ )
Earlier quoted context omitted.
This is just intellectually dishonest. It completely depends on whether your libraries have breaking changes and how your app is structured. Many legacy projects use old versions of ORMs and frameworks that don't support PHP 8. So now you're also upgrading code igniter and you're looking at hundreds of files that call it's ORM
No. If we're talking about tech debt (that's not what parent was talking about by the way) then JS is a magnitude worse. Running old projects from JS ecosystem can require multiple miracles, not only code refactoring. And your example, codeigniter, is one of the worst examples in PHP. Not only it is a framework that has minor usage: https://trends.google.com/trends/explore?q=codeigniter,larav... It is infamous for be…
Saying Code Igniter is not used in a lot of places because of Google trends is wrong for a lot of reasons, but the biggest of which being your graph shows laravel and codeigniter neck and neck a decade ago. Who cares whether new projects are started in code igniter? PHP is mostly legacy apps, and there are other frameworks with similar nightmare stories.
Again, JS is bad too, but we have to completely rewrite sites due to some PHP framework upgrades because PHP let's people do really dumb ORM templating.
I have no idea what you're referring to with your distinction between tech debt and server upgrades. I'm talking about server upgrades, clearly. I'm just saying if you upgrade PHP on an old project chances are things will break. This happens with Laravel and Slim too.
Earlier quoted context omitted.
You're making no sense. Functional programming is more than just "about functions". DOM APIs are the embodiment of 90s-era OOP. There's literally nothing functional about them. All [1] "functions" are methods defined on very specific objects. You can't even get a proper reference to them without binding them to specific object instances What exactly is functional about this? const newDiv = document.createElement("div…
> What exactly is functional about this? A series of function calls that each do something and each returns a value. > Okay, here's an easier question. What will happen here, and why? A function call that does something and returns a value, because in this language complex types are passed by reference.
Functional programming uses stateless, immutable transformations to contorl data flow. The second you instantiate an object with some internal properties that change in memory, you are no longer programming functionally
Earlier quoted context omitted.
Just want to say I appreciate you for doing that.
Thanks :) It just seems like good practice. I want my sites to be as fast, minimal, compatible and as usable as possible, while still looking and feeling modern.
Earlier quoted context omitted.
You haven't worked with Vercel. Just connect your git account and you have a fully git-flow based server, with preview urls for every PR. Especially for small projects ideal. Running it on a VPS is a skill on it's own, for both, if users had known to use NVM (which is explained in most top articles in Google) it would have not been a problem and if they don't know they should accept the learning pains of running prod…
> Upgrading PHP version is even more painful, I've tried to do version updates, and was alway easier just to build a new server. I upgraded PHP 7.2 to 8.3 for a business client yesterday. It was a CentOS VM. It took maybe 5 commands, no server restart involved either. I could barely bill an hour and that is because I kept tail -f their logs to see if everything went smooth. And it did. How is that painful?
You might have had a smooth experience, and happy for you. But PHP didn't have, maybe it does now, such a good version manager as NVM.
But yeah we also had once where all the way back where we didn't do it with NVM and that was a pain in the ass.
Earlier quoted context omitted.
No, if you actually make modules with jQuery where it’s creating it’s own DOM tree, it’s no different from what React & Co are doing. Reasoning about the DOM structure has almost never been an issue in my almost 20 years of professionally doing this junk. The complexity has always been elsewhere.
And you're arguing the complexity that has to be somewhere should go in your custom built jQuery modules instead of components built with a well-known framework? I spent years maintaining front-end code built by devs who believe their way of doing things was better than what's popular in the industry and I disagree about jQuery entirely. jQuery is a low level tool and always ends up biting people as the project grows…
jQuery + the DOM are well known frameworks. ;P
Earlier quoted context omitted.
see, this is where i'm not cool with this newness. i've spent years getting away from procedural, and switching to functions, classes/methods. now, we want to get away from that and go back to procedural? that's all fine and dandy, but you're trying to have a new trick conversation with an old dog that just doesn't care. you're bringing some sort of logic to a conversation where it's not needed. it works for me. i do…
> now, we want to get away from that and go back to procedural? AFAIK, we are all still programming browser UI with Javascript. It is an imperative language, about as stateful as you can get. Now, if you managed to do your frontends with Haskell or Prolog, I'd be interested on learning how.
Earlier quoted context omitted.
You normally want to see things locally as you develop them. Vercel is cool and all, but doing a git push and waiting for the build every time you want a refresh? Nah, that's not viable. And almost everything mentioned above for deployments applies to your own dev machine as well.
Okay then your comment is weird, windows & mac dont have distribution with node versions lower then LTS. It can be an issue on ubuntu/linux having an outdated registry. But nextjs clearly states minimum node version in their docs: https://nextjs.org/docs/getting-started/installation And how to install every version you want NVM, that's on the user if it didn't work. That's not something different then can happen with…