For all the hate PHP gets (or used to get) it’s ecosystem is amazing. And so is the language and standard library itself for the most part. It still inherits some of the original issues, but a lot of work has been done to minimize them.
It’s funny because despite all the fearmongering about Microsoft’s Github acquisition it feels like it only improved since then, while Gitlab has done a shitton of questionable and shitty decisions, a ton of critical security issues and in general feels like (at best) they don’t know what they are doing.
The only thing Gitlab has going for itself is that it’s self-hostable, but they still retain a large amount of control.
This is cool but it’ll be a nightmare to update.
Also, chances are that if you use Alpine the person using your image already has the base layer downloaded, so your image might actually be “bigger” for most people.
Yep, exactly my thoughts. Unfortunately very few developers really think (about related but not completely adjacent code) when they implement stuff (and that’s when they are even “allowed to” by the task requirements) and even fewer have true knowledge of security and common pitfalls and whatnot to avoid such issues.
And even when you have those you still need good practices and code reviews where the rest of the slip ups is caught.
Ehh their engineering simply seems to be subpar. I’ve read some of the CVEs and if they followed best practices the issues should’ve never happened. It doesn’t inspire confidence.
Well then you aren’t probably taking advantage of most of the stuff AWS offers and is actually really good for. Which isn’t really criticism, but then I wouldn’t really call it cloud? It’s more like just infrastructure as a service.
Oh I didn’t even mean that; just the (possible, shorthand/unreadable) syntax alone, weird typing, etc. seem like it’d be hard to work with.
It’s also funny because “allowing clusterfucks” is a huge reason why PHP was so hated; when you took care to write it properly it wasn’t bad even in the early days.
…so you have not, in fact, used PHP in the past decade or so. Thanks for letting us know.
With AWS especially there is a shitton of proprietary stuff. Most of the friction is in knowledge however; the cloud environments differ, are configured differently, have different limitations and caveats, etc. Someone who has only ever worked with AWS will have to learn a lot of things anew if they switch. Hell there’s a reason why “AWS engineer” is a dedicated role in some companies.
Now, if you only manually set up some VMs and configure them like you would a regular server then sure, it’s easy to migrate. But when you are missing 99% of the features of the cloud environment are you actually using it?
When you use a cloud solution (and especially one with a vendor lock in like Amazon) then yeah, you are fucked there too and I’d question why you did it in the first place.
If you have your own infrastructure - be it a server at home or whatever - then you can always just move it elsewhere, get some other ISP, whatever. There is no lock-in. Inconvenience, sure, but you can migrate elsewhere. That’s just not true about all the other things mentioned, or the friction would be much higher.
Ruby seems like a clusterfuck for anyone who doesn’t work on a project alone, change my mind.
You got it backwards there. PHP was pretty bad (mostly because it was easy to pick up so novice and shitty programmers used it a lot), but got insanely better, and it absolutely stood the test of time - most of modern web still uses it and it isn’t going anywhere. There are also few languages that would have such a robust ecosystem where you could whip up a solid, complete app in a few hours. JS comes close but its ecosystem is a clusterfuck. Everything else has poor third party support - be it libraries, connectors to various services or just simply best practices (for web).
Have you used modern PHP with its ecosystem and frameworks? It’s actually really solid, and really good at what it aims to do.
So while this is probably a good answer to the hypothetical question, that’s actually not a good thing, you realize that, right?
Special tools exist because different problems require different solutions. And sure, then can be a huge overlap of those tools, but you can’t literally do everything with a single tool; chances are it’d be a shitty tool. Either you can’t actually do everything with it, or it’s so complex that you don’t want to use it in the first place.
Javascript is somewhere in between, in the sense that it’s both kinda terrible for most of the jobs you mentioned, while also not actually usable for “everything” - i.e. it’d be a terrible language for anything that needs to be performant or reliable. Hell, we have JS in crap like Gnome now and it’s a nightmare.
Or, you know, Gitea or such.
Because while you do have control (and “copies”) of the source code repository, that’s not really true for the ecosystem around it - tickets, pull requests, …
If Microsoft decided to fuck you over you’d have a hard time migrating the “community” around that source code somewhere else.
Obviously depends on what features you are using, but for example losing all tickets would be problematic for any projects.
Apparently Mozilla won’t be even accepting PRs there so it doesn’t matter much.
How do you network with zero or close to zero initial “connections”?
Sure it’s easy to get jobs when you already have a dozen happy clients who recommend you to others. But how do you start initially? Through friends and their connections?
I mean that has been their business model for some time now, just like with most other software nowadays. But unlike most other software their prices are extremely reasonable; when you buy it consecutively for years you get progressive discounts. I actually *need * only one editor but I pay for them all because the cost of the full package is just slightly higher and their IDEs are amazing. A few times a year I use one of the “other” editors for personal projects and such.
Yep… And you can’t donate to Firefox development. You’ll only fund the nonprofit and its goals, the money doesn’t go to Mozilla Corporation who do the actual development.
Also, this isn’t even compatible with copyright law in some countries. I.e here you can’t give up authorship at all; you can only grant an irrevocable, perpetual license (that might even prohibit you from distribution yourself and such) but you’ll always be able to say “I made this” no matter what their license says.