ex1fm3ta

it will cost a kidney + Apple would remove the keyboard and sell it back to you for 499$.

I still think those expensive Apple monitors (which even had RAM) were intended to be 'iMac Pros,' but due to stagnant growth in the all-in-one market, they never saw the light of day.

they put some on macbook neos ... But one thing for sure, Apple reserve those flashy colors for entry levels models (Ipad 10/11th gen, Macbook Neo).

if you care about data-retention policy or you have to use european models ...

Automated vulnerability detection existed long before the era of artificial intelligence; many people have been doing this for a long time. All the existing tools and documentation paved the way for what AI is capable of today. Furthermore, undisclosed vulnerabilities still do exist—often discovered by state-sponsored actors who exploit them for opaque purposes (frequently operating outside the legal framework of the country in question).

hmmm not sure about this one, the disease was already there it just available to anynone (not only for state sponsored actors) and the vaccine is globally available at a fraction of what it cost to build it.

unless you are not into home automation you cannot understand how useful this is. Years ago I bought a slightly broken Ipad Pro just to hang it on the wall and control my lights. But I agree the screen size is not right. I cant do shit besides listening to music

Yesss this was needed so much.

it has to be. But you can ClaudeCode it works fine straight out of the box. I need custom workflow because I want to keep my independance in case Anthropic start acting like Uber on pricing.

Nope. Memory and data sharing for training are turned off. (I put 'turned off' in quotes because I don't know if Anthropic really keeps its promise. Often, it is cheaper for companies to break the law and just pay the fine.) I also use adversarial review and the '10th man' rule a lot. In fact, I spend more time planning than executing. I explicitly told Claude never to make a choice without proving it with numbers. By numbers, I mean benchmark results and score-based decisions (for example: 0.5 points for speed, 1 point for libraries, 2 points for documentation). The only thing I doubt are benchmark numbers, because they change depending on the hardware and what you test. Anyway, we always end up choosing PostgreSQL for large projects or SQLite for light ones (which makes sense).

Huawei can do something funny in this new trade war era.

I feel you, I am completely lost with all new ''graph flavoured DB". I keep challenging those (with the help of Opus model ) and the answer is always the same "use progresql".