The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,860 other subscribers

Archive for September 26th, 2024

Do Not Stare: protip: when referring to your favourite programming language’s features

Posted by jpluimers on 2024/09/26

Cool idea: [Wayback/Archive] Do Not Stare: protip: when referring to your favourite programming language’s features

protip: when referring to your favourite programming language’s features, call them spells instead to sound more mysterious and cool.
👎 “memory safety feature”
👍 “memory safety spell”

--jeroen

Posted in Conference Topics, Conferences, Development, Event, Software Development | Leave a Comment »

Now open sourced with a really restrictive license – WinampDesktop/winamp: Iconic media player

Posted by jpluimers on 2024/09/26

Winamp is a multimedia player launched in 1997, iconic for its flexibility and wide compatibility with audio formats. Originally developed by Nullsoft, it gained massive popularity with still millions of users. Its development slowed down, but now, its source code was opened to the community, allowing developers to improve and modernize the player to meet current user needs.

https://github.com/WinampDesktop/winamp

Via https://x.com/dosnostalgic/status/1838739822816514308

Like, this is the worst license I’ve seen in a while. One isn’t even allowed to *create* a fork.

5. Restrictions

• No Distribution of Modified Versions: You may not distribute modified versions of the software, whether in source or binary form.

• No Forking: You may not create, maintain, or distribute a forked version of the software.

Official Distribution: Only the maintainers of the official repository are allowed to distribute the software and its modifications.

Related:

  1. you cannot contribute without forking https://x.com/circuitrewind/status/1838746690511352095
  2. it’s incomplete too https://x.com/circuitrewind/status/1838747170846933202

    The source also appears to be incomplete in at least one area that I just checked.

    There is the mc.exe binary that a few of us have been wanting source to for a very VERY long time. They have the binary, and no source for it still.

 

Posted in Uncategorized | Leave a Comment »

When you broke code, finding back where it got broken is easier if you have small change increment (i.e. bisection and binary tree search)

Posted by jpluimers on 2024/09/26

A while ago [Wayback/Archive] b0rk (Julia Evans [Wayback/Archive) wrote an interesting Tweet on finding back where you broke code of which the OCR text reads like this:

strategy: change working code into broken code

If I have a working version of the program, I like to:

  1. go back to the working code
  2. slowly start changing it to be more like my broken code
  3. test if it’s still working after every single tiny change
·      ⬊˙˙⸳              OH THAT’S WHAT BROKE IT!!!

I like this because it puts me back on solid ground: with every change make that DOESN’T cause the bug to come back, I know that wasn’t the problem.

by JULIA EVANS @bork wizardzines.com

This is similar (her arrows were of varying length) to using a binary search algorithm hunting for where the code was broken using bisection: repeatedly halving your search space to quickly zoom into the problem.

Another important aspect is that small commits while fiddling to solve an issue can help you determine what small commit was actually solving the issue.

Read the rest of this entry »

Posted in Algorithms, Conference Topics, Conferences, Development, DVCS - Distributed Version Control, Event, git, Mercurial/Hg, Ruby, Software Development, Source Code Management, Versioning | Leave a Comment »