4,396 karma · joined November 11, 2015
macOS font rendering has been worst in class since they removed subpixel-antialiasing. It's now a blurry mess on regular displays.
> Are saunas and blood donations not also effective for this?
Yes, plasma & blood donations are good at reducing PFAS blood concentration. Some(?) firefighting foam contains PFAS, so they tend to have high blood concentrations. Donations have shown to significantly reduce that: https://pmc.ncbi.nlm.nih.gov/articles/PMC8994130/
That said it's so trivial to do, why haven't you done that already?
ADA mandates computer accessibility, as frequently interpreted by courts. CCPA & GDPR mandate a whole bunch of stuff. Hardly the first plunge.
It can't be explained by images and fonts alone, I agree, but images and fonts alone are still enormous compared to 70kB. On my screen an "e" on this site is 10*11 pixels. Subpixel positioning means we need at least 6 copies of each letter, subpixel antialiasing means we need three channel alpha (3 bytes per pixel), we have variations of bold, italic and bold-italic, 95 printable letters in ascii, that's a low-ball of 750kB for one size of one font. This comment page alone has 4 different sizes, I'd expect a chat app to have a few more.
The GP to your original did set the bar at 70kB, mattmanser then explained that images and fonts easily exceed that, and then you called that poor resource management. Sounds like we're on the same page here, but you seemed to have missed the context of the comment you initially replied to.
Caching glyphs is good resource management and with modern screen resolutions, color displays and subpixel-antialiasing you just simply need more than 70KB of RAM.
> sublime consumes 200mb. I have 4 text files open. What is it doing?
To add to what others have said: Depending on the platform a good amount will be the system itself, various buffers and caches. If you have a folder open in the side bar, Sublime Text will track and index all the files in there. There's also no limit to undo history that is kept in RAM.
There's also the possibility that that 200MB includes the subprocesses, meaning the two python plugin hosts and any processes your plugins spawn - which can include heavy LSP servers.
My grandma does this all the time from her Linux laptop. My grandpa needed help getting it to work the first time under Windows.
Yea, who needs performance or security in a web framework!?
std::unique_ptr<int> a;
printf("%d\n", *a);
Similarly unique_ptr::operator[] doesn't (and can't) do bounds checking, for example: std::unique_ptr<int[]> a = std::make_unique<int[]>(2);
printf("%d\n", a[2]);
There's also no attempt to limit the construction of invalid smart pointers, for example: int num;
std::unique_ptr<int> a(&num);
Smart pointers simplify memory management, and they're slightly harder to misuse than regular pointers, but they simply make no attempt at providing memory safety.Smart pointers and containers are nowhere near memory safe, just enforcing their use gets you nowhere. `std::vector::operator[](size_t)` doesn't check bounds, `std::unique_ptr::operator*()` doesn't check null.
> Imo the strong point of rust is compile error if you try to use an obj after move (unlike c++ with undef behavior
The state of a value after being moved is defined by the move constructor. It is unspecified by the spec, but it's generally not undefined behavior.
What do you think whataboutism is?
Compared to suburbia where neighbours started mowing at 7am, loud parties went late into the night and dogs barked all day, it's oddly quiet.
As for coconut there's Lactones, which - you guessed it - occur naturally.
> OK for vanilla, however most of the fruit artificial flavors are compound that have nothing to do with the elements from the natural fruit but at some point, someone in the food industry decided it tasted "similar" to the natural fruit.
Care to provide a source?
On the other hand, disappearing ink has been around for a long time.