JavaCV VS dotty

I'm using https://github.com/bytedeco/javacv/ and trying to set a little server up where I can view the livestream of a camera through the server. I want to try to make a little security camera type project with a raspberry pi. (I know that the library might not work on the pi, but one thing at a time.) If I can get the server working with livestreaming, then I believe I can change any camera library I might end up using.

How is it different from JavaCV?

I'm attempting to make a simple video converter app in Java using JavaCV, i downloaded the Jar files and put them into my repo. this is my current folder structure all of the Jar files are inside the 'libs' folder.

JavaCV to generate the complete mp4 from the rendered frames

I like Java, but if I was doing a pure OpenCV project I would do Python or C++. Anyways, I think looking at examples is the best way to learn. If you use the JavaCV wrapper there are plenty of examples over here https://github.com/bytedeco/javacv/tree/master/samples

Just checking my code. I ended up using this: https://github.com/bytedeco/javacv. Specifically the javacv-platform library: http://bytedeco.org/builds/.

Check this out, this works pefectly inside scala projects so you can do like that: https://github.com/bytedeco/javacv

Dotty? Was it still the name later?

http://dotty.epfl.ch/

I think this might be related to this issue.

You can look (and EPFL collect feedback) about EPFL implementation of async/await: https://github.com/lampepfl/async. Also you can look at dotty ticket about this: https://github.com/lampepfl/dotty/pull/16739

The reason I’m not currently an opaque type user as they do not play well with the tagless final style we use, though I am patiently awaiting some attention on my bug report: https://github.com/lampepfl/dotty/issues/17281

Links: - https://dotty.epfl.ch/ - https://scala-native.org/en/stable/ - https://www.scala-js.org/ - https://typelevel.org/ - https://zio.dev/ - https://github.com/scala-native/scala-native/pull/3120 - https://github.com/lampepfl/dotty/pull/16517 - https://dotty.epfl.ch/docs/reference/experimental/index.html - https://scala-cli.virtuslab.org/ - https://scalameta.org/metals/ - https://docs.scala-lang.org/scala3/guides/migration/compatibility-intro.html - https://www.scala-lang.org/blog/2023/04/18/faster-scalajs-development-with-frontend-tooling.html - https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html

Scala Native has much more control on how the Scala AST is compiled, and can easier workaround platform limitations, eg. lazy vals in Scala 3 required reflection config for Native Image (see this and that), while in Scala Native we could mitigate problems with unsupported usage inside in other ways within the compiler plugin.

By the way, you might be interested in this recent PR which overhauls the scala 3 macro docs: https://github.com/lampepfl/dotty/pull/17060.

For example, this issue (https://github.com/lampepfl/dotty/issues/12840) was blocking the migration, it was reported more than a year ago and the fix was finally released a month ago (https://github.com/lampepfl/dotty/releases/tag/3.3.0-RC2).

For the record, there is an implementation of :javap which is close to being done but might need a volunteer to get it over the finish line: https://github.com/lampepfl/dotty/pull/12210

im glad to tell you that in 3.3.0 a lot of these -Wunused lints will be supported: see https://github.com/lampepfl/dotty/pull/16157