produces higher quality sperm

That's really important for the sperm destined for the septic system, sure...

... Fantasy worlds out there that would look epic as a AAA fantasy blockbuster triology. Raymond E. Feist comes to mind. Bernard Hennen, Guy Gavrial Kay, Brandon Sanderson and countless other top-shelf fantasy authors and epic worlds. Can't we just leave LOTR be? It's gotten an excellent film adaption, one that will stand the test of time if it doesn't get diluted with trash like it already partially has. Please stop right now.

I think we may be truly witnessing the dawn of western culture and it effing hurts.

... to all their competitors, grab the deckchairs and some popcorn and watch everybody else tear each other to shreds. Brilliant move if you ask me. 8-)

... in at least one key aspect: The cash going around is almost exclusively from the deep and wide warchests of large megacorps. Which means if a bubble pops it likely will just be a little fart for regular people and we can get rehired for our bullshit desk jobs.

Shouldn't the super-fast rotation of massive black holes counteract at least some of their gravity vertical to it's axis? Could that - at least hypothetically - eventually cause a black hole to break apart into bits of regular non-black-hole matter, if it spins fast enough?

Sorry if I'm sounding silly here, I'm a 5th-grader when it comes to astrophysics but perhaps someone with knowledge could offer some insight?

How many billions did that game make them? Seriously, this just be one of the highest grossing videogames ever, no? How long has it been going? 9 years? That's pretty epic if you ask me. This game was nothing other than an epic success (no pun intended).

Modern devices and machines appear to me like some hilarious Brazil-style cyberpunk joke-reality. Imagine an effing cyberattack bricking a lock on your car or engine-starter. LOL! Well, I guess it's not called "Internet of Trash" for no reason.

... is likely going to be the mid- to further out future of coding. Presumably de-compiling into some human-only language not intended for re-compiling is going to become more and more of a thing. No need to go through all the hoops of countless programming languages and frameworks just because some naked apes like to each turn their own little software world into a stack-religion.

Some form of containers is going to remain though. Especially to isolate problems and find bugs isolating logical components into different chunks is likely to remain a thing if source code isn't available.

What APIs and functions exactly are being banned? And even if, migrating a PWA to something a little more old-school is trivial. Back in the day we even did async FEBE before XHTTPRequest even existed. Given, (re)loading zero-width frames to transfer data back and forth is quite steam-age Ghetto-style by todays standards, but the upside is it also works in browsers from 1998. 8-)

One of the big reasons I went with Android and not Apple when the mobile software craze started was that Apple was "We own you and the entire pipeline you use to bring software to end-users" and Google was "We don't care as long as you use our toolkits and services - which are totally FOSS btw."

This new totally-not-the-old-Google registration requirement is a hard turn-off for peer-group opinion leaders like myself. There are still FOSS Android alternatives, yes, so anybody doing Android development isn't suddenly entirely out in the cold, but this is a serious damper for my Google enthusiasm and I'm pretty sure others are thinking the same.

This is why I stuck with Web btw., even though Android Studio, Kotlin and Co. were very enticing. You never know when some corp. is going to pull out the rug from under you. That's why FOSS _and_ cross-platform (i.e. Web) is the only way I roll. Google can go all M1cros0ft and I'd barely miss a beat with any of my software projects.

Maybe this is the beginning of the end for Google? Couldn't say but it would be a shame. Of all Megacorps they were my favorite.

I have multiple AI services in my recently purchased Jetbrains Junie subscription. Right now I'm using codex for my work. It feels like having a pro developer team of 10 API experts at your service and ready to answer any request on your code base or any complex question right away. I've already taken the back seat and let AI do must of the hard work as per my instructions andrequests.

It's absolutely amazing. I've been professionally doing webdev for 25 years now and never had this competent a colleague, mentor or even senior. I Review every change and submit on my behalf. I do sometimes catch surprisingly human slipups (a few collisions with super-strict property typings, plural and singular naming lapses, etc.) but the AI fixes those instantly when I point them out. AI in turn finds mine too and points them out and asks if it can fix them. The context window lasts the whole project and the suggestions AI makes for next steps and improvements are really good and even inspired. Seriously.

The best part is that I can discuss the more abstract aspects of the app. I swear I have never had this consistency of competences when discussing my work and projects with someone else. I do not need anybody else on my "team" anymore. Not for coding that is. True thing.

Here's an excerpt of my ongoing work discussion with AI ( this is real! ):

>>>>>>>
> Could you explain the reasoning behind implementing a Baseline service? Is this a good practice and if so, why?

> Short version: Yes, itâ(TM)s good practice here because you need the same Baseline metadata (file list + meta.name/type) in multiple places (Baseline routing + Mainview). A service is the cleanest way to share that data without duplicating fetch logic or tightly coupling components.

Why it makes sense:

â Single source of truth: one place to load and cache the list of Baselines.

â Decoupling: Mainview and Baseline donâ(TM)t need to know how to fetch or parse the index.

â Less duplication: avoids copy/paste HTTP logic in every component.

â Easier to evolve: if the index format changes, you update one place.

â Easier to test: you can stub the service.

Downsides:

â Slightly more code and indirection.

â If the data is only ever used in one component, a service would be unnecessary.

Given your setup (routing + entry generation), the service is a good fit. If you want, I can keep it simpler by moving the logic into Mainview and passing data down, but that couples the components more tightly.

If AI pans out only half of what we expect, the world will look very different in a few years time.

Disclaimer: German here.

Even with current prices for electricity the cost effectiveness of fission is questionable at best. Germans are actually capable of math and engineering and the tree huggers weren't the reason replenishing plant Wackersdorff, the fast breeder at Kalkar and eventually renewal of fission in general was cancelled. It was boring back-room clercs repeatedly doing the math and coming up short that did this.

And if you don't believe this you can ask France how their all-out "fission only" plan of past decades is panning out these days.

That there may be some marginal strategic value to fission in wartimes might be true but the tenfold of that can be said about renewables.

As QR code on paper. Twice.

Hope they learn their lesson.

USians with means moving abroad, scientific panels advising the US, tourists steering clear, regulars avoiding conferences in the US, effing Iceland and Norway suddenly looking to join the EU (certainly didn't see that one coming). ... I have to be honest, I'm a tad worried about where the US is headed.

And I have a hunch that I'm not the only one. ...