XML has a bad rap because people went a bit (ok a lot) overboard with it in the early years, pretty much like what happens with a lot of other technologies, but as far as structured and human-readable data formats with good schema and tooling support go, it’s pretty much unbeatable. Now that JSON is the New Good Tech and XML is the Old Bad Tech, too many developers use JSON where XML would absolutely make more sense, and then we end up with unholy abominations like Portable Text, which is JSON pretending to be XML, and is so incredibly verbose and monumentally stupid that it feels like some sort of joke esolang data format rather than something being used in a production system. But no, here we are, god is dead and JSON is XML.
XML is terrific for building eg. structured markup languages with more complex markup than what something like Markdown can provide, and have the resulting files be comparatively readable, at least in comparison to the JSON-based alternatives – compare HTML to Portable Text, for example. XML has such a bad reputation – partially deservedly – that people just automatically assume it’s not a valid tool for anything modern, even when the modern “NoSQL”, “structured and typed data is for nerds, suck it” JSON solution is a giant pile of shit compared to the XML alternative
I mean, I’ve never used JSONs before but I imagine you could still write to them in realtime at least, as inefficient as that sounds lol. So you could probably get the same results on an actual text editor if you could modify it to update the text automatically when it detects a change instead of prompting the user
Git is one of those things that take a bunch of learning to understand but is makes perfect sense once you do. I read like half of the pro git book and after that I was like it’s so simple! If course it still requires you to read half a book…
For some reason I’ve always been able to visualize version control systems and workflows pretty well and understand how they work. I used to host a CVS server when I was in college back in 2001 so my teammates and I we could collaborate on our lab projects. Then moved on to Subversion, which I used for a very long time. Then I worked at a small company who used Canonical’s Bazaar and finally joined a big corp who used Git.
Throughout the years I simply developed some good practices that I applied to Git and that seemed to be enough. But, I’d occasionally get into this detached head state that I didn’t really understand. And this happened often with my teammates at that job. They’d end up with bizarre scenarios. So I started reading the book and experimenting and was soon pretty solid in Git and ended up being the SME on that topic for our team. Everyone would come to me when they got stuck.
I’m still learning new shit about Git even 8 years later lol. But, the step from being a newbie to a normal user is really big.
Cloning a repo to build the source code isn’t even remotely hard.
When you manage the repo of an entire team who work together on different release versions of a product using a very specific workflow with squash commits and cherry-picking? And when team members fuck up the repo’s history with a bad git pull/push? Yeah, it gets more complicated.
Even with merge policies, if someone doesn’t understand what they’re doing or how it works, it won’t help.
Last project I worked on, we asked our developers to rebase on the parent branch and squash on their pull requests. But, they often encountered conflicts because they never updated their branch. They would pull the parent branch into their feature breach, or do a regular merge, or merge different other branches together and you’d end up with commit duplication everywhere. They didn’t have any discipline.
They are all named some variant of “tutorial_Ch01” or “testprogram” probably. And one repository named “My Unnamed MMO” (or some other overly complex but trendy genre) that has like 12 lines of code so far and a crappy drawn pixelart png.
A real answer to your question though, as long as you can get it to reconnect, even if you have to close the window first, it should still have your changes to the file ready to save. These will be cached (somewhere?) unless you close the file.
There’s something really depressing about an AI telling a suicidal person they’re not alone and referring them to the vague notion of “national resources” or “a helpline”
Funny that predictive text seems to be more advanced in this instance but I suppose this is one of those scenarios that you want to make sure you get right.
I’d just wish to not be in Hell talking to Satan… I mean, literally anywhere else talking to literally anyone else is by definititon a better situation to be in.
To all contradictory replies, I said NOT be in Hell.
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.