litchralee@sh.itjust.workstoProgramming@programming.dev•Winamp source code is now on GitHubEnglish
31·
23 days agoI lost it when coming across this commit: https://github.com/WinampDesktop/winamp/commit/67c68e6dc24f36b266427034d016fb86ef4d486c
I lost it when coming across this commit: https://github.com/WinampDesktop/winamp/commit/67c68e6dc24f36b266427034d016fb86ef4d486c
Can you please kindly link to that article, if it’s publicly available?
This reminds me of a post I once saw, describing a person who (ab)used the C preprocessor to make an Old English version of C. It was clever, but obviously unmaintainable in a collaborative setting.
If this DreamBerd language is statically compiled, then it might still rank slightly above Tcl, a language I’ve had to use in production and despised every moment of it.
A few months ago, my library gained a copy of Cybersecurity For Small Networks by Seth Enoka, published by No Starch Press in 2022. So I figured I’d have a look and see if it it included modern best-practices for networks.
It was alright, in that it’s a decent how-to guide for a novice to set up sensible, minimum network fortifications. But it only includes an overview of how those fortifications work, without going into the additional depth needed to fine-tune or optimize them for specific environments. So if the reader has zero experience with network security, it’s a worthwhile read. But if you’ve already been operating a network with defenses for a while, there’s not much to gain from this particular text.
Also, the author suggests that IPv6 should be disabled, which is a terrible idea. Modern best-practice is not to pretend IPv6 doesn’t exist, but to assure that firewalls and other defenses are configured to handle this traffic. There’s a vast difference between “administratively reject IPv6 traffic in/out of the WAN” and “disable IPv6 on all devices and pray no one ever connects an IPv6-enabled device”.
You might have a look at other books available from No Starch Press, though.