It's indeed quite possible to sneak in some symbols even in capture less lambdas. It all makes sense in the end.
A short and to the point reminder on how to manage properly a "layer cake" architecture.
It's been around for a long while now. This is an interesting way to complete the software craftsmanship view which didn't quite capture the "living ecosystem" side of our field.
Due to the strict type system this kind of conversion is not necessarily a given. There are ways though, and you can even keep it performing well.
A little article about a different type of grids for strategy games. Some of the consequences are very interesting.
Nice and clear indicators of how decentralized the fediverse and the "atmosphere" really are.
This is already an old article now. Still the core of it still rings true. The optimistic note at the end of it didn't come to pass though.
Good reminder of this important but imperfect guide to software design. There is some ambiguity on what "simplest" actually means. Still it helps keeping in mind that simple is rarely easy to find.
We got many options nowadays. Most of them are likely better than just making the underline disappear on links.
This is indeed an area which could be better handled in SQLite. It needs to be carefully checked when introduced in a project.
The idea is interesting... Seeing how the search engine space is degrading quickly I'm tempted to try this actually.
It's indeed a nice little pattern to use when the type system allows for exhaustiveness checks of destructure operations. Allows to gracefully handle extension of structs in the future.
Clearly Citrix is drowning as a product... How can people still trust the provider after such an episode?
This stays true, most projects are maintained by a single person and that's a problem. Where is the support from all the businesses benefiting from FOSS?
Long but thorough collection of all the nice improvements CSS brought the past few years.
Interesting talk. The tools presented can indeed go a long way helping people figure out what's wrong with a piece of code or learning some of the harder parts of a language.
Not every vulnerability reports are born equal... This can be a waste of time when the vulnerability is on the reporter end.
This can be useful indeed to explore concurrency issues. It requires some work though.
The approach is good, the results are encouraging as well. Not much effort and a very visible change. We need more such initiatives.
The situation is still complicated for maintainers... And companies benefiting from their free labor don't get it. This leads to really stupid situations.