Will things like setting up a “stack” in portainer on docker be able to use the github alternatives like codeberg? or will those kinds of things need to be rebuilt?
Anyone got a commmand line tool change all my stuff? Because if I have to do change all the remotes all the time, for dozens of projects I’m going to lose my mind.
Also the migration on gitlab/codeberg looked like an amount of effort that doesn’t round down to zero.
(note, the GitLab Enterprise Edition, which is provided to the public on gitlab.com, is (like GitHub) trade-secret, proprietary, vendor-lock-in software)
Isn't EE source-available but proprietary? Plus if you just use the free tier you're not using any enterprise features
How long ago? ROOT (and other frameworks like GEANT) using C++ has been the standard for over 15 years, but probably longer. I think my advisor was of the last generation that had to write in Fortran.
Nah, Python 2.7 got way more support than it ever deserved because people just refused to switch to 3. Hell, people were starting new python projects on 2 after 3 came out.
For about the first five years of its life, it was eclipsed by Perl. That’s about it. I don’t think anything will ever unseat Python as too many people’s first and last language.
BASIC was meant as a teaching language. Python is a real language that’s simple enough to be a teaching language. It also runs the same dialect on every machine, which BASIC never did.
Being the second best language at everything, it gets used for everything because people don’t want to learn the first best in any given niche. Python isn’t the best choice for numeric applications, but with NumPy, it’s adequate, so why bother learning R? Even if you knew R already, you’re going to run into a lot of Python code for that domain from other people. You’ll be swimming against the current, and why bother?
Python is one of my primary languages (the other one being Rust). But it honestly isn’t the easiest language to teach - I’m saying this from experience. There are so many concepts at play - name binding, iterators, generators, exception chains, context managers, decorators, … . I could go on and on. Teaching becomes hard because any basic question could become a journey into the rabbit hole of python semantics.
Python is, however, a good first language for self learners. (Note: teaching vs learning). Python behaves intuitively. It’s designed in such a way that if you guess something about the language, you’ll probably be right.
Web testing is also done in python. Selenium has support in all major Python test frameworks. I’ve done SE-only tests in Robot, hybrid SE/Python using BDD with Behave, etc.
Unless I’m testing a language-specific API, I’m probably going to use Python…
I’m guessing that’s because you’re a python developer though. If you’re a frontend developer who knows JS then why wouldn’t you use that for your tests? (Apart from the fact that JS is horrible, but you’ve already accepted that suffering by becoming a web dev)
@nifty I have nothing against Ruby and think it’s a nice flexible language. At the peak of RoR though, all the asshats were all over Ruby.
My problem with Ruby wasn’t even RoR, it was with the way the asshats valued creativity “cleverness” which seemed to mean writing code in the most cryptic ways possible. These folks took what should be an expressive language and wrote scripts that rivaled Perl’s worst “read once and never again” scripts.
This wasn’t “creativity over code” so much as it was the tail end of y2k and all the greybeards were canned so none could teach the shiny whiz kid how to code like an adult.
Without the linus-like code review sessions, they never learned why and how to improve.
Now their kludge-bro mentality has raised a whole new generation.
And that’s why people don’t know not to flatpak or npm themselves into a solarwinds sploit.
RoR is too much magic for me. Getting started with any new code base is such a pain that I never want to do again. As a manager, I’ll avoid any job post that mentions Ruby. I have maintained projects written in Delphi, Centura, Java, C#, PHP and none of them even come close to the pain of RoR. Java and C# are notorious for ceremonial interfaces but that’s nothing compared to trying to figure out RoR automagics.
Maybe in enterprises settings what you say makes sense, but for the small to medium startups I usually work for, RoR is great. It’s super easy to prototype and switch lanes. If I had to do what I do in Java I’d go insane. As for Delphi…
The RoR “magic” being obtuse is extremely exaggerated most of the time and more meme than reality. If you think PHP is better, by which I guess you mean Laravel, how on earth is that less “magical”? React? Next? I’ll take Ruby any day.
React can go fuck itself with a pineapple, fuck that piece of shit. Every project I’ve had to deal with that used React was an absurdly bloated mess because it imported fuckloads of React plugins and addons.
There is a lot of magic in Java. Try Spring Boot for example, and things magically connect together with annotations, or somehow methods get injected onto interface on the fly, or an http interface maps onto a function with parameters because the runtime is doing it. This is most evident when you set a break point in some class and there might be 4 or 5 mystery functions it passed through between it and where you thought it was calling from. Sl4j, Lombok, Hibernate are doing the same kind of thing.
I worked at Shopify up until a year ago. github.com/shopify/shopify repo powers almost every inch of Shopify’s infrastructure and is entirely a rails monolith. It is not the same as saying Twitter is still rails.
@towerful I mainly program in Go, so when I see all that extra software I notice how much easier it is when I get to just rely on the Go runtime. It does a lot of the heavy lifting done here, but the resulting code is not as clean. Actually just today I read through Mastodon’s code to track down a bug in my in-progress ActivityPub service (in Go) and found the Ruby really easy to navigate!
It probably wasn’t a big deal when it was a niche project until Twitter imploded. Then all the public instances got overloaded with new users and the limits became obvious.
A better design is Lemmy which is written in Rust so it has far more scalability. It’s compiled and because it’s tokio / actix based, it can also do a lot more stuff asynchronously so it’s not spawning thousands of threads to cope with concurrent requests.
@SpaceNoodle I’ll always be sad how GitHub helped popularise centralised workflows. Such an amazing opportunity for a big cultural shift, but it didn’t go anyway as far as it could have.
Git owes a lot of its popularity to github. Without it, there’s a good chance that mercurial would have taken over. In addition, the centralized workflow was what made both git and github popular. It simplified git usage enough to let a lot of novices get started.
I’m in no way a fan of centralization that github represents. But I think a decentralized workflow using git was a lost opportunity. People complain a lot about the git-email workflow. But I see no reason why it couldn’t have become as easy as using github if the effort spent on github was spent on git-email tools and user experience.
Even in 2024, I say that Ruby is one of the best common languages available. While there are some weird syntax choices, and a lot of rope to hang yourself with when it comes to subjects like metaprogramming, it is a better Python than Python, in that it has a clean way to approach problems, and a simple structure to make coding clean and easy. The best part of Ruby is that its tooling is great at pushing best practices, like concise methods, good naming conventions, tests with single/aligned assertions, etc. I’ve taken many lessons from Ruby into other languages I use.
Rails, on the other hand, is totally different. Today, Zed Shaw’s essay on Rails is as accurate as ever, in that many Rails shops have just ignored years of best practices on the web, and opt to do things their way because it’s “better”.
programmer_humor
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.