9 ms·
Virtually Unlimited Memory: Escaping the Chrome Sandbox
- Despegar 8y agoUnrelated but does anyone at Google still work on Blogger or is it going down the Google Finance path of neglect and eventual shutdown?
- techntoke 8y agoPersonally I hope it goes away. I would like to see Google focus on enabling bloggers and site creators to host their own sites and work to build and automate open source projects into their cloud products. There are so many static site frameworks for bloggers at this point that it would be ideal for them to do something similar to Netlify and work on great themes for Hugo or other static site generators.
- coldtea 8y ago>Personally I hope it goes away. Yeah, let's let millions of words, and thousands of invaluable posts go to bit rot...
- techntoke 8y agoThere are already a lot of tools for migrating Blogger sites. I'm sure they could setup a migration path to their free cloud tier.
- dcbadacd 8y agoYou're assuming every blog is cared about by its owner, what if it's just the readers?
- snazz 8y agoSwitching it to read-only/static and offering migration paths would satisfy both parties then.
- arthur_pryor 8y agoif you like something or think it's important, and you want the internet to preserve it for posterity, force it to be crawled by the wayback machine: https://web.archive.org https://web.archive.org (usually stuff i want to save has already been crawled, but i always find it satisfying when something i plug in there hasn't been archived yet)
- Waterluvian 8y agoI'm going to guess around 99% of bloggers don't want to think at all about site creation and hosting. They want to buy/pick a theme, modify it a little, and focus on the reason they're there in the first place.
- techntoke 8y agoAnd this could be accomplished. Check here for some solutions: https://gohugo.io/tools/frontends/ https://gohugo.io/tools/frontends/ GitLab already integrates with Hugo for one-click site hosting and deployment using Pages: https://gohugo.io/hosting-and-deployment/hosting-on-gitlab/ https://gohugo.io/hosting-and-deployment/hosting-on-gitlab/
- Waterluvian 8y agoWhat percentage of bloggers do you suspect meet the "assumptions" criteria on that page? I'm fascinated by how tech people perceive the other 99% of web users/content creators.
- techntoke 8y agoI'm not saying it is perfect, but it could quickly be made ready to be as simple as Blogger is today.
- joshuamorton 8y agoShort of being hosted for you, no, it simply can't.
- Etheryte 8y agoI've used Blogger on a semi-regular basis, say, once a month for countless years. It still receives occasional updates every now and then, last time last year if I remember correctly. So there's certainly maintenance crew assigned to it, even some new features have been added. I do agree that it's a pretty niche product in their lineup these days.
- pcwalton 8y agoThis is yet another use-after-free in C++ code. It's modern C++ code written by excellent programmers following state-of-the-art security practices. Smart pointers, lambdas, you name it: it's all there. Yet a critical memory safety vulnerability still slipped through the cracks.
- saagarjha 8y agoNote that the bug was caused by broken code that creates an unsafe, unretained reference to a smart pointer.
- pcwalton 8y agoWhich you do in C++ every time you use an &-reference.
- saagarjha 8y agoBut that's not modern C++ anymore–the whole point is to have RAII manage your pointer's lifetime so it doesn't dangle.
- pcwalton 8y agoReferences are absolutely modern C++. There isn't a nontrivial C++ program in existence that doesn't use references.
- int_19h 8y agoYes, and most of those references are to locals that are passed as arguments to function calls that will never take their address. In other words, it's pass-by-ref - which is perfectly safe - not pointers. To obtain a reference to an object that is managed by a smart pointer, you would have to, at the minimum, explicitly dereference that pointer with *. In most cases, this also happens in an argument context, and the caller will maintain the pointer. It breaks when the pointer that's managing lifetime is a part of mutable state that the callee can touch somehow without returning - then it can cause the object to be freed while still holding a non-counting reference to it. At that point, you basically need something like Rust lifetime/ownership tracking to prevent such unsafe situations from happening.
- ramon 8y agoI knew about this unlimited memory for years Chrome uses all the memory it can get. This is why I was testing firefox the other day.