senfiaj

6 ms·

61.
by senfiaj 4mo ago
For its time it was a decent idea. Software was smaller and simpler. But today (and even before 64-bit) software is larger, more complex, we also need memory protection / isolation and more flexible memory allocation / sharing, so
62.
by senfiaj 4mo ago
But once you have written in assembly, you could start to write the next version in the higher level language. The first version (written in assembly) doesn't necessarily have to produce the most optimal code, just good enough and corr
63.
by senfiaj 4mo ago
Writing an optimizing production ready compiler doesn't seem to be an easy task, even today. I mean you can fork a compiler or look at the code, but maintaining your own one alone doesn't seem to be realistic. >> - not writi
64.
by senfiaj 4mo ago
Interestingly, there is llms.txt (like robots.txt) which is a new emerging standard to aid AI in crawling and gathering data from your website.
65.
by senfiaj 4mo ago
32-bit int isn't too much overhead. Just 3 additional bytes. I bet it's almost always better than c style strings. In the vast majority of situations the price isn't that bad, considering you make strings much more secure and
66.
by senfiaj 4mo ago
You can still use null terminator for compatibility (std::string does use this), but just not rely on that in your own code.
67.
by senfiaj 4mo ago
Well, not saying to always use it, but if the string size is big enough, the overhead of 2 ints becomes relatively vanishing. For generic dynamically sized strings it probably has more advantages than disadvantages. But in any case, sure, i
68.
by senfiaj 4mo ago
Exactly, you can't write clean concise code when working with c strings. Almost every c string manipulation requires cognitive load: "Is the buffer size enough (including null terminator), should I reallocate it?", "I ne
69.
by senfiaj 4mo ago
I wonder, why not use a string buffer paired with its length? For example, maybe use struct that has char pointer, and 2 ints (occupied length + total buffer length). Almost like c++'s std::string. This null terminator thing really suc
70.
by senfiaj 4mo ago
It still needs JS. It just avoids using canvas and does DOM manipulation + CSS instead.
71.
by senfiaj 4mo ago
Yeah, but after a certain point the win is negligible. Huge code can also increase cache misses which will slow down things.
72.
by senfiaj 4mo ago
Actually, WASM32 usually runs in a 64-bit browser, so it can utilize most of the 64-bit instructions and general purpose registers. The problem is it's much harder to ensure that 64-bit pointer don't access browser critical data s
73.
by senfiaj 4mo ago
Not sure about SIMD. If you mean WASM, the main advantage of WASM32 over WASM64 is execution speed if it runs on a 64-bit runtime. This is because pointer accesses are simply 64-bit base pointer + 32/33-bit offset (the 32-bit pointer v
74.
by senfiaj 4mo ago
Sometimes I wonder whether it's possible to run the wasm code in a separate sandboxed process to eliminate a lot of checks. I mean optionally, because normally JS calls wasm code synchronously in the same address space. The bridge will
75.
by senfiaj 4mo ago
If MS isn't going to fix this, I'm not going to use Windows 11 again. https://waspdev.com/articles/2026-03-12/i-ll-probably-never-...
76.
by senfiaj 4mo ago
But this raises the barrier to entry into programming if LLMs are capable of doing the vast majority of junior/mid level tasks. This can ruin the lives of many average people for whom programming was one of the few truly possible jobs.
77.
by senfiaj 4mo ago
I guess it was awkward to use languages that had higher level than assembly in order to write 16-bit programs that required more than 64KiB of memory. And also not quite portable, since they were all tied to x86 CPU. Those were messy times
78.
by senfiaj 4mo ago
Yes, on Wayland the color picker can only pick inside Chrome window.
79.
by senfiaj 4mo ago
>> It's all so frustrating watching the Wayland folks reinvent everything, poorly, and after more than 10 years it's still not there yet. The whole project started in 2008, so almost 18 years.
80.
by senfiaj 4mo ago
>> Chrome's PIP is a stupid workaround for Windows and Mac because they do not have robust window management. What are you talking about? It's very convenient when I watch video while I do some work or entertaining thing on
81.
by senfiaj 4mo ago
Yes, exactly. This security paranoia makes the devs' lives much more complicated. I have seen many apps turning off advanced features, such as screen color pickers. Automatation tools can be broken. Apps cant know their window position
82.
by senfiaj 4mo ago
As far as I know, there are multiple Wayland implementations. Which is also not good because it creates fragmentation and potential inconsistencies (some subtle differences in behavior, differences in bugs, etc). Maybe Hyprland solves the i
83.
by senfiaj 4mo ago
What's sad is that after many years Wayland still lacks several things/features that X11 has/allows. Some of them are intentionally not implemented because of security paranoia. For example, Chrome "picture in picture&qu
84.
by senfiaj 5mo ago
The argument is from the generator implementation point of view. Using regular escape is much simpler. Unlike regular escape, you still cannot use CDATA for attribute values. CDATA might quickly become a footgun because it can give you a fa
85.
by senfiaj 5mo ago
> The OP seems to argue "don't use CData, because the escape sequence for ]]> looks confusing" - and that's just vibes, not a proper argument. There are more arguments listed. One major one is about not being unifo
86.
by senfiaj 5mo ago
My first impression was also that such a huge project was too good to be true (especially that it is supposed to replace Ubuntu) if it was written from scratch. And then also noticed that it was AI assisted. Didn't run it and don'
87.
by senfiaj 5mo ago
For me it seems fine. Sometimes when I click on the headings I have to press back several times, but this is because they have anchored links.
88.
by senfiaj 5mo ago
This is mostly about when you write your automated feed generator.
89.
by senfiaj 5mo ago
What requirments are you talking about? Human readability? IMHO, RSS is for feed readers, not humans. When looking at https://news.ycombinator.com/rss , the RSS isn't that human friendly at all, all line breaks are rem
90.
by senfiaj 5mo ago
But are most people going to read raw RSS? Just out of curiosity, I checked HN RSS, it still escapes character in a regular way (without CDATA) for titles. So, just keep 2 versions of XML escape instead of one?

More ›