Live data from Hacker News

Microsoft Clipchamp

clipchamp.com

121–130 of 136 posts

Re: Microsoft Clipchamp

#122
post #68

Earlier quoted context omitted.

Of course it will, so the question becomes "why drive away Firefox when it works fine"?

Quoted post unavailable.

With or without sarcasm, your comment adds little to the conversation, and encourages flaming - that is why it is being downvoted.

Re: Microsoft Clipchamp

#123

Earlier quoted context omitted.

What, exactly, is making the website work fine on Chrome/Edge but not on Firefox? Are you using some bleeding-edge API that isn't available in Firefox yet?

In my experience it's simply developer resources. In my entire career, I've never seen a complex web app "just work" across multiple browsers without some, if not a lot of, effort. Testing on all browsers all the time is a significant cost to velocity. It almost always makes more sense to build for a single browser first, then figure out where the comparability issues are once you have an actual product.

> It almost always makes more sense to build for a single browser first, then figure out where the comparability issues are once you have an actual product.

I agree, and most places I've worked with has been the same. But I think only once, after following that process, have we ended up in "Damn, this works 100% in Chrome but is completely broken in Firefox". Sometimes something works faster/slower in Chrome/Firefox, but without requiring something like the Web MIDI API, most things just works the same across browsers, minus some minor things regarding CSS that has to be taken into consideration.

I guess what I'm looking for with my previous comment, is not so much of a general/philosophical answer of "Why you block Firefox but not Chrome?" but rather a specific answer to "What ended up being broken in Firefox but working in Chrome?"

Mostly helpful for my own curiosity, but in the strange case of finding things that works in Chrome but not Firefox, leaving a report at https://webcompat.com/ can be very helpful for the general health of the web as well.

Re: Microsoft Clipchamp

#124

I used this software (the app version) a couple weeks ago for the first time. I grabbed a great clip while playing a game and wanted to show it to a friend, but I didn't want to send the full 500MB 60s video when the clip was only ~6 seconds. I didn't want to spend a ton of time downloading proper editing software so I gave it a shot. It's a little clunky if I'm honest, it feels like an evolution of Windows Movie Mak…

LosslessCut is my go to for that sort of thing

https://github.com/mifi/lossless-cut

Re: Microsoft Clipchamp

#125
post #65

Firefox users are asked to please stay away: It looks like your browser is not supported To use Clipchamp, make sure you're using the latest version of Google Chrome, or the latest Microsoft Edge

Using Firefox with the user agent changed to chrome seems to get around this

I recall that the advice given to web developers for a long time was to query browser capabilities instead of relying on a user agent string. If this site is indeed relying on the user agent string, I don’t get why larger companies which probably have better capable teams resort to this.

Re: Microsoft Clipchamp

#126

Earlier quoted context omitted.

Is clippy necessarily evil? I mean we have the floating action button in some apps, clippy just provided FAB like functionality with some personality. Then again, the FAB is pretty horrendous too most of the time, so maybe it's not the best way. But I think in some very limited cases it could be a good way to provide shortcuts that bypass huge stacks of menus. Modern apps have gone in a more lightweight direction tho…

When people call Clippy evil, it's not because of his role as an assistant for Microsoft products. Rather, they're referring to his later actions in running several cryptocurrency pump and dump schemes. It was really a tragic fall.

Well, desperation can drive people to all kinds or things, especially if they are ignorant of the consequences.

If he still had a job, and had better AI, perhaps he wouldn't have turned to crime?

Re: Microsoft Clipchamp

#127

Earlier quoted context omitted.

In my experience it's simply developer resources. In my entire career, I've never seen a complex web app "just work" across multiple browsers without some, if not a lot of, effort. Testing on all browsers all the time is a significant cost to velocity. It almost always makes more sense to build for a single browser first, then figure out where the comparability issues are once you have an actual product.

> It almost always makes more sense to build for a single browser first, then figure out where the comparability issues are once you have an actual product. I agree, and most places I've worked with has been the same. But I think only once, after following that process, have we ended up in "Damn, this works 100% in Chrome but is completely broken in Firefox". Sometimes something works faster/slower in Chrome/Firefox,…

In my experience it's subtle bugs that don't appear on one platform but do in the other. webcompat is great for true deviations from the spec but there are plenty of cases where things work for no good reason and it's a chore to figure out why.

I'm also a bit curious why blocking Firefox is preferred versus stating which browsers are supported.

Re: Microsoft Clipchamp

#128

Earlier quoted context omitted.

Hi! Engineer who actually works on Clipchamp. Sorry you ran into that issue. Firefox support is in the works - we plan to support the same set of browsers as the other Office features, as described here: https://support.microsoft.com/en-us/office/which-browsers-wo... If this tech looks interesting, come join us! We have a bunch of open engineering positions in Brisbane that are 100% WFH from Australia: https://career…

What, exactly, is making the website work fine on Chrome/Edge but not on Firefox? Are you using some bleeding-edge API that isn't available in Firefox yet?

https://caniuse.com/?search=worker%20module

This is something I just personally bumped into in switching from webpack to vite (svelte app).

Not often that FF is the problem. Usually it's Safari but that is becoming less common.

I think I can work attend it, we'll see next week.

Re: Microsoft Clipchamp

#130
post #111
post #88

Earlier quoted context omitted.

Virtualdub

Now that’s a name I’ve not heard in a long time. Is it still under development? Back in my teens I was really wanting to get into 3D animation and virtualdub was one of the first tools I used to create reels since the free modeling and rigging tool I used at the time didn’t have any editing capabilities.

It seems that not very much, but this is a lot of the case of finished software: it's good for its job. The author is not gone though, there is a blog post from a year ago.
Post reply on HN