ZoomZoomZoom

At least both get paid in not-pretend money.

This is a google problem, but only secondary.

The crux of the matter is that there's nothing that protects an open project besides reputation, and nowadays in the digital space it can be cheaply farmed.

Laws could help, but they only work when you undertake purposeful actions to be covered by them, like register a trademark, and it's never cheap.

Imagine you're in a local band playing shows. It's 3 month old and you have no issued records. A second band tighter with venues takes your name and starts performing under your moniker. You have no money to take that to court and good luck making a case. You can't do anything besides screaming on the web or, don't know, kicking a few butts. You change your name.

If by AI you mean the LLM-based tools common now, then I don't want the commits in PRs I'm going to review to bring any more noise than they already do. The human operator is responsible for every line, like they always were.

If by AI you mean non-supervised, autonomous conscience (as I believe the term has to be reserved for), then the answer is again no, as it's as responsible for the quality of its PRs as humans.

If the thing writing code is the former, but there's no human or responsible representative of the latter in the loop, then the code shouldn't be even suggested for consideration in a project where any people do participate. In such case there's no point in storing any additional information as the code itself doesn't have any value (besides electricity wasted to create it) and can be substituted on demand.

Commit comments are generally underused, though, as a result of how forges work, but that's another discussion.

Why shouldn't this be a simple wrapper to tie Delta to some kind of file browser or a thing like television[1]?

[1]: https://alexpasmantier.github.io/television/

Years ago replacing Notepad with an alternative was a given and everybody had their favourite. Before UTF everywhere you needed at least proper character encoding handling, other features followed.

Surprisingly, some of the projects such as AkelPad are still alive.

Win32 made things easier, as well as things like Delphi and Scintilla later.

Just checked my archives, and my own naive but functioning attempt measures whole whopping 36520 bytes, though not without the help of an executable packer, which was a fashion then.

Mostly works fine under Wine, though it is about the legal US drinking age.

It's not polite to deny a country the agency to backslide on their own.

The corrupt class is, of course, following the oppression guide, so graciously provided and field-tested by their northern neighbour, rather diligently.

