aulin

Isn't GaN already the base for blue led and for all current white-ish led lighting?

Here they are somehow eliminating the need for phosphors for color conversion but they didn't say how.

I mean, if GaN is a problem we are already in a bad shape.

How about port that is lowercase in ssh and uppercase in scp?

Dear OpenAI, the target audience of your blog or at least of this blog post understands English pretty well. Why won't you give them a simple way to disable the shitty ai translation and read the original content? Why translate it at all in the first place?

EDIT: found the button, all the way down in the bottom of the page... I hate this so much, give me the original content, I will decide if and when I need translation

Leave my consecutive short sentences alone. And jetbrains mono.

If you can't clone it it's not a repo

After you see it skip reasoning so many times and saying "actually the simplest fix is" the laziest thing ever you get kind of tired of babysitting it.

Not familiar with jj and don't want to get into bike shedding, but how is describe supposed to be a good name for history rewrites?

So far they did not change it, and none of this applies to business and enterprise accounts. My idea is that it can still be viable as most businesses will have plenty minimally used licenses with just a few power users abusing the request model.

Well that was probably the most important general skill even before this.

Opus 4.6 also just got dumber. It's dismissive, hand-wavy, jumps to conclusions way too quickly, skips reasoning... Bubble is going to burst, either some big breakthrough comes up or we are going to see a very fast enshittificafion.

They won't. These are not "issues", it's them trying to push the models to burn less compute. It will only get worse.

What did poor copilot do now?

> I need to try the command line version.

Is there any other?

GH Copilot is still the best deal, while it lasts

Admit I didn't follow the announcements but isn't that a matter of UI? Doesn't seem something that should be baked in the model but in the tooling around it and the instructions you give them. E.g. I've been playing with with GitHub copilot CLI (that despite the bad fame is absolutely amazing) and the same model completely changes its behavior with the prompt. You can have it answer a question promptly or send it on a multi-hour multi-agent exploration writing detailed specs with a single prompt. Or you can have it stop midway for clarification. It all depends on the instructions. Also this is particularly interesting with GitHub billing model as each prompt counts 1 request no matter how many tokens it burns.

If you are on a us ansi keyboard and switch to a iso layout (most European layouts are iso) you have I believe two unreachable keys. And the arrangement of the others is slightly different you will have to adapt your muscle memory anyway.

Altgr-intl is pretty good for when you code and write English most of the time and occasionally need accented letters. If you need to write a lot in your native language it's better to get a local layout keyboard.

Seems to me the most expectations they had with the library was about the compression stuff and it did not include that. So in the end it was mostly rev eng. Also in this specific case you are using the library code as documentation about the hardware, the code itself has little value. I doubt it would configure as license violation.

They don't get as hot when parked under the sun though.

I am not wrong. You simply are not the kind of developer I am thinking about. And believe me the other kind is way more represented.

In my every day experience that's pretty risky. The periphery as you call it is often an area where you lack the expertise to spot and correct AI mistakes.

I am thinking about build systems and shell scripts. I see people everyday going to AI before even looking at the docs and invariably failing with non-existent command line options, or worst options that break things in very subtle ways.

Same people that when you tell them why don't you read the f-ing man page they go to google to look it up instead of opening a terminal.

Same people that push through an unknown problem by trial and error instead of reading the docs first. But now they have this dumb counselor that steers them in the wrong direction most of the time and the whole process is even more error prone.

I use pihole for dhcp and it's extremely easy with dnsmasq. Hope their settings overhaul does not break this.

dhcp-option=tag:nospam,option:dns-server,x.x.x.x dhcp-option=tag:spam,option:dns-server,y.y.y.y dhcp-host=client1...,set:nospam dhcp-host=client2...,set:spam

Self-esteem that easily turns into hubris though. I think the real seniority shows when you are able to work on a legacy codebase full of the shittiest code and not have the slightest desire to rewrite it all.

Also when the issue is a bug the information you'll find in the tracker is usually about the symptoms and says nothing about the fix.

I prefer email. I'd really prefer if people read what I write though. The big problem with email is people can't read.

No experience with slack but channels in teams are pretty terrible.

Notifications off by default so people create new channels with you as a member, write extremely important information inside them and you find out weeks later.

Each post is like an announcement so nobody uses them for the everyday trivial stuff you need a channel for. For casual technical discussion, asking for help. Whenever you post in a channel, assuming people enabled notifications and your post will be actually seen, everyone is compelled to answer as the UI screams for attention.

And don't get me started about it hiding part of a post by default so you answer thinking you read everything but you missed an essential part because post was 4 rows and 2 were hidden.

you don't have the time because you spend it bruteforcing solutions by trial and error instead of reading the manual and doing them right the first time

Yes I've had plenty of experiences with orgs that self host everything, I don't think it's a minority it's just a different cluster than the one most represented here.

Still I believe hosting is somewhat different, if anything because it's something established, known players, trusted practices. AI is new, contracts are still getting refined, players are still making their name, companies are moving fast and I doubt data protection is their priority.

I may be wrong but I think it's reasonable for IT departments to be at least prudent towards these frameworks. Search is ok, chat is okish, crawling whole projects for autocompletion I'd be more careful.

This subthread started with someone from a no AI policy company, people are dismissing it with snarky comments, along the line of your code is not as important as you believe. I'm just trying to show a different picture, we work in a pretty vast field and people commenting here don't necessarily represent a valid sample.

Those are risks both for the individual and for the company when there are contracts in place with third parties involving code sharing.

Other risks include leaking industrial secrets that may significantly damage company business or benefit competitors.

> Thought exercise: what would seriously happen if you did let some of your proprietary code outside your network

Lawsuits? Lawful terminations? Financial damages?