boris

13 ms·

31.
by boris 2y ago
> Feature Detection Is Better than Version Detection The problem with feature detection (normally referred to as configuration probing), at least the way it's done in ./configure and similar, is that it relies on compiling and
32.
by boris 2y ago
Yes, pretty much. I think it would also be good (but admittedly risky) to accept third-party contributions (even new features) to the old version. In other words, instead of trying to force people to use a new license they could have tried
33.
by boris 2y ago
I am not demanding anything, I am merely exploring if the "license rug pull" problem has a better solution. Redis paid dearly for it (justifiably or not) so if we can find a less costly option, wouldn't it be a good thing? I
34.
by boris 2y ago
They could still maintain it by, say, backporting bug fixes. And also accept contributions from people who prefer to stay on the old rug. It is extra effort for them and it is risky (everyone might end up staying on and contributing to the
35.
by boris 2y ago
I think you are missing my point: I am not saying there is no entitlement or that it's not bad (I've been on the receiving end to know it's true). I am merely wondering where it's coming from. Culturally, at least most o
36.
by boris 2y ago
Everyone agrees the unreasonable entitlement of many OSS users is bad but I don't see much analysis of where this entitlement comes from. Maybe it's the loss aversion: you first gift them the software but then by refusing to maint
37.
by boris 2y ago
> The only problem I've seen is that occasionally the server ssh process will get stuck, so you have to log in to the server and kill it. You also need ClientAliveInterval on the server side (in addition to ServerAliveInterval on th
38.
by boris 3y ago
Based on my experience running open source projects for a couple of decades, not replying/engaging is the only way. Don't reward incompetence with a response -- are they paying attention, have they done their homework? (paraphrasi
39.
by boris 3y ago
The article lists some specific limitations of the meta build systems but doesn't really get to the underlying, fundamental issue with the approach. Which leaves the possibility of these specific limitations being addressed somehow and
40.
by boris 3y ago
> Their pricing is either free or insane with little middle ground. I pleaded with a sales rep - I'm happy to stay on the free features but give you some money for "support" but they wouldn't take my money. Utter madn
41.
by boris 3y ago
> Swift on Linux already and companies like Apple or Amazon are using it as well in production systems. Hm, any citations on the latter? That is, companies like Apple and Amazon using Swift in production systems on Linux, especially for
42.
by boris 3y ago
It may be improving but it's not there yet, let alone battle-tested with years of production use in serious applications on Linux. And we are talking about a distributed database here, where a bug can very well lead to it eating your d
43.
by boris 3y ago
Strange... Presumably production deployments of FDB are on Linux. Last time I heard, Swift support on Linux is second-class. Is the plan to deploy on Mac OS instead of Linux? Or is Swift support on Linux sufficient for FDB needs? I must say
44.
by boris 3y ago
I am a C++ programmer and if you told me those things, I would just flip a bozo bit on you and carry on coding, no religious flame-war is warranted.
45.
by boris 3y ago
> I'll stand corrected on the technical details of the build2 implementation of modules. Thank you. > I still think the p1689 is a more robust implementation I agree prescan has advantages, like being easier to integrate into ex
46.
by boris 3y ago
> https://wg21.link/p1689 Ah, that. It's just a new -M output. It's still cannot handle header units though without a major extension to the preprocessor semantics, which so far only Clang managed to implement
47.
by boris 3y ago
build2 use the module mapper API which was available long before 2021: https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Module-Mapper... You can try the examples here https://github.com/build2/c
48.
by boris 3y ago
> but not all library files are architecture-dependent. While this is definitely true, the presence in /usr/share/ of many files from library packages on my system (Debian) still suggests that architecture-independent file
49.
by boris 3y ago
└-- lib |-- cxx | └-- foo.cppm ---> this is a module interface (does `export module foo`) └-- libfoo.a Hm, .../lib/ normally contains architecture-specific files so I wonder what was
50.
by boris 3y ago
> So far, CMake 3.28 (still a Release Candidate at time of writing) is the only build system that implements dependency scanning and the ability to consume external libraries that provide modules, and the BMIs are built locally rather th
51.
by boris 3y ago
The Makefile in the article is actually incorrect and only "works" by accident: main.o must have a dependency on mod1.pcm which is one of the outputs produced when compiling mod1.ccm and is needed whenever compiling any transactio
52.
by boris 3y ago
> lack of flexibility compared to AMD's platform You mean flexibility to claim ECC support but not doing any validation to make sure it actually works? Does any AMD motherboard manufacturer actualy states that "ECC is supported
53.
by boris 3y ago
There are several plausible levels of "support" where ECC is concerned: 0. Not supported at all (i.e., if you plug ECC RAM, your system won't boot). 1. ECC RAM can be plugged but the ECC functionality is not used (i.e., there
54.
by boris 3y ago
As the name suggests, this wraps the whatever build system that the dependency is using rather than replacing it with Meson. Say if you depend on Boost and Qt, you will end up using both Boost Build and CMake in addition to Meson (most like
55.
by boris 3y ago
> Unfortunately, it seems like this is a very specialized skill set that the vast majority of developers seem to find boring, uninteresting, and drudgerous, and finding someone qualified and interested has been exceedingly difficult. The
56.
by boris 3y ago
> I'd settle for people using stdout and stderr correctly. I use this as a litmus test when looking at an unfamiliar codebase: if the author couldn't care less about writing diagnostics to stderr instead of stdout, there is lit
57.
by boris 3y ago
The good guy who thought this would be the wrong decision all along but who got caught up in the middle of it has resigned. I bet people who thought (and perhaps still think) this was the right decision will not resign. Politics is a bitch.
58.
by boris 3y ago
Titanum.
59.
by boris 3y ago
One thing that seems to have helped (anecdote of 1) is getting a longer (quality) HDMI cable and making sure the end that connects to the MacBook goes in as straight as possible. As you may have noticed, there is quite a bit of play in that
60.
GCC 13 Released(gcc.gnu.org)
167 points by boris 3y ago|19 comments

More ›