It would be unwise to overstate their (elite's) autonomy, considering economical and cultural ties on all levels, though.

I sincerely hope it's just me having trust issues.

Looks like Andreas is a mighty fine engineer, but he's even better entrepreneur. Doesn't matter if intentional or not, but he managed to create and lead a rather visible passion project, attract many contributors and use that project's momentum to detach Ladybird into a separate endeavor with much more concrete financial prospects.

The Jakt -> Swift -> Rust pivots look like the same thing on a different level. The initial change to Swift was surely motivated by potential industry support gain (i believe it was a dubious choice from purely engineering standpoint).

It's awe-inspiring to see how a person can carve a job for himself, leverage hobbyists'/hackers' interest and contributions, attract industry attention and sponsors all while doing the thing he likes (assuming, browsers are his thing) in a controlling position.

Can't fully rationalize the feeling, but all of this makes me slightly wary. Doesn't make it less cool to observe from a side, though.

In Nim too, although, the author doesn't like it much.

Not really? One is the cause (bad management/tech debt/problematic architecture/no public interest, etc.), the second is the effect.

Healthy and not extremely niche Free Software projects don't disappear. My software stack I rely on daily mostly barely changed in 15 and more years.

The amount of businesses closed, sold and products abandoned or swapped for the more controlled/exploitable ones is numerous, on the other hand.

To be fair, only the mesh part of the problem is quadratic. Reliable hole punching is not that easy either. As far as I know, there is a level of circumvention in case the unwrapped WG is blocked too.

The integrated service is very valuable and obviously genuinely popular.

I stand corrected.

Although, the problem is not so single-layered. Do I understand the situation correctly, in case of iOS, to not be subject to additional limitations of the platform that restricts the distribution of your products to the extents that the laws of the countries where your business is registered require, all the user has to do is to fork the main repo (which is, thankfully, BSD), build a minimally acceptable GUI, pass Apple certification, publish the app in the app store, and Bob's your uncle?

If you're sold on Tailscale due to them "being open" (as they semi-officially support the development of Headscale), keep in mind, that at the same time some of their clients are closed source and proprietary, and thus totally controlled by them and the official distribution channels, like Apple. Some of the arguments given for this stance are just ridiculous:

> If users are comfortable running non-open operating systems or employers are comfortable with their employees running non-open operating systems, they should likewise be comfortable with Tailscale not being open on those platforms.

https://github.com/tailscale/tailscale/issues/13717

A solution like this can't really be relied in situations of limited connectivity and availability, even if technically it beats most of the competition. Don't ever forget it's just a business. Support free alternatives if you can, even if they underperform by some measures.

What a weird use of "Romanesque" and "Baroque". Doesn't compute for me at all.

Don't know about the States, but across the pond from there, THX 1138 is not as well known as it probably deserves. I hope the public here can appreciate this Sci-Fi movie and Duvall is great there.

https://en.wikipedia.org/wiki/THX_1138

Dunno about using legislative moves, but yes please. The stupidest solution to a problem no one had. Moving layouts, unreachable footers, no or unsatisfactory indication of one's position.

All just to remove navigation clicks no one minded and reduce server loads, in exchange for users suffering laggy lazy loading (or, what a hate-inducing pattern!) inability to preload, print, search or link.

I believe it's a joint effect of muscle atrophy (vocal folds lose mass and become thinner), lower testosterone levels, stiffening of the larynx and the general loss of elasticity (stiffer things vibrate with a higher frequency). I'm no expert, though.

To be clear, we're talking about 60+. Before that, the pitch usually is on a decline.

That's not odd, it's a known common trajectory of a male voice range during the lifetime. If the vocal cords aren't ruined, if course.

If the malicious nodes are properly participating in the network, shouldn't it be a net positive for I2P?

I don't expect them to be traffic-heavy, if it's just the control plane.

> You know what else is far-seeing? A creature that has been alive for centuries.

Well, hello there!

Yep, always forget about '--forceBuild'. You can see in the script above the nimcache directory was overriden to tmpfs for the measurement, though. Caching will be helpful in real usecases, of course.

Nimscript is cool but very limited, not being able to use parts of the stdlib taht depend on C. Hope this will change with Nimony/Nim 3.

One of the coolest tricks is using tcc to compile "on demand." This allows you to use a compiled language like Nim for scripting, with almost no noticeable performance difference compared to interpreted languages.

  #!/usr/bin/env -S nim r --cc:tcc -d:useMalloc --verbosity:0 --hints:off --tlsEmulation:on --passL:-lm
  echo "Hello from Nim via TCC!"

Here's a comparison (bash script at [1]) of a minimal binary compiled this way with different interpreters. First line is the noise. Measured by tim[2] written by @cb321.

  1.151 +- 0.028 ms     (AlreadySubtracted)Overhead
  1.219 +- 0.037 ms     bash -c exit
  2.498 +- 0.040 ms     fish --no-config --private -c exit
  1.682 +- 0.058 ms     perl   -e 'exit 0'
  1.621 +- 0.043 ms     gawk   'BEGIN{exit 0}'
  15.8 +- 2.2 ms     python3 -c 'exit(0)'
  20.0 +- 5.7 ms     node   -e 'process.exit(0)'
  -2.384 +- 0.041 ms tcc -run x.c
  153.2 +- 4.6 ms     nim r --cc:tcc  x.nim
  164.5 +- 1.2 ms     nim r --cc:tcc -d:release x.nim

Measured on a laptop without any care to clean the environment, except turning the performance governor. Even with `-d:release` compiling nim code is comparable.

The fact that tcc compilation cycle measures negative here is a nice punchline.

[1]: https://gist.github.com/ZoomRmc/58743a34d3bb222aa5ec02a5e2b6...

[2]: https://github.com/c-blake/bu/blob/main/doc/tim.md

> The difference is that we've more or less hit a stable Pareto front in education and healthcare.

Not even close. So many parts of the world need to be pumped with target fund infusions ASAP. Only forcing higher levels of education and healthcare at the places where it lags is a viable step towards securing peaceful and prosperous nearest future.

I'll be that guy.

For what boils down to a personal take, light on technicalities, this reads like uncannily impersonal, prolonged attempt at dramatic writing.

If you believe the dates in this blog, it's totally different in tone, style, and wording to a safely distant 2021 post (https://www.iankduncan.com/personal/2021-10-04-garbage-in-ne...).

It made me feel paranoid just in about three paragraphs. I apologize to the author if I'm wrong but we all understand what my gut tells me.

Swap partition is set and forget. Can be detected by label automatically, never fails.

Swap file means fallocating, setting extended attributes (like `nocow`), finding file offset and writing it to kernel params, and other gotchas, like btrfs not allowing snapshotting a subvolume with an active swap file.

Technically it's preferable, won't argue with that.

Yeah, until you need to hibernate to one. I understand that calculating file offsets is not rocket science, but still, all the dance required is not exactly uninvolved and feels a bit fragile.

It's not like it's easy to shuffle partitions around. Swap files are a pain, so you need to reserve space at the end of the table. By the time you need to increase swap the previous partition is going to be full.

Better overcommit right away and live with the feeling you're wasting space.

I was pretty sure I'd be corrected in some manner, being two of the aforementioned three. Thanks.

...old lazy and wrong! Capital K is for Kelvin.