sai_c

10 ms·

61.
by sai_c 6y ago
Here's my take on it (and why I don't do side projects anymore). Roughly: As musician you grab your instrument and play. As a writer you pick pen and paper and write. As a chef you slice your stuff and cook. Me, starting with an
62.
by sai_c 6y ago
Yeah, but I think there is another saying that is still true in 2020: "Time is money". ;-). Edit: Corrected typo.
63.
by sai_c 6y ago
I think (for this discussion) we should have a more clear definition of embedded. Yes, ARM processors are used more and more, but there are really A LOT of embedded systems out there, which are still, for example, 8 bit. As an embedded dev,
64.
by sai_c 6y ago
"Yes, but in Debug/ReleaseSafe it's much stronger than C with sanitisers." Is it also stronger than C with Frama-C? Are you sure you hit all the execution paths during development? Pervasive casts? Not under MI
65.
by sai_c 6y ago
"I mean, this is only true if you ignore the myriad ways in which C allows you to manifest memory unsafety and undefined behaviour" Which Zig has as well in release mode.
66.
by sai_c 6y ago
Yes, this is my experience as well. On the other hand if you change the language, say every two years, when is the right point to dive in? Is it at some point (say i missed the last four years of language development) hopeless to catch up?
67.
by sai_c 6y ago
Yes indeed, Ada/SPARK would be better suited, but suffer (unfortunately) from a hefty price tag, not every shop is willing to pay. Especially if there are no lifes at stake should your software crash. Rust has the (imo) above stated pr
68.
by sai_c 6y ago
At this point in time, i agree with this analysis. But what for a C programmer (systems/embedded) remains to be seen, is, if any of the new languages (say for example Rust, Zig, Odin) can (or want to) offer one of C's strengths mo
69.
by sai_c 6y ago
"I also got the impression comp.lang.ada tended to be a bit more um... conservative, if you will." Hehe, yes definitely. But considering the projects some of the participants worked on, i can understand why. For those project
70.
by sai_c 6y ago
"I have a hard time imagining an experience even remotely described as unusable." Ok, so i should give FSF GNAT a try then. I always tried AdaCore's package. It's unfortunate that comp.lang.ada isn't available anymo
71.
by sai_c 6y ago
As I said, I tried the FSF version at about 2018. Might be way better now, I don't know. My experience with gcc (C, not C++) for personal projects is exactly zero bugs. So, you see, experiences can differ ;-). When saying "you nee
72.
by sai_c 6y ago
Yes, I know it is in gcc. But compared to the AdaCore version, there are way too many bugs (at least when I played with it in 2018). And for any commercial endeavour (even if just a small company, say one or two developers) you really need
73.
by sai_c 6y ago
Because Ada is not a language for quick and dirty. It's a language that is only fun and usable if you apply engineering methods to the whole project (a.k.a requirements, documentation etc.). Most projects out there don't. Quite fr
74.
by sai_c 6y ago
Sorry, will do so in the future. Thx.
75.
by sai_c 6y ago
Besides writing "int *p" instead of "int* p" I also always use one line per variable declaration, which should avoid confusion when the first style is used. But that's my personal preference. Edit: c