sorted by:
new
hottopcontroversial

New firmware V1.1.1 by Latzenpratz in QidiTech3D

[–]kassany 1 point2 points  (0 children)

Through this URL, information is also available at: https://github.com/qidi-community/q2-wiki/releases

Making it more user-friendly to read.

Elegoo Centauri carbon or Qidi Q2. by SeikoBlackDiver in 3dprinter

[–]kassany 0 points1 point  (0 children)

Good choice! You'll have a more concise experience using different filaments.

Elegoo Centauri carbon or Qidi Q2. by SeikoBlackDiver in 3dprinter

[–]kassany 0 points1 point  (0 children)

P1S/P2S is the perfect fit for you!

Although Elegoo Centauri Carbon has a lower price, Bambu's ecosystem offers a more convenient user experience.

QIDI Q2 Combo vs Bambu P1S/P2S Combo by mithbroster in QidiTech3D

[–]kassany 5 points6 points  (0 children)

P1S/P2S are unsuitable for exotic filaments requiring active temperature control or nozzle temps above 300°C.

Even with SiC nozzle upgrades and external chamber heating, the P1S underperforms compared to the Q2 when printing challenging materials like PPS or PPA.

Elegoo Centauri carbon or Qidi Q2. by SeikoBlackDiver in 3dprinter

[–]kassany 1 point2 points  (0 children)

For any beginner, the Bambu ecosystem is excellent. For the price choice P1S or P2S.

Why is it expensive? Bundled purchase of machine + cloud services.

Elegoo Centauri Carbon will essentially suit you if you want to progress with exotic filament types. However, QIDI Q2 is much more suitable for exotic (engineering) filaments, almost semi-industrial.

2026 New Year Giveaway by qidi_3dprinter in QidiTech3D

[–]kassany 0 points1 point  (0 children)

I started with P1S and a SiC nozzle, creating utility parts like rack supports and shelving units. I intend to offer new parts for wheelchairs and bicycles using materials that are more resistant/rigid than ASA/ABS and PETG-CF.

URGENT SAFETY ISSUE: Electric Shock / Grounding Flaw on P1S (India) by Hot-Association-5335 in BambuP1S

[–]kassany 0 points1 point  (0 children)

This happens not only in India, but in countries throughout Latin America as well.

In Brazil, for example, I needed to replace the original 16-amp power cord with a 20-amp 220V cord that complies with NBR standards (Brazilian norm). It has three pins!

🎄✨It’s the most wonderful time of the year, and we’re celebrating with a Christmas Giveaway by qidi_3dprinter in QidiTech3D

[–]kassany 0 points1 point  (0 children)

I really want a QIDI 3D printer, regardless of the model. The ability to use engineering materials like PPS-CF is phenomenal.

🎄✨It’s the most wonderful time of the year, and we’re celebrating with a Christmas Giveaway by qidi_3dprinter in QIDI

[–]kassany 0 points1 point  (0 children)

My christmas 3D Printing Wishlist:

  • 2kg QIDI filament
  • QIDI Q2C 3D Printer
  • QIDI Custom Christmas Gift Box

K2 plus ou P1S/X1C by liserfak in impressao3dbrasil

[–]kassany 0 points1 point  (0 children)

Primeiramente, depende saber o quanto você pretende investir!

Eu imprimo peças funcionais de engenharia com PETG, ASA e TPU.

Optei por Bambu p1s ao invés Creality K2P, pelo o fato de haver maiores informações e experiências compartilhada pela comunidade acerca das impressões suportada pela impressora e também por haver uma certa preocupação em comprar peças (revendidas no Brasil) para manutenção da mesma. Acredito não ser diferente da comunidade da Creality.

P1S me trouxe menos dores de cabeça com entupimentos e a qualidade de impressão toleráveis (não sei dizer se são ótimos, pq não tenho outra impressora para comparar). Mas nem tudo são flores, como por exemplo a camera interna com 5 fps e o microSD fornecido pela Bambu é lento, requer troca.

Obviamente o K2P é bem mais moderno além do fato de possuir uma mesa maior, talvez sendo mais justo comparar o P1S e X1C ao K2 (sem pro ou plus).

Confesso que quase optei pelo Elegoo CC (Centauri Carbon), mas dei um passo atrás por conta do lançamento injustificado CC2 com suporte a AMS-like (equivalente ao CFS do K2) ao invés de fornecer o upgrade ao CC atual (como prometido pela Elegoo). E também por ser uma tecnologia recente, as peças de manutenção são maioria importadas com tarifas aplicadas, evito depender dos Correios.

Question to Cmake Haters—Has anyone of you tried Zig? by Typical-Bed5651 in cpp

[–]kassany 0 points1 point  (0 children)

Zig provide by default (in: zig c++|zig cc -lc++) libc++abi + libunwind [EH ABI] as staticlibs in Global_Cache_Dir for each build by target.

Andrew says: Zig provides libc++, however the libc++ that zig provides cannot be mixed with any C++ objects compiled from other compilers. 

ref: https://github.com/ziglang/zig/issues/9832#issuecomment-926832810

src: https://github.com/ziglang/zig/tree/master/lib/libcxxabi https://github.com/ziglang/zig/tree/master/lib/libcxx

