12/27/2022 0 Comments Direct url mailman hostgator![]() ![]() Facebook naturally employs a few people to work full-time on Mercurial, and I don't think they're the only ones.)Ītlassian's decision about Bitbucket is regrettable. (The majority of engineers at Facebook all work in one enormous Mercurial repo. Mercurial isn't going anywhere or shutting down anything it's open-source software with some very large users and committed developers. > when mercurial shuts off the hg we'll even lose the source to some of them.Īre you perhaps thinking of when Atlassian removes the Mercurial repositories hosted on Bitbucket? Nonetheless, the screams from the first ones scared the later. I should know, I've been moving from industry to industry for 10 years, all my clients are different, but most of them end up with similar stuff in their repo because Pareto is a thing. Most migrations are Django/flask websites, math teachers exercises, physicists scripts, sysadmin tools, etc. Well guess what, that's not what most migrations are about. The fact is, people love to complain, so you will hear massively people with that particular example from the movie industry, or this guy who coded this Fortran extension that was in such a tough situation. They are full of dumb operational logic that can be ported 80% by 2to3, and a bit of manual fix. It's a good counter example: it was long, hard, and required very gifted people (thanks Hawkowl !).īut most projects are not like that. ![]() The hardest code base I saw ported was the Twisted project. People want to hear about better perf or fancy features, not better error messages or banned logical errors. It's just not stuff what had be sold to the public. Python 3 is a vastly superior language when it's about introducing less bugs or debugging existing ones. But most projects get away with 2 weeks of investment. Unless you have a very rare irreplaceable dependency or some terrible C extension, porting is easy. People complained a little but they got it done.īy experience, people with large Python projects often overblown the difficulty of porting in their head. It's amazing what you can accomplish when you have no choice. That's got to be one of the advantages of proprietary systems. 2 years later, Rosetta stopped working, so there was no way to run old apps on current hardware at all. If people spent half as much energy upgrading as complaining, this would have gotten done 5 years ago.Īpple took only 3 years to go from first announcing a new CPU architecture to releasing an x86-only OS. Professionals don't get to use this as an excuse to badmouth torx, and stick with phillips. If we switched from phillips to torx, and your favorite tool brand didn't make torx drivers yet, you've got to either convince them to start, or switch brands. That means if the current version of the language no longer supports your favorite library, you need to fix the library, or find a new one. If you choose to use a dependency, you're vouching for it. ![]() (Unless your manager makes drive-by commits of py2-only code, months after you all agreed that all new code should be p圓-compatible, and then leaves town for a multi-week vacation.)ĭependencies? I helped upgrade a couple third-party modules, too. There's a library ("six") to help, and in almost all cases you can write 2-and-3 compatible code, which means you can go piece-by-piece. Python 2 to 3 (at least by 3.3 or so) was one of the easiest transitions I've ever done. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |