The thing I'm curious about is how much would it impact sports podcasting/etc if they clamped down on the gambling advertising. And to be clear I'm not saying that is a reason not to clamp down, just anytime I watch any podcast about sports there is all but guaranteed to be at least one ad for a major sports betting site. Plus how much of the new TV deals for various major league sports in the US was driven by the expected sports gambling ad revenue during the games.
I used to use clojure, but one of the reasons I stopped was I personally found tools like Maven cumbersome to work with. I admit that was 8 years ago or so, so there's a chance it got better, but once people are driven away by tooling issues it takes a lot to convince them to give an ecosystem another chance.
An example of this ossification of understanding is how people still think dotnet is Windows only because they stopped caring before Core/Modern dotnet became a thing
How many people are waiting for it to hit 1.0? I am.
I am interested in Zig, but until they can guarantee a stable point for an extended period of time I have limited interest. Same way with Rust gamedev I'm keeping an eye on Bevy but want it to hit 1.0. Some things pre-1.0 is fine, but more core pieces of dev like the language often warrant requiring greater stability guarantees.
Hollow Knight is a great game, even with the fact from a story PoV you can probably skip it, I simply do not recommend it. To most (myself among them, and metroidvanias are one of my favorite genres), HK is one of the games at the pinnacle of the genre.
In some situations and particularly for helping new hires get on board mob programming can have value, but as an introvert being in a call/huddled together constantly is exhausting and not for me.
Thank you. I really do not understand why anyone trusts Unity to keep this for only non-entertainment if it proves successful. They only backed off before because the backlash was so bad. Assuming that means they won't try to find ways to slowly bring it back in the future is dangerous to me.
MAUI not supporting Linux feels like such a huge whiff. It is clearly possible to get at least decent cross platform support that includes linux in .net considering Avalonia exists.
MAUI is supposed to use native ui components, AvaloniaUI just uses Skia.
I think going with a non-native approach would kinda make Linux a clear second class platform, especially with all the native features that need to be rebuilt?
Is there any multiplatform ui framework that's actually "native" for all the different linux ui toolkits?
I don't know that many production compilers are in them, but how much of that is compilers tending towards self hosting once they get far enough along these days? My understanding is early Rust compilers were written in Ocaml, but they transitioned to Rust to self-host.
It is interesting that there's so much discourse about the effort people have had to put into data structure and algorithm stuff for interviews, but then people refuse to take advantage of the knowledge studying that gives you towards trivial effort optimizations (aka your code can look pretty similar, just using a different data structure under the hood for example).
That's because people don't get it. You see people saying things like "It's pointless to memorize these algorithms I'll never use" - you're not supposed to memorize the specific algorithms. You're supposed to study them and learn from them, understand what makes them faster than the others and then be able to apply that understanding to your own custom algorithms that you're writing every day.
postmortem is looking back after an event. That can be a security event/outage, it can also be the completion of a project (see: game studios often do postmortems once their game is out to look back on what went wrong and right between preproduction, production, and post launch).
It's weird that we use "postmortem" in those cases since the word literally means "after death"; kind of implying something bad happened. I get that most of these postmortems are done after major development ceases, so it kind of is "dead" but still.
Surely a "retrospective" would be a better word for a look back. It even means "look back.
