I don’t have experience with Jujutsu, but I always have the same problem with these alternative frontends, which is that I’d still want to be proficient with the original. If you need to look up how to fix something or you want to help others in your team or you want to script something, then the language to speak is simply the Git CLI.

And I don’t feel like I even use the Git CLI enough where a different tool could be so much better that it’s worth learning both.
Obviously, your priorities may differ, but yeah, that’s just always the reason for me why I prefer the Git CLI, even if it were objectively more difficult to use.

It’s mainly horrid, because it means you have to code extremely defensively (or I guess, use a different API).
You can’t rely on new Date("not a date") aborting execution of your function by throwing an error. Instead, you have to know that it can produce an Invalid Date object and check for that. Otherwise a random NaN shows up during execution, which is gonna be extremely fun to try to find the source of.

I understand that it’s implemented like that partially for historical reasons, partially because it’s often better to display “NaN” rather than nothing, but it’s still the sort of behavior that puts me in a cold sweat, because I should be memorizing all kinds of Best Practices™ before trying to code JavaScript.

(saying something more realistic like “2015” or whatever your inexperience or AI told you to)

User input is probably the big one where this API is gonna get stress-tested…

Hmm, I can believe that it was based on java.util.Date, but I don’t remember that being as unpredictable. I guess, a different API to begin with, would have avoided a lot of problems, though…

I’ll let the hivemind know that we’re supposed to have only one opinion.

The devs have access to the source code. Why would they put something like this two layers deep into the documentation? It’s like those people that think Mozilla is evil, because Mozilla openly talks about what they’re doing. If they wanted to be evil, you would know jackshit about it.

I mean, for what it’s worth, I’m a seasoned dev and just did a run where I tried to answer everything as it makes sense to me (which is “throws an error” or “invalid date” for all of them) and I also got a score of 4/28.

…and two of those points were given to me, because the quiz interpreted my answer differently than I meant it.

In other words, this quiz exists to highlight that JavaScript’s Date functions make no sense.

Should be noted that Ctrl+[Shift+]Tab behaves as you describe by default, but there’s a checkbox in the settings to make it go through tabs left-to-right, so it’s possible OP changed that behaviour…

Not if you never get your application into production…

I wish this was as much of a joke as I’m pretending. It’s so common for software projects to get cancelled that lots of tooling differences are just in terms of how long they let you not deal with long-term problems and how violently they do then explode into your face.

For most of the development lifecycle of a GCed project, you’re gonna ignore memory usage. And if you’re lucky, it can be ‘solved’ by just plonking down a thiccer piece of hardware…

Yeah, it’s easy to underestimate how big of a leap it is from a toy application to real-world usability. Not just in terms of security, but also:

• useful error messages
• logging / monitoring
• configuration
• building a distribution
• deploying in a reproducible way
• documentation
• integration with existing infrastructure
• data migration strategies
• etc.

This adds a lot of complexity, so you’ll need to learn additional complexity to be able to deal with it at all:

• modularization
• version control systems
• software specifications (via unit/integration tests)
• team communication
• helper tooling, like package managers, linters etc.

Learning about all this stuff takes years, especially if no one in your surroundings has much experience with any of it either. Professors don’t have the time to gain or retain this experience, since they already have a different full-time job.

My advice would be to get students to do internships or to take a job as a working student in a company/organization. Sometimes, these can be shitty for the students, but they can often provide significantly more real-world context than college ever could.

It’s a Google Docs link…

I mean, he did fuck up a good chunk of everything…

Ah, interesting. I went from garbage-collected languages where thinking about ownership might be useful for keeping complexity low and occasionally comes up when you manage lists of objects, but ultimately isn’t needed, to Rust where well-defined ownership is enforced by the language.

So, I wasn’t aware that ownership is even as concrete of a thing in other languages…

I agree that the default isn’t great, but from the link that @tal@lemmy.today had posted, there is actually a way to move the inventory button to where you want:
https://samsinventory.docs.luanti.org/files/videos/touchscreen-editor.mp4

So, they go into the menu, then press the “Exit” button.
Unfortunately, that video is already out of date again, as there’s now a general “Settings” button where the “Touchscreen Layout” button was. But in those settings, you can select the “Touchscreen” category and then that button is near the top.
Then it works like in the video again, by pressing “Add button” and so on.

Oh wow, so it’s kind of suffering from success, in that you might have understood it better, if it didn’t have a translation for your native language… 😅

Hmm, is there a way to improve that, like a different word that’s normally used? I could probably contribute a fix for the translation to the project…

There should be a menu-button with which you can open the inventory:

KDE Discover and GNOME Software can install from FlatHub (or other Flatpak repos, if you add those).

Yeah, so much of it is a mediocre/old joke overlayed on a generated image.

I’m guessing, there’s people out there, who genuinely just flood social media with these mediocre posts to try to grow accounts or similar…

Hmm, not sure, if I’ve heard of it. I’m guessing, we’re not talking about simply drawing a UML class diagram…? Is it for figuring out which object will have to clean up which other objects, in non-GCed languages?