I was about to reply with a “oh, really? Whoops, I maybe should I have looked a little deeper” and edited for the post title, but I’m not so sure, looking into the first link you posted.
RE: phabricator…I don’t know what that service is or is for, so I can’t comment if there’s any proof therein.
But the “how to submit a patch” page linked has a section that seems to at least suggest that their Github repo is now first-class, per the first line of the section.
So, there are a lot of words in the post that I’m not familiar with (LoRA, Oobabooga, CivitAI). However, I think those are details about the actual library or package you’re looking at, so I will not touch any of that.
I can strict answer the question “what is Yarn?”
Long story short, it’s a direct “competitor” to NPM (Node Package Manager). In the earlier days of Node and NPM, Yarn was an attempt to improve certain weaknesses perceived in NPM (including speed and security). Yarn is still used in many codebases, but it’s become less popular over the years as NPM has resolved many of the things that Yarn sought to fix. Also, Yarn version 2 made a major design change which some have viewed as too radical (though I’m unclear on the details as I’ve only dabbled in v2).
You’re right, that’s a distinction I failed to make
I get it…I’ve never been the maintainer of a codebase that’s deployed on trillions of devices, and backwards compatibility is something to be taken seriously and responsibly when you’re that prolific. I do not begrudge SQLite or any large projects when they make decisions in service to that.
However
It always makes me feel oddly icky when known bugs (particularly of the footgun variety) become the new standard that the project intentionally upholds.
So, I will start by saying “Yes, you can do it. It’s not too late and programming is fun and fulfilling”.
However! One thing my experience has taught me in seeing people approach and bounce off programming is: programming is a fail-til-you-get-it type of endeavour. Your first several years will be littered with broken code, because there are a thousand little things you have to bump up against before you unlock one more puzzle piece.
So! If you go for it, persevere! You aren’t a bad programmer, or a slow learner, because you can’t get your code to work. Every single one of us ran into the same issue, and we just had to push through, learn to Google, and try again until it sorta-kinda works. You in 10 years will be embarrassed by what you write in your first years
I started Game Grumps over a decade ago, and still enjoy most videos to one degree or another. Most games they don’t finish, but they always have at least one game that they are working through
I have been playing Evoland Legendary Edition. The 2 games bundled are surprisingly dissimilar, with the first being almost a parody game of extremely short length, and the second being a fairly fleshed-out, 20 hour RPG-lite, with a story of real stakes (highly inspired by Chrono Trigger).
Very worth it if picked up on sale, just be prepared for the tone-whiplash between games.
It…seems like there may be some issues with the repo…
That’s a fair point. I’ve always assumed it was a form of rate-limiting, but you’re right, that’ll be part of their analytics at least
Oh, whoops! I didn’t notice its timestamp when I read it 😅
I don’t hate YAML, but it has the same issues languages like PHP and JS introduce…there are unexpected corner cases that only exist because the designer wanted the language to be “friendly”
For what it’s worth, I have been a convert from naive to aware for a couple years now. I used to like to think naive == UTC, but when data comes from unverifiable sources, you can’t know that for certain…
Yes, testing infrastructure is being put in place and some low-hanging fruit bugs have already been squashed. This bodes well, but it’s still early days, and I imagine not a lot of GIL-less production deployments are out there yet - where the real showstoppers will potentially live.
I’m tenatively optimistic, but threading bugs are sometimes hard to catch
I’m curious to see how this whole thing shakes out. Like, will removing the GIL be an uphill battle that everyone regrets even suggesting?Will it be so easy, we wonder why we didn’t do it years ago? Or, most likely, somewhere in the middle?
That’s hot
I probably have about 3-4 hours remaining on Tales of Xillia on the PS3. I’ve really enjoyed this one (this is my 4th or 5th Tales game, AFAIR). Hoping to finish before the week (weekend?) is up.
Putting aside the “should/shouldn’t do” argument, I was also wondering if the code is even viable. I imagine that ‘ls’ and ‘sudo’ are probably pretty ubiquitous, but I bet there exist some Linux installs out there with a different shell than ‘bash’, and some might not have ‘grep’ too. That would lead to some pretty cryptic bugs for the end user, eh?
What a strange article. The reasoning for why 22 is interesting though very straightforward, and the rest of the article is essentially “I asked for port 22, and they gave it to me”. Little fanfare, little in way of storytelling conflict.
Not an issue in and of itself, but strange with a title of the form “This is the story of…” That sort of titling usually begets intrigue and triumph over adversity, dunnit?
Well, this has piqued my interest. I’m glad it’s more substantial than a straight remake/remaster
If you aren’t married to Hugo as your solution, I will recommend giving Eleventy.js a look.
It’s a static-site generator, but a good amount of flexibility is afforded by virtue of using pure JS to generate view data (which means that you can do any conversions needed, manually or with NPM packages if needed for more proprietary data formats), and it supports a bunch of templating engines too.