Roughly 75% Rye as base malt for the body, then 25% golden naked oats. Mash at 163F (not a typo). Water profile with a lot of Chloride, though I use tap water because my city water is really good. I've tried quite a few yeasts with this setup, but S-04 has given me the best results. 1.023 OG to 1.010 FG. I do a separate BIAB mash + sparge for this because full volume mash would be WAY too watery, it's already pushing it. Though honestly the goal isn't to extract sugars, it's to extract flavours and that sort of gives you a different way to approach your brew day.
Acid League is somewhat decent, not quite as good as a really nice bottle of wine but pretty good. Sadly the cost is a bit prohibitive, especially for what it is.
It looks really nice, but I'd really like a larger one that supports drop-in. Being able to just show up without having to deal with an elderly relative trying to find a button to answer is really a killer feature.
I've used the Echo Show 10 with the drop-in feature for my mom with vision issues (basically can't use touchscreens) and it works fairly well. That said I fully agree with you that something like this would be really excellent. A full-sized person's face and head in 3D is far easier to recognize and understand than a poorly lit 2D 10" display.
I do wonder how much of that is just getting a nice new laptop? If the average user was handed the equivalent laptop with an Intel CPU but told it was an M1 would they notice? Would they also think it was nice and fast?
This is more common than you might think. Back when I worked on a COBOL compiler at IBM one of our test cases was an "expert system" that turned ~20 lines of business-specific DSL into ~100k lines of COBOL. It was extremely un-fun to deal with.
I can pretty much guarantee that there was no discussion with management like that. From experience, live ops games are essentially a perpetually broken code base that was rushed into production, then a breakneck release schedule for new features and monetization. I've personally had this conversation a few times:
Programmer: Loading times are really slow, I want to look into it next sprint.
Management: Feature X is higher priority, put it in the backlog and we'll get to it.
Having just read that book, it's not that laziness is bad or good for data structure performance. It's mostly that you can't use a data structure designed for one paradigm with the other and expect the same performance characteristics. Laziness can make things faster (I think the CatenableQueue was a good example of this), but it can also make things slower (take your pick of examples).
In all I guess I'm not disagreeing with you at all, I just wanted to provide a bit more context and get some more use out of that book.
If you want to get really deep into this, you can read the book Linkers and Loaders by John Levine. It's useful if you're writing either a compiler or an OS, or if you really want to understand the subtleties of how executables are loaded and executed. It may not help you solve your immediate linking or loading problem, but it'll at least help you understand how you got there and what they computer is trying to do.
I found it interesting that the attacker looked for help on the attackee's own site. I guess it truly proves how good of a repository of information StackOverflow is.
> > This terrified the Swift compiler engineers, they were worried that untested complier pass orders would expose untested bugs
> This would scare me too.
For what it's worth a few (10ish) years ago we did this with the J9 compiler at IBM (technically just the backed that was shared between Java, C++, etc). Same idea with simulated annealing. It did end up finding some really strange bugs, but they were bugs that were present regardless, we just hadn't found the right test case for it. We did end up getting some performance out of it, but not nearly as much as you'd expect. It mostly boiled down to running a few extra constant folding passes.
Just to add another data point, I had a 2005 Mazda 6 V6 Wagon and I tracked the fuel usage for an entire year. Ended up a 10.2L/100km. Something I found was horrendous compared to my friends' Corollas and Civics.
There's also some AOT options for the JVM to get a faster startup, along with -Xquickstart. I definitely agree with the "you're loading an entire IDE" statement.
That looks more like coupling the state with the UI. You could try refactoring your code in an MVC/MVVM style like react such that the state isn't being modified during a UI draw. That sort of out-of-sync issue can happen even with retained mode UIs. I wouldn't say it's fundamental to the paradigm that you intersperse your business logic into your UI. Granted at large scales basically any UI framework falls apart.
I'm really not sure about the English/French intersection. There's quite a few names that I've definitely never heard in French and would be super awkward to pronounce. Names like Gaylord, Montgomery, Barbara. It seems like the source for French names wasn't really that reputable.
D has a nogc flag that can be used on methods and taints methods down the line. It's pretty neat. I'm a big fan of D, but I still think I wouldn't write a Kernel in D. I find it much more suited to quicker smaller programs, kind of like Python but with better typing. The script support for D is also really neat, and I've used that instead of Perl a few times.