For some amount of time, yes. I have a Galaxy Nexus phone which is now a couple years old. KitKat (4.3) runs fantastically on it, and after experiencing Android L on a new tablet, I really don't care for its changes.
What I have noticed since Lollipop's release in November is that the application updates to the Material UI style (plus whatever else underneath) has greatly slowed down the GMail, Google's News&Weather, Play Store, and Play Music apps on my phone. Since this round of updates, when returning to home screen after running the play music GUI or news/weather, the launcher has to reload all the app icons, and it's actually a few seconds before the home launcher is ready to use. My phone has been fantastic, but the November app updates have just crapped on it.
The frustrating part is that I keep my phone fairly minimal -- no twitter, no facebook app (another POS) -- just to maximize battery life and keep it running fast. All my efforts are wasted now due to the apps I listed above. It sucks, because I really like this phone and don't feel like EOLing it yet.
I liked the default music app from about the G/H timeframe. It worked great for me, was fast, and playback was responsive. The current Play Music app is a piece of laggy shit. I'll just have to try some alternative apps.
What's the crime? A lot of nonviolent crimes are felonies. If I were looking for candidates, my consideration of an employee would entirely depend on what the crime was, and what my legal counsel thinks.
And also, especially in drug-related offenses, the felony limit can be quickly reached by an exaggeration of drug mass. LSD charges, for example, are typically trumped up because they weigh the grams of paper, not the micrograms of LSD on it. Or here in Austin, where a guy was facing PCP possession charges partly based on the weight of the tray of brownies he baked (couple pounds), instead of the mass of PCP actually in the brownies. (But, he did have a bottle/supply of PCP which *was* a serious issue, but the charges based on the brownies was absolute nonsense.)
Something tells me the man from Tacoma is lacks faith in the Omnipotent One (according to doctrine). The FOI request seems a bit
Dear submitter, if you want to include text that says "they have released a video, here's the link" then link to the video, not some ad-laden secondary site.
The video is on youtube, at https://www.youtube.com/watch?...
You know what? Pretty well, actually.
Several years ago on a whim I began asking for discounts everywhere. "Do you have any promotions you could apply to this?" is what I would typically ask. I was shocked to find that most of the time, there is something, like a 10-20% coupon or similar that they can throw at it. Or, if not a direct discount, say at a restaurant, they may give a voucher for a free dessert or appetizer. The worst answer is they say "no, sorry, don't have anything I could do" and you leave it at that.
So, while the peon running the register may not be able to change prices, they are often empowered to provide a discount if prompted.
Python is my go-to language for quick code sketches, framework ideas, etc. That's the power of dynamically typed languages, it's very easy to throw code together to test ideas, and is what I value in "scripting" languages.
As much as I like Python, even with it's quirks like len() is a function on a sequence not a member, the one thing I despise is the whitespace-describes-structure. I have lots hours due to an auto-format of code run amok. Suddenly, all the code following an if-statement is now the body of that statement. It just doesn't make sense to not have block delimeters. With every other meaningful language under the sun using curly braces, why couldn't Python? I like the *idea* of clean code like Python code, and I enjoy reading Python code, but I prefer to have explicit block syntax.
As an aside about spelling mistakes, I agree, and Python doesn't help you there (unless you are reading a misspelled class field). One trick I use to fortify larger Python programs is to define slots on each class to explicitly define the members. If your code accesses a mistyped member name, that name will not be in the __slots__ list and the python runtime will raise an exception. Not only do __slots__ protect you from name typos, they are faster than regular fields for some reason. I've shared this tip with other pythonistas, and nobody else has heard of doing this; I can't believe others aren't doing this, too.
First of all, I'm of the mindset that it's probably best to not list every issue fixed, and especially not list every bug reported publicly. Many bugs reports are bogus, and it's certainly possible for a large number of "reported issues" to detract from the true quality of the current version. For a new product I would never make this information public. But that's neither here nor there since in the OP's situation, they are public. So, let's go with that.
What I would do is based on a Freakonomics episode where a company (furniture company, or appliance company, whatever it doesn't matter) inadvertantly stopped advertising in some of their major-market newspapers. While it was an intern's mistake that this happened, what they found was that there was no impact (i.e. no reduction) of sales in those markets. So while a logical person would say, "Let's scrap advertising in those markets forever and keep the cash," the people in charge instead said "but we *have* to advertise." Preserving expectations/status-quo won out over rational thinking, and the difference was millions of dollars.
I would put a challenge to the marketing and sales departments. If they think public disclosure is hindering sales, let them prove it. Pull the publicly-visible bug tracking for a period of time and if the marketing and sales people are right, sales will go up compared to similar periods in previous years. If, however, customers are unhappy with the "secrecy", take that into account as a ding against the approach. But I'd be firm -- if you pull the bug info, the sales better increase.
Of course, before you issue a heavy-handed challenge to M&S, maybe just ask your existing customers about it. "We are considering pulling our publicly-visible bug tracking/reporting but have no plans to change our update cycle, just the reporting. How does this impact your business, and how does it impact your decision to use Product X?" Use that as a basis to continue current practice, or start the M&S challenge.
I also acknowledge I am anothing but a keyboard jockey in this horse race.
Although they plan to have translators to move old code forward, do you really trust automated translators enough to run them on huge chunks of production code?
Yes, certainly. It's called running the automated translator and NOT blindly checking in the generated code. There's no concern here.
There is never time to do it right, but always time to do it over.