matsemann

It's factually incorrect that gopro hasn't kept up with image quality. One independent comparison I saw for instance put the gp13 in front of the others in most situations except low light. So if anything it's contested who's better/worse, far far from the statement in those videos.

It's factually correct and widely known that lots of tech "reviewers" get paid by the competition to shill products, was a whole scandal even with how Insta360 was caught telling reviewers not to mention their sponsorship. The contracts also often forbid them do do direct comparisons. Also funny how there will be a hundred identical reviews, as they all got the same script.

So, my statement is true. If you've watched a couple of videoes telling you to buy dji/insta360, it's very very likely you've been lied to.

So, ball is in your court.

Agree. Gopro recently released a DaVinci plugin for 360 videoes, which is great. But I often would like something in between the advanced DaVinci and the simple mobile editing. After the release of Max2, the Quik app got a big overhaul and is quite capable now. But it's still mobile, and Gopro Player (for desktop) is then now even further behind on capabilities. Same issue with Insta360 (both mobile and desktop, never tried Dji's apps)

A gopro isn't worse than the competition, nor at a premium.

What makes gopro the standard in proper productions (and science etc) is that they're so hackable with the gopro labs software. With that, all the other cameras are toys in comparison for professional usage.

many YouTubers suggesting outright against GoPro since they haven't kept up with image quality.

Fyi: This is a lie, the youtubers are paid to tell you this.

No, it doesn't. Gopro actually hss gps and sensors built in, most dji cameras don't (does any?). You need extra hardware, or provide the data yourself. While in gopro you just enable it on the clip.

