Yeah, or their parents argued a lot and they don’t want to end up in a relationship where this is the case. This can also mean they’re quick to exit a relationship as soon as the first conflicts need to be resolved, because it feels like a sour relationship to them.
Oh yeah, I do think setTimeout executes in parallel, so only the largest element determines the execution time. It was difficult enough to make that sentence make sense, so I didn’t want to cram that detail in as well. 🙃
I mean, it does scale with the size of the input. Just not with the count of inputs, but rather the size of each input element.
To me, a big part of it is that I’m tired of commodity art. I don’t care about your pretty pixel soup. I’ve seen other pixel soups before that were similarly pretty.
And I’ve been tired for many years, long before every middle-manager under the sun could cook up their own pretty pixel soup.
Back then, it was humans trying to make a living off of their passion and then settling for commodity art to make ends meet. I was cheering them on, because they were passionate humans.
Now that generative AI has destroyed that branch of humanity, there’s no one to cheer on anymore.
Even if generative AI never existed in the first place, I’d like to see commodity art being relegated to the sidelines and expressive art coming into the limelight instead.
Tell me a story with your art. About your struggles or a brainfart you had, or really anything. This comic is great, for example. There’s emotions there and I can see the human through the art. I would’ve chosen a very different illustration for whatever, for example, which tells me a lot about the artist, but also about myself.
I have never had that kind of introspection with pretty pixel soups.
I agree in general, that a crash is much better than silently failing, but well, to give you some of the nuance I’ve already mostly figured out:
Currently implementing error handling for a library I’m building and the process is basically to just throw all of the information I can find into there. It makes the error handling code quite verbose, but there’s no easy way for me to know whether the underlying errors expose that information already, so this is actually easier to deal with. 🫠
However there are things when the Ai is helpful, especially for writing tests in a restrictive language such as Rust.
For generating the boilerplate surrounding it, sure.
But the contents of the tests are your specification. They’re the one part of the code, where you should be thinking what needs to happen and they should be readable.
A colleague at work generated unit tests and it’s the stupidest code I’ve seen in a long while, with all imports repeated in each test case, as well as tons of random assertions also repeated in each test case, like some shotgun-approach to regression testing.
It makes it impossible to know which parts of the asserted behaviour are actually intended and which parts just got caught in the crossfire.
Yes, catastrophic software bugs…
Personally, I don’t think that more research will particularly change our outlook on that. Anything “geo-” is incredibly political.
Even if we find a solution that genuinely just reverses the effects of climate change, there’s gonna be some regions that see short-term disadvantages from that. Or even regions that merely imagine some catastrophic weather events were caused by making the planet cooler, even if they would’ve been hit by worse on a warmer planet.
Those regions may go against all reason to stop the geoengineering from happening.
It also has to be said that the CO2 in the atmosphere isn’t just pumping up the temperature, it’s also causing ocean acidification. Corals get dissolved by the sea water getting less alkaline. And corals are the basis for a whole lot of life on Earth.
Which is again one of those points, where I just don’t see research finding much better of a solution than algae and trees. You can hardly beat or improve the efficiency of just letting nature happen.
I guess, we could start pouring lye into the ocean instead, but we’d need quite a lot of it. So, I’m also not particularly convinced that it’s more cost-effective than letting nature happen, even leaving aside the problems we could cause with lye build-ups.
I’m no subject matter expert, but I imagine, if there was scientific consensus as to what’s a sensible geoengineering change to make, then we would be on that immediately. Oil companies could invest a fortune into that and it would still be beneficial for them.
A teacher showed us the documentary An Inconvenient Truth and the real truth I learned from that, is that the majority of adults are irresponsible crybabies.
Somehow I like the look of both this:
And this:
The bottom one certainly has its own vibe. That with dark theme and monochrome icon set would look cool.
That is a good tip. Unfortunately, I am too fish to understand it. 🙃
I just type ps and in 9 out of 10 cases, my shell suggests ps -ef | grep <process-name>. So, it’s actually less for me to type than “pgrep”…
Ah, that was a brainfart. I do use pkill primarily. I just use the other command, when I’m not sure what the process is called…
Well, as was already said, tooltips don’t work on mobile, at least not unless you write custom code.
And I’ve seen concepts for various marquee solutions, which attempted to fix the problem of the text start not always being readable, by e.g. only making the marquee scroll once after you click on it.
If you enjoy these marquee solutions, then more power to you, but the need for custom code is what keeps me away again.
Just making it horizontally scrollable is a beautifully simple solution in comparison.
Yeah, I especially don’t understand it here, because it’s a graphical tool. You don’t have to keep backwards compatibility.
Even if you’re worried about people depending on the format that’s being piped, you could keep only the piped format stable. We have the technology.
Yeah, I would often just grab htop because I had no idea how to read the CPU usage out of top.
For example, for me it says:
%Cpu(s): 0,4 us, 0,4 sy, 0,0 ni, 98,8 id, 0,0 wa, 0,3 hi, 0,0 si, 0,0 st
Now that I look at it, I can guess that us and sy are supposed to be user and system time. And I guess id is supposed to be idle.
I have no guess what the other numbers might be, though. And well, I would often like to see the CPU usage per core.
Now I know that I can just press 1t and get effectively the same view as in htop.
I might learn top’s filtering workflow, too. But so far, I always killed processes with ps -ef | grep <process-name> and then kill <pid>, which isn’t particularly more cumbersome, so will see…
It’s probably supposed to make it more hip and personal. And the frequent complaints about misunderstandings are free marketing.
On a related note, one of my coding side-projects is a web music player. And I had the problem that fitting the song, album and artist names into a layout is tricky, because they can be very long.
And yeah, then I realized that <marquee/> is actually a valid solution for that. Lots of music players do use a marquee-style display, when the length exceeds the available space.
Alas, it still isn’t actually a good solution. Marquees make sense as signs, but not for an interactive UI. It’s pretty much always a better UX, when you just make it horizontally scrollable, so that the user can read the start and scroll, if they want to read the rest.
Yeah, I also recommend this. Particularly with laptops, it’s good to have a full-fledged desktop environment, since you’re more likely to need WiFi, power management, easy display configuration etc…