When Firefox was new it was considered a controversial skunkworks project. The idea that Mozilla might not be an integrated suite anymore upset a lot of the existing users, believe it or not, especially as Firefox bore a rather strong resemblance to the primary competitor at the time..... Internet Explorer.
Firefox is caught between the rock and the hard place that many products get stuck in: a competitor comes along that leapfrogs them with a design that appeals to the majority of the market. But it also is disliked by a minority of the market. They pretty quickly lose the majority to the competitor and are left with the ever-shrinking minority that vocally disagree with any change.
This isn't like "oh, I can eventually break this lock by smashing it", it's "this lock opens if you tap it in the right place". It takes seconds, and requires nothing in the way of fancy technique or specialized tools.
Yes, we all get it, any lock can be defeated - but this isn't the right story to use that stock comment on. This isn't someone smashing a small lock with a big hammer - this is someone demonstrating how defective a particular lock is, and it makes for an entertaining little video.
Do you have any idea how incredibly valuable "metadata" is for signals intelligence?
Yes. What's your point?
That's more or less what he just said, so I'm not sure how rewording it makes it "forgivable"...
Outlook is used by big organizations that don't seem to know any better, there is little to no chance of them moving to Mozilla.
However most others will use web based tools such as GMAIL just because they are just as handy as any application. With the fact that it won't fill you hard disk up.
I owned a '99 Accord V6 from 1999 to 2007 which was really bulletproof. I think EGR valve and the alternator went out, but both were replaced under some special extended warranty.
I expected the tranny to go out on that car, but I sold it to a guy who drove it for a year and then sold it to someone he knew who was still driving it as of a year or two ago, no tranny issues.
I also owned a 2003 CR-V for about two years -- no problems with that vehicle, but it got sold when we upgraded to a 2005 Pilot. The Pilot was equally reliable, but I think some part of the front end drive system got worked on -- it was my wife's car, so I don't remember the details. We sold it for decent money last summer when she bought an Acura MDX.
Honda actually settled a class action lawsuit regarding oil consumption -- http://www.autoblog.com/2013/1...
I know a guy who owned two VWs with quart-a-month oil consumption, told by the dealer that was normal. How that's normal for anything that's not two cycle I'll never know.
Luckily, your average McMansion has 5-8 bedrooms, and thus, can easily house a small assistd living center.
You must be a wiz at Ad-libs.
You analogy is poor. Shoes are not meant for addons and plugins. Unless someone say causes a shoe failure because of a faulty third partly shoelace.
With cheap fake shoes with Nike logo, Nike and law enforcement can go after the rip off. As for the 3rd party apple add on. Well they just happened to make a device that fits in the wall, and fits in an iPhone. The fact you put them together is your own fault.
Well most larger companies that have salespeople who will just blatantly lie about their skills and resources. When they try to interview someone who is honest, they look like a bumbling idiot.
So let me grill you on industry buzzword x. I haven't heard of x before. after you look into it, you realize it is the same thing as other industry buzzword y, which you had decades experience in.
Yes, that is very common. It is chapter 1-3 then jump to the end of the book.
I once had to work with some code where they guy purchased a database engine for some software he was working with. Then he skipped using Database SQL Commands to manage the data, and went straight into direct library calls to the low level engine. Creating tables without table definitions, and the data was in essence unreadable across systems. Any change and reporting required coding the system to parse the data.
While reading the instructions Chapter 1-3 were about setting it up. End chapters were about using the low level stuff for last resort.
He thought he was mr. bigman for writing such low level library calls. But it was pure crap, that made the product tough to manage, and any chance requires hours of code analysis, to make sure it got the right data.
Before flash we had Java Applets, or Active X, after that and before HTML 5 there was an attempt to make silverlight useful.
Flash had all the GUI elements we wanted, easy to code, and loaded relatively quickly and used a lot less bandwidth than other methods. Adobe went out of its way to make sure it ran on major OS's and browsers.
Until HTML 5 HTML didn't have too many way to handle Vector graphics, or animations. Not blaming early versions of HTML because with average speed being a 9600bps modem. Its early design were good for document delivery. However by the late 1990's HTML became an Application Interface protocol, you can complain about that, but it happened and it won't go back. Flash was the only decent choice for richer set of data.
Now there were cases where Flash was used where it shouldn't be. A lot of stuff you can do in HTML 4 was done in flash. But that doesn't make flash a bad product it was the best tool for the time.
Today not so much, and it should be time to sunset it. But to say it stunk is giving it a gross disservice.
I think US car quality went into decline with emissions standards and ever-escalating UAW labor costs that forced them to cut engineering quality to maintain margins. There was also probably something of a monopoly mindset where foreign brands by and large were a lot less available and not desirable by American standards (small, slow, etc).
It's funny, but I've heard horror stories about Mercedes reliability and few positive things about Audi. BMW I hear mixed bag stories -- expensive to maintain, but not completely unreliable, either. My wife and I owned a VW Jetta 20 years ago that was junk.
We've had excellent luck with Honda, but my understanding is they've had their own problems -- "a quart of oil a month is normal" and Toyota has had its sludge problems.
Dropping support doesn't mean it won't work. It just means if it doesn't Google will not help you to try to get it to work.
If you want to compile it, and adjust the dependencies so it works with 32bit. More power to you. Google just won't bend over backwards to make sure all the plugins work with you or crash after you fill up a bit too much ram.
for this to get "noticed"?
so much for open standards and open source software... 'its safe. you can look at the code yourself"... it took two and a half fucking years for someone to do just that.. and just to find an easter egg, not an embedded and obscured vulnerability.
No, it didn't take 2.5 years to get noticed. Look at the comments on the final commit, it was noticed and commented on by another team member the same day it went in. https://github.com/http2/http2...
The public didn't notice, but I'm sure many people involved in the project did... the commit wasn't in any way obscured. It just wasn't interesting enough for anyone else to notice.
It is easier to change the specification to fit the program than vice versa.