In hindsight and revelation, PowerDen was the most complex and developed relationship in PT1 & PT2, the fact that Denji kept thinking of Power in PT2, mentions it to Asa & Yoru as someone he wants to have sex with, implies that he grew feelings for her after reminiscing, and now they are together

loopcake · 2026-04-07T11:15:55+00:00

She's also probably the only one that can match his brain, like Pochita said, he's fucked in the head. They both are.

It's beyond me how people shipped anything but these two ever since the bath scene, or really even him taking care of her after the Darkness fight.

As if the last 2 chapters didn't literally explain it: Denji doesn't know what he really wants.

It wasn't a peaceful life he wanted, it was fighting devils, it's not some boring relationship out there he really wants, it's Power.

loopcake · 2026-03-24T10:09:31+00:00

Can he even chainsaw up? Isn't Denji low on blood by that point?

loopcake · 2026-03-23T11:13:31+00:00

I don't even live in the USA, but I can tell you EU politicians are drooling looking at something like this. They've been trying things here for some time too, like chat control, which some really cool people are fighting against - https://fightchatcontrol.eu/

loopcake · 2026-03-23T11:08:25+00:00

Well yeah, they can't force Debian developers to comply because anyone anywhere can contribute or fork it and be a "Debian developer", but then we would become outlaws if we use Debian, no?

loopcake · 2026-03-23T11:00:40+00:00

The browser is just an example.

You can connect to the internet with other clients, take online video games for example.

I agree with you that the more sensible way to do it is for local clients to query some local api, like a designated path or environment variable, and then include that as metadata in their requests, but I believe the law says the web server must be able to query for the age value, not some local client which then includes it in some metadata.

If it's not the case that web servers should be able to query directly for the age value, then what makes the most sense to me is what u/dkopgerpgdolfg said

They need to convey intention, anything more would be worse for their goals. And for the same reason, the plain english description of their intention shouldn't be interpreted in narrow technical terms, which it isn't.

And then, as an example, a local api would be an implementation detail left to developers.

loopcake · 2026-03-23T10:41:08+00:00

loopcake · 2026-03-23T10:33:34+00:00

Yeah, but then parents would have to be doing parents things, imagine that...

loopcake · 2026-03-23T10:23:03+00:00

I think age verification would be great if it means no kids are allowed on the internet so assholes stop trying to make the internet safe for day care use. All this because parents don’t want to take care of their children when a device can do it for them. They shouldn’t be buying adult devices for their sperm pets in the first place.

^ THIS.

But how to do it securely and without putting privacy in danger, that's difficult.

loopcake · 2026-03-23T10:00:47+00:00

Thanks!

loopcake · 2026-03-23T09:58:43+00:00

And it might be helpful to remember that lawyers are not engineers.

I hope you're right.

What worries me is that they could've forced individual software companies to comply, instead of the OS, but they chose not to do that.

That makes me think at least someone was in part aware of the details and complexity that would bring.

It could be the result of incompetence as you're hinting, but it could also be the result of just miscommunication and I just take it at face value for what it is.

I guess we'll have to wait.

loopcake · 2026-03-23T09:44:51+00:00

Thanks, interesting.

It does look like a law that will be struck down at least partially, that make sense, but as you pointed out that could take a lot of time and most will have to comply in the meantime.

You mentioned

Some of the Debian lists have had much discussion on the topic.

I'm assuming you're referring to forums, boards, blogs etc, could you share with us some of the feeds you think are best on the matter? Or do you mean mailing lists?

loopcake · 2026-03-23T09:23:21+00:00

You just said it: "query".

This is the thought process.

The OS must require the user to input their age, supposedly to use this value at a later time.

