mmstick

10 ms·

31.
by mmstick 9y ago
That's because ESR is a very ancient version of Firefox. Many things don't work on ESR. You need at least Firefox 52.
32.
by mmstick 9y ago
I highly doubt that anyone depends upon a personal blog for food.
33.
by mmstick 9y ago
> You wouldn't be getting much pushback if you simply justified it as "It's what I want to do" Actually, if you look at the top level comments that I've made, that's exactly what I said. What I'm getti
34.
by mmstick 9y ago
> This is completely incorrect. Not only does Brotli have literally nothing to do with the transmission medium and whether it's encrypted, but just to be sure I just tested it and Chrome was perfectly happy to render a Brotli-encode
35.
by mmstick 9y ago
It supports HTTPS perfectly fine. I am even on the HSTS preload list. You can't get on this list unless you have a HTTPS website that meets standard requirements. https://hstspreload.org/?domain=mmstick.tk
36.
by mmstick 9y ago
> What about serving uncompressed content over https? I have limited bandwidth. I don't want to serve uncompressed content over HTTPS. > What about serving up an error page when the user's browser odesn't have compresso
37.
by mmstick 9y ago
> You had to go out of your way to break support for these browsers. Literally every HTTP package (including Rocket) out of the box handles uncompressed files. You had to modify it to add always-on Brotli encoding. I did not have to go o
38.
by mmstick 9y ago
> You've already positioned yourself as trying to take a principled stand against software that doesn't support Brotli in the hopes of convincing the software authors to add support for Brotli. Now you're saying you don&#x
39.
by mmstick 9y ago
I'm not sure where your confusion is. It doesn't matter that HTTPS is an encrypted form of HTTP. I do not support HTTP, which means that I do not support HTTP without encryption! End of story. Attempting to access the site via HTT
40.
by mmstick 9y ago
All vendors do not support Brotli compression with the HTTP protocol. Brotli is only supported when accessing a site through HTTPS. Moreover, as Brotli compresses and decompresses faster than Gzip, whilst simultaneously producing smaller fi
41.
by mmstick 9y ago
I don't use Apple products, nor am I user of Safari. It's not in my interest to request for Brotli support in products that I do not use. > I think it's safe to say the overwhelming majority of software that issues HTTP re
42.
by mmstick 9y ago
This is because I don't have a HTTP website! The website is HTTPS-exclusive. If your tool does not support HTTPS, it will certainly not work on my website. > wget and curl both also fail to decompress your site's contents. I&#x
43.
by mmstick 9y ago
It's not user-hostile at all. It is quite simple. I don't want to implement gzip support, and I definitely don't want uncompressed content. You can't demand me to implement what I don't want to implement for my webs
44.
by mmstick 9y ago
That would require that I cache both a gzip and brotli variant of each page and content that is requested. I see no reason to support gzip just because a single company has refused to implement support for Brotli. Firefox, Chrome and Edge a
45.
by mmstick 9y ago
I see it as more of an Apple problem. Everyone else's web browser works fine, but Apple's doesn't. The main reason why companies like Apple still don't support Brotli even though the competition has supported it for more
46.
by mmstick 9y ago
Naturally. Since moving to HTTPS, I have dropped support for gzip, and I will not be re-adding it. There is no benefit in continuing to retain legacy gzip support. Brotli can compress and decode faster than gzip, and it produces smaller fil
47.
by mmstick 9y ago
You need a web browser that supports Brotli compression -- the standard compression algorithm for HTTPS. Safari does not support it, but everyone else does. Even Edge. http://caniuse.com/#feat=brotli
48.
by mmstick 9y ago
You might like to know that I've had great success with full stack web development using Rust. My website ( https://mmstick.tk ) is hosted with the Rocket ( https://rocket.rs/overview/ ) web framework and
49.
by mmstick 9y ago
Except that the US, a major proponent of modern medicine, ranks very poorly compared to other nations in the infant mortality charts -- especially against countries that prefer natural non-western medicine, and life expectancy is clearly li
50.
by mmstick 9y ago
> The thing is that style lets you ignore errors in cases where the error isn't gonna happen. That's usually bad, but in games it's often fine because you control everything. The equivalent in Rust requires an `unwrap` of
51.
by mmstick 9y ago
You clearly don't read what you write. > I would love to use Rust in games (I currently work in games) but it's not clear that it would work out. There are many contradictions in your posts on here.
52.
by mmstick 9y ago
Seems you need to learn what trolling and logic are before using those terms.
53.
by mmstick 9y ago
Just check out Google's GitHub repository.
54.
by mmstick 9y ago
You've living in some serious denial. You were given a point that proves that your line of thought is incorrect, and you continue on to completely ignore that point by stating that it is correct. So tell us, o'wise one, why is tha
55.
by mmstick 9y ago
This is just outright denial. Bethesda titles are rife with segmentation fault galore. Even their most recent titles suffer the same terrible CTDs as all of their previous titles.
56.
by mmstick 9y ago
There's already a few games written in Rust on Steam's Greenlight program. SHAR was even greenlit. Stating that it isn't clear that it would work out is basically stating that you are choosing to ignore that it has and is bei
57.
by mmstick 9y ago
I had zero issues learning and then creating software with Rust shortly thereafter. In fact, we even have recent threads in the Rust user's forum from people that have picked up Rust and already have some software solutions implemented
58.
by mmstick 9y ago
The HTML pages are generated dynamically from content in my database, in the same manner that Wordpress works. Once a page for a URL has been generated, it is indeed gzipped with zopfli and stored in a concurrent hash map so that future req
59.
by mmstick 9y ago
Use of unsafe in Rust is not required or recommended in most, if not all situations. That said, auditing a handful of small unsafe blocks is easier than auditing an entire project.
60.
by mmstick 10y ago
This is the same line of logic and statements repeated by C and C++ programmers that shortly thereafter get showed up with a list of CVEs in their 'modern C/C++' projects. Remember the recent Curl developer PR disaster?

More ›