skysight-inc/HackerNews huggingface dataset:
Reality Check: What Does, and Doesn’t, Protect Your Smartphone
I never spent that much, but I upgraded a 4MB RAM 486 in '94 to 8, then 16, and then 32MB (at $200 each, waiting a few months between each purchase while RAM prices were dropping). Once I got to 32MB (the most the PC could hold), I could run Linux, X11, emacs, gcc, and bash at the same time without swapping, which was about a 10X speedup.
> External storage seems to be pretty rare on Android though?

Not too rare. Google doesn't like it, so their stuff usually doesn't have it, but Samsung, HTC, and LG seem to have it in most of their flagships, anyhow. Maybe a generation skipped, here or there. It's not guaranteed, but not rare. I checked some budget phones from Blu, for the other end of the price spectrum. Some of those have microSD slots, too.
It's very basic. I can tell it to run Visual Studio Code but I can't tell it to open a specific project using Visual Studio Code.

I can't tell it to open the terminal and activate a Python virtual environment (let alone open Visual Studio Code built-in terminal and activate the env).
Yes and no.

Dressing abnormally does indeed show that you're either unfamiliar with the norms in the industry or you're deliberately violating them. Agreed.

In finance, it's sort of reasonable to be concerned about someone showing up in jeans and a hoodie. A good part of that job is being able be "corporate" and adhere to norms. If you can't do that in an interview, how will you treat clients?

In a coding interview for a tech company, adherence to social norms is not particularly valued. Weirdness is tolerated, if not celebrated. So it's fairly different.

Tech companies would be far more accepting of a candidate in a suit than a finance firm would be of a candidate in jeans and hoodie. That said... it's still probably best to just avoid the risk of subconscious (or even unfair conscious) bias.
Thanks for sharing! Your article is what I was looking for and didn't find when I was working on the audio :) That is an interesting approach which I will definitely try.
That's not yak shaving. Yak shaving is trying to fix issue A and running into issue B. So you try to fix issue B and run into issue C, etc.

This post is about engineering a future-proof solution rather than fixing bugs.
Why would echo chambers, where people are surrounded by those who think like them, convince anyone that they are alone in their beliefs?
I wonder if you could tell it to open a Workflow automation and have the automation perform that - would be nice.
It works on my old Android 5 phone in Chrome 58. Amazing that it's supported so quickly at this stage of wasm development.
On the other hand I pretty well fit the implied description of someone who would go on to be very successful and yet I did not. I'm doing okay. I took my shots and they didn't work out.

