Random tip: Kala Namak is a condiment which tastes a lot like egg yolk. If you sprinkle it onto some cooked white beans, that’s kind of like scrambled eggs (well, it is different, but also good and might satiate a craving).
Basically, Kala Namak is salt+sulphur. Egg yolk also contains sulphur, and well, sulphur is one of the minerals we should be eating anyways.
So, you have to start it while your cursor is over the wallpaper, but then you can click on windows to kill them, right?
The engine makes it so HTML, CSS, JavaScript etc. are downloaded and turned into pixels you can look at. The browser embeds an engine for that purpose, but then also has a URL bar, tabs, bookmarks, a history feature and so on.
The Edge engine before Blink was called “EdgeHTML”.
Yep, works in KDE.
Oh, that is actually the part I do agree with. I don’t think everyone will, but I do actually think JSON is easier to read and write (correctly) than YAML. I specifically wrote that JSON cares the least about that, because it was designed to just serialize JavaScript objects into strings and back. As far as its original purpose is concerned, no one would ever need to hand-edit JSON. Which is also why it doesn’t support comments (which is still somewhat of a dealbreaker for a configuration language, although I guess for your proposed workaround, one could potentially use a JSON flavor which supports comments; potentially, you can even write your JSON in the YAML file with comments directly and then not convert it, since YAML is a superset of JSON).
As for documentation, yeah, it is possible to convert, but it makes it more annoying, particularly also if you then can’t easily re-use configs in another project. And if you’re working in a team, having to explain to all your team members, how they can convert the official documentation, is also not really acceptable…
I love this comment. JSON is by far the format that cares the least about being human-readable or -writable, but you’re seriously proposing writing it rather than YAML. And I kind of don’t even really disagree. But a big problem with that strategy is that you won’t find documentation for how to write the configuration in JSON.
What comes sort of close, is that you can define so-called “schemas”, at least for JSON, TOML, YAML and XML. Here’s what that might look like for JSON: https://json-schema.org/learn/getting-started-step-by-step
I don’t know, if you can actually generate a GUI from such a schema, though. They’re intended for validating existing data, so I don’t know, if they give you enough data to work with to actually provide a GUI. For example, you don’t really have a human-readable name in these. The fields are rather called e.g. “productName”.
Yeah, some distros have GUIs for system settings, like openSUSE and Mageia, but advanced users will often even take that as a reason to not use those distros, because they themselves don’t need that on their system. And because not many advanced users use these distros, it’s hard to recommend them for noobs, because it makes it more difficult to find help resources. Kind of a stupid situation…
That’s not a typo: https://k3s.io/
It’s basically a Kubernetes cluster, which you can run locally on your PC. Really useful for playing around with Kubernetes before you move to a ‘proper’ environment.
Even just the choice of programming language makes a big difference. Running a JVM language or NodeJS, Python, Ruby etc., you can be bottlenecked by a Pi. Meanwhile, Rust or C/C++ will use barely a fraction of those resources.
I do like the picture, too.
Option 1:
echo 1
Option 2:echo 2
Option 3:echo 3
I have a feeling how it came up with that 3… 🙃
Oh yeah, we did find out right then and there how to set it like in GNOME. But well, you know how it is, if there’s potentially dozens of these tiny differences, then finding the correct customization does become tedious and there is a chance of some things just not being configurable in quite the same way.
Is that the default on GNOME? I happen to have the same workflow configured on KDE, except I use WASD instead of arrow keys. 🙃
Yeah, I specifically wrote “the key above tab”, because on our German keyboard the ^ is there, but it’s still the same keybinding, so presumably GNOME determines it based on key location rather than the produced symbol.
I have a colleague, who’s super deep down the Linux rabbit hole and he always ran GNOME. I was never quite sure, if he actually prefers it, or if he just does not care, because he’s doing most things in a terminal anyways.
Recently, our IT department made a change, which accidentally switched him over to KDE. He could easily switch back, but he’s been checking KDE out instead, and yeah, it’s been super interesting.
He definitely has some of that GNOME workflow baked into him. For example, under GNOME you can use Alt + the key above Tab to switch between windows of the same application. In KDE, that shortcut exists, but the default keybinding isn’t exactly usable.
Another minor complaint was, for example, that using Meta + arrow-keys doesn’t move windows between screens automatically when you press it repeatedly. That’s a separate shortcut under KDE, with Meta + Shift + arrow-keys.
EDIT: Apparently, I misunderstood him, his complaint was that Meta + Shift + arrow-keys moves the window between screens in a weird way. It just picks some kind of order for the screens and then goes between them as previous/next, even though you press the left/right arrow keys. There even is the more appropriate shortcut key for left/right, but it’s just not the default binding.
Meta + arrow-keys does work for moving windows between screens.
He’s aware that he may need to relearn some of his workflow, but yeah, will have to see, if he sticks to it. His emotions are nigh impossible to read, unfortunately. 🙃
While writing the comment above, I was thinking that there are some uncivilized languages that allow you to call functions in the same class without an explicit self.dont() or this.dont(), so technically you can magically transfer data like that.
But having a variable goingToCrashIntoEachOther in a class would be a bit weird.
In my head, the drones were going so fast that just slamming into the brakes wasn’t enough and you’d rather have to dodge. Not sure, if that’s only in my head or if I actually saw the video of these drones a long time ago.
But yeah, if they are going really slow, then that could work.
Maybe you’d even have them back up a bit and then turn at a random angle before trying to continue flying, so you don’t end up in the deadlock you described. 🙃
I don’t know about most painful, but my dad bought a phone many months ago and last week, he wanted to know how to turn on the flashlight on it. I was ready to edit the notification dropdown or give a five step explainer or whatever.
Turns out, nope, you just pull down the notification bar and there’s a pretty obvious flashlight button right there. The problem is, you see, he did not know you could drag down the notification bar. There were dozens of notifications there.
I really cannot blame him either. I don’t know what UX designer came up with just putting a bar at the top and expecting users to know that you can drag on it. But yeah, still, ouch.