Subsequently I saw this article that seem to indicate there was a stance to potentially remove the API all together if Chrome sees fit.
https://www.theverge.com/2019/...
If Chrome has plans to remove the FileSystem API if it sees no legitimate use outside of the aforementioned discovery technique, would this have any impact on the FileReader API in any way shape or form? I only ask this as the FileReader API is key component of a major web project of mine.
I would be lying if I didn't say that it gets annoying to learn on this site about all the crappy shit MS has been pulling with Windows 10 since it's release. If my laptop hadn't fried over a month ago I don't think I would have to worry about this as much but since I needed a replacement device asap and most of us still have that one program that only runs on windows (for now, anyways), I had to bite the bullet. Thankfully there are some dedicated to finding this crap and letting the rest of us know.
What I want to know is where is companies like Walmart, Amazon and others alike when it comes to things like this? If AT&T is funding Rubio's campaign, you would think that sites that provide online sales would provide "anti-funding" to candidates who would then voice their "paid for" opinions on having the bans overturned and stopped? The more people you can get online, the more likely you are to make sales.
Just a thought...
I had planned on seeing the movie but after reading the reviews I'd probably have to save the being illegally downloaded is the best thing for its viewer count right now! lol
I still have an AOL email address. Have had one for quite some years. I only have it for the same reason I have multiple different web browsers on every machine I own. Just like the browsers, use one for goofing off, another for serious stuff and so on. It's not that I am paranoid or anything, I just consider it good practice. Just like I here from the end users of old software I work to replace and make better, "just because it's old doesn't mean it doesn't work..."
Subsequently I saw this article that seem to indicate there was a stance to potentially remove the API all together if Chrome sees fit. https://www.theverge.com/2019/...
If Chrome has plans to remove the FileSystem API if it sees no legitimate use outside of the aforementioned discovery technique, would this have any impact on the FileReader API in any way shape or form? I only ask this as the FileReader API is key component of a major web project of mine.
I would be lying if I didn't say that it gets annoying to learn on this site about all the crappy shit MS has been pulling with Windows 10 since it's release. If my laptop hadn't fried over a month ago I don't think I would have to worry about this as much but since I needed a replacement device asap and most of us still have that one program that only runs on windows (for now, anyways), I had to bite the bullet. Thankfully there are some dedicated to finding this crap and letting the rest of us know.
What I want to know is where is companies like Walmart, Amazon and others alike when it comes to things like this? If AT&T is funding Rubio's campaign, you would think that sites that provide online sales would provide "anti-funding" to candidates who would then voice their "paid for" opinions on having the bans overturned and stopped? The more people you can get online, the more likely you are to make sales. Just a thought...
Time to break out the Ratchet and Clank games again! :D
I had planned on seeing the movie but after reading the reviews I'd probably have to save the being illegally downloaded is the best thing for its viewer count right now! lol
I still have an AOL email address. Have had one for quite some years. I only have it for the same reason I have multiple different web browsers on every machine I own. Just like the browsers, use one for goofing off, another for serious stuff and so on. It's not that I am paranoid or anything, I just consider it good practice. Just like I here from the end users of old software I work to replace and make better, "just because it's old doesn't mean it doesn't work..."