My class valedictorian, in a bizarre coincidence, lives next door to me (even though we moved across the country and didn't plan it). He is a very rich ex VC who now has a decently successful startup going.

So as much as I would like to use this article to prop up my ego...
Wow, fantastic work!!
> SoftBank's endgame is here...

I don't think there is an endgame. Softbank simply wants to grow its wealth over time.

> Instead of doing something a la YCombinator?

YC is not scalable. After a big long process handful are selected who qualify for a small amount of investment and only handful of them succeed. At least by stage 1 hardly ~ $500M will be invested and Softbank has like $$$$$.

Much better to wait and let YC do the filtering and once you see something is successful invest in them for a long term gain.
They aren't Japanese companies like SoftBank, so they don't need to be as concerned specifically with the yen. Though you can be sure that Apple or any large company with foreign cash flow actively manages currency risk.
When Colleges Dangle Money to Lure Students Who Ignored Them
Will you guys follow the trend recently and Open Source your code base?
What? He was caught spamming and defrauding customers on the App Store, and under the pressure of the developer community that believed his story about a "friend" using his credit card/hardware/name they actually gave in and would have let him get away with it... All for the small price of admitting that at the very least he should have read the e-mails they send him before suspending the account.
I think that the price is fair: Apple's Automator, even shell scripts with the OS-supplied "open" command, provide significantly more functionality for quickly setting up a workspace. This tool's worth is the convenience of not having to write such an automator/shell script by hand.
Linapple – Apple IIe emulator
It's common in machine learning to define a parameter space $\Theta$ that is a subset of Euclidean space with a number of constraints. For a simple example, $Theta$ could be an elipse embedded in $R^2$. In existing Haskell, it is easy to make $R^2$ correspond to a a type, and then do automatic differentiation (i.e. backpropagation) over the space to learn the model. If, however, I want to learn over $\Theta$ instead, then I need to completely rewrite all my code. In my ideal language, it would be easy to define complex types like $\Theta$ that are subtypes of $\R^2$, and have all my existing code automatically work on this constrained parameter space.
I don't. I would like to live in a world where no one ever thinks it.

I think the only way you get there is by keeping dialog open with the people who do think it. If you refuse to listen to them, you strengthen their belief that they're seeing something other people are unwilling to look at.

And I think trying to "no platform" those people only strengthens their rhetorical position, making it easier for them to extract sympathy from moderates, which normalizes rape culture and quite possibly leads to more rapes. Which is really tragic.

But all of this is just a smaller part of a general failure of feminist policy to do anything with perpetrators besides punish them. Restorative justice is starting to catch on in feminist circles, at least in terms of lip service. But it's a tough sell, because it's completely at odds with the basic feminist methodology of "Step 1: Separate the situation into Oppressor and Oppressed. Step 2: Direct all available resources towards the Oppressed. Step 3: Fuck the oppressor up, if you can. Though you probably won't be able to. #lesigh #patriarchyamirite"

Of course, that is totally understandable. When you live in a society that systematically fails to punish perpetrators, and willfully ignores your calls to punish them, where else does that lead besides a laser-focus on self care and becoming psychotically obsessed with trying to punishing perpetrators?

And Men's Rights has a totally impoverished accounting of the situation, being able to say little more than "Not all men!" and "Women are perpetrators too!" which doesn't advance the dialog at all either. Those are orthogonal situations, and don't address the underlying issue which is that the victim/perpetrator dialectic obscures the root of violence, so it can never be pulled out.

We should all listen more carefully to the black civil rights community, who is leaps and bounds beyond the rest of us in drawing a nuanced picture of violence and ways to see through it to community healing.
What kind of printing, paper? T-shirts?
See bos's comment above. It's mostly just poor relative to what I wish it had. You can see the subhask library for a small taste of what I wish it had.
The other strength that Go has over D is that Go, being used by Googlers, is much more likely to have better networking support. Two examples come to mind: HTTP2 support (Go was used for either the first or second implementation of that and has standard library support), and TLS cryptography, where Go has it's own suite written by experts, where a good portion of the non Microsoft ecosystem relies on OpenSSL. For web/app servers, CLI tools, and networking stuff, I think Go has a strong set of options. Go also has a nice cross platform story for that subset of programs (networking and CLI tools).

That set of good internet sensibilities is what attracted me to Go in the first place, and why I still like working in it in my spare time. If D has a similarly strong story in that area, I'd love to know about it.
Bare metal in this case is far from being 'Bare' or 'Metal' for that matter. Impressive none the less.
Sounds like a lot of good work.

But, in "Git repo", what the heck is a "repo"? A repossession as in repossessing a car?

In the OP with "Everything you want to know about Visual Studio ALM and Farming", what is ALM -- air launched missile? What do air launched missiles and "farming" have to do with Visual Studio?

To Bill Gates and Microsoft: For my startup, I downloaded, read, indexed, and abstracted 5000+ Web pages from the Microsoft Web site MSDN. That took many months. Then I typed in the software for my startup, 24,000 programming language statements in Visual Basic .NET 4 and ADO.NET (Active Data Objects, for getting to the relational data base management system SQL Server) and ASP.NET (Active Server Pages, for building Web pages) in 100,000 lines of typing. For that work, all of it that was unique to me and my startup was fast, fun, and easy.

Far and away the worst problem in my startup, that delayed my work for YEARS, was the poor quality of the technical writing in the Microsoft documentation.

Some of the worst of the documentation was for SQL Server: Gee, I read the J. Ullman book on data base quickly and easily while eating dinner at the Mount Kisco Diner. But the Microsoft documentation was clear as mud. Just installing SQL Server ruined my boot partition: SQL Server would not run, repair, reinstall, or uninstall, and I had to reinstall all of Windows and all my applications and try again, more than once.

Quickly I discovered that documentation of logins, users, etc. were a mess: Basically the ideas seemed to be old capabilities, attributes, authentication, and access control lists, but nothing from Microsoft was any help at all. Eventually via Google searches I discovered some simple SQL statements, I could type into a simple file and run with the SQL Server utility SQLCMD.EXE; that way I got some commands that worked for much of what I needed. Now those little files are well documented and what I use. For getting a connection string that worked, again the documentation was useless, and I tried over and over with every variation I could think of until, for no good reason, I got a connection string to work. Once I tried to get a new installation of SQL Server to recognize, connect to, and use a SQL Server database from the previous installation of that version of SQL Server, but the result just killed the installation of SQL Server.

Again, once again, over again, yet again, one more time, far and away the worst problem in my startup is making sense out of Microsoft's documentation. I found W. Rudin, Real and Complex Analysis fast, fun, and easy reading; Microsoft's documentation was an unanesthetized root canal procedure -- OUCH!

So, again, once again, over again, yet again, one more time, please, Please, PLEASE, for the sake of my work, Microsoft, and computing, PLEASE get rid of undefined terms and acronyms in your technical writing. Get them out. Drive them out. Out. Out of your writing. Out of your company. Out of computing. No more undefined terms and acronyms, none, no more. I can't do it. You have to do it. Then, DO IT.
That's certainly an unusual request/demand. On the other hand, it seems clear that Apple didn't make a mistake. Even if the Kapeli guy wasn't personally responsible for the fraudulent activity (but there's some evidence he might have been), it still occurred, on an account using the same credit card as his, and it was reasonable for Apple to initially assume the accounts were operated by the same person and ban them. Further, the specific "accurately stated" language the rep suggested, about the accounts being linked and trying to unlink them, seems to indeed be accurate. So is it that unreasonable to ask him to make a statement to that effect?
The issues are marked as "won't fix". The only responsible course of action, IMO, at that point is to publicly announce the vulnerability.
All of it and even more could be done with Automator.
Wouldn't it be better to have students learn on hardware itself? I guess if the chips are write only or are too hard to flash it would make since. Or if cost was a limiting factor.
I've always thought of git blame as a bit of Linus personality infusion into the git CLI. Aliasing that to "praise" kind of misses that bit of fun.
1. I'm not saying a week for preparation overall. I'm saying a week to learn the core algorithms and data structures. Frankly, that's probably much less than a week to learn.