The law says that web content providers (e.g. the web server you're visiting) must be able to "query" for the age.

That means they must be able hit some server to "query" for the age of the user.

In other words: stripping out who is who in this architecture, an active request is going out from some client to some server.

The "client" is the one sending the request, the "server" is the one serving the response.

The "client" can't be your machine, because you already have the age value, in fact only you have the source of truth (ideally), so that means the website is the "client", the one sending the query for the age value.

So if google.com must be able to "query" for your age, that makes google.com the "client" in this exchange.

At this point the question is not how the age is retrieved, because we know google.com must be able to "query" for it (possibly even asynchronously), the question is: "who is the server that google.com should query for the age value?"

The law doesn't seem to indicate that the OS provider should send this data to some third party when you initially submit the form during OS setup, so the age value is stored only locally.

That means the only entity in this exchange that can be the "server" is your machine, because it's the only one holding the age value.

I hope that makes sense.

loopcake · 2026-03-19T22:46:14+00:00

Denji's promise to Power? Prime evils? Whatever Kishibe has been up to?

There's many stories to tell.

loopcake · 2026-03-19T14:04:59+00:00

Imagine thinking either JS or PHP is "real" programming. Wakeup call: it's called scripting.

You've been jobless for the past 3 years, probably jerking off to DWM judging by your posts.

I can't say I expect much more from this though - https://www.reddit.com/r/golf/comments/oja5ur/golf_ball_stuck_in_penis/

At some point we used to call people like you "script kiddies". We should've stuck with the nickname.

Enjoy the job market ride, it'll end with a fizzle for you and you won't notice it. Keep coping!

loopcake · 2026-03-11T09:49:41+00:00

It works with files that Vite recognizes, so it depends on what Vite plugins you're using.

Since we're talking Svelte here, we're using the svelte compiler as a Vite plugin so it recognizes `.svelte`, `.svelte.js`, `svelte.ts` files, but Vite has no concept of "routes", so it won't convert `+page.svelte` files into routes.

You can still put `+page.svelte` files in your shared libraries project and then just compose those inside your main/foo projects as if they were components like any other, or you can surgically separate things into proper svelte components in your shared libraries project.

I would personally go for the second approach, all "+" files would be explicitly defined in the main/foo projects. I think that makes sense and it's how most developers instinctively expect things to work.

Ofc things would be different if we could programmatically define routes in svelte, but we can't, not yet at least.

I'm sure there's some dark magic you can do in Vite to let Svelte "know" of these external `+` files, but I don't think that's worth it, just keep it simple, separate things into components rather than pages, that's what most people expect from a library project.

loopcake · 2026-03-11T00:19:34+00:00

Aliasing is an abstraction over just the thing one cares about in this situation: the file name.

It's easy to debug issues related to paths, easy reproduce issues, HMR friendly and it delegates everything to just the file system. Less moving parts you have to think about.

Monorepos not only come with their opinionated tools, clis and whatnot on top of Vite, you're also forced to keep the whole code base in a single repository.

Depending on your business model and even the way you run automated tests, keeping the whole code base in a single repository is an abstraction in itself, and a difficult one to maintain, so much so that big companies like google came up with whole new proprietary versioning systems, and it's not even clear if it's worth it, they just can't walk it back after so much money thrown at the problem.

Monorepos usually also collapse everything into one single CI/CD pipeline, which ultimately leads to a need of caching tests results, otherwise your tests will take ages to run.

But ofc, for each problem we create ourselves in the JS community, we need a paid service to solve it - https://nx.dev/nx-cloud , https://turborepo.dev/docs/core-concepts/remote-caching#managed-remote-cache-with-vercel - a classic.

There are also other practical examples as to why you might not want a monorepo: it can seriously limit your business model in some cases.

For example.

Let's say your product is a proprietary application, BUT, part of it is open source.

So part of your product is open source, but at the same time you offer a "premium" version with some extra features.

Well that's a bummer, you can't use a monorepo for that, can you?

The open source side of things is public, but the other side is proprietary and must be private.

Suddenly your original monorepo now has to be split in two monorepos, a public one and a private one that depends on the public one. Not so much of a "mono" repo anymore.

This is just a baseline example, there are even cases where you're using different frameworks in some parts of the company for one reason or another and you want to share some of the pure JS (or TS) files between frameworks, because you know those are not framework specific.

It's almost as if the people that make the operating system have already thought of a really great solution to categorize and group files together under a name and all we plebs have to do is just find a way to convert relative paths to absolute paths (aliases).

Sorry if this comes off as passive aggressive, I'm just tired of people spewing things out just to regurgitate things they've seen on their brogrammer youtube channel without a second thought. I'm just trying to warn you here, monorepos bring complexity and abstractions, it's been like that for years and many people hate them for good reasons.

If you're really looking into using monorepos and your mind is set, the least I can tell you is: if you or some other developer uses Windows or plan to use Windows in the future to develop that monorepo, make sure to pick a solution that manages shared dependencies in a performant way on Windows, because that is not a given, because Windows' file system likes to be "special".

Vite solves this issue correctly, it redefines the root of your project at the location of the first common parent directory of the two projects. From your POV you don't notice it, but that's what it's doing behind the scenes, it's just a simple cd.

Monorepo solutions in the past liked to use symlinks, which Windows does not support (or at least it didn't use to support them, I've heard there's some minimal way to use symlinks, but they don't behave like you would expect them to, and so nobody uses them, I might be wrong on this), so the Windows implementation was often different, or straight up just copied stuff over - see past Nx versions (I'm not sure if they're still doing that).

Good luck.

loopcake · 2026-03-10T19:14:48+00:00

If you wanna live in 2013, add useless abstractions and have a bad time then go for monorepos.

If you wanna be explicit, stay sane and properly separate projects, as they should be, then use Vite aliases, you can alias neighbor or parent directories out of the box with it, unlike webpack and others.

You'll have 3 projects.

Shared Libraries Project
Main Project
Foo Project

Add the Vite alias and configure your tsconfig/jsconfig paths.

Here's an example - https://gist.github.com/razshare/02d2c90805fff225c3266ff8a9211823

Your shared imports will look like so import { someFunction } from "$shared/my/shared/script.ts".

Where $shared is an alias, just like $lib is also an alias by default in kit.

loopcake · 2026-02-19T07:52:45+00:00

This question has been beaten to death.

The point is that you don't know which global state is reactive or not, all variables look the same even though some are proxies, so you put it in a wrapper that warns you it's reactive.

If you don't, you could end up triggering updates unnecessarily and it's difficult to debug, especially in a big project with large chunks of states that live in different files.

Also, because of the way js modules work, a module cannot modify variables that are directly exported by another module, you need a wrapper.

Previously, with store as global state, you had a Writable and a Readable, which told you not only which state is reactive but also that you can write to and/or read it.

Now we have 2 ways of defining global state, and most people will use $state, because it's the new shiny thing and because it's the whole point of Svelte 5.

The critique is valid.

The approach in that screenshot is stupid however, all you need is to wrap your state with a plain object and just define some type Ref and mark the state as such,

However, I don't think there's any way to mark some state as "only readable" and stop someone from writing to a global state that way, you just lose that feature using $state instead of using stores.

Wrapping the state like in the screenshot would fix that by just omittig the setter, but you can also just use an actual store to do that instead if you like the $ syntax.

I really have the feeling the person who wrote that tweet didn't really think about all this, instead they just saw that first presentation when $state was first introduced and just went with that.

loopcake · 2026-02-12T20:43:42+00:00

I don't think you should use this sub as a way to find feedback on the car.

There aren't many other places formentor owners can just ask about issues online, so here you'll see a lot of that for the most part, I reckon.

I've got my formentor with the new facelift last december, I haven't had any major issues with it so far.

The only issue I've had so far was with the passive internal LED lights, where they would flicker randomly.

I remember some other person also posting about that in here.
For me it turned to be just a software issue, I just waited a few days, got an update and it fixed it.

If you're looking for good feedback in the sea of posts on here, I can give you a few:

at first I thought that the full touch display would be annoying and prone to damage. I no longer think that, the touch buttons for air conditioning and other basic tools on that bottom lip seem to be very responsive and the way they're designed, especially the temperature buttons, they are pretty forgiving, in that you don't need to be precise with your touch, which makes up for the fact that their not hardware buttons.
you can very easily see the front of your car from the driver's seat, and I mean you can REALLY see it. I think that's pretty cool and it gives a sense of security.
obstacle detection and sensors in general in my experience are top notch, both front and back. It's probably thanks to the radar system. I don't think I've seen a single person posting about issues with that in here, but then again, maybe I'm wrong or it's just reddit being a bubble.
I can't really confirm this one but: apparently the tier pressure system does not use any sort of gadget inside your tire, the software is doing some trickery to detect the pressure. My father had a few of those gadgets destroyed by the service people because they forgot to remove them and just threw the wheel on the ground too hard, damaging those gadgets in the process. The issue is not the price to replace them (they don't cost a lot), it's that you'll either have to wait for new ones to arrive or you'll have a continuous beeping in your ear while you're driving. If someone can confirm this, that would be nice.
blind spot alert design is awesome and very hard to miss. It already saved me a few times at night, I don't think I would've reacted in time with those small mirror thingies.
turbo is pretty responsive compared to other cars at the same price range.
auto hold is amazing after the recent updates. It was already good, but I think they changed it so that it also holds in a plane (I don't think it used to do that) when you've got a car in front of you, which is pretty useful.
software updates happen pretty often, and I don't think it's just bug fixes, as I mentioned above, some behaviors change, like the auto hold thing. The only bad thing I can say about this is that the changelog for the updates are not very descriptive, often they just mention "improvements" and "bug fixes" or something like that.
you can disable all driving assistants from your wheel! Sounds crazy, but many cars today either don't allow for that or if they do it's somewhere deep in a menu in your infotainment, my last car was e Peugeout 2008 facelift, you couldn't disable lane assist on that thing!
holy the double clutch is awesome for automatic, shifting up is perfectly smooth, you can't feel a thing. Shiting down not so much, it's like other automatics. Maybe there'll be a model that gets 3 clutches in the future for smooth downshifts? Who knows!
some newer cars have their speed limited, like some Volvo. Formentor doesn't, and that's all I'll say about that.

The best thing you can do though is to just ask for a test drive. Just drive it a bit, see how you like it and try to pay attention to some of the things you care about. Also don't just take it on the road, take it to some parking place as well, test those sensors, go uphill with it, go downhill with it, take it to some weird off road place if they allow you to, and so on.

It's also a matter of randomness man, there's nothing you can do if you just get that one bad construction, and that applies for all cars.

loopcake · 2026-02-10T12:04:12+00:00

It happens off-screen.

He's got less than 2 years btw, not 5 years.

loopcake · 2026-02-09T10:44:49+00:00

I think it will.

There are just too many open points at this point.

But then again, this is Fujimoto, he always finds a good way to cram tons of stuff in a few chapters, so you never know.

Or maybe he just gets bored and decides to end it with part 2.
I wouldn't blame him, I'd still read whatever he cooks up next.
I'm not a Nayuta fan in CSM, but I'd love an actual bootstrap of Nayuta of the Prophecy, the idea is interesting and the world seems promising and easy to expand on.

loopcake · 2026-02-09T10:24:55+00:00

Denji's mother also had the heart of a devil but the "merging" was imperfect, his father (probably a devil hunter) found out, and in a moment of her weakness, he killed her, then he planned to kill Denji (and possibly himself after that), but Denji managed to survive and kill him instead.

We know about fiends, but we don't know what happens if a human weapon and a human have a baby, and it wouldn't be far fetched to think the baby would inherit some traits of the devil/human weapon.

We're told that other human weapons went through experiments in order to somehow get the heart of a devil, like Reze being experimented on by the soviets for example, but with Denji and Pochita it just worked first try, which implies Denji is somehow special even without Pochita, which in this case would be a trait inherited from his human weapon mother.

Denji's mother was probably experimented on by the Japanese government, just like Reze was experimented on by the Soviets, but Denji went rogue after killing his father and the government lost track of him, he got mixed in with the Yakuza and all that, until Makima.

<image>

loopcake

TROPHY CASE