dejected_warp_core @ dejected_warp_core @lemmy.world

Posts

2

Comments

1,138

Joined

2 yr. ago

Real question is: how many smaller cars can I fit inside it?

It's a feature, not a bug!

I'm not a geologist, but I'm imagine that the deep ocean would be a colossal underwater glacier, with intermixed sedimentary layers. Kind of like what we have with methane hydrate deposits, only much, much deeper. The super-deep ocean simply wouldn't exist, and we might not even know about the Mariana Trench, or a lot of other sea floor features. Also, it's possible a different proportion of the world's water would be frozen in this way.

With ice as a part of the sea floor, it would also interact with subduction zones at continental edges. That might push a LOT more superheated water into volcanoes, faults, and everywhere else water could go. That would probably make for a lot more geysers in such areas, and volcanic eruptions would be far more energetic.

The trajectory of human history and technology would also be changed. There might have been fewer ice bridges between continents during the last ice age. Ice-skating wouldn't become as common a thing until we get refrigeration. Harvesting ice in the winter would require bodies of water to freeze solid first, making it impractical except in shallow areas.

I'm also going to wager that glaciers would behave differently too. I don't know enough about their dynamics, but I wonder if having meltwater on the bottom helps lubricate their movements somewhat. Kind of like a lava flow, only slower. Inverting that relationship might make glaciers far less mobile.

It pushes your code to be very tree-shaped

This is basically where my learning took me. I had to develop this notion that there was a preferred directionality to ownership and data flow, like "grain" in a piece of wood. Everything is easier if you go with the grain. "Tree-shaped" works too, since it basically is the call graph of a (single threaded) program.

The point where I realized all this was when I tried to do a very Python/JS-brained thing: return a closure from a function. The moment you try to "curry" values into the closure, you have to "move" them to solve for ownership, lest you bring timelines into the picture. Which isn't always what you want in a generic and reusable function. And sure enough, the standard lib and other popular libraries want you to pass a closure to functions instead.

This was my experience too, until I learned a few things.

• If you're coming from another programming language, the equivalent capabilities you're probably used to are Box, dyn, and Rc.
• Dynamic dispatch (dyn) isn't really necessary a lot of the time. Identify where you absolutely need it and solve everything else through other means.
• You wind up with lifetime specifier problems if you try to do a lot with references (&). Instead, try to re-think your structs and functions using composition and clone/copy instead. It's less efficient, but it's easier to optimize a running program, too.
• Rust enum, match, if let, and ? are weird, but are where you get the most leverage in the language. Try to master them.
• derive[...] is a first-class feature with a lot of standard lib support. Always use this to make your custom types mesh with the standard lib more seamlessly.
• If you are experienced with the "Design Patterns" book, you absolutely need this: https://rust-unofficial.github.io/patterns/intro.html
• Macros are an advanced feature, but help get you around limitations in generics and the type system in general. it really is worth knowing, and like the preprocessor in C/C++, isn't avoidable at the intermediate level.
• The compiler digs deep into your code to figure out types where they're not explicitly declared. I've seen it reach into the return type, call-spec, and function calls within that function, to figure out types for things. This is very hard to observe without an IDE that's checking syntax on the fly. Lean into both of those for more readable and maintainable code.
• if and match are expressions, not statements! You can use either block to evaluate to a single value, useful in composite expressions like let. Example; let x=if y>20 { y } else { 0 }; Or use them to return values from functions (w/o need of a return statement).

I will say this: for me, learning rust was 80% un-learning habits from other languages.

People tend to not like it when they have to change habits, especially if those took a long (and painful) time to acquire.

In this particular case, this is the same complaint Go faced with its form of explicit error handling. And Java, for that matter.

Honestly, Rust does a killer job of avoiding checked exceptions and verbose error hooks by way of the ? operator, and requiring all possible match branches to be accounted for. If you embrace errors fully, by using Result<> and custom Error types, your program gets a massive boost in robustness for not a lot of fuss. I recently learned that it gets even better if you embrace enum as a way to define error values, and make sure it implements useful traits like From and Display. With that, error handling code gets a lot more succinct, permitting one to more easily sift through different error values after a call (should you need to). All of that capability far exceeds any perception of clunkyness, IMO.

