I’m wondering if HDR means something different to me, because I see HDR images all the time. I can share HDR images via phones (this seems to be the default behavior on iPhone/Mac messages), I can see HDR PNG stills on the web (https://github.com/swankjesse/hdr-emojis), I can see wide gamut P3 images on the web as well (https://webkit.org/blog-files/color-gamut/).
Sure, me too! I can take a HDR P3 gamut picture with my iPhone and share it with all my friends and relatives... that have iPhones.
What I cannot do is take a picture with a $4000 Nikon DSLR and share it in the same way... unless I also buy a Mac so I can encode it in the magic Apple-only format[1] that works... for Mac and IOS users. I have a Windows PC. Linux users are similarly out in the cold.
This situation so incredibly bad that I can pop the SD card of my camera into an reader plugged into my iPhone, process the RAW image on the iPhone with the Lightroom iPhone app in full, glorious HDR... and then be unable to export the HDR image onto the same device for viewing because oh-my-fucking-god-why!?
[1] They claim it is a standards-compliant HEIF file. No, it isn't. That's a filthy lie. My camera produces a HDR HEIF file natively, in-body. Everything opens it just fine, except all Apple ecosystem devices. I suspect the only way to get Apple to budge is to sue them for false advertising. But... sigh... they'll just change their marketing to remove "HEIF" and move on.
Sure, but Apple doesn't fully support HEIC either.
They support only a very specific subset of it, in a particular combination.
Some Apple apps can open third-party HEIC-in-HEIF files, and even display the image correctly, but if you try anything more "complex", it'll start failing. Simply forwarding the image to someone else will result in thumbnails looking weirdly corrupted, brightness shifting, etc...
I've even seen outright crashes, hangs, visible memory corruption, etc...
I bet there's at least one exploitable security vulnerability in this code!
It probably depends on the codebase, but I find the best motivation for writing solid commit messages is reading commit messages. Tools like gitlens make this really easy.
Almost daily, I use commit messages and history as part of understanding why a decision was made, why a seemingly obvious alternative wasn’t chosen, etc. seeing the commit title on every line, and hovering to see the full message has become a core editor feature for me.
It’s kind of like testing, the more I do it, the more I want to do it because the value is so consistently reinforced.
There’s nothing like being able to track down exactly why a decision was made 6 years ago in a part of the code base you are struggling to understand written by someone who left before you joined the team.
10,000% this. Attaching JIRA tickets, etc. to the commit helps for searching as well. I've worked with a number of people who do not believe in this and it drives me insane ; I try to enforce it, but there's a lot of messages like "fixed bug" that have zero context or detail associated with them.
I don't understand why so many engineers are like this.
Attaching JIRA issues makes a ton of sense for features that are described in JIRA. If we're talking about a bug that was found by a developer, unmotivated by a ticket, it would generally make more sense to just describe the bug directly in the commit message. This is of course not true if the JIRA tickets are used for something else downstream, like informing users of fixed bugs, or tracking changes.
The other issue with tagging JIRA tickets is that junior developers will believe that to be enough (you can just read the ticket) and wont understand why they need to describe the change from a technical angle, when it's already described in JIRA.
Commit messages are immutable. Linking them to a bug ticket gives you a mutable place to record any new information about the bug that you discover in the future. (For example, that it affected more cases than you originally thought, or that the fix caused another bug.) This new information will be discoverable when starting from the original commit (found e.g. by doing a blame on a particular line of source).
To fail to do so is a gigantic missed opportunity in my opinion. You never know when you will need it.
Attaching ticket numbers has always been enforced by automated checks wherever I have worked, so it is not necessary to “try” to enforce it.
Similarly with AI it is fairly simple to have eg a pre-merge check that validates the commit msg is somewhat useful. This could be implemented for example with GitHub org level checks that must run in a PR.
> If you're big enough that we'd be screwed without you then take whatever risks you like with impunity".
I know financially it will be bad because number not go up and number need go up.
But do we actually depend on generative/agentic AI at all in meaningful ways? I’m pretty sure all LLMs could be Thanos snapped away and there would be near zero material impact. If the studies are at all reliable all the programmers will be more efficient. Maybe we’d be better off because there wouldn’t be so much AI slop.
It is very far from clear that there is any real value being extracted from this technology.
The government should let it burn.
Edit: I forgot about “country girls make do”. Maybe gen AI is a critical pillar of the economy after all.
> I’m pretty sure all LLMs could be Thanos snapped away and there would be near zero material impact.
I mostly agree, but I don't think it's the model developers that would get bailed out. OpenAI & Anthropic can fail, and should be let to fail if it comes to that.
Nvidia is the one that would get bailed out. As would Microsoft, if it came to that.
I also think they should be let to fail, but there's no way the US GOV ever allows them to.
> Nvidia is the one that would get bailed out. As would Microsoft, if it came to that.
> I also think they should be let to fail, but there's no way the US GOV ever allows them to.
There's different ways to fail, though: liquidation, and a reorganization that wipes out the shareholders.
OpenAI could be liquidated and all its technology thrown in to the trash, and I wouldn't shed a tear, but Microsoft makes (some) stuff (cough, Windows) that has too much stuff dependent on it to go away. The shareholders can eat it (though I think broad-based index funds should get priority over all other shareholders in a bankruptcy).
Why would Nvidia need bail out? They have 10 billion debt and 60 billion of cash... Or is it finally throwing any trust in the market and just propping up valuations? Which will lead to inevitable doom.
I expect the downvotes to come from this as they always seem to do these days, but I know from my personal experience that there is value in these agents.
Not so much for the work I do for my company, but having these agents has been a fairly huge boon in some specific ways personally:
- search replacement (beats google almost all of the time)
- having code-capable agents means my pet projects are getting along a lot more than they used to. I check in with them in moments of free time and give them large projects to tackle that will take a while (I've found that having them do these in Rust works best, because it has the most guardrails)
- it's been infinitely useful to be able to ask questions when I don't know enough to know what terms to search for. I have a number of meatspace projects that I didn't know enough about to ask the right questions, and having LLMs has unblocked those 100% of the time.
Economic value? I won't make an assessment. Value to me (and I'm sure others)? Definitely would miss them if they disappeared tomorrow. I should note that given the state of things (large AI companies with the same shareholder problems as MAANG) I do worry that those use cases will disappear as advertising and other monetizing influences make their way in.
Slop is indeed a huge problem. Perhaps you're right that it's a net negative overall, but I don't think it's accurate to say there's not any value to be had.
I'm glad you had positive experiences using this specific technology.
Personally, I had the exact opposite experience: Wrong, deceitful responses, hallucinations, arbitrary pointless changes to code...
It's like that one junior I requested to be removed from the team after they peed in the codebase one too many times.
On the slop i have 2 sentiments: Lots of slop = higher demand for my skills to clean it up. But also lots of slop = worse software on probably most things, impacting not just me, but also friends, family and the rest of humanity. At least it's not only a downside :/
Depends on the doctor. My doctor at One Medical proactively ordered an ApoB test just to be safe after I successfully got my LDL in check through diet and exercise.
Let’s be honest. It’s a mess targeting iOS. It’s like the old days with VB - first 80% done in no time, last 20% takes forever, requiring ever more elaborate hacks to get around stupid restrictions (eg try hiding the keyboard associated with a TextField when you tap on a Picker).
Plenty of cities have good access to nature and green spaces.
I grew up in “nature” (aka a forest that emerged from not working farmland iykyk) and every ride to school, the grocery store, a friend’s house, or heaven forbid medical care or a restaurant visit involved 30-45 minutes of driving. That sucks.
Also, the concentration of a place can allow for not using land elsewhere, making overall access to nature a lot easier.
From Seattle there are three national parks within an hour or two drive, because the planning laws were put in place to prevent suburbia up to the foothills of the parks.
Be on the look out, I had really bad semaglutide side effects and had to stop. Thought microdosing would help, but the side effects just ramped up more slowly, culminating in what I assume was gastroparesis (my food just stopped digesting for over a day and I couldn’t eat despite being hungry and depleted, not to speak of the rest of the digestive process).
I also had drastically degraded (increased) resting heart rate, (decreased) heart rate variability, and exercise intolerance - a normal easy run started to make it feel like my heart would explode and gave me palpitations. Off it, I can run a 5K and beyond no problem, if my knees cooperate.
Food noise came into the picture much worse than baseline after I stopped, although it did eventually come down and I’ve been able to start losing weight again after a few months off. Berberine seems to help, at the expense of giving me nausea like semaglutide, but no other side effects.
I also have this. I haven’t tried with cars, but the ANC seems to really amplify some deep bass sounds from the environment. To the point I hear things I wouldn’t ever notice before (e.g. different states of my air conditioner).
The problem is it comes through as an extremely loud rumble, usually in only one ear at a time.
Not a high pitched squeal, but a low pitched rumble. Goes away if I remove and reinsert, but immediately comes back in short order.
I can make it go away but only by using tips that don’t fit as well, and therefore don’t reduce noise as well (and also fall out of my ears while running).
What am I missing?
reply