kangs

I worked with Moto on simple security improvements a few years ago and while they understood the competitive advantage they would get, being a now-small player - I also wasn't convinced that they were fully committed, their support apps and base image were still full of software i wouldn't recommend to say the least.

I hope they are now. There is a void to fill.

Disappointing news to say the least. this doesn't save that much space and power.

Pixel series aren't the fastest- they're far behind. They're also not the cheapest, they're amongst the most expensive.

The reason people still buy it is that they get a certain level of software quality and UX features, as well as security commitments that make Pixel and all of Android safer as it allows for fixing vulnerabilities quickly for everyone. MTE was one of these.

When Google stops doing this, what's the point of buying a Pixel? I'm also not confident that Motorola will pick up the slack in practice.

- Software is copy-able for nearly free. - Hardware is not. Even if you have the plans, you've to build the infrastructure for it, and its a fairly finite, physical item.

Both are however hard and expensive to produce. It's much better for profits to develop and sell the hardware, and copy the software someone else spent resources on.

rust is pretty nice actually

it is getting there, and not so slowly though. The remaining problem is that it's still just a tool. Telling a random dev "make zig faster in a one shot PR" isn't going to give good results either.

In the past, OSS projects were self-selective because you needed to be able to make working code, and if you did, you probably also reasonably did the right things as you spent years learning this, and have some sort of reasoning behind your feature, need, etc.

Today, even if the LLM was perfect and could reason well, it still does the bidding of the prompter - and you no longer have self-selection. Heck, it'll be difficult for zig devs to decide what's actually made by an LLM or a human anyway, I'm sure there's already LLM generated code in there - but at least these [human submiters] still need to be reasonably good at code.

I wonder if we'll end up with "only human with trusted badge of honor" can commit, and/or "LLMs now reason well enough to tell you: 'no, f off, this feature, plan, idea is garbage I'm not generating it" hehe.

When i was a kid, my dad had a Mac with the A/V PAL-SECAM cards. Hooked up a make-shift copper wire antenna and wrote a decoder with the free codewarrior cd folks gave me at Paris' Mac convention (we were 12 and crazy I guess). Good opportunity to learn powerplant and c/c++.

I ended up brute forcing most of it as I did not really understand what I was doing, but it turns out, with enough time, you get things going.

Wish the pages were still up, I lost that software long ago, and I'm sure my code was garbage (not that its much better today, but at least I can blame Claude..) and fun to read.

The 90's were fun.

hello faster horses

it's actually just trust but verify type stuff:

- verifying isn't asking "is it correct?" - verifying is "run requests.get, does it return blah or no?'

just like with humans but usually for different reasons and with slightly different types of failures.

The interesting part perhaps, is that verifying pretty much always involves code, and code is great pre-compacted context for humans and machines alike. Ever tried to get LLM to do a visual thing? why is the couch at the wrong spot with a weird color?

if you make the LLM write a program that generate the image (eg game engine picture, or 3d render), you can enforce the rules by code it can also make for you - now the couch color uses an hex code and its placed at the right coordinates, every time.

just run bazzite already

hello b/Googler :)

or, solid state batteries, graphene, fusion, quantum computers, agi =)

bicycle weight ratios are completely different from even motorcycles. a bike wheel can quickly become heavier than the frame for example.

google even has specially signed fw that let you root the device and unlock anything that doesn't rely on the passcode. secureboot passing and all. i can't imagine that the nsa doesnt have them. after that you just gotta crack the usually very simple passcode. wouldny be surprised if thats what cellrite has lol.

hey you aren't supposed to notice :)