phoronixrly

You at least have a PIN on top of thatm right? Right?

I can say the same about any opinion of an LLM 'programmer'

I'm not mad that VScode is popular. I am mad at people that are not appalled by the resource use of vscode and clones, by the sluggish UI, by the abysmal security (with the latest example being the multi-billion bitcoin theft), by the walled garden that allowed a backdoored extension despite its very stated purpose... You know, all factors that a competent programmer would find important when making a choice of tools...

No, now you are running an IDE that is badly pretending not to be a browser, while an entire second application has to work in the background eating even more RAM to provide you with access to documentation for each function at the cursor...

I presume Dropbear, thus musl-based OpenWrt routers are also not affected? Not that Dropbear has been an example in that regard.

That was always the issue... Rewrites were done before LLMs and the results were the same... There was never a point in time where the bottleneck was production of code, it was always review, testing, QA, fixing bugs and edge cases, and that is when only focusing on the technical part of delivery, and leaving out communication and synchronisation within the company and between company and clients...

My (35) physician explicitly advised me against my 8-10 hour road cycling sessions pointing out changes in the heart wall thickness he was already able to observe.

The article tells me more about the dangers of overtraining at an advanced age than the usefulness of wearables. The wearable was useful for the researchers after the person had already passed away.

Also, considering the number of such workouts he completed and the fact that it seems he was aware of his deteriorating heart, he carried on? Even despite reported fatigue? Mad respect for his determination.

I am tired of the fact that even my hobbies have now been taken over by LLM-wielding imbeciles. Nothing better than going through LLM output your whole work day only to tune in to your favourite community after work to see an absolute idiot throw a slop grenade and refuse to accept that the LLM served him bullshit...

> His ultimate message for the team was to “stop lovingly handcrafting all our code and use AI more.”

What more is there to say?

Oh no, AI boosters are completely fine with firing devs as well

Precisely, exfiltrate the pin, unlock the real one.

tpm2totp used to do this, and it also eliminated the need to divulge the secret used to unlock the TPM, I now see that it has not seen a commit in 2 years.

I also hear mjg59 is looking into encrypted swap hibernation support, so there's a slim chance there will be some development on the system-attestation front.

This is still vulnerable to evil maid. You need to be able to attest the system before you enter the PIN.

oh no, I am long past any delusions that any problems will ever be solved, I just want it all to end

Please let this come sooner...

Why would I ever use a UUID PK if I had the option to use a serial one instead?

Wow... That is some nitpicking... The major issue these UUIDs solve for me is the fact that using a random UUID as a primary key of a relational database leads to horrible performance...

It has never crossed my mind to decode the timestamp from them so I save myself a 12-byte column, neither has it crossed my mind to have them monotonic in a distributed system...

I know this is bait, but maybe their reaction should be to go and vote so that the persons who think rape should be OK (as per leaked e-mails btw) don't get to decide?

Is this a positive thing? I read it as the AI results not correlating with test data...

Here's the missing part, as per the PHP announcement

> On October 21st at 07:41 UTC, more than six hours before the coordinated release, Chainguard unilaterally broke the embargo and published built images containing the fix. Like other distributors, Chainguard had received the patch in advance so its users could update the moment the vulnerabilities were disclosed. Any attacker could now study the fix in binary form while every other PHP user was still waiting for the release. This disregarded weeks of work by many parties toward a coordinated disclosure.

Can anyone explain the lack of the irresponsible disclosure in the 'Responsible' disclosure timeline? The one that happened just before the coordinated release?

It is not going away, but it is not going anywhere, too.

Rails is dhh's taste in programming materialised. If he's no longer using it by definition it is on its way out (i.e. no new features, no enhancements) whether he still manages people depending on it or not.

Another way to look at it is that ddh's taste has now completely shifted from doing things the Rails way to not looking at code at all.

No, it does not. The reasons are not technical though - the main reason is the project being led by a person who does not use it or in fact write any code, and on top of that is obviously not quite mentally stable. Depending on such a project brings too much risk.

Using frameworks and libraries in general still makes sense though, as it is chiefly concerned with code reuse.

Only if you're into vibe coding.

Ah, Chrome ships JXL when we already have a better codec for the web!

As a Balkanian I vouch for this. Even what little you pay as taxes gets embezzled and you are always on your own.

Here's one from Filippo

The Most Backdoor-Looking Bug I’ve Ever Seen - https://words.filippo.io/telegram-ecdh/

> AI-native mathematicians

What a world we live in...