shiomiru

7 ms·

31.
by shiomiru 11mo ago
I can usually read JS generated by TS, but calling the C Nim outputs "human-readable" is very generous considering it flattens most structured control flow to goto. (It's hard to do it otherwise, Nim has to deal with excepti
32.
by shiomiru 11mo ago
I should've worded differently. By the narrative of this website, Google is "paying" Mozilla & Apple to remove XSLT, thus they are "controlled" by Google. I personally don't quite believe it's all tha
33.
by shiomiru 11mo ago
Ironically, that text is all you get if you load the site from a text browser (Lynx etc.) It doesn't feel too different from <noscript>This website requires JavaScript</noscript>... I now wonder if XSLT is implemented
34.
by shiomiru 11mo ago
To clarify, I think it's fair to say "I use GitHub because I don't think MS is that bad" (I disagree, but it's at least a consistent view.) I only take an issue with "I think MS is morally reprehensible but e
35.
by shiomiru 11mo ago
If it's not a magical achievement, then surely competitors could replicate it too. Of course you can't put a million users today in a service used by a thousand yesterday, but I don't buy the "non-profits don't scal
36.
by shiomiru 11mo ago
I switched because btop provides vi-like keybindings. For htop I think you have to use a fork to get that.
37.
by shiomiru 11mo ago
But your confidence in GitHub's continued existence comes from its network effects, no? And competing services can only gain such network effects if more people use them. So to me this feels like a defeatist argument.
38.
by shiomiru 1y ago
Sixel came earlier, and already fulfilled the basic requirement of "put pixels on screen in a single well-defined format" (something not even iTerm2's protocol does.) Kitty is a lot more complex: it accepts five different enc
39.
by shiomiru 1y ago
It's deep in the uncanny valley. Even ignoring the writing style, the entire post is about the incredible insight of "you can build TCP on top of UDP" using a forced analogy. No further analysis, no real world example, just
40.
by shiomiru 1y ago
It says > the encodings defined in Encoding, including, but not limited to where "Encoding" refers to https://encoding.spec.whatwg.org (probably that should be a link.) So it just means "the other spec defines
41.
by shiomiru 1y ago
> It would greatly simplify browser code and HTML spec. I doubt it would make a dent - e.g. in the "skipping <head>" case, you'd be replacing the error recovery mechanism of "jump to the next insertion mode&quot
42.
by shiomiru 1y ago
I've done something like that in my TUI browser: https://codeberg.org/bptato/chawan/src/commit/3f2fffd882ff47... It just spins up a background process when a canvas context is created and sends draw
43.
by shiomiru 1y ago
> The point is they are not even compliment to their "own" spec. They are part of whatwg. I think web devs have too much faith in the "standard"; the WHATWG specifies anything supported by two implementations, and wit
44.
by shiomiru 1y ago
The whole post is obviously LLM spam. e.g. > It is the conductor [emoji] that directs the symphony of independent Spaces. this pattern is a meme by now.
45.
by shiomiru 1y ago
Also, SMTP straight up leaks your IP address when sending e-mails (the "Received" header.)
46.
by shiomiru 1y ago
The Unlicense isn't "just" public domain though, it also has a fallback clause that explicitly lists things you are allowed to do ("copy, modify, publish, use, compile, sell, or distribute"). So I think the intent
47.
by shiomiru 1y ago
I had to work around this recently - it involved reimplementing my poll wrapper on top of select(), with the proprietary macOS extension that makes it support unlimited fds. (Of course -D_DARWIN_UNLIMITED_SELECT is completely unportable, s
48.
by shiomiru 1y ago
> It looks well-intended The recent PuTTY domain squatting debacle has made me suspicious, and indeed... if you look closer, you'll notice that the owner of ublockorigin.com is also advertising his completely unrelated products
49.
by shiomiru 1y ago
It already exists for Sixel: https://github.com/saitoha/xserver-sixel ...but at that point X forwarding or VNC seems more useful.
50.
by shiomiru 1y ago
But that's also completely unremarkable, given that word for word translation in any two languages is expected to be a lossy conversion.
51.
by shiomiru 1y ago
> The problem is they abandoned rails for react. Which, it seems, was a result of the M$ acquisition: https://muan.co/posts/javascript
52.
by shiomiru 1y ago
> Telling people to ignore code points Nobody is saying that, the point is that if you're parsing Unicode by counting codepoints you're doing it wrong. The way you actually parse Unicode text (in 99% of cases) is by iterati
53.
by shiomiru 1y ago
> I think the real reason most are so obsessed with blocking crawlers is they want “their cut”… I find that an unfair view of the situation. Sure, there are examples such as StackOverflow (which is ridiculous enough as they didn't
54.
by shiomiru 1y ago
Right. If anything, it's the opposite: removing XSLT reduces the complexity of existing browsers, allowing new ones to catch up faster. To me it seems that some people just really like using XSLT, and don't want it gone. Which i
55.
by shiomiru 1y ago
Neither is it required in Nim. A Nim object is a stack-allocated value type, without refcounting. You can put that in a heap-allocated seq (pass-by-value with move semantics), ref (refcounting), a custom container (you decide), or ptr (unsa
56.
by shiomiru 1y ago
ARC's ref is similar to C++'s shared_ptr, or Rust's Rc - with that alone it might still count as "GC'ed". But ARC also has ownership semantics, and hooks for custom containers: https://nim-lang.org&
57.
by shiomiru 1y ago
And if you don't want to install Java, there's also a C++ implementation: https://i2pd.website/
58.
by shiomiru 1y ago
> As if oligopolization of the browser space wasn't a deliberate objective of the WHATWG. So why is it that when once in a blue moon the WHATWG tries to do something that also happens to help new implementations, web devs come in to
59.
by shiomiru 1y ago
> No, adding complex new interfaces and then demanding that every browser implement them quickly is what does that. New interfaces forced into the spec without concern for complexity have led to the demise of existing browser engines.
60.
by shiomiru 1y ago
> Things can remain backwards compatible forever. This is exactly the attitude that has left us with only three complete extant implementations of the web, two of which are controlled by an ad company. Indeed, to me it seems that at some

More ›