Modding Windows is akin to building a sand castle. It might be fun, beautiful, but very much impermanent. You can expect it to be washed off with the next Windows update.
I've done it before on Windows 7. Resized system clock, resized start menu button, removed "Terminate batch job (Y/N)?" warning in cmd, etc.
Most annoying is that VirtualBox stops working with the patched uxtheme.dll.
...
Life on Linux is great. My modifications stick for as long as I want. Permanently if I get my patches upstream.
0 and O, and l and I that look the same in a single font is a crime of modern typography.
Also, I remember 8x16 VGA font that came with KeyRus had some slight differences between Cyrillic and Latin lookalikes,
that brought some strange sense of comfort when reading, and especially typing the letter c, because its Cyrillic lookalike is located on the same key.
I thought oxfmt would just be a faster drop-in replacement for "biome format"... It wasn't.
Let this be a warning: running oxfmt without any arguments recursively scans directory tree from the current directory for all *.js and *.ts files and silently reformats them.
Thanks to that, I got a few of my Allman-formatted JavaScript files I care about messed up with no option to format them back from K&R style.
> running oxfmt without any arguments recursively scans directory tree from the current directory for all .js and .ts files and silently reformats them
I've got to say this is what I would have expected and wanted to happen. I'd say it is wise to not run tools designed to edit files on files you don't have a backup for (like Git) without doing a dry-run or a small scope experiment first.
While I can get behind things such as "use version control," "use backups", etc. this is definitely not what I'd expect from a program run without arguments, especially when it will go and change stuff.
What? The very first page of documentation tells you this. The help screen clearly shows a `--check` argument. This is a formatter and uses the same arguments as many others - in particular Prettier, the most popular formatter in the ecosystem.
How were you not expecting this? Did you not bother to read anything before installing and running this command on a sensitive codebase?
I do usually run new tools from somewhere harmless, like ~/tmp, just in case they do something unexpected.
But most formatters I'm used to absolutely don't do this. For example, `rustfmt` will read input from stdin if no argument is given. It can traverse modules in a project, but it won't start modifying everything under your CWD.
Most unix tools will either wait for some stdin or dump some kind of help when no argument is given. Hell, according to this tool's docs, even `prettier` seems to expect an argument:
> Running oxfmt without arguments formats the current directory (*equivalent to prettier --write .*)
I'm not familiar with prettier, so I may be wrong, but from the above, I understand that prettier doesn't start rewriting files if no argument is given?
Looking up prettier's docs, they have this to say:
> --write
This rewrites all processed files in place. *This is comparable to the eslint --fix* workflow.
So eslint also doesn't automatically overwrite everything?
So yeah, I can't say this is expected behaviour, even if it's documented.
Not taking a position but the design of rm strengthens the position that recursive by default without flags isn’t ok. rm makes you confirm when you want changes to recurse dirs.
I expect invoking a command-line tool without any arguments to perform the most common action. Displaying the help should only be a fallback if there is no most common action. For example, `git init` modifies the current directory instead of asking you, because that’s what you want to do most of the time.
I know feels aren't the objective truth but I feel like most people would default to running "new-cli-tool --help" first thing as a learned (defensive) habit. After all quite a bit of stuff that runs in a terminal emulator does something when ran without arguments or flags.
I assume you mean what’s more properly called Java style [1], where the first curly brace is on the same line as the function declaration (or class declaration, but if you’re using Allman style you’re probably not using classes; no shade, I’m a JS class hater myself) [2] or control statement [3], the elses (etc) are cuddled, and single statement blocks are enclosed in curly braces. Except I also assume that oxfmt’s default indentation is 2 spaces, following Prettier [4], whereas Java style specified 4.
So maybe we should call it JavaScript style? Modern JS style? Do we have a good name for it?
Also, does anyone know when and why “K&R style” [5] started being used to refer to Java style? Meaning K&R statement block style (“Egyptian braces” [6]) being used for all braces and single statement blocks getting treated the same as multi-statement blocks. Setting aside the eternal indentation question.
I never liked the idea of running Flash inside the web browser, but a single file .swf game format is almost as good as any ROM game dump.
Some games didn't mind running locally from an .swf file, but some others had a "URL protection", presumably to prevent
people from embedding their flash games at other websites, and they didn't make an exception for localhost.
Long time ago I've fixed hundreds of such flash games using RABCDAsm and made them work in standalone Flash Player.
Took a brief look at Flashpoint Archive, it seems their way to fix URL check is to spin up a web server to present an address the game expects.
As a bit of background, flash games were often sponsored. The bigger websites would pay hundreds to thousands of dollars to put their (clickable) logo in the beginning of a game, and sometimes would also have either timed or permanent exclusivity to their website.
Is there a standard patch format for this use case, where you could keep the original files and have a second file that patches them at load time to make them runnable?
As Flash files are often compressed, a patch wouldn't be any smaller than having an original and a fixed copy. You'd have to invent a new patch format that operates on an uncompressed SWF.
It seems crazy to me that the offered way to install an extension on Chrome is to click a button on a privileged website,
and then the installed extension autoupdates without an option to turn it off.
I hate the idea of installing stuff without an ability to look at what's inside first, so what I did was patch Chromium binary,
replacing all strings "chromewebstore.google.com" with something else, so I can inject custom JS into that website and turn
"Install" button into "Download CRX" button. After downloading, I can unpack the .crx file and look at the code, then
install via "Load unpacked" and it never updates automatically. This way I'm sure only the code I've looked at gets executed.
Deluxe Paint 2 for DOS was my favorite drawing program, so had to check this out, pretty nice!
The only thing that stops me from recommending it is non-integer zoom levels, which is especially bad for pixel art.
Moving layers around was also confusing, had to click Layer → Transform → Free Transform to be able to move things around. It would be much more obvious if there was a move icon in the tool panel that does just that.
I've found Xfce with Wallis theme to be quite comfortable after I ditched Windows 7. Been using it for 3 years now.
Also I enjoyed how easily I could modify it:
- xfwm4: zoom only to multiples of integer, nearest neighbor only
- xfwm4: stop moving zoomed area after the cursor when Scroll Lock is on
- xfce4-screenshooter: supply custom actions with parameters %x %y %w %h of a selected rectangle, allowing me, for example, to select a rectangle and then launch a screen recording script.
Never found the use for multiple desktops, though.
The only part that irritates me is having to interact with the GTK file chooser (file open dialog). Someday I might be annoyed enough to replace it.
The file chooser can be somewhat tamed in the settings editor. For example to get the buttons back to the bottom of the dialog where they belong: disable the "DialogsUseHeader" setting under "xsettings" in xfce4-settings-editor
I've done it before on Windows 7. Resized system clock, resized start menu button, removed "Terminate batch job (Y/N)?" warning in cmd, etc.
Most annoying is that VirtualBox stops working with the patched uxtheme.dll.
...
Life on Linux is great. My modifications stick for as long as I want. Permanently if I get my patches upstream.
reply