- Posts
- 5
- Comments
- 1330
- Joined
- 6 yr. ago
- Posts
- 5
- Comments
- 1330
- Joined
- 6 yr. ago
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.
- JumpDeleted
Permanently Deleted
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.
- JumpDeleted
Permanently Deleted
It's probably supposed to make it more hip and personal. And the frequent complaints about misunderstandings are free marketing.
- JumpDeleted
Permanently Deleted
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.
Damn, even when I don't mention it, it's apparently obvious that I'm gushing about Rust. 😅
I had the Rust CLI Book in mind: https://rust-cli.github.io/book/index.htmlEspecially, if you have experience in another language already, the first chapter shows you how to develop and ship a useful Rust application in a short amount of time. And then the second chapter contains all the detail information, which you might need, after you've run off and started building your own thing.
But yes, Rust By Example is also really great. It happens a lot that you search "xyz in Rust" and it's one of the first results, and always worth clicking on.
I see the value in reading documentation front-to-back for picking up all the little tidbits of information (or at least knowing where they're documented), but yeah, ultimately I need to be building something to really process the information.
Kind of my sweetspot is documentation that makes you build along, but doesn't overstay its welcome. As in, don't cram all the details along the way, but rather just dish out important information on rapidfire.I will run off building my own thing in the middle of the tutorial, if that isn't the case, whether I want to or not. As soon as it's quicker to learn by dicking around with the code, I will do that and then I've spoiled future chapters, so likely won't return.
- JumpDeleted
Permanently Deleted
Well, and the other joke is that it's a department that tries to predict crimes before they happen. If they're "successful" and the arrest happens beforehand, then the crime never happens and they're locking up an innocent person.
Not sure about video playback, but I feel like the PeerTube website is much more efficient. The YouTube website is amazingly badly coded...
You generally have to fork to create a PR...
What also surprised me is that the speed difference depending on medium is actually quite substantial. For example, glass has a refractive index of about 1.5.
So, the speed of light in glass is c/1.5 ≈ 200.000 km/s, i.e. 66% of the speed of light in vacuum.
Yeah, the exponent threw me for quite a loop, too. Had me wondering what kind of formula you used to get Euler's Number involved. 🙃
If we leave realism aside for a moment, though, the difference is that:
- a carry slot limit restricts how many distinct kinds of items you can have, whereas
- a carry weight limit moreso forces you to leave behind duplicates of items or to e.g. make a choice between heavy armor vs. having auxiliary items.
It depends on the game what's more fitting for the overall design, but yeah, ultimately you want to prevent the player from optimizing the fun out of the game.Having very heavy armor or dozens of healing potions can be boring, since there's no risk anymore. But having one of each different kind of item can also kill the fun, because having the perfect solution for every situation is just as boring.
Yeah, and you'd often get a separate junk inventory, along with a one-click button to sell everything from there. I guess, at least it was an attempt to solve the problem...