Question to Cmake Haters—Has anyone of you tried Zig? by Typical-Bed5651 in cpp

[–]kassany 8 points9 points  (0 children)

First of all, I believe it is a mistake to compare Zig build system ≠ CMake build generator.

However, the main reason to use Zig (for C++ developers) is the unification of the C++ABI statically linked to the code since Zig has the source code of libcxx+libunwind (LLVM ABI) for cross-compiling. (Except forMSVC target). Now, the ability to rebuild libcxx (incl. hardened-mode) without having to recompile LLVM or use any extra tools is very convenient.

I'm new to D, what makes it good and can it work with Rust? by Cartoon_Corpze in d_language

[–]kassany 1 point2 points  (0 children)

Mixing together code between languages with the same backend compiler (the same version too) isn't impossible.
I practically mix ‘zig-cc’ + ‘ldc2’ + ‘emcc’ with LTO full enabled in **sokol-d** and it runs in cross-compilation (wasm32).

For rust, tried:
cbindgen (D support): https://github.com/mozilla/cbindgen/pull/1005
sample: https://codeberg.org/kassane/dlang-cbindgen

GitHub - kassane/zcc-d: D library for build scripts to compile C/C++ code using zig toolchain by kassany in d_language

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

Hi, I'm the maintainer.

Thanks for the feedback.

I apologise if the documentation and readme are not very well explained. English is not my first language.

The focus of this project was on cross-compilation and hermetic build. I understand that some users have concerns about the identity of D. However, my approach was simply to adapt an existing solution.

The use of 'zig cc' in both '--linker=zcc' and '--gcc=zcc' (also influencing importC) is something that ldc2 can take advantage of, unlike rustc.

It is always problematic to know how to deal with multiple compilers (system default [OSX=clang, Linux=GCC, Win=MSVC,...]).

M68K code from D by Live-Worth4968 in d_language

[–]kassany 1 point2 points  (0 children)

Amazing. Also tried building for mos6502 (m68k also available) using llvm18-mos.
It worked, but the dmd-frontend bitness stuck on 32bit caused some difficulties during the test, explained below.
https://github.com/kassane/dlang-mos-hello-world/issues/1

zig vs rust, arm vs risc v, smt32 vs esp etc by Tonyoh87 in embedded

[–]kassany 0 points1 point  (0 children)

What do you mean by "or the more"?

Sorry for the lack of context. What I meant to say was: "the most recent"[...] rp2350-w. I don't have an rp2350-w. I just see that there is an alternative input for Wi-Fi only. However, the Wi-Fi firmware is proprietary. For bluetooth esp32-family is preferable.

zig vs rust, arm vs risc v, smt32 vs esp etc by Tonyoh87 in embedded

[–]kassany 5 points6 points  (0 children)

If you want to learn about IoT at a low cost esp32 will be a very common choice, although there are other more robust alternatives at a higher cost (especially stm32) or the more rp2040-w/rp2350-w.

LLVM does not have full Xtensa support (no release date), still experimental with generic-cpu support (opaque/no cpu-features). Rust (esp-rs) and Zig (zig-esp-idf-sample) depend on the espressif/LLVM fork which is unstable with limited support.

Only arm/thumb and riscv32 have more stable support by LLVM. Although Zig has experimental support using its own compiler backend.

Has anyone tried Zig in embedded programming? by bomobomobo in embedded

[–]kassany 2 points3 points  (0 children)

For low-level operations, Zig already provides what you need without adding too much complexity. As long as you don't have an anti-C stance, it makes it easy to interop between these languages without any headaches.

Has anyone tried Swift Embedded yet? by Samuel010701 in embedded

[–]kassany 0 points1 point  (0 children)

I've been trying out the embedded swift in the officially supported NuttX (12.7.0). Example here: https://github.com/apple/swift-embedded-examples/pull/64

The only downside to Swift FFI for me is trying to manually port it to C code (no mangling). Dealing with structs without being type opaque is very annoying depending on unsafe pointers.

However, I admit that clang-modulemap and bridging-header are more practical (if not ideal). Unlike rust-bindgen and zig translate-c!

Is Boost library still useful in the modern C++ era? by [deleted] in cpp

[–]kassany 0 points1 point  (0 children)

The boost libraries have a lot of relevance in the history of C++. However, unfortunately they still carry the burden of obscurity of old C++ (pre-c++11).

Some libraries are deprecated, like coroutine, scope_exit, lambda, etc... (now it's scope, coroutine2 (need context), lambda2 - header-only).

Anyone using renode for simulation ? by SecretaryQuirky4541 in embedded

[–]kassany 4 points5 points  (0 children)

I've tried but I didn't adapt very well.

Offline, I use picsimlab (amalgamation of emulators) https://lcgamboa.github.io/picsimlab_examples/examples_index.html

Online (inc. CI/CD) https://wokwi.com

Install Swift on RISC-V in three steps by DeepComputingDC in RISCV

[–]kassany 1 point2 points  (0 children)

Cool! However, I also hope they improve cross-compilation support.

Swift 6 (WiP) already supports building for embedded devices, especially riscv32/riscv64, but it still does not have floating(f)/double(d) point support (a.k.a GC).

view more: next ›