Nice, but doesn't accept Waking Violet as a valid Nintendo Switch game
344 karma · joined July 8, 2020
2) Do not use Vec<T> to pass arrays to C. Use boxed slices. Do not even try to allocate a Vec and free a Box... how can it even work?!
3) free(ptr) can be called even in ptr is NULL
4) ... I frankly stopped reading. I will never know if Rust actually needs Go's defer or not.
Of course these are my guesses, I don't think the "purpose" of boxedwine is ever explicitly stated.
I only play single player stuff and have a backlog that just keeps increasing, I can't keep with the pace. They aren't the most publicized AAA titles though (BG3 probably bring an exception given its popularity, and the Zeldas thanks to Nintendo).
It's just like music, where there's plenty of good one being made, but can't be found anywhere close to the top 10 hits or on radio (at least, for the kind of music I like).
So yeah... One can dream, but the dream is, for once, alive (mostly thanks to GoG, Steam and Humble).
Not the greatest tools out of the box, but still better than nothing.
Really anything rather than a thing that has only drawbacks.
As far as readability goes... can't see a difference with monospace text, maybe even worse as fonts tend to be thinner and need adjustments. Maybe a little better with proportional text on websites and documents.
One suggestion: where you talk about using AsRef<[T]>, might be worth suggesting IntoIter, where it makes sense? IIRC that's what std uses for functions that aim at being generic over data structures and iterators (I might be remembering wrong, though).
In any case let's not digress from the truth: amazing list.
And yet when I needed to rent a car, I rented a gasoline one.
Why?
Because car rental is pretty much the worst case for an EV.
If I rent a car I'm likely abroad, with zero knowledge of the recharge network and often not great options in terms of costs because most are national (at least, here in Europe, only notable exception being Ionity).
I'm also likely to drive long distances, with no routine, and little planning capacity.
And whatever other reason one would pick an EV for (noise, pollution, fuel cost, one pedal drive comfort etc.) they are all negligible when applied to a 2 weeks vacation.
Reasons: - practically every developer who is remotely interested in assembly programming knows the x86 basics and most experts have a better knowledge of x86 than other architectures with the possible exception of ARM
- x86 is very hard for the hardware implementation, for the programmer (especially with the x86-64 improvements) is not bad at all. Its bigger defects are variable instruction length, something that has no impact on coding, and tge amount of legacy stuff that exists mostly for backward compatibility (e.g. x87, enter/leave, bcd instructions, hw task switching, segments, real mode and v86 mode, etc.) and are just being ignored by programmers as stuff that is now irrelevant if they have not been removed from 64bit long mode at all.
- I don't know modern MIPS, but the MIPS architectures of the past were not programming friendly at all, with stuff like delayed slots (basically instructions that are executed even if the code branched somewhere else), heavy reliance on the compiler to provide perfect instruction order, etc
Vanity is just another explanation, and the hope that the CVE gets "famous" like heartbleed or spectre or meltdown.
Source: I'm the owner of 3 domains (not security related fwiw) but zero businesses.
I think it's a sensible choice: try lowering the policy and everything blows up. Much better than the alternative of silently ignoring the call or, even worse, silently lowering the policy
Plus, identity theft is not an uncommon crime.
> "The remainder are simply stupid. This is approximately the composition of the organization writ large. The number of people at this organization who dislike their job, their stakeholders, and their salary but don't leave even though they no longer have the energy to work is astonishing, and that alone is enough to constitute stupidity as per Cipolla's definition."
Because, apparently, a person cannot be burned out and at the same time still need food, a home, or whatever they needs a salary for, not to mention they might be on temporary visas and cannot risk being unemployed or any of the other billions of totally sensible reasons keeping them from leaving their jobs.
So to answer your "maybe"... nope, no empathy, no wisdom.
Pros: pushes only the differences, keeps history, can be rolled back, works offline (push fails but commit works), offers a time log of changes.
Commit messages are not needed really - the timestamp is enough and rolling back is only for exceptional events (e.g. accidentally deleting important stuff, etc.).
This is usually associated with dark mode because:
1) on older monitors, even CRTs, black was actually dark gray
2) on a 60Hz CRT, white background was a flicker-fest
But, many of today's dark mode UIs choose a background colour that is too dark, and the result is as shitty as light mode.
That wouldn't be that bad if only OSs and WMs kept the ability to customise theme colours (Windows was good on that side, now not anymore, the only exception out of the common ones is KDE) and if applications actually respected OS style instead of delivering their own theme.
But that aside, I feel your pain around min() and max(). In my case, I feel the problem comes from language (I mean, the real life one): I speak Italian and in Italian the words for "at most" are "al massimo" (i.e. "at max") and the words for "at least" are "come minimo" (i.e. "as min") that is, the exact opposite of their mathematical meaning. I've taken an habit of reviewing 3 times any piece of code where I write "min" or "max" for this reason.
1) it has never been removed, afaik Word still uses OOXML, so Word would keep being infringing
2) LibreOffice would probably be infringing too, as ODF is also XML based
So... it has to be some other form of XML tool and not the file format.
As for Joel's comment, IIRC he was an Excel PM before OOXML; in any case his blog post refer to the binary format that precedes OOXML. I'm pretty sure OOXML is equally if not even more complicated, as the product themselves are way more complicated than they appear, but the fact is that he was talking about a different thing.
Edit: as many users pointed out, it's not the file format itself, but the ability to add arbitrary attributes/elements to the file format XML as additional data.
It's super easy to lose control, I can't believe it but what a major difference dropping that daily piece of chocolate, the sugar in the coffee and the soft drinks made.