netbioserror

It's the only country in the hemisphere without another functional demonym. Posts like yours are vapid, pedantic, and tiresome.

I would think the dominating factors in Oregon and California are their uplifted soft geologies. The orogenies that lifted the West have resulted in an elevated, cliff-bounded sandy coastline along the Pacific that has been aggressively eroding for a lot longer than humans have been there.

If mass is proportionally equivalent to energy, then this can't be true. The photon is the fundamental energy unit. Right?

Then wouldn't it be "one-photon"? I've heard (but don't fully understand) that massed particles are simply photons trapped in toroidal vortices, which gives them an outward charge field and lets them interact with the Higgs. Annihilation supposedly just being untangling the toroid.

Nim defaults to this kind of stack management and value semantics, except the `ref` and `ptr` trapdoors are there whenever you need them. So like this, Nim requires no memory annotations or semantics for good, safe default behavior.

Goose is a straightjacket by comparison. I've never enjoyed languages that plant a flag on one mechanism and force users to adapt.

I've only dipped my toe in, but it compiles fast code and works. Can't argue with results.

The turning point is approaching: Interest rates will gradually overtake all other gov't expenditures. All politics will revolve around shoring up the parasitic drain on the rest of absolutely everything.

I made an internal GUI tool for company in Godot. It uses GDExtension to interact with OS systems, namely serial/COM ports. Yes, you can make quite good desktop GUI applications in Godot, with mostly its default toolkit!

Also, exploring minified Godot template compilation led to me distributing a 24 MB portable package (10MB zipped). Astonishingly efficient.

Why not have WMs and DEs specialized for specific disability categories?

Yeah, I got the impression that Reticulum's main claim is that it replaces the IP stack with a future-proof, encrypted protocol for routing regardless of the underlying network medium. Which is not an insigificant claim to test, but boy would it be fantastic.

There's a third way here. It could be called many things: Single ownership by default, automatic stack lifetimes, hidden unique pointers, etc. The main idea is that the lifetime of dynamic heap data is treated no differently to primitive stack data: Clean it when it goes out of scope. Rust and C++ require you to specify this manually, but Nim is unique among native-compiled languages in that is does it by default, with tools to opt-out. An advantage of this approach is that combining immutable values and static analysis can reduce most parameter passing to borrows, again, without needing the programmer to specify, by default. The main cost being that some assignments, especially crossing the variable-to-immutable line or vice-versa, would require a copy.

LLMs are vectoring towards solving problems of software quantity. What remains is judgment, caution, and taste for quality.

Much as computers have made creation in other industries much easier, we're likely to see a glut of crap software made by non-programmers that does not meet any quality bar because these are the sorts who think "lines of code" was the hurdle to overcome.

That is definitely not what the Maya did. Or really any civilization with large permanent cities. The record of forest cutting once settlements reach a certain size is consistent and global. The Amazon simply experienced a full civilizational collapse and more than enough time untouched to recover.

It might suffice to say: The myth of sophisticated indigenous ecosystem engineers who harmonize with nature is a European trope.

Whenever any culture larger and more settled than hunter-gatherers has traditions of forest management and ecosystem balance, don't immediately attribute to them magical wisdom that Europeans somehow lack. Consider that those traditions are an ancient memory of one or more catastrophic ecosystem collapses and the practices of the people who survived them.

To recognize the possibility, one has to grapple with incredible scale and deep time: In roughly 300 million years (1/10th of the time life has been around), the Appalachians split off from the Atlas; the Atlantic Ocean first started splitting open; uplifts underneath North America pushing the West up from the seabed and caused the rivers to carve millions of acres of sandstone landscape down, leaving towering plateaus, cliffs, and eventually river chasms. Over the 3 billion years before that, what was carried away like so much sediment? What was subsumed by subduction boundaries?

On a much more recent timescale, one of the dominant theories of the emergence of civilization places the ancestors of the Sumerians in a stupendously fertile valley at the bottom of what is now the Persian Gulf, eventually flooded during the retreat of the glacial maximum and covered in Tigris & Euphrates sediment. It could be the very origin of regional flood and primordial garden myths. But it's all buried.

I know the link is by the creator of Odin, but I can speak personally for my passion for seamless tools. I have ever had as seamless, high-flow of a development environment as I do now using Nim with Sublime on Mint at work. Every one of these tools is intended to slide out of the way of your thoughts, and they do so deftly. I'm never fighting the tools; instead, the tools are facilitating me transforming my thoughts into compiled programs. All of my time and energy is spent formulating a sound model rather than fiddling with configs or fighting obtuse features.

What "constructive" argument is anyone supposed to give about authorities having warrantless access to all private conversations?

The fatal flaw here being that secondary sources and tertiary ad infinitum are all always motivated. It's inescapable.

Calisthenics is a really easy way to push intensity at basically 0 risk of injury. They're all compound and depending on the variation could require high reps, but between push ups, pull-ups, squats, their numerous variations, and accessory work, I would challenge anyone to actually injure themselves while also being able to push to true technical failure.

I recently learned, through visual intuition, how the relative perception of time between two subjects changes as relative speed between them changes. It's because they are observing each other from an "angle" in the time dimension. And in that time dimension, angles do not trace circles, they trace paraboloids.

If I'm remembering correctly, this is also why the energy required to "reach" the speed of light for subjects with mass parabolically goes to infinity. I'm also guessing it can directly trace a proof down to why kinetic energy increases quadratically.

A significant portion of the population DOES want to read and engage with long-form content and discussions. They simply don't want it to be drivel. Traditional corporate/state journalism produces drivel. Substack is flourishing for a reason.

Man, all of the confusion and gnashing of teeth in the C++ world really makes me grateful for my job. Smaller company, I solo develop a central module on the product stack, and I was able to evaluate languages for the project.

Nim became the obvious choice, and I wasn't a fanboy before. Simple semantics, in a very functional style oriented around data's value. References and identity have to be trapdoored. Everything is single-owner unique lifetimes by default, no annotations or best-practices required. You end up writing extraordinarily functional/procedural code that produces very fast and memory-safe binaries, it fits right into C++'s niche.

The only objection I could steel man was that the standard library and most packages are composed of relatively pure functions that return new values, so allocations are happening there. But when types as complex as data frames can be semantically used as just values, and you know they have scoped lifetimes by default, the benefits are obvious.

With all of C++'s insanely specific, subtle, implicit, compiler- and platform-dependent behaviors, I've often wondered when the industry will finally consider its dominance an artifact of first-mover inertia and simply move on. There are vastly better ways to do all of the things it does, while easily exposing levers for the the things it's considered to do exceptionally well.

Janet is ALMOST an incredible tool...but what I want is a very clear bifurcation between the standard library's stateful mutating procedures, and stateless value-returning functions. I ran into that wall hard trying to make something non-trivial.

It also turns out that the mix is due to the standard library leaning on raw C loop iterations underneath whenever it can. Which is great! But it confuses the library's interface paradigms.

The most fun I have playing Magic is a "Reasonable Cube" sealed draft:

Buy or make a cube with a very normal distribution of cards, nothing crazy (I bought a cube made by Card Kingdom some time ago). There will be 90 spells per each of 4 players. Shuffle the whole deck, and deal out the 90 per player. Now you simply make 40 card decks, typically with ~25 spells each. There will be lots of wiggle room for sideboards or even side decks. Then run a little tournament.

The games are usually that ideal Magic scenario: Nail-biting back and forth gameplay, where anything powerful has a cost and games come down to the wire.

Ah sweet, manmade horrors beyond comprehension.

Nim does much the same. It prefers the stack, wraps dynamic heap types in value-semantic unique pointers by default, and avoids implicit copies wherever it can. I could see compiled languages trending in the stack-managed direction long term.

A creative's best work is born from constraints. It's why PICO-8 exists for people nostalgic for that specific olden era. I think the PSP could make a fantastic target for meatier handheld-focused games that put design first, as many of its second-tier games did. Lots of great strategy, platforming, and racing. A beautiful wide-screen with just enough resolution, just enough horsepower to drive it with rich, saturated 2D and some 3D, and a basic enough control scheme to rule out the lame tech-demo category of 3D action games. I cannot describe how much WipeOut, Namco Museum, and Tactics Ogre time I had on my PSP.

The entire Internet can bear the burden of free speech. I hold encyclopedias to a much higher, gatekept standard.

Agitprop like "aesthetics are fascist" is pretty blatant opinion. Live up to your own standards.

A) Non-argument. B) Repositories of knowledge should not contain anti-knowledge.

Are you seriously suggesting an encyclopedia should be packed with crackpot conspiracy theories, academic charlatanry, quackery, and agitprop? Or does that not defeat the point? Keep the author's biography, but his "theories" are best left for a footnote in the biography, or websites that explicitly serve as a museum for failed ideas.