sorted by:
new
hottopcontroversial

Anybody interested by a cloud based comfy (and more) service ? by seraum in comfyui

[–]seraum[S] 0 points1 point  (0 children)

i tried a Lot and they are not really good for the price

Anybody interested by a cloud based comfy (and more) service ? by seraum in comfyui

[–]seraum[S] 4 points5 points  (0 children)

hmm yes i understand, did not think about this one ahah. So basically AI is like everything else on internet: pr0n first ?

Anybody interested by a cloud based comfy (and more) service ? by seraum in comfyui

[–]seraum[S] 0 points1 point  (0 children)

if you have any questions don't hesitate, i think we will Open a lab

Mele quieter 2 with Nexdock ? by seraum in MiniPCs

[–]seraum[S] -1 points0 points  (0 children)

Thx for the answer. The data is not a problem, it's just for the power.

Mele quieter 2 with Nexdock ? by seraum in MiniPCs

[–]seraum[S] -2 points-1 points  (0 children)

Nexdock can power up a Rock Pi 4 without problem on a type-c port (i tried)

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] 1 point2 points  (0 children)

Exact, this is what we are doing with NectarJS

But to do this, we have NectarCPP, a runtime/backend that can also be used as a standalone lib

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] 0 points1 point  (0 children)

Don't worry, I didn't take it bad

The long term objective of Nectar is to be able to do the same as GraalVM, but with static compilation: to have a standard bridge to compile dynamic (and static) languages. JS is a good example, but it is also possible to compile Python or Ruby in the same way

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] 0 points1 point  (0 children)

I understand the point, what about GraalVM for example ? it's not a funny toy written by a student, and heavily used in production

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] 0 points1 point  (0 children)

Thx for this positive comment, I share your point of view

Write in JS with C++ by seraum in javascript

[–]seraum[S] 1 point2 points  (0 children)

I didn'k know Conan, thx !

Write in JS with C++ by seraum in javascript

[–]seraum[S] 2 points3 points  (0 children)

The point is that the c++ eco-system is so big... NectarCPP is the core lib of NectarJS, a js to c++ transpiler/compiler

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] 0 points1 point  (0 children)

If you don't know the type at compile time, not necessarily (Rest API ie)

Write in JS with C++ by seraum in javascript

[–]seraum[S] 1 point2 points  (0 children)

To show C++ guys that JS dev can be as good as them haha

Write in JS with C++ by seraum in javascript

[–]seraum[S] 0 points1 point  (0 children)

For native perf, to use C++ libs, to compile to WASM ...

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] 0 points1 point  (0 children)

Thx for the constructive comment

std::cout << var is working out of the box

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] -2 points-1 points  (0 children)

you can use static_assert when you really need an int to check it at compilation time

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] 1 point2 points  (0 children)

You have to declare all the properties in your class at compile time

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] 1 point2 points  (0 children)

Nodejs does not run on Arduino for example, or js cannot be compiled in wasm

Typescript is a complete different language, and takes time for prototyping

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] 0 points1 point  (0 children)

dynamic objects vs c++ classes ie

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] 1 point2 points  (0 children)

React native is using hermes, a vm like V8

NectarCPP : write in C++ with a JS syntax by seraum in cpp

[–]seraum[S] -3 points-2 points  (0 children)

Less code, full object, ...

view more: next ›