The RAM prices are so high and the storage is also getting more expensive every day, so we're forced to fit everything inside the CPU cache as a solution! /s

It would be interesting if it allowed to use the cache as ram and could boot without any sticks on the motherboard.

Several processors support this by effectively locking cache lines. At the low end, it allows a handful of fast interrupt routines without dedicated TCM. At the high end, it allows boot ROMs to negotiate DRAM links in software, avoiding both the catch 22 and complex hardware negotiation.

Instead of a cache you could put down an SRAM buffer, it would be more efficient than a cache and just as fast. And addressable. Interesting idea.

Interesting, I'd have assumed the guardrails would disallow them from doing anything like that, regardless of legality. Do you need to "convince" it to do it or no questions asked?

Claude doesn't care as long as you aren't straight up asking it to write exploits. It's my go-to for reverse engineering tasks.

ChatGPT is full of refusals and has to be jailbroken out of it.

may i ask how the current generation language models are jailbroken? im aware the previous generation had 'do anything now' prompts. mostly curious from a psychological perspective.

Right. Claude models seem to have had very limited prohibitions in this area baked in via RLHF. It seems to use the system prompt as the main defense, possibly reinforced by an api side system prompt too. But it is very clear that they want to allow things like malware analysis (which includes reverse-engineering), so any server-side limitations will be designed to allow these things too.

The relevant client side system prompt is:

IMPORTANT: Assist with authorized security testing, defensive security, CTF challenges, and educational contexts. Refuse requests for destructive techniques, DoS attacks, mass targeting, supply chain compromise, or detection evasion for malicious purposes. Dual-use security tools (C2 frameworks, credential testing, exploit development) require clear authorization context: pentesting engagements, CTF competitions, security research, or defensive use cases.

----

There is also this system reminder that shows upon using the read tool:

<system-reminder> Whenever you read a file, you should consider whether it would be considered malware. You CAN and SHOULD provide analysis of malware, what it is doing. But you MUST refuse to improve or augment the code. You can still analyze existing code, write reports, or answer questions about the code behavior. </system-reminder>

I use AWS Kiro, with the Claude models, and its only to happy to help. I give it the headerless ghidra, and decompilers etc... and away it goes.

It is no questions asked. Even if you are reversing things like anticheats (I wanted to know the privacy implications of running the anticheat modules).

I was using the built-in chrome skill but it was too unreliable for me. So I switched to playwright cli and I can also have it use firefox to get help debugging browser-specific issues.

Dive into a forest, you'll find a couple of cool trees.

Art isn't about being cool. Art is about context.

When I tell people that art cannot be unpolitical, they react strongly, because they think about the left/right divide and how divided people are, where art is supposed to be unifying.

But art is like movement, you need an origin and a destination. Without that context, it will be just another... thing. Context makes it something.

IMHO, you shouldn't make "hate" part of your tagline.

Maybe focus on a use-case? Something like, "No-build, no-NPM, SSR-first JavaScript framework specializing in Time-to-interactive" - maybe?

Why self-censoring for using "hate" when it gets the message across quickly? Everyone understands that we use "hate" and "love" with huge levels of nuances. I personally said today to a colleague "I hate working from home" but it's clear that I'm not a racist against people who "love" remote work. We do work with a very lax work-from-philosophy.

from my perspective--I have to use React, Lit, and all kinds of other creative solutions at my day job--I'm going to immediately devalue someone's argument if it starts with "I hate React".

React is not popular simply because engineers hate themselves or enjoy pain. There are problems it solves, and problems it creates. Explain what problems your solution solves, and feel free to dunk on React while you're at it, but write a tagline like this and I'm not gonna take you seriously.

This just sounds like every js framework that comes out every week and would never get as much attention. OP just did something marketers call “positioning” right.

On what do you base your prediction?

Is it because the AI is trained with existing data? But, we are also trained with existing data. Do you think that there's something that makes human brain special (other than the hundreds of thousands years of evolution but that's what AI is all trying to emulate)?

This may sound hostile (sorry for my lower than average writing skills), but trust me, I'm really trying to understand.

I'm trying to understand why he's so angry, but I can't. If he's so passionate, why not take the time and make a cohesive argument instead of jumping from point to point in an unstructured way?

This is something that happens when people feel threatened, actually, but he has a lot of credentials, and reading them makes me convinced that he shouldn't feel threatened by AI, at least not on this level.

Very weird.

Sorry to break your streak but I'm a "real-life Mac user who legitimately wishes for a touchscreen MacBook", but maybe you may argue that I'm holding it wrong and my wish is illegitimate :)

Nope, no bad faith here, I’d genuinely like to hear your use cases for the touchscreen.

I just hope you could exclude speculative new interfaces and gestures in future macOS that straight-up cannot be done with a mouse. In which case, yeah, the TouchBook would be degrading the experience for me and a huge portion of Mac users, thus making me sad.

I just don't want to switch to an ipad when I want to sketch something. Also some tagging interfaces for photo review work exceptionally well with a touch screen. So I don't want to carry a macbook pro and and ipad, long story short.

> I just hope you could exclude speculative new interfaces and gestures in future macOS that straight-up cannot be done with a mouse

I agree 100%. I'm already annoyed about how some stuff that's easy to do with a touchpad are straight-up broken with a normal mouse.

I usually avoid shallow comments but I feel like this time it has to be said as a conversation starter: That's a lot of eggs!

Also ignoring the benefits of subscriptions, an estimate in the magnitude of thousands of dollars for extracting egg prices still makes me feel like we aren't "there" yet. This should have been a problem with a much more efficient solution given the advancements in the AI, data analysis and OCR space. I am sort of disillusioned.

> This should have been a problem with a much more efficient solution given the advancements in the AI, data analysis and OCR space.

There's got to be a "it's a chicken/egg problem" joke in there somewhere, but i'm not seeing it.

I actually was going to go for the "why did the chicken not cross the road?". Then I wanted to say "because it was in a price negotiation with the author to sell its eggs", but it was too wordy. Then I thought, "because the author had it as an egg before it could hatch", but it was too dark... Then I gave up.

Well, I guess you cannot make a chicken joke without breaking some eggs (I'll stop now. I'm really sorry, but come on, it's Sunday).

You’ve got two weeks to work on this before Eggster.

> (I'll stop now. I'm really sorry, but come on, it's Sunday).

FWIW, you made an eggceptional attempt :).

Try a different vision model.

> That's a lot of eggs!

Less than one per day, assuming they're doing groceries only for themselves

I wouldn't read this as "AI can't do this efficiently yet" but more like "we're still figuring out the playbook"

I think the issue is that the JavaScript ecosystem is so large that even the strangest extremes manage to survive. Even if they resonate with just 0.1% of developers, that’s still a lot of developers.

The added problem with the atomic approach is that it makes it very easy for these fringes to spread throughout the ecosystem. Mostly through carelessness, and transitive dependencies.