juliangmp

My experience with vendor toolchains is that they generally suck anyway. In a recent bare metal project I chose not to use the vendor's IDE and toolchain (which is just an old version of GCC with some questionable cmake scripts around it) and instead just cross compile with rust manually. And so far its been a really good decision.

Why? Foss software also benefits from less dependency hell.

Thats cool and all but the majority of the country still has one, or at most two choices :/

> The most concerning limitation in the German market is the unavailability of native Glass Fiber modems, that can accept as input a Glass Fiber connection: at the moment, providers install their own Glass Fiber modem.

Im actually quite okay with that. Why should I have to pay for specialized hardware that won't be usable if I move and the new apartment uses DSL or docsis. Give me an rj45 (or sfp for some fiber connections) and let me put whatever Router I want behind it.

This is legit! If you disable your adblock you even get a suspicious ad

For me, yes it would.

I have less than zero interest in art that isn't made by humans.

"Why don't you just clone the repo?" Yes. Why dont you?

If you're gonna grab a repo to make a code theft machine then at least dont ddos the servers while you're at it.

Have you actually read one a Free/Open-Source license? Like for example the MIT[1] license:

  Permission is hereby granted, free of charge, to any person obtaining a copy of this software [...] to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software [...]

Or the FSF's definition[2] of Free Software

  The freedom to run the program as you wish, for any purpose (freedom 0).

Or the OSI's definition[3] of open source.

  5. No Discrimination Against Persons or Groups
  6. No Discrimination Against Fields of Endeavor

It's almost as if this concept is at the very core of FOSS.

[1]: https://mit-license.org/ [2]: https://www.gnu.org/philosophy/free-sw.html#four-freedoms [3]: https://opensource.org/osd

Emphasis on the freedom, especially the freedom to use by anyone for any purpose.

If it took some people in the FOSS space this long that it also includes people, companies or purposes they disagree with, then I don't know what to tell them.

Sure, I put quickly put them into a small markdown file. At my job we have a cmake interface target that handles these (along with some version checks and project specific stuff), but I can't publish that of course. I might put these into a cmake file at some point, not sure.

https://codeberg.org/JulianGmp/sane-args-cpp

I think this is cause most developers just end up using steam's APIs for these things and since steam will be most of their sales they don't bother. I have seen games using epic's solution in their steam distribution.

i do wonder how hard it would be to integrate multiple of these APIs so that the end user could invite anyone from any platform, though i imagine you'll still need some sort of middle man / lobby server...

Either way, I'm not a fan of having to generate lobby codes every time I want to play baldurs gate 3 with my friends who have it on steam

Yeah, it can quickly lead to analysis paralysis. I've set up three laptops with a Linux on them for non-tech friends and family members and deliberately went with distros that "just work" (Debian and Fedora specifically).

In general I'd recommend sticking to the simple options and not going into niches unless you/the user actually wants or needs to.

Most sensible Compiler flags aren't enabled by default... I keep a list of arguments for gcc to make things better, but even then you'll also wanna use a static analysis tool like clang-tidy

There was a grant in 2023 which was supported by the European Comission. So I think the topic itself isn't entirely unknown. https://nlnet.nl/project/Forgejo/

What for? Plenty of maintainers for various distros are from Europe and/or the EU.

For example: https://map.debian.net/

God I hope so

I've never once asked a question on there Mostly because you can't unless your account has X something-points. Which you get by answering questions.

This threw me off so much when I got started with programming. Like why are the people who have the most questions, not allowed to ask any...?

Honestly, until encrypted client hello has widespread support, why bother? I mean I did it for fun the first time and now with caddy its not a lot of effort. But for a personal blog, a completely static site, what benefit do you get from the encryption? Anyone monitoring the traffic will see the domain in clear text anyway. And they'd see the destination IP, which I imagine in this case being one server that has exactly one domain pointed at it.

I think there's quite large gap between vitamin D deficiency cause you don't get any sunlight and getting so much sunlight that it's unhealthy.

String handling (or arrays in general) has got to be the single aspect of C that I despise the most. Its clunky to use, often needs unnecessary copying (e.g. atoi) and makes it really easy to invoke undefined behavior.

I still don't get why a simple ptr+size type hasn't made its way into the language. #embed got in but I guess a new type would have been too much... at least we got bool after a few decades.

Also, for those that want the trimming behavior of strncpy but with the null termination, you can replace the strncpy calls with snprintf. You should also always enable -Wstringop-truncation.

Stable interfaces and not being in versioning hell (cough libc) would actually be good for FOSS as well.

If you make a piece of software today and want to package it for Linux its an absolute mess. I mean, look at flatpack or docker, a common solution for this is to ship your own userspace, thats just insane.

Ahh, if you're on KDE then Okular should do the trick, it should even update live when you update the markdown file.

It's a fine line to ride. You want both stability and new technologies and you have to find a balance between them.

And obligatory: experience and competence may be correlated, but they are not the same.

That is an actually terrible pattern, the standard should mandate nodiscard on operator[]. Or maybe finally cast that cursed operator implementation into hell where it belongs.

But alas, existing code is considered sacred in the C++ cult so we must never ever inconvenience anyone maintaining legacy code, no matter how broken it is.

If you're looking for a CLI markdown reader then I'd recommend glow.

https://github.com/charmbracelet/glow

Mdbook passes a version and the renderer/preprocessor can/should do a version check. Since it uses semantic versioning I would expect it to abide by those rules.

There's some example code in their docs (fn handle_preprocessing in the no-op preprocessor) which I've actually included in a preprocessor I wrote some time ago. https://rust-lang.github.io/mdBook/for_developers/preprocess...

I get where you're coming from but I'm not sure if PDF generation was a goal for mdbook to begin with. I'm pretty sure they're working on it now, but I'd stick to a domain specific tool, personally I find typst excellent to generate documents for prints.

For simple HTML docs mdbook is also excellent. I don't know if you could combine these two domains into one tool nicely. To me they're just too different.

although I have made presentations with mdbook using custom written preprocessors and a custom renderer (all of which were extremely crude, but did the job)

> I once hoped things would improve when Xilinx launched the Zynq line, combining a processor with FPGA fabric. Instead, the accompanying tools were so unusable that they made things worse, pushing developers even further away.

I once tried to use Xilinx' Vitis (2025) to make a small-ish piece of software running on such a Zynq chip. After wrestling with it* for like 5 weeks, me and my colleagues decided to ditch the entire Xilinx suite entirely and just pick a compiler and make a bare-metal binary with it. The FPGA part is done by a separate team of course, so us traditional software devs can stick with decent tools. We actually opted for a Rust toolchain and I'm extremely glad we did this, despite the additional time it took.

I don't know how my FPGA colleagues work with the proprietary toolchains and not go insane.

*The IDE is effectively a wrapper with a custom python API around cmake and gcc. It's not very well written cmake and I also don't know how they configure the linker that it does the weird things it does.

I assume you mean rustup, not cargo specifically or am I wrong?

I think platformio's selling point is multiple target boards via ts config. That and you can use an actual editor instead of the arduino "IDE", although I'm not a fan of vscode anymore either.

I also think they have some testing features built in, though i never delved too deep.