janaagaard

Yeah, I get that some prefer it the other way around.

The HTML anchor should have a target="_self_or_blank_depending_on_what_the_user_has_configured" option.

Why all USB-A ports instead of USB-C? (I counted 4 USB-A and just one USB-C.)

I think the links should open in the same window (like they do here on HN) instead of in a new tab/window. If I want a separate tab, I can Cmd+click and Browsers don't have the reverse option for opening in the same window.

What are the rules? Is it okay to use autocomplete? Are spell checkers accepted? What if I used an AI chatbot to figure out something instead of a traditional search engine?

It sounds like the root issue is that some people prefer opening new tabs while others prefer staying in the same browser window. I surfed the web when all links, even across websites always stayed in the same browser window, and I still prefer that. But I can understand that some people prefer opening new browser tabs instead.

I think web browsers should revisit how they handle links with target=_blank/_top, and show different cursers when hovering and let users customize the default behavior.

The iPad would go from a never-buy to a buy-right-away for me, if they added user profiles.

I am crossing my fingers that that Apple's rumored Home Hub will change this.

In total the thickness went down from 7 to 6 pixels, which is a 14% decrease, making it 14% more likely to miss it.

But also a 14% higher chance that you won't hit it by accident.

This is not a situation where bigger is simply better. If the thickness was 50 pixels, that would make it pretty much impossible to not resize the windows. I am one of those who believe that there are still people at Apple who care deeply about user interfaces. Given the amount of attention paid to the regions for resizing by dragging the corner, I actually assume that they also took a second look a dragging the edges, and concluded that 6 pixels was better than 7.

SO peaked long, long before LLMs came along. My personal experience is that GitHub issues took over.

You can clearly see the introduction of ChatGPT in late 2022. That was the final nail in the coffin.

I am still really glad that Stack Overflow saved us from experts-exchange.com - or “the hyphen site” as it is sometimes referred to.

Lately, I see a lot of drivers who turn on their brights and just leave them on and this includes cars with the older halogen and even incandescents. This is a change in behavior.

I suspect this is because more and more people don’t know how to turn it off and/or don’t know what the blue indicator on the dashboard means.

As you mention, Tesla model 3 seems to be the worst offender. Could this be caused by a bad interface in that car? How does the brights indicator look in a model 3 and you turn off the brights?

Kudos on making Bash readable.

(https://github.com/AnandChowdhary/continuous-claude/blob/mai...)

Same here - on a 12 Mini. My wife and my mother have the same phone, and I have recommended that they hold back on upgrading.

I really hope Apple will address this in a dot-upgrade later this year, but I am afraid that the market share of the 12 and 13 models are too low for them to justify this.

but now Apple has essentially decided that this Liquid Glass will be mandatory after a year of support for "compatibility mode" that disables it for your app.

What exactly does this mean? Are there references in Apples design guide lines that explain this in more details? (Or wherever this would be documented)

I want this for YouTube.

And depending how you drive you might not use friction brakes at all.

I’ve been told that should remember to use your friction brakes once in a while, to keep them in shape. Is this still true with cars that have effective engine brakes?

As I understand it, the brilliant idea is that the small variantions in brightness of the pixels look just like standard noise. Distinguishing the actual noise from the algorithm is not possible, but it is still possible to verify that the 'noise' has the correct pattern.

A Danish audio newspaper host / podcaster had the exact apposite conclusion when he used ChatGPT to write the manuscript for one his episodes. He ended up spending as much time as he usually does because he had to fact check everything that the LLM came up with. Spoiler: It made up a lot of stuff despite it being very clear in the prompt, that it should not do so. To him, it was the most fun part, that is writing the manuscript, that the chatbot could help him with. His conclusion about artificial intelligence was this:

“We thought we were getting an accountant, but we got a poet.”

Frederik Kulager: Jeg fik ChatGPT til at skrive dette afsnit, og testede, om min chefredaktør ville opdage det. https://open.spotify.com/episode/22HBze1k55lFnnsLtRlEu1?si=h...

- "4.4% of all the energy in the US now goes toward data centers"

- "by 2028 [...] AI alone could consume as much electricity annually as 22% of all US households."

What would the 22% be if compared against all US energy instead of just all US household?

The React example feels dishonest because it could be a lot simpler:

- All the imports are only needed because a UI library was used. This is not necessary.

- It also looks like 'User' is imported, but not used anywhere.

- The curly braces and the return statement can be left out.

- React.FC<> is unnecessary, you can just specify the type after {users} or, at least, simplify React.FC to FC.

I was also confused. It looks like the article has been corrected, and now uses the familiar 'o3' name.

I really hope Europe seizes this as an opportunity to start pushing public money, public code.

https://publiccode.eu/en/

After using Prettier to format my code and turning on format-on-save, I pretty much don’t use the tab key anymore. This doesn’t invalidate your point, - I am merely guessing as to why the tab key seemingly has been reassigned.

These charts should be on a log scale.

Their time line UI was really good: Go back in time to see emails and texts. Go forward in time to see upcoming events and weather info.

I was never in doubt about was button to press. I have had my Apple Watch for many years now, but still fumble around with basic stuff like turning on the torch light.

You could select what apps you want to also trigger notifications on the watch. And easily pause notifications for an hour or for the rest of the day.

If your kid is having troubles leaning to ride a bike, I would suggest trying one of the bikes from Woom (https://woom.com/). Especially in the smallest models for 4-5 year olds, these bikes much lighter - almost half weight - than a lot of the alternatives. They also cost a lot more, but the high resell value makes up for some of this.

They also have balance bikes.

Bluesky. A lot of the devs that I followed on X have moved to that platform.

Yeah, I agree that StackOverflow it but a shadow of what it used to be, and that this is a shame. But I don’t think that AI is to blame for this - all the interesting discussions had already migrated to GitHub issues. AI is just the nail in the coffin for SO.

I also could not figure out the difference between FTWA and Safari's "Add to Dock..."? Is FTWA an equivalent meant for other platforms like Windows?

This is so lost in Agile.

My personal experience is that you have to blame the people and not the method.

I would define my current project as very agile in the sense that we only have details plan for what to do a week ahead at the time. Each week the team has an hour long meeting where we present what we have done, and discuss if it's good enough. If something like a hover region is found to be wrong it will get fixed for next week. If you find this issue while working on something else, you make task and PR and just fix these smalls things. I feel like this way of working is what what meant by the people who invented the idea of making software development agile.

I agree. The best interview experience that I had was to be sat in front of a small app that had lots issues, both big and small, and also a lot an not-really-issues-but-still like inconsistent code styles and names, and code comments and code that weren't aligned. This was a great starting point for both me and the interviewer. The interviewer had a list of things to ask into about the code, so that we didn't get stuck.

I believe 'var' was introduced in C# to make it much easier to work with LINQ, where you can easily return a subset of properties - without var you would have had to declare interfaces. I think ReSharper is responsible for the rapid proliferation of using var everywhere.