SC 2 recently went free-to-play. If the rest of their catalog is added to Game Pass, that will be something. Blizzard games have been stubbornly expensive years after release. I wonder what this means for Battle.net?
2,602 karma · joined November 15, 2013
SC 2 recently went free-to-play. If the rest of their catalog is added to Game Pass, that will be something. Blizzard games have been stubbornly expensive years after release. I wonder what this means for Battle.net?
Without necessarily taking a position on the ethics, I would point to macOS and its derivatives as a clear example of this. Apple invested significant resources into a successor to System 7 called Copland, abandoning it in 1996. While the purchase of NeXT in 1997 hugely influenced the design of OS X, look at all of the free and open source projects that accelerated its development: Mach, Clang/LLVM (and GCC before it), KHTML, KJS, CUPS, much of the BSD and GNU userland, and the list goes on.
macOS, and by extension iOS, would not be where it is today without its open source core. Put a little spit and polish on it (no small thing, of course), add a kernel extension named Don't Steal Mac OS X.kext, and voila: new O/S.
I saw conflicting reports about whether Google Fi was affected by T-Mobile's reported text message censorship. I don't know where it stands on this iCloud Private Relay issue.
I have this fantasy about a browser history on steroids that remembers not just the URLs, but the contents of everything I've ever visited. Not necessarily 100% retention of images and layouts, but at least searchable text. There are so many times when I'm simply unable to convince Google to find a page I read a few years ago. I've probably even bookmarked a project or two along those lines.
If you look at the fastest approach the author tried in the second "UUID insertion rate" graph, it actually stores a modified UUID in a 36-character string. There is a missed optimization to store the modified UUID as 16 bytes, rather than 36, but imposing some order on the keys is the dominant improvement.
I can't say that I've used the app to as good effect.
If you want to be descriptive, name the purpose of the loop variable. If it's an array of foos or an array named foo, then use something like fooIx. Then when you loop over an array of bars, use something like barIx. If you're counting retries, call it retryIx or retryCt (or something that describes what you're retrying, like loginAttemptIx).
Depending on the context, i may be fine. However, a single-character name like that is bound to be reused, which is a bad smell.
One thing that puts a clock on it in the intermediate to long term is camera support, which I gather from the README is a significant maintenance task. The project will bleed users if it doesn't support their new cameras.
Edit: it looks like Nebulosity sold for $95. Some other software in this space I see mentioned on the Cloudy Nights forum are Astro Pixel Processor (€ 165), PixInsight (€ 165), and Siril (free).
Off topic, but I wonder if anyone knows whether it's possible to use rustc with lld, instead of link.exe? I tend not to have Visual C++ on my home systems. Is it as simple as the Cargo equivalent of LD=lld-link.exe?
My impression has been that MusicBrainz has more typos and weirdly formatted metadata than FreeDB. Now that I know more of its background, I'll look into it more. My CD collection is mostly ripped to full-album FLAC + CUE, so correct metadata will likely be an important part of converting to MP3 for streaming.
> We then take that value, and use a salt (a random string per user) and do another 100,000 rounds of hashing, and compare that to what is in our database.
https://blog.lastpass.com/2015/06/lastpass-security-notice/
While it's true that the client-side hashing means that LastPass never sees your plaintext password, the first hash effectively becomes the password. Then it's on LastPass to treat it as such, which they claim to do by hashing it again.
Edit: another link describing the use of PBKDF2:
https://support.logmeininc.com/lastpass/help/about-password-...
> Werner Koch wrote the software, known as Gnu Privacy Guard, in 1997, and since then has been almost single-handedly keeping it alive with patches and updates from his home in Erkrath, Germany. Now 53, he is running out of money and patience with being underfunded.
https://www.propublica.org/article/the-worlds-email-encrypti...
https://news.ycombinator.com/item?id=9003791
Recall that this was in the wake of Heartbleed, a vulnerability that exposed our dependence on OpenSSL, another critical, and chronically underfunded project.
The project got a nice boost after that article, leading to this Ars Technica story about the windfall:
> Given the ramshackle state of massive GnuPG code base, it's not clear what's the best path forward.
http://arstechnica.com/security/2015/02/once-starving-gnupg-...
https://news.ycombinator.com/item?id=9011138
Nonetheless, a fundraising campaign followed just two years later. It turns out that $150K isn't actually that much of a windfall.
After a week of this nonsense, it occurred to me that maybe I could start over with a physical SIM card. I chatted with frontline support again, and he said he was positive that would work. (So why didn't anyone suggest that?!) I couldn't use the old card, because it was clearly beyond their capabilities to reactivate a perfectly good SIM card, but I was able to buy a new one at Best Buy and complete the process in about five minutes.
I would have swapped the card in the first place and been blissfully ignorant of the eSIM fiasco, but I somehow had it in my head that the iPhone used a smaller card than the five-year old phone it was replacing. It may not be eSIM's fault, per se, but if the design is dependent on carrier competence, it's fatally flawed, as far as I'm concerned.
On the Kinesis Freestyle Edge, I actually like the per-key RGB lighting as well. Most of the alphanumeric and punctuation keys are red, the home keys are green, and the rest are blue. I also turn off the backlight for keys that I don't use, like PRTSC. It looks gaudy as hell, but I feel like it makes it easier to find certain keys in the Freestyle's slightly unusual layout, and to come back to home position.
The other thing I like to do with RGB lighting is to make different layouts different colors--QWERTY is all blue to distinguish it from my multi-color Dvorak.
Indeed, the post essentially brags about how big it is:
> In Version 1.0 there were a total of 554 functions altogether. Yet between Version 12.0 and Version 13.0 we’ve now added a total of 635 new functions (in addition to the 702 functions that have been updated and upgraded).
With these batteries-included languages, mastery of the language really requires mastery of the library.
This is done by initializing a (unsigned) vrbl "perturb"
Is "vrbl" a term I should know, or just a prvrs abbrvtn for variable?Edit: although David Wilcox is fun live, I suggest you look for the studio version with the flugelhorn part; e.g., https://www.youtube.com/watch?v=kEBncfBVmxQ.
This is the first thing I look for in these announcements. .NET 6 is the successor to .NET Core 3.1.
I agree with the sentiment of defining a graph in code, but I really wanted to give it a nudge from time to time, like swap these two nodes so the arrows don't cross. I'm only an occasional user, so maybe there are ways to do it.
https://github.com/ziglang/zig/issues/4786
It was closed in March of 2020.
https://andrewkelley.me/post/zig-cc-powerful-drop-in-replace...
HN discussion:
https://news.ycombinator.com/item?id=27872596
previous discussion:
https://www.infoworld.com/article/3633002/the-future-of-rust...
Steve is probably objecting to the paragraph that starts, "Given that Matsakis and Miller both work at AWS, it's not surprising that the [Rustacean] principles started out as a spin on Amazonian tenets."
There are lots of other libraries, and surely some faster ones, but I haven't felt any need to change. I was nervous when I got an inexplicable overload ambiguity in xlclang++ for AIX, but it went away when I grabbed a newer version of the library.
> There is no UB at compile-time; the compiler is required to issue a diagnostic whenever it encounters one. With sufficient coverage, you can thus verify that your functions don’t contain UB.
> A lot will be from before 2000, before we had things like "Agile" and "unit tests" and "widespread version control", so you can't extrapolate any of their conclusions to what we're doing. As a rule of thumb I try to keep to papers after 2010.
While I admit that even in the late 90s, it seemed strange to me to see citations from the 70s or 80s about projects from the 60s (like, say, OS/360), I'm not convinced that so much has changed in the last ten to twenty years as to render all previous research irrelevant.