2. Yes, it does throw false negatives. Lots of people get hired with zero prep though. I generally say about a month of prep is where you hit pretty low returns from more time. But that doesn't mean that you need a month, or that a month will be enough for you.

3. I'm not sure I see your point here. If coding interview prep is a different skillset from coding competitions, then you wouldn't do coding competitions in order to do interview preps.

4. Some candidates do shut down because it's not what they're used to. A well-trained interviewer can mitigate this to some extent (not always). Some people will also shut down at a computer. Interviews will always be an artificial environment and people can freeze for different reasons. At a whiteboard, it's often a bit easier to unfreeze candidates and create a happier atmosphere.

5. That's fine. As long as I can read it, it's fine. And if I can't read it and you can explain to me what you're writing, that will also work.
> don't promote this fraudulent* developer

He WAS fraudulent, however he still makes a useful tool and seems to have since corrected his ways, so I'd give him a second chance.
I'm not so sure about that. Being CEO of a startup is not as glamorous as it is in the west, but money is available here for startups. After I finished my contract teaching English in Japan, I was torn between going back to programming or opening a brewery. Money would have been no problem on the brewery side. Even just casually exploring the situation, I had more interest than I knew what to do with. I was even offered a building to house my brewery.

As some other people have mentioned, I suspect SoftBank has a specific goal in mind and is buying up companies that give them particular capabilities. They're not just investing with the goal of getting a return. What their ultimate goal is, I'm not really sure, though.
"Maybe you ran your SQL query a few times, fixed the errors you got, eyeballed the results, and called it a day. That’s not good enough for code integrated with a product."