The fact that this probably doesn't even optimize to a lookup table just gives me pain.

It's basically the UI equivalent of this:

Yes, it's a fully-functional date picker and also deviously, wildly, uncomfortably outside of aesthetic norms. Also, there's a lots of fun, invalid combinations of input outside of the usual "February 30th" shenanigans.

Why yes, that's my birthday: the 32nd of Septunepril. What's the problem?

They're literally incapable of imagining anything else. Otherwise, we'd have radically different outcomes from all this.

It also didn't take long for the aftermath to become racially charged, either.

As it turns out, the folks most impacted by hurricanes and other weather events (e.g. flooding) are people of color. So, sending FEMA late to these sorts of things just reeks of malicious compliance.

• https://journals.plos.org/climate/article?id=10.1371%2Fjournal.pclm.0000026
• https://pmc.ncbi.nlm.nih.gov/articles/PMC9574315/

This is why I'm mostly okay with hunting deer, here in the US. We displaced their predators so it's on us to make up the balance. I say "mostly" since, like others are saying in this thread about taking habitat away from kangaroos, the better answer is to give them an actual functional ecosystem to live in.

The trick is to find the right message and tone for the moment. I also think change like this is necessarily incremental. It's possible that with enough doom-and-gloom around a pending "market correcting event", that helping everyone reduce grocery bills by eating vegetarian a few nights a week, would be the right message.

I'm going to say that every layoff has a cover story. The goal, reduce the workforce make/save money, is really the only justification needed. Everything else is PR, and an attempt to stay out of legal hot water.

That's always worth considering. A phone app doesn't take a big operating budget to launch and maintain. Especially for state-actors.

That's easy. It's more dull here, and there's less lock-in.

No, really. Social media without the dopamine-pump-style algorithm behind it is far less stimulating. Meanwhile, the Federation model itself allows us to abandon nodes that are co-opted by bad actors. So there's always somewhere else to go with all your favorite stuff when things go sour.

The best take on Black Flag I ever read was something like: "It's a great game, except for all the Assassin's Creed parts."

Ah yes, that brief moment of cold panic where you sincerely contemplate being deathly ill but still able to do something about it... right before your memory kicks in.

Dry, salty, black olives. Best paired with a light beer and a blazing-hot summer day.

Pickled jalapenos are just fantastic. Hot, sour, flavorful, and just versatile at 'waking up' all kinds of food.

Capers are great on all kinds of savory dishes where you want a little salt and sourness, but other pickles would just be overkill.

Canned black olives belong on pizza, and the occasional loaded nacho plate. They're kind of awful in other applications.

As for the classic dill pickle, ever had one in Dr. Pepper?

Yup. Learned that one back in the 3rd grade. This stuff is hard if you're not experienced enough to know how people work.

On the upside, I learned that one cannot buy their way into other's good graces, especially if they're going to require you to modify your behavior to get there; they're lying and that was never the issue. On the downside: holy shit that hurts once it goes wrong the first time.

As an adult I can also appreciate that there are situations where you can "buy your way in" to a club or status of some sort. IMO, those situations are generally not worth it to begin with, requiring an never-ending stream of cash to keep up appearances. Plus, it surrounds you with other people that also believe, and are invested, in the program. It's a recipe for elitism at best, and a big 'ol grift at worst. Better friends and relationships can be had for $0 everywhere else.

I was introduced to flyweight RPGs a few years back and I absolutely love what they can do in the hands of a creative group.

Roll for Shoes is about as minimal as it gets. You will need one D6, and something to track player inventory. The game world is best started by the GM in the abstract, letting the players fill in the world's details through creative use of questions that prompt die rolls. This is fantastic for players that want to stretch their improv skills.

Lasers & Feelings has a tad more structure. Everyone has exactly one stat that sits on a spectrum of "lasers" to "feelings". The difficulty of challenges in the game sit on the same spectrum. Depending on the nature of the challenge and what the player's stat is, a single D6 roll decides the outcome. Everything else is role-playing in what is encouraged to be a Trek-like setting.

In my experience, Roll for Shoes usually turns into a cartoon-esque "let's see what else is in my backpack" affair, that usually ends with everything on fire (because of course it does). Lasers & Feelings typically devolves into Lower Decks. All of these are positives in my book - I'd play again in a heartbeat.