I'm a big fan of the Go programming language because of this, but also by extension of "boring technology" (https://mcfunley.com/choose-boring-technology). It's hard to be able to make an impact in this regard in the B2C projects I usually have though.
[1] https://web.archive.org/web/20161021183035/https://www.sqlit...
It sounds really cool. And even if in the end everyone benefit from that, I wonder who requested that (if someone did)... I mean, it's expensive to test up to that level...
And while Airbus confirmed they are using SQLite, they did not claim they are using it in safety critical parts, which D. Richard Hipp confirms here: https://news.ycombinator.com/item?id=18039303
So good to see this. I have seen so many developers use the latest C# features heavily, to avoid looking weak.
Older developers (like me) have opposite problem and I have been fighting for months to not upgrade .NET4.8 to .NET8 due to compatibility with our current deployment chains etc. In the end I had to admit that using .NET8 for everything is going to work too and is going to give us access to better tools and new tech either through some teething problems.
There is no such community push but like anywhere else, you'll see folks get excited about new toys and then try to force them in to try them. It's not any worse for C# than anything else.
Yes. Engineers use the latest features heavily to demonstrate that their skills are current.
One of the worst such features is "var". Some tools even flag your code for not using var when you could. Inappropriate use of "var" makes code harder to read (and even MS documentation says this) and makes code slightly less reliable too.
https://en.wikipedia.org/wiki/C_Sharp_3.0#Local_variable_typ...
Besides making the code harder to read, "var" also makes your code less reliable as seen in this example: https://circles.page/567f44465c28b00bf8ed6cf9/Csharp-Type-In...
The problem you see is independent from var.
I disagree with this too, I think your example is a classic case of preprocessor directives making it difficult to know what your code is doing because the build system is going to conditionally change your code. Var or not, you can't even know what's being compiled just by looking at the file, and that's a larger problem than the use of var
https://learn.microsoft.com/en-us/dotnet/csharp/language-ref...
I have seen code that sorts numbers as strings, because nowhere in the code was the intent stated that the array is supposed to hold numbers. As a result, if the programmer forgot to convert strings to integers at input time, the bug is never caught.
See: https://circles.page/567f44465c28b00bf8ed6cf9/Csharp-type-in...
There are, occasionally, the “wow, I got to have that” moments and those are great, but rare.
> Our aim is to produce timeless code that will be readable, understandable, and maintainable by programmers who have not yet been born.
But not a global. Unless someone ports it to Collapse OS/Dusk OS, that would be a true LTS plan
That he was contractually obligated to do so, and that he kept that in mind, probably effects his attitude towards shipping certain things.
Completely off topic, but I think it's a fun quirk of English that sometimes the choice of a/an will tell you how a person pronounces a word. You can spot whether someone has an American or British/Australian accent by whether they write "a historian" or "an historian", for example, even if you've never heard them speak.
That said, I think the future of SQLite is basically guaranteed on account of being open source (as much as anything in this world can be guaranteed anyway). Look at Rust: it's done fine since Mozilla stopped sponsoring it. Go will be fine when/if Google stops sponsoring it. etc.
"Hipp, Wyrick & Company, Inc., or "Hwaci" for short, is a small North Carolina company providing knowledge services to clients around the world since 1992. Hwaci is an S-Corporation owned by the husband and wife team of Richard Hipp and Ginger Wyrick."
Companies are a standard mechanism to provide continuity past the lifetime of a single person. A corporation, if it truly adheres to the laws and bylaws, has enough formalisms to ensure such an organization and its products continue to be supported past a lifetime.
I am not concerned with whether it has a future. But I do fear that the absolute manic focus on code quality, testing and support may take a dive when other programmers take the helm. I am not claiming that there are no developers who are equally careful and/or skilled, but whether the culture of SQLite will persist is, to me, still an open question.
I'm also curious about this for other projects such as Shakti/k9 [1]. Apologies if not referred to correctly as I'm not familiar with these tools, so consider this a question as much as a comment:
A seemingly obscure implementation of a complex tool with a relatively high learning curve and just three maintainers that is supposedly a key component in a number of domains using high-frequency timeseries data (finance, etc.)?
What's the cost/complexity ratio in incorporating technology like this into your system? Or is it much less than the impression I get as someone that's jsut a curious passer-by?
Shots fired at the rust community.
... and further, you can do it in an open, standard fashion over SSH:
stego-tech•15h ago
This is a gold standard for documenting source code, in my experience. It doesn’t entirely solve the “bus” problem, but reduces the barrier to entry for new maintainers or project resuscitators substantially by making it easy to understand what’s going on and why decisions were made.
Admittedly, my own code is also in that 35% range for commenting, so I’m inherently biased towards that threshold specifically. YMMV.
mattashii•15h ago
It's rather easy to get over 50% by putting a comment above each line of code, containing the output of an LLM that's asked "what does this line do" and supplied with exactly that line of code. It's much harder to make sure the comments make sense and actually add value.
hansonkd•15h ago
If the llm can produce similar enough comment from scratch, would it be better to just have an IDE that dynamically injects comments when you need as opposed to them being in version control?
LostJourneyman•14h ago
Comments in source code are always going to meet the maintainer's intention and will much more likely cover the use cases that comments are meant to cover - unintuitive cases or decisions, unclear algorithms, general usage to point maintainers in the right direction, and so on. More importantly, comments in the source code require no additional tools or other dependencies and as such are more dependable.
0cf8612b2e1e•14h ago
I would instead be willing to consider some kind of QC assessment. Where does AI think the comment does not match the code because something has fallen out of sync.
hansonkd•13h ago
> all comments that cant be reproduced by llm
Not remove all comments.
meaning if your comment is so low quality that an LLM will generate it for you by reading the code, then it doesn't belong in VCS
datadrivenangel•15h ago
They try!
bux93•15h ago
vasco•15h ago
pdpi•14h ago
stego-tech•12h ago
This naturally gets me close to the 1/3rd mark, I find, without really trying. When that code is shared with others, they typically report back that it’s very easy to read quickly and make adjustments.
But again, that’s my entirely subjective experience.