The crispy aliasing of the audio has always felt cozy to me. It’s also a bit of a signature of the system, like the wobbly polygons on PS1. I appreciate that there are ways to change the sound, but it feels a bit rude to label it broken or defective.
I strongly disagree here. I was so hyped for the GBA that I bought it on release day, only to be disappointed later. One of reasons is the lackluster sound; seriously, Nintendo had already built an impressive sound system for the SNES, and then the GBA just had a software-driven DAC? Why did the cheapened out so much?
Same as for the PS1, I always found the wobbly polygons and warping textures painful to watch.
Sony made the SNES sound chip, and the GBA was power-constrained by AA batteries. Those are the two biggest reasons I can think of just off the top of my head.
I think they're showing it in the two videos on the page, though it's a bit subtle.
From what I understand, they were struggling to have good color resolution (distinguishable colors) at lower brightnesses. The first video demonstrates that well, especially if you look at red, which seems to be almost the same pale red color throughout the 10 or so LEDs that color occupies.
The second video, I assume, is after the temporal dithering is applied. If you focus on red again, you can see a much more smooth transition from red, to magenta, to blue.
Boyscouting works because you don’t need to get permission to fix tech debt when it is bundled with something else. 98% of those tickets you file to fix warts will never be addressed because the business demands that time is spent on features that make money.
Wholeheartedly agree. This issue comes up in job interviews and forces people into faking confidence in spite of not knowing. Honest people be damned if they give the impression of anything less than absolute confidence.
Just an anecdote, but the Arc A380 on my kids’ Fedora gaming PC has run everything on our Steam library just fine. A mix of older and more recent titles. I’m sure there are games that don’t work well, but it was cheap and it’s been rock solid.
I might be a minority here, but I don't really consider the Android OS a feature I want. As a Remarkable 2 owner, I've come to really appreciate the long battery life and purpose built OS. There are no "app" distractions, and it has become an essential part of my daily work flow for note taking and e-book reading.
I wish Daylight success, but at their price, its not a compelling offer for me.
Yeah I was surprised to see it ran Android after watching the trailer showing a lady doom-scrolling on her iPhone before accepting the warming comfort of using the Daylight. Another trailer showed happy contemporary hippies in the forest, or their modern workspace with more plants than walking space.
I figured it was a breath of fresh air from modern devices because it was simpler in its capabilities. But if it's running Android it seems like you'd just be doomscrolling in black and white.
Seems like something that could be solved pretty easily by having self-control and not installing those apps on the device.
Besides, I would have no interest in doom-scrolling black and white anyway. My app timers on my phone, when they switch to greyscale, I immediately lose interest on whatever it was.
I had to do a double take regarding the single click "issue" because later in the article it is mentioned that scroll bar behavior was changed to accommodate users with RSI.
So what is it KDE? Do you care about RSI or not? I'm no longer a young person anymore, and appreciate any features to prevent RSI. I think its silly to relent on the single click due to "new user pressure".
At least there is still an option for it, I suppose.
The biggest handicap of cut for me has always been that it cannot split on blanks (TABs or SPACEs), you have to choose between TAB or SPACE. So I wrote an awk script that can print field ranges like cut, but recognizes blanks. Now I will see if I can get tuc worked into my muscle memory.
I’m not defending cut here, but using sed is also pretty straightforward and fits its purpose. I’d argue that using the existing general-purpose tools is better than creating custom narrow-purpose tools in simple cases like this one. Besides maintainability and familiarity, it also exercises your proficiency in applying the standard tools.
I believe "negative index" means array[-1] is the last element in array, array[-2] is the second-to-last element, etc.
In the context of "cut", it would mean being able to do something like:
cut -d" " -f1--2
the "-f1--2" (read: fields from 1 to minus 2; it's a range) means to select from the first field to the second-to-last field. (that double "--" is pretty awkward, to be sure!)
Some programming languages (ruby is the one that I know) have this feature for accessing array elements.