Of courses, for more advanced stuff you might want to provide the telemetry yourself (like the gopro doesn't know your wattage). But it does have much more than dji out of the box.

Eh, I have a Hero 4 black. And if you as the other commenter only think about resolution it can look like that, but the difference is enormous.

4k on a gopro 13 is far far far clearer. And the stabilization is night and day. Half my hero4 videos are mostly blurry shakes and quite jarring to watch, with a bad fov. The stabilization on modern gopros is magical. The bitrate and quality is orders of magnitude better. You can now pull good quality stills from the video if you want. Hero4 can't handle anything but perfect blue sky in the middle of the day. Etc etc

It's mostly FUD and/or paid reviewers. Both DJI and Insta have good products, but also very good at sponsoring in a way where things get reviewed very in their favor, making people have an impression that doesn't quite match reality. So the meme one constantly read online about how gopros are so much worse is false. They have their issues, but mostly trade offs.

My use of AI is correct. My coworkers use is not.

I'm saying it in jest, but it's also a bit true. Not necessarily because we use it any differently. But because my use of AI saves me time. But their use of AI adds more to my plate, no matter if it's slop or not.

Jensen Huang himself says

Not that I disagree, but it doesn't refute the original argument. It could even support it, class protecting their own from more people figuring out there's no clothes on the emperor.

It's said to imply they have no bias. But someone using Codex or AI agents heavily already have a bias here, just to be clear. Because the discussion isn't just about bun/anthropic/zig/rust, but also between AIs role in coding. So them touting their use of Codex, while not Claude, can still be a bias, especially in the direction they're trying to absolve themselves from.

Not sure I agree. Having a complete rewrite like you propose is a huge project, and a very scary flip. And I honestly don't see the value in doing it like that. So now you have the same mess as before, just re-written?

Best I've seen it done is to move module by module. So if you want to do "X", you now have to do it in the new system. And the big part of the rewrite of X is figuring out the specs and making it better along the way. Then people also actually want to move.

This is a game for me. I play lots of scrambled letter games (mainly https://squaredle.app/ every day). Time pressure ruins it for me.

What's the point of the rewrite if it doesn't fix the underlying issues, though?

A rewrite being a good idea often hinges on the ability to simplify. After a decade or more, it's now apparent what the application should and shouldn't do, so one can build it with those learnings and shed all tech debt from how it grew organically.

Aka preserving all behavior is not what I would want from a rewrite. The point would be to make decisions on what behavior should be kept and what complexity can be removed. An AI can't do that. It can help with execution if the decisions are made, but they're made by being very intimate with the codebase and floating all cases and then talking with stakeholders.

Thanks! Did look at it a while back, and currently no instance where I can provide my street views, unfortunately. Hopefully more instances will come soon. And also hope that more mapping apps will use this data, it's a chicken&egg problem I guess.

Panoramax is still unfortunately very lacking outside a French instance. I've tried to contribute my street view images, but it's not used by anyone or anything as far as I can see.

I upload street view pictures to Mapillary, which again can be used to automatically infer info into OSM (like signs etc)

But I feel very few OSM mapping apps use street view / have it as a feature. But for me it's the main feature I use Google Maps for. Like checking road conditions or finding nice places to camp when bikepacking. Which is why I also upload my stuff to Google (cars can't access most of these areas), but I'd prefer open alternatives.

I probably only use 1 % of Astro's features, but I like how it's enabled me to build static sides as back in the days, but with a build pipeline.

So I can use components, reuse stuff, include stuff etc, basically what I would do with PHP back in the days, but now it spits out a compiled page I can host for cheap (often even free). And easy to add in some interactivity when needed. Like I render a list as a component, and very easy to ship some dynamic filtering on the frontend using the same code, but the content is still statically in the html, so served fast and good SEO.

Yeah, yeah, people say that all the time. But it's not the dash itself, it's how it's so stiff and obviously not written by a human. "No screen glow, no keyboard, no chat UI." and other bullshit.

Why should I waste time reading this link, when the "author" themselves didn't write and, probably not even read it themselves.

About (2), it reminds me of a video I saw once of someone trying to take a picture at a sport event, or how my parents try to do it. Hold the phone with an awkward grip to point it towards what you want, with one hand free. Accidentally touch the edge of the screen and click something with the gripping hand. Then try to zoom in with your free hand, but one finger hits the screen first due to the angle of the phone so you do a swipe instead and go to selfie mode. Swipe fervently to get back. Try again, click screen to focus. But just as you click a notification pops up and you press it.

No, tapping something visible and seeing what happens is discoverable. And Apple used to have skeuomorphism to help with affordance. Swiping from various directions and other hidden shortcuts aren't discoverable, and my guess is most users can't find half of the features of their phone.

Yeah, for a decade now it's been a UX disaster. It "works", because so many people are used to it, but look at a new user trying to navigate iOS, it's bonkers. Swiping from random directions achieves different things (and how would you even know you can?). The home button has like 11 different functions depending on how you press it and when.

I tried the same on images of disks in my back. The ai picked a slice not from the middle and used that to say they were too small (since it was looking at a slice towards the edge) and basically told me my life was over and my pain would last forever.

Luckily my disks were fine. Wouldn't trust it. Additionally, an MRI of a pain-free, healthy human still would show lots of things and damage. Unless it coincides with a symptom, it's probably harmless. That's why the history is important when looking at images. Can't just upload something and hope for findings.

No, I know for a fact the cause where I live is the climate, they can now survive where they earlier couldn't. Sure, there may be other reasons other places, but that wasn't what I wrote. I wrote about my town. Why that is so hard for you to grasp is honestly baffling, heh.

There's a difference between "I didn't like their salad" (opinion) and "they don't pay their bills" (a fact, that could be defamation if not true)

It's a fact, though. You got too hung up on altitude, which I guess is just a proxy for temperature when I compare to neighboring towns. Been mentioned on the news etc that more and more towns get disease bearing ticks here, due to conditions for them getting better with global warming. Not sure why hearing a negative effect from global warming triggered you so?

No ticks at the altitude I reside. But with global warming it's slowly creeping up towards the towns further down. Same with Spanish slugs. Will soon be able to thrive here as well.

If anyone feels negative, I recommend seeing a psychologist.

Telling everyone that disagrees with you to see a psychologist is certainly something. The delusions of grandeur may make your statement quite ironic, heh.

Because it could be strategically good to increase their market share and loyalty when everyone else is increasing their prices, for instance? But no, the "fiduciary duty" thing trumps everything, I guess.

Even with plain ASCII we sometime struggle with the various scanners, as they emulate keyboards. So for instance using : in the barcode as a separator of values becomes wonky if the OS has a different input language than expected.

I've never even used it and still I read every changelog posted here. So interesting and good writeups.