Biggest lie ever. That's pretty much a production-quality code here.
1. Well, how could you enforce this? How do you know a project is open source?

2. Dash was pulled from the App Store due to conflict between Kapeli and Apple. See the links in the comments above for details.
That has nothing to do with what a "product" is.
I've not used Idris too much, so I can't say for sure. My guess is that the answer is that it could do everything I want type-system-wise, but there are things I want outside of the type sytem that I don't think it could do.

For example, I want the compiler to automatically rewrite my code to be much more efficient and numerically stable (see the HerbiePlugin to the GHC compiler which goes this https://github.com/mikeizbicki/HerbiePlugin). My understanding is that the Idris compiler gets much less engineering work done on it (outside of the type system), and so getting efficient running code will be too difficult.
Like it or not, the average smartphone user's security is at the mercy of their vendor. The pace and priority of updates is not up to the typical device owner, nor do security researchers have any say - it's up to Apple and Google. Fully exposing flaws in the software they write can have a real impact on millions of people who don't have much of an alternative.

If you as a security researcher reasonably believe the vendor has neglected to patch the vulnerability, and you release exploit details, you have made things less safe for security-unaware users. There's no way around that. You already gave the vendor the opportunity to fix the problem. Now you are giving attackers the tools they need to take advantage of it.

You and I might care about abstract principles of corporate responsibility, but the typical user just wants to avoid getting phished, and I can't help but feel open disclosure has a lot of potential to harm them. I hope it's worth it.
I remember having these kinds of discussions with coworkers in a previous job where I did Clojure daily.

I don't necessarily want to comment on the particular details here. You may agree or disagree with elements of any one particular style guide; many depend on your team and audience.

With that said, I would make these comments. First, your team might find value in choosing an existing style guide and updating it as you go. Second, it might use pairing as a way of letting these decisions happen organically.
I'm pretty sure it was for a product (server side), not an internal dev tool. Back in 2000 one of my roommates was an intern with the VS team and he said a lot of the devs were using emacs.
Porn was alive and well before. Forums as well. Blogs came later, if I remember right. Online gaming existed, but was much smaller (of course).
Approval ballots is just a special case of ranked ballots with only two ranks, so as far as considering and honestly rating a large number of candidates is concerned, it shares any problem ranked ballots have.

While there are some good arguments for allowing ties in ranked ballots (unforced vs. forced preference), I think there are pretty big problems with forcing tied rankings.

> If it can handle proportionality almost as well as single transferable vote

I don't think it can, but because there is no clear mapping between actual preferences (or preferences that would be provided on an unforced preference ballot) and approval ballot (or any other limited-rank-preference ballot) markings, that's a hard empirical question that's not really analytically addressable.
> A lot of big corporate projects are guilty of just throwing everything in one tree like this where for some bizarre reason you are checking out jpgs and video files.

Would you want to build chrome without it's icons for bookmark folders, the launcher, etc.? No?

What about a game without it's intro videos? Even if you need to debug a crash during the initial intro, related to playing said video?

Some people prefer this kind of content to be managed with a different, media focused version control system, or a separate tree, but now you have 2+ disparate distribution / version control systems to try and keep in sync. You do have options like git submodules now for some VCSes, but I haven't been impressed with their workflow, and they weren't always an option. I will gladly burn several gigs just to simplify my workflow - I've got the spare SSD and bandwidth. I've had fully built checkouts in the hundreds of gigabytes range.

And don't get me wrong, "hundreds of gigabytes" is getting annoyingly large if the IT department skimped and bought me a 250GB SSD. I'll abuse directory junctions to offload some of that onto mechanical drives. This is relatively fire and forget though - multi-repository is not.
I love it! A minor question: is there any way to have profiles, so to speak, so that I can switch between official and 'casual' online identities?
Git has submodules too and teams usually have access control on the main server used for sharing commits.
> makes me dread it

What you're experiencing here is a lot more equivalent to someone putting up an HTML page that contains links to .exe binaries to run a 3D game. Except with WebAssembly, you get to skip the downloading .exe and executing it in a safe sandbox steps.

The .exe binary wasn't open source before, and it isn't now.

So I don't see why WebAssembly is causing feelings of dread for you.
This seems... maybe a little overblown.

I mean, considering I program in React every day, I find this characterization of Facebook's engineers maybe a little insulting. They seem to be perfectly aware their tools are usable by others, and probably went out of their way to make them as usable as possible by others.

Anyways, whatever, my two cents are a lot less passionate than yours, so carry on.
Amory Lovins on clean energy and rare earths
How is the clustering of these articles actually work?

Pretty interesting!
A mixture of some good observations... with some regretabble bits of fanboy-ism thrown in. For example:

Don’t. Give. Up. Ever.

What they’re testing is your ability—and your willingness—to tackle problems that seem completely baffling. They are looking for you to keep working toward a better and better answer. If you’re ever about to give up remember this: The interview process is designed to challenge you, and even the best candidates feel “stumped.” The question is this: What do you do next?

Just when we thought the fad had finally crested on this patently useless, and more to the point, gratuitously toxic style of interviewing... here's another puff piece to keep the cargo cult going for another 12 months or so. As if the interviewers (themselves most likely just a couple of year out of college) could even hope to simulate the pressures of genuine, real-life, high-pressure technical or operational dilemmas through the device of a made-up puzzle problem or two.

Especially since, about 97 percent of the time, the quality and caliber of grit that brings the most value in business environments isn't of the "solve this made up problem, which I know the answer to (but am hiding from you so I can, you know, watch you think on your feet) -- or hit the road, Jack" variety. But rather of the "no one has any idea where this problem came from yet, let alone whether it's even really solvable" sort. And for which the most effective response, in the vast majority of cases, is decidedly not to go down the next immediately visible rabbit hole and fight the problem to the death... but rather to find a way to avoid going down said rabbit holes in the first place. (Typically by revisiting the stated requirements, and finding what the true customer need is, for example).

And if people think they can simulate these kinds of dilemmas -- let alone "test for" a candidate's ability to tackle them, in an interview context... frankly, they're kidding themselves. Which, being as the true "purpose" of these questions seems to be to buttress the egos of those asking... is apparently perfectly fine, in some quarters.
> Really interested to hear user feedback from today's #istio announcement and where it will have the biggest impact.

Okay: I immediately deeply, profoundly, bitterly hate and despise your announcement and for just one, really simple, dirt simple, but totally unforgivable reason: What the heck is a "microservice"? You never said.

That word, microservice, is not in a standard English dictionary, so you are writing undefined jargon, gibberish, junk and not English. You are insulting me and even worse yourself.

Instead, write English. Get rid of the undefined jargon.

Got it?

This was a difficult lesson?

> the biggest impact

Until you learn to communicate at, say, the late elementary grade school level, e.g., learn to write English, the impact promises to be minimal.
Being cautious and keeping in mind that Son Masayoshi has not had a stellar track record of deploying capital outside of Japan and in North America. Majority of his big headline acquisitions have not played out. Please correct me if I'm wrong, I recall these points from an Financial Times article a few years ago.
Or by hand. Does not mean there's no value in a streamlined solution.
Grid+: ConsenSys Starting Electrical Utility Using Ethereum
In other words, it's because Go has the backing of a huge software company, while D doesn't.