skysight-inc/HackerNews huggingface dataset:
Method count has nothing to do with size.

Look at your own link:
Java => 16,306
Scala => 67,608 (Already in multidex territory)

Proguard removes most of those methods, but you'll still need multidex for any non-proguard build like tests and debug builds.

And if you do grow an app past the point of being trivial as that example is Proguard gains will not be nearly as drastic

Multidex on pre-Lollipop ruins app start time, and only very specific types of apps can go to targeting minSdk 21

Predexing with Multidexing and Proguard are also slow for development for non-trivial apps. Your measure of "how long it takes to pick up a phone" is far from scientific", but to compare, not a single app non-trivial app I've worked on is so simple that installing a fully compiled APK over ADB would be less than a 5-10 second process.

That would leave 0-5 seconds for the entire app to build, proguard, and predex (with multidex). Not possible.

Gradle 2.2+ has the SDK download feature, and before that everyone I know was already using "sdk-manager-plugin", not even for convenience on dev machines (it's not that often that SDKs come out after all), but for CI builds.

Protify is not Scala exclusive if one really wants to use it, but JRebel also has a more mature Instant Run solution. Instant Run type features are useful for very specific types of changes that I don't find to be very common anyways. The layout editor + proper use of the edit mode flag and the tools namespace can already reliably replicate half of what I see instant run and co used for, with the added benefit of having even speedier development cycles.

Also: Typed resources are part of Google's databinding library, not that I know anyone who uses findViewById when we have libraries like Butterknife

To me using languages other than Java for Android dev is a risk about balancing mindshare, UX, and continued support for workflows in Android.

Kotlin has mind share, UX doesn't suffer, and it's gotten big enough that while Google has not come out officially and said it's supported, it's mindshare is large enough that Google knows that efforts like Jack and Jill cannot adversely affect workflows (The transformation API is great example, if projects like Realm, Dagger, and co didn't have so much mindshare I doubt it'd be much of a priority for the project).

Scala on Android has a much smaller mind share and is much less proven despite it's maturity, can kill UX a lot easier because of an insanely method-expensive core library which brings in thousands of methods once you use certain features, and is has not gained enough traction to to have to work around Google's plans than with them.

To me the proof is in the pudding, if there were real gains to be had with Scala it'd have more traction than it does.
Sorry, computer, I am not going to war, even if it will rise another civilization.
For reference: https://www.ovh.com/us/vps/vps-ssd.xml

Located in Beauharnois, Quebec, Canada.
GraphiSoft ArchiCAD 20 Crack and Keygen Full Version Download
Yes. It is fundamentally a marketplace abstracted for the end user.

It evolved into this way over time, and I didn't set out planning to build it this way.
Given that they are apparently getting out of the ISP business because of the startup costs involved, I'm wondering how they'll do getting into the car business, which must have even higher startup costs.
Here are a few things that I experience on android.

-When snapchat is foregrounded my phone wont go to sleep.

-Sometimes the camera will just go black, hang, and crash the entire app. I don't know why, im guessing it could be filters.

-Taking a snap with a filter applied sometimes just takes the photo without the filter.

-The memories section is useless, and seems to only exist to keep pictures out of my freely accessible storage.

-Adding things to the images like text or smilies is okay for a single item, multiple things on an image becomes very cumbersome with you resizing things you didnt want to resize.

-the main inbox screen is very cumbersome, tap views a snap, sometimes it lags, and i tap again, only for it to show me a snap for less than a second and disappear. Double tap replys if you just viewed a snap, If you don't double tap perfectly it may think you want to swipe right to chat.

-Inbox keeps getting slower, I get instant push notifications and tap one to go to my inbox, only to wait 2-3 seconds for the inbox to update, sometimes on top of that it hasn't even received the data and i hate to wait for that too.

-Chat and text messages are stupid, You will lose messages because you swipe back to your feed the exact time someone sends you a new message, and kaput the text is gone forever, sometimes messages stay and sometimes they don't and i cant figure out why. I used video chat once and it was a horrible and laggy experience, one which i've never tried again.

-Stories are starting to add ads, which i understand, but the comic event where "the ads load faster than the real content" happens.

-If a story hasn't downloaded the next snap, the app just stops responding until it is downloaded and ready. Most of the time it will register any tap in that frozen state and will skip the snap when the picture/video is finally loaded.

-a few controls like text/drawing color are 1-2 millimeters wide on some phones and makes selecting them infuriating.
It's amazing what people can get up to if they're not being distracted by the internet or other popular media.
systemd-nspawn is great! The workflow feels much more native than Docker on GNU/Linux host. The easy integration with networking, BTRFS snapshots, etc is very powerful.
While I deeply respect Bob Lutz's accomplishments in the auto industry it's clear to me that he's sadly lost touch with reality. He's quite simply lived past his time.

Note that this comes out the day Tesla declared a profit and the stock went up.
Technically, this is not specific to Android phones. It's a hardware flaw and also possible on iOS.

edit: Correct, I was confusing it with Row Hammer.
Editing binaries: easier than it sounds
Years ago a man made a computer program that could compose music. He kept getting told things like what you are saying. That it's soulless, that computers can never make real art, that it has no emotion, that it's just regurgitating patterns, etc.

Eventually an orchestra agreed to play one of the works. People liked it. Until they found it was composed by a computer, and then they hated it. People are insanely biased against computers.

That said, the algorithm was not a neural network. NNs do have problems producing music, they forget long term patterns quickly and so the works are easily distinguishable from human music. But it's possible this could be solved in the future with some new techniques at training NNs with longer term memory. I don't think it's long before the world is full of AI produced music. And you won't be able to tell.
Sadly no, I'm consistently reverting back to my 21ux, the jitter of slow stylus movement drives me nuts on the surface pro 4
Harvard's CS50 Switches from C and PHP to C and Python [video]
Gotcha. Then here's a translation into Scala from the link you provided which I believe maintains the spirit of the clojure version:

object Fizzbuzz
{
def apply (amount : Int) : TraversableOnce[String] =
1.to (amount).map { n =>
(n % 3, n % 5) match {
case (0, 0) => "FizzBuzz";
case (0, _) => "Fizz";
case (_, 0) => "Buzz";
case _ => n.toString
}
}
}

Fizzbuzz (100).foreach (println);

EDIT: When I said "Gotcha", I meant that as in "understood" and not in an adversarial manner. Quite the opposite, actually, as this is a respectful thread which I believe both parties have enjoyed.
Forgive my ignorance, how this is possible on iOS?
That is certainly something I've also come across. This kind of functional style is very readable once you understand it, but it does have a learning curve just like learning what "for(var i = 0; i< length; i++)" means.

I actually did a little presentation to the team about how to refactor a for loop to an self implemented where/filter function to explain the connection. For me, realising that all the where was doing (or at least potentially, there might be some behind the scenes optimisations going on) was passing in the condition for an IF in a FOR loop suddenly clarified everything for me.

In case anyone's interested, this is these are the code steps (javascript)

var people = [{name: 'bob', gender: 'male'}, {name: 'dave', gender: 'male'}, {name: 'sarah', gender: 'female'}];

var getAllMen = function(population) {
var returnList = [];
for(var i = 0; i< population.length; i++){
if(population[i].gender === 'male'){
returnList.push(population[i]);
}
}
return returnList;
}

var males = getAllMen(population);

___

var getAllMen = function(population) {
var returnList = [];
for(var i = 0; i< population.length; i++){
if(isMan(population[i]){
returnList.push(population[i]);
}
}
return returnList;
}

var isMan = function(person){
return person.gender === 'male';
}

var males = getAllMen(population);

___

var filter = function(anyOldList, filterCondition){
var returnList = [];
for(var i = 0; i< anyOldList.length; i++){
if(filterCondition(anyOldList[i]){
returnList.push(anyOldList[i]);
}
}
return returnList;
}

var isMan = function(person){
return person.gender === 'male';
}

var males = filter(population, isMan);

var females = filter(population, function(person){
person.gender === 'female';
});

var females = filter(population, person => person.gender === 'female');
var females = filter(population, x => x.gender === 'female');
Well it worked, I just bought a painting.
> Am I taking crazy pills here?

If you are, then so am I. Could just be all the glyphosate though...
No, that's not what "probably carcinogenic" means. There is a 5 point scale, yes, likely yes, less likely yes, unstudied, no. It has been studied which removes the unstudied. However, they don't say there is enough evidence to say "Yes" or "No."
OpenStack on Kubernetes with CoreOS's Stackanetes
The assumption that Berkeley students are smart makes me say that.
There's an architecture neutral close relative to LLVM bitcode: Google's PNaCl.

"PNaCl bitcode is based to a large extent on LLVM IR as of version 3.3" (https://developer.chrome.com/native-client/reference/pnacl-b...)

It's targeting x86, amd64, arm and mips and shipping for a good while. Seems a bit quiet lately though.
This isn't news. That's why open offices are often so annoying. Good circumaural headphones are indispensable there.
On a side note, it makes me very sad how Wikipedia editors are often pushing some political agenda. I'm relying on it for less and less topics. Clearly nothing that can be affected by US politics or SJW-style controversies.
Is it useful to have a college degree?
Honestly: I think they are spending most of their time moving existing working infrastructure into containerized infrastructure and figuring out how to deploy their blog on k8s. They are working on learning libraries that abstract abstractions.
They're not getting out of the ISP business. Sure, it's been slowed down, but what did you expect to happen when national ISP's are slowing the deployments to a crawl by suing their local governments to try and block Google?
I would say that they have done most of what you ask.

No.
All satellites for many years were only launched as part of the space race between the US and the USSR. Of course there would be no satellite communication without the space program.

https://en.wikipedia.org/wiki/Explorer_1
Well there's quite a few configure file formats in the world. Some are keypairs, some are hierarchical, there's the popular .ini format, and many others of course.

So say you don't really care what's in /etc/ssh/sshd_config, but want to make sure it doesn't have passwords enabled. With puppet you could:

augeas { sshd_config:
context => "/files/etc/ssh/sshd_config",
changes => [ "set PasswordAuthentication no"],
notify => Service[ssh]
}

So basically augeas provides set, unset, match, remove, append, and related functionality for pretty much all configuration types. Then you just each whatever tool you are using (like puppet) about augeas and you suddenly can easily manage 100s of file types.
I don't get it. Why would unaware JSON parsers choke on `Infinitiy`, `NaN` or `-Nan`? JSON has no concept of schema.

So if a parser sees "Inifinity", which it doesn't have any concept of, why would it do anything except treating that as string of a word "Infinity"?
I think you're confusing this with the DrK KASLR bypass using TSX that was also on the frontpage recently. This is specifically a Linux bug, and isn't applicable to iOS.
They published the studies they looked at:

http://monographs.iarc.fr/ENG/Monographs/vol112/mono112-09.p...

I would not say it's a clear yes, but there is some evidence for a cancer link across a range of studies.
> I'm curious how you could possibly lose money in a business like this.

Given all the stories that were going around for a long time about how offering through businesses like this was a losing proposition for most customers (really independent of the truth of those stories), I'm not surprised that there could be trouble making a profit in it.
Hackers for Good: How Anand Prakash Rescued Facebook
Presumably you can use the jog dial off-screen and for any number of things, in which case it would be useful to almost everyone for volume control, scrolling through lists, adjusting values in control panels and so on.

Obviously video editors use them, but I know of professional photographers who find them really useful in moving through a catalogue while editing photos too.
In my entire career (as a professional software developer) I'm pretty sure every employer I ever worked for gained far more from my own personal development off the clock than they ever gained from any training they provided, not least because the main "training" most of them provided was simply a chance to use my skills and develop my experience. I therefore find the whole idea that an employer is somehow nurturing and developing someone in our profession and so should be entitled to everything that person ever does, even off the clock and even into the future, a bit bizarre.

Even if it weren't, employers aren't hiring machines, they're hiring human beings. If they've become so greedy that they have forgotten that, I see no reason our laws shouldn't compel them to treat their employees (and past employees) properly.
Microsoft has been accused of "cheating" on SunSpider before because IE/Edge's dead-code elimination optimizations recognizes particular code patterns in SunSpider:

http://arstechnica.com/information-technology/2010/11/lies-d...

https://news.ycombinator.com/item?id=1913102
Or for certain classes of their customers (maybe governments?) to develop in-house solutions that become "good enough" that they expect to lose those customers in the future.
If they were to, would you buy it?
AI and data are the new oil, so beware folks - when the peasant workers are no more needed, you may want to watch out for the dictators trying to take over the ship.
My theory is that they are getting out off Fiber / ISP business not because of costs, but rather the goal of Google Fiber has been met. Back in 2012 there was a real risk posed by ISPs, however with effective lobbying ensured Net-Neutrality becoming adopted as an official policy, and with next president likely being from the same party. There is no longer need for Google Fiber as it was in 2012. Also maybe there is another technology thats more lucrative which is on horizon and thus Google is recusing itself from making likely to fall investments in optical fiber network.
You're mixing that up with rowhammer. The exploit that this article is about is a bug in the Linux kernel.
How to Borrow Library Books on Your Kindle, Phone or Tablet?
I absolutely agree with you about performance stuff, if you are in a position where milliseconds matter this may well not be the right way of doing things.

Also, to open up another interesting area, Linq operating on IQueryable objects can do some pretty interesting stuff in the background, merging sql queries and the like. I've never looked into if it does anything similar for IEnumerable - although I will should the situation come up.

FOR and IF are indeed valuable, but that doesn't make them not smells. For me a code smell is not an anti-pattern - it is just an indication that something has the potential to be wrong. If you are writing lots of IFs and FORs in your code that might well be fine, but it has a good chance of causing problems. Smells, for me, just mean "justify this decision" - not "never do this".
Heated Debates Ignore an Overheating Planet
Shouldn't the "they trust us" show both iOS and Android versions?
As production technology improves, producing your own resources becomes cheaper than the military action required to take it from others, which gives producing societies an unbeatable economic advantage.

A tribe of pillagers could destroy a hamlet, but could never compete with the resources of a walled down.
Nice writeup. I do think this quarter is a bit misleading because of the 139million emission credit. Howerver, I believe they've done just enough to move the needle and support investor confidence.

By the way, huge fan of HashiCorp Mitchell. ;-)
One thing that baffles me with Google Drive is security and permissions. To go through a folder and all of it's sub-folders to unshare or fix things is a tedious pain.

Plus, all the random cloud apps that require access to all files in Google Drive make it worse.

Object storage with the notion of buckets seems much simpler to manage.

How to others deal with or rationalize Google Drive security?
This is hilarious, I wholeheartedly agree. I cannot stand popcorn in the office, especially since the microwave is a high wattage variant and nobody watches the popcorn so it burns frequently (with the fire department making an appearance recently)
I wonder how many people carelessly run a script that downloads, builds, and executed something with root access. If that zip gets compromised (i.e. The source means harm) there is no end to the pain a careless user can endure. It is like blindly copying and running shell commands you don't understand with sudo rights.

My intention is not to offend the author by the way :). It is to remind people to understand these kind of scripts and their risks before you run them.
That's a very good suggestion. But the reality is that will never, ever happen. Linus and the Linux community as a whole exist in an echo chamber.

They never resort to looking outside their little bubble world to see how others solved problems they are trying to fix. They simply are not capable of that. They constantly reinvent the wheel and reinvent it poorly. They should have simply adopted kqueue, ZFS, dtrace, jail(), etc. but didn't. They choose to refuse to see how others solved problems and use the good solutions of others.

It's one of the most damaging things about that community.
Good thinking! I wonder if it will get patched soon enough
Yes, anyone who is charged with something serious should go to trial. It's expensive, but you're locking a person in a cage with criminals for years of their life (incidentally to be repeatedly beaten and raped, but we can leave aside problems with the CJ system that aren't explicitly plea bargains for the moment), not choosing a floral arrangement.

I agree the extreme and severe punishments exacerbate the problems with plea bargains but plea bargains are bad by themselves, in isolation, even if other punishments are fair.

The government should NEVER be in the business of giving people special treatment and rewards for waiving their fundamental rights because it's more convenient for the government. Everyone has the right to a trial, but people who exercise it are punished. Which means people don't REALLY have a right to a trial. Imagine if the government promised it would tax people less if they chose to avoid engaging in political speech critical of the government. This case is identical to a plea bargain. Except it's less serious, since it's about money, not about jailing somebody.

I'm okay with someone pleading guilty and throwing themselves at the mercy of the court and asking forgiveness. Then it's up to the human beings in the trial to decide how to handle it. Creating a formal system where you do this in exchange for something tangible? Before a trial? No. Innocence or guilt is too important to be bartered like that.
Even the table they presented it on looks like it was lifted from an Apple Store...
Similar experience here. I use iPhone, MBP and iPad. Originally thought that having everything under one umbrella would be a huge help, but the reality is the syncing is such a pain that I never do it. Took me many, many months to even get AirDrop working between my own devices. iTunes is very frustrating to use in managing iOS devices.
You're thinking of Arthur C. Clarke (pedo).
It wasn't condescending at all. On the contrary.

Partly I was tripped up because I have used Meteor and they handle everything for you. Before that I was using PHP and making SQL queries to MySQL directly.

In both of those cases I was able to get directly at the database. What you're saying is that I need a middle-tier that acts as the layer above the database but below the client (obviously.)

You mentioned Node.js. I know what that is and I know it's not a database. So it needs to connect to a database and then pass off data to the client. This is the piece of the puzzle I'm missing in my mental visualization.

I've learned that Laravel works well with Vue so I'll start there.

Thanks!
They aren't getting out of the ISP business; the article notes they are not expanding Fiber to new cities but are pursuing other avenues for providing broadband access.
That's the main issue with Docker right now. They've built an amazing static compiler that works with any language, but there's a question as to whether that compiler is worth 1B.
I have found the Caspian Report tremendously useful for improving my understanding of global dynamics - https://www.youtube.com/user/CaspianReport/videos
Programmatically Open, Create, Convert Excel Files WITHOUT Microsoft Excel
Just as taste is a subjective thing as is often hard to articulate... I think my biggest complaint about that code is that I had to read all of it to make sure there weren't other cases where the card gets eaten. And try to follow what was going on.

Taste-wise, an easy fix for this is to do early exits. Instead of nesting, you could easily do (I'm on mobile so no fancy formatting):

If card is not valid: return message

If user is not valid: eat card; return

Etc

Now that's my personal taste. It makes it way simpler to quickly skim and understand what's going on.
Yeah, here is an interesting experiment.

Take Alphabet's Q2 Earnings[1] and note that in the 3 months ending June 30, 2016, Alphabet generated 6.9B$ of free cash flow. That is after all the expenses they could think up to take out of it like building new data centers, offices, snacks, google I/O attendee gifts, whatever. Now divide that by the number of employees, 66,500. That means that there was just over $105,000 per employee in free cash flow. If they spent 5% of that, on a per employee basis, that would give them $1,750 per month for additional office space for that employee. Really posh office space is like $20/sq ft per month so divide that by $20 and you get 87 square feet of really nice office, add that to the 1/4 of a cube that employees currently get and you have 100 sq feet or a 10' x 10' room for each and every employee.

So no, with a 5% hit to their free cash flow they could give every single employee an office, or at least their own 10' x 10' cube, but they they would rather that money sit in cash or cash equivalents earning basically a couple of cents on the dollar.

Since the investment rate of return is about 2% for cash equivalents, and the productivity rate of return would be on the order of at least 5%, you could say they were being dollar wise and productivity foolish.

[1]https://abc.xyz/investor/news/earnings/2016/Q2_alphabet_earn...