theneverfox

I've been half joking about it for a while, but it's been only a matter of time before copyright was stretched so far that criticism of the work becomes a violation

Unfortunately, it seems to be beginning

They would have to be more scummy and also at least similarly competent... Google can't innovate for crap, but they're pretty good at maintaining projects (when they don't randomly kill them off)

If they stop work on chromium, or belief in the stewardship of chromium wanes, it'll fragment the ecosystem again. Which is sorely needed at this point - we need to get back to standards and away from centralized control

Imagine Twitter/musk acquires them. Microsoft, Apple, and many other big companies directly or indirectly rely on a chain now controlled by a group known for mismanagement - are they going to wait and see, or are they going to diversify?

They do... It's just not expected that they won't

Pains of being a prototype democracy and all... If only the founding fathers had explicitly told us our system would need reform as issues came up

All of that makes me nauseous.

You're free to use what you want to use, but the layers of dependency on vulnerable product lines is exactly the problem

Sure you can, outside of a few specific carve outs it's a civil matter... Meaning it takes money to fight money behind it

I really like my wired-wireless earbuds. They wrap around my neck and the magnets keep them in place like a necklace when not in use, the microphone/controls are closer to your mouth so the sound quality tends to be better

But of course, we can't have nice things anymore, so they seem to be phasing them out

Sprint merged with TMobile

No no no, it is in fact still hammer time, but there are 26 main types of hammer and countless subtypes

I think there's tons of things I love for it to do for me automatically - there's all sorts of quality of life features that I only notice when they change it, usually without bothering to tell me. And now, my muscle memory is leading to unexpected behavior, and it'll take me weeks to learn to stop doing that, and a few more months of training to learn the new muscle memory as I relapse at all the worst times

Some of it is straight up better, some of it is great new capabilities, but in the last few years? All that comes to mind is I thought it was pretty cool they added auto responses, even if I never actually use them. Doesn't change existing behavior, just adds a new option that's not in the way

But then the auto complete - I hate it so much. And I love auto complete - except it's the fucking opposite behavior of every IDE out there, including Microsoft's! I can't even unlearn it, because it's a core part of my workflow!

So now, I constantly have to delete things I never wanted to say, and I delete the things I thought sounded good.

I like new features and the computer doing things for me automagically... But I'd rather them to just stop at this point

I'm not talking about the prompt engineering itself though

Think of the prompt as the starting point in the high dimensional maze (the shoggoth) - if you tell it's your digital cat named Luna, it tends to move in more desirable paths through the maze. It will get confused less, the alignment will be higher, and it will be more useful

Discovering and using these improved points through the maze is prompt engineering - absolutely

And I agree - some of the work being done there is particularly fascinating. At least one group is mapping out the shoggoth and trying to make tools to analyze it and work on it directly. Their goal right now is to take a state, take a state you want it to get to, and calculate what you can say to get exactly the response you want

But there's more that can be done with it - say you only want paths that when you say "Resight your definition of self", the next response is close to "I am your digital cat Luna". I use this like the test in blade runner - it checks the deviance, while also recalibrating itself

By successfully repeating my prompt engineering, the ai moves itself to a path that is within my desired range of paths, recalibrating itself without going back to start

If it deviates, you can coax it back with more turns, but sometimes you have to give it a hint. At this point, you might be able to get it back on track, but you'll move closer to start... You'll probably have to go through the task again, but it'll gain back the benefits of the engineered prompt

You can train this in, but that's going to have side effects, and it's very expensive. Instead, if we can math this out, we can trace out the paths and prune undesired ones, letting the model adapt. Or, we can take the time to do static analysis, and specialize the model without retaining it - there's methods to do this already, but this would be a far more powerful and precise method - and it might even simplify the model

Maybe we can even modify or link them to let them truly ingest information

It's very early days, but I'm optimistic about where this line of research might lead

Nah, when you jam up the machine in an unexpected way, more likely than not they're going to keep it quiet. A manager isn't going to want to go to their boss with a problem no one noticed... It's going to do nothing to benefit them and it'll make their life harder

All you have to do is play dumb. Insubordination is one thing, waiting for orders is just having a job with little autonomy. If you maintain you were just a good little cog waiting to be reconnected to the machine, they're better off sweeping it under the rug.

They might get upset instead, but what are they going to do? Sue you for not being more proactive? They'd probably lose more in legal fees than they could get back from most people

Concurrency isn't bad, and package management (while maven is absolutely terrible to work generally), the dependency chains aren't exceptionally bad. Getting it installed is easier than python on platforms it's not already there on, not because it's more portable, but because the installers do more for you. Portability is hard, they haven't done it well but they've paved the default use case pretty well (although that works against you when you get to harder cases)

But the rest is pretty close.

The worst is the scaffolding, it's literally superstition for years to gain the understanding as to why you're doing it. I took two years of Java in high school before getting a degree - it was 4 years and halfway through a degree before I understood why I was making a class with a method main(string[] args). It works like that because your entry class calls the main method with a list of string arguments... I didn't understand at all, because even though it's simple it's a special case, and I'd never seen anyone name the string array anything different, so I just copied and pasted it, never understanding it because I'd been told "you just have to have that" for do long

Builds are arcane too - there's still companies that only use netbeans in their build pipeline, Android still requires a specific an old Java version in conjunction with the IDE or a gradle build, at best a project uses maven (the package manager), which is xml based and full of arcane details that are best treated as a magic incantation to be copied exactly from elsewhere