skysight-inc/HackerNews huggingface dataset:
It's not just over tuning, but finding me things I might have missed. Not necessarily popular things, but thinks that appeal to me.

For example, I get emails from Pocket "You saved a popular article..." And I think "Who cares?" Don't tell me what I know, tell me what I missed. YT is similar. It recommends things I've watched. I'm looking for new and interesting and I'm getting yesterday's news? That doesn't excite me.
How did clojurescript use node modules / APIs before?
Not that I know either, but the quality control process is possibly a source of much cost of production. Every part must pass a series of tests during and after production before deemed ready for sale. Every failure of a test costs time and money. These yield rates are either low with low cost manufacturing, or, high with high manufacturing costs. This could be part of it.
You can't handle the checksum
Yes, I've been using edge. Every single Google page has a top bar bullshitting me about how awesome the page will look on Chrome. I dismiss the bar, it comes back in a day. On all Google websites.
You're incorrect, they do not support Wi-Fi. I think you were thinking of the chips in the watches.

I have AirPods, and they were pretty fantastically. I've had occasional issues but it's rare enough it doesn't bother me at all.
So, neat trick: "git clone" your local Dropbox copy somewhere, and you get the benefits of "commit" and "push", but it's local; and then your remote is synced via Dropbox :)
Support Car Neutrality!

Imagine if you could get cars with bigger engines with more power and had to pay to do so.

Imagine if you could get cars built with higher quality generally and had to pay to do so.

And of course countless other differentiating characteristics.

Obviously, if everyone can't have a bigger engine or higher quality or whatever, then nobody should. Everyone should have exactly the same cars and it should be illegal to make them otherwise just because some people can choose to pay more!

Why? Because better hurts our feelings. Why should those able and willing to pay more, get more?
In this case, don't you mean have your frappuccino and drink it?
I like edge because it uses less ram and uses less battery. I can run my VM without swapping like crazy and my laptop lasts almost twice as long on battery.
btrfs snapshots have a lot of gotchas. Quoting myself:

https://news.ycombinator.com/item?id=14724820
Currently, the Grease/Tampermonkey userscript and the Chrome extension driver script are separate entities. We're working to either make them one and the same OR be exclusively driver scripts, and the real work is done somewhere else.

If you want to make this a suggestion that we can track, open up a new issue ticket at https://github.com/yczeng/hackernews-newsfeed.
What am I on about? The new era of the robber barons and how it hurts our entire industry as a whole. I've been in the tech industry for 20 years now and the Ubers of the world make all of us look bad. We shouldn't reward bad behavior or the Machiavellian idea that the end justifies the means. Uber will fail and the new tech bubble will burst. They've proven time and time again that they're incompetent and so far have squandered billions in investments. This will scare investors away from the tech industry just as it happened in the early 2000s. It took years for our industry to recover and here we are again repeating history. Those who do not learn from history are doomed to repeat it.
Check that issue again. Before you posted this they agreed and pushed the issue to the add-ons team. Do not track should turn off Analytics.

But that's not my point. As I said, they could well be wrong, but it's over the top to argue that it's Mozilla's fault for disclosing this in the privacy policy (which apparently no one reads). If you are so privacy conscious that this bothers you that much, the privacy policy should be required reading.
Perhaps he meant that state and local taxes can result in consumers buying from out-of-area suppliers to dodge those taxes, like many "mail-order" operations have always been... including, until a few years ago, Amazon.

This may even still be the case. In CA, anyway, Amazon and the FTB made a deal a few years ago such that Amazon generally collects CA sales tax on sales to CA addresses.
I think what you're seeing is less the Rust community and more the community of computer users that have been forced to use C/C++ software for decades now. Up until Rust, there were many easy reasons why developers could justify their choice to use C/C++. And so users had to live with the frustrations of running code written in those languages because there really were few well-known alternatives.

Now Rust comes along with its safety claims (which are mostly true) and suddenly these computer users have what they believe is a legitimate complaint. They now see the frustrations with running C/C++ software as no longer facts of life but, instead, development externalities that users are forced to pay based on the decisions of the developers.

And so you have a bunch of people who've likely never written much in either C/C++ or Rust who are trumpeting Rust because they're sick of dealing with CVEs, segfaults and all the other 1970s baggage that the C-cosystem imposes. And it doesn't help that C/C++ developers tend to react defensively and take the advocacy as an impugnment of their developer honor. Saying "It's only inept C/C++ developers that write code with UB or memory safety issues. Disciplined developers can write safe C code!" just infuriates people even more since the weight of evidence suggests that any non-trivial C program will eventually have a bug or vulnerability of this kind. Humans make mistakes. That's an immutable fact that we need to take into account when relying on humans to do anything. Programming is a thing that is part of that anything. To err is human, to catch as many of those mistakes as possible is the compiler's job.

But I think both the Rust community and the Rust-resistant community should be wary of those trumpeting Rust who are part of neither of those groups. There are many good reasons to use Rust and some good reasons not to. Often times a hybrid Rust/C solution would be the best. We should be careful to try to take ego out of the decision making process as much as possible. And we should remember that when users are asking for Rust, what they're really asking for is an end to the pain that they've had to deal with. If it can be accomplished in some other way, then that works too.
MP3.com and SoundCloud are not as comparable. SoundCloud has really re-defined how new music is released and how new artists promote their music.
OnlineVideoConverter.com Not Working? Fixed
I love this, it's so great to see here the idea that even in a big city there are more important things than rushing somewhere.
Change Tape to Cloud and I think you're on to something.
> You can just use that if you'd like.

Isn't the ability to just include a js file going away in version 15? react_on_rails already pulls in v8 when all I wanted was for the browser to load it, and it requires I stick my components in a weird place. With Vue, components can live with the rest of the view code and I don't have to write JSX (which I hate), or React's verbose alternative. Plus, whenever I look up information it alsways seems to be geared to node.js users.

A long time ago I wrote a DOM templating engine in like 10 lines of ES5, and what I really wanted was a faster and more complete version of that. Vue fits in much more nicely.
I wasn't directly involved in this decision and I've never worked on our mobile apps, but I do work at Lucid. Almost the entire engineering team can write Scala. About 3 people can write Kotlin. That was a big part of it. The lead engineer on our Android app is also a Scala wizard.
Well..."truly viable" means different things to different people. I'm a devops jock (so build systems never really scare me, and that's probably the nastiest part of React Native) but my background is in application development and I got up to speed with React earlier this year. I built in five days a well-scoped but nontrivial app I'm releasing as soon as I get my LLC and EIN situation figured out (I might Show HN it) and I'm extremely happy with the result. The app works as-promised on Android and iOS; I have some additional stuff to do before I launch the iOS version because theming isn't 100% between iOS and Android, but it was recognizable and usable from the jump and it by-and-large worked as intended.

The downsides are mostly what you'd expect. You're welding together a JS bundle with Java (Android) and Obj-C (iOS) generated projects to create a deployable and that's a little fragile, though it's not really a problem. `react-native link` exists to try to help with that by automating the insertion of dependencies that require going outside of JS (stuff like Firebase or other native-API integrations); on one hand, I've never gotten it to work, but on the other, I know both Android and iOS development separate from React Native so it's totally not something I even think about. That probably also encapsulates most bugs I might run into with packaging, etc. to the degree that it's really hard for me to answer your question. I already know both of those environments and most of how they get wacky; stacking a little on top of that's not really a big deal.

The hardest single thing to do was integrating Firebase because I got some wacky Gradle error, but I figured it out. The second-hardest thing was parsing every JS package (460 packages, yeeesh) in my app so I could make sure I included their licenses in the deployable to be compliant with the licenses (and I am certain some of the licenses I included are actually from the build tools, but whatever). There are 500kB of licenses in my app, hidden in an 'about' dialog box that I expect nobody will ever open, but if that's as hard as it gets...meh.

Debugging is worse than it could be, but it's React/Redux in a very constrained environment, I'm not worried by it. And there are often no platform-agnostic wrappers for stuff (I needed in-app billing as my app is time-limited demoware, and I have two separate codepaths), but let's be real--that's not much of a thing.

I like it. React and Redux are comfortable ways to handle state management and I don't spend much time thinking about it. It means not writing Java or dealing with Android directly and iOS development is certainly no worse, and probably a good bit better, than it was before. It's faster to make something that looks and feels good. Also, and it's a little thing, but the react-native project creation tools are awesome and they make getting off the ground really easy.
Use http://www.telerik.com/fiddler or https://www.charlesproxy.com or https://mitmproxy.org

If they pin certs it can be harder but not impossible.
Innovation: This Clothe Checks Your Heart Rate and Recharges as You Move
I'm waiting for other people to tell you to implement this, but without JavaScript.
To be fair, at 300 points per square meter it's a lot higher res than the highest EA 25cm resolution data, with its very patchy coverage. But the EA's 1m data covers about half the country so you're right, this featured NYU data is a long way off being the "largest public LiDAR data set ever collected", unless I'm missing something.

If anyone's interested, here's something I made with the Environment Agency (and Natural Resources Wales) data:

https://houseprices.io/lab/lidar/map
If you want this as a feature, you can provide it through a pull request OR submit it as an issue ticket on the repo, and we'll get to it.

Either way: https://github.com/yczeng/hackernews-newsfeed
* shameless plug * Create a RSS feed with Feedity: https://feedity.com
The title exactly contradicts the content.
Glad to hear it! :)
On a single thread.

ZFS is well pipelined for multicore throughput.
I chuckled as well.
Oh, thanks. Somehow I was imagining "poems" in a very different sense. The way that you've described it makes sense, and I look forward to taking a look at them with this understanding.
I've found Vue code to be the opposite, at least for my use case. It is easier to read and more in-line with naive expectations as it looks like handlebars or any other templating solution.
Solid writeup. From someone who does/did a lot of this professionally:

1. Android typically is easier for this kind of work (you don't even need a rooted/jailbroken device, and it's all Java/smali),

2. That said, instead of installing an entire framework like Xposed that hooks the process to bypass certificate pinning, you can usually just decompile the APK and nop out all the function calls in the smali related to checking if the certificate is correct, then recompile/resign it for your device (again, easier on Android than iOS),

3. Request signing is increasingly implemented on APIs with any sort of business value, but you can almost always bypass it within an hour by searching through the application for functions related to things like "HMAC", figuring out exactly which request inputs are put into the algorithm in which order, and seeing where/how the secret key is stored (or loaded, as it were),

4. There is no true way to protect an API on a mobile app. You can only make it more or less difficult to secure. The best you can do is a frequently rotated secret key stored in shared libraries with weird parameters attached to the signing algorithm. To make up for this savvy companies typically reduce the cover time required (i.e. change the secret key very frequently by updating the app weekly or biweekly) or by using using a secret key with several parts generated from components in .so files, which are significantly more tedious to reverse.
Useless feature imo. SC was better without it (noticeably faster load times). How much server cost do they save if they eliminate comments?
In that scenario a lawsuit would be the least of Twitter's problems. Best case scenario could easily be a treason charge.
We'll take that into account.
If you're concerned about privacy, you should not step outside. The drones are watching you and phones listening to you.
Notice to the W3C of EFF's Appeal of the Director's Decision on EME
Vue fits nicely with jquery because it adds two-way databinding, and you can use jquery for everything else.
I'm going to start celebrating these now. Holidays in honour of the two Russian officers who refused to start WW3
We're about 1 security breach away from Twitter becoming a serious national security issue. I hope Trump has 2FA to login, but if someone got past Twitters internal system and started tweeting as DT then really bad Shit could happen.
"How can you do a park on America and not talk about slavery?"

Wow, this guy is really with it. Probably going to get some blowback, but he's right.

"This park will deal with the highs and lows . . . We want to make you feel what it was like to be a slave, and what it was like to escape through the Underground Railroad."

Sometimes you should just shut your mouth when you're ahead.

If Disney can do it without gross cultural insensitivity, I think it could work.
> sbt-android doesn't allow you to use Android Studio, which is also a huge handicap.

Some of our team uses Intellij, some use Android Studio to do Android dev. Both work fine with sbt-android.

> You can use the same libraries, the same build system, the same IDE.

This is true of Scala as well. Granted the gradle scala plugin is not great (though it does seem much better than when I last looked at it). sbt-android-gradle lets you use gradle and sbt side by side for android apps. For a while my team used this.

> The sbt-android plugin mentioned may work, but will never have the feature set of Gradle integration.

I'm curious if you know of any of these features sbt-android is currently misisng. I believe some of the new Android O font stuff might not work yet. Instant Run might be the next thing to be mentioned but it's replaced really well by sbt-android-protify.

> Scala 2.12 requires Java 8, and support for Java 8 bytecode has only been introduced in O

This is (imo) the worst part about all of this. Even Android O isn't the full java 8 bytecode so scala 2.12 still doesn't work.

> all of this is why Android developers love Kotlin

Yeah, I think Kotlin is a godsend for Android. One thing I don't think I mentioned in my original post was that Scala benefits from Google's kotlin support as well. It means many tools google produces (new arch components come to mind) operate on bytecode instead of source. So they (more or less) automatically work for scala too.

Certainly kotlin was thought of from the ground up as an Android language and it shows.

You also mention method counts a few times. I admit this is somewhat of a problem but it's also worth pointing out that sbt-android runs proguard automatically for you during release builds. We haven't come close to 65k (with or without proguard) and 70% of our method count comes from android support libraries published by google not the standard library methods provided by scala. We also target api 21 so multi-dex is not really the headache for us that it used to be.
Xposed is the reason I am never getting anything but an unlockable Android phone.
Ha! this is great.

I made a similar one that replaces newsfeed with a todo app that unlocks when you complete your work: https://chrome.google.com/webstore/detail/todobook/ihbejplhk...

It will also optionally replace Hacker News, Product Hunt, Reddit, Twitter, and Youtube homepages/feed with the same todo app. Basically all the sites that stop me from doing my work (HN is one of the worst for me)
"2,147,483,647 large coffees? I'd better get to work." - some poor Starbucks employee
Awesome read. Just enough info given to attempt yourself, without giving it away.
you can just select your phone from your laptop these days and it auto-pairs and turns on tethering. pretty slick.
Are you logged in? It's not on the logged out page. Then again, Amazon probably doesn't care about the logged out page much anyway.
Ask HN: I'm doing a podcast on Australian tech stories, any suggestions?
My name is Andrew Stuart and I'm commencing a podcast interview show soon where I'll be interviewing tech startups, founders, developers, anyone doing something interesting in technology, business and software with a strong connection to Australia.

Australia is full of smart people, business people, software people and there's a great deal of exciting startups, companies and projects happening in Aus. I want to surface some of those stories.

I want to find out the origin stories, how things came to be, who had the ideas, who built it, how did the ideas change over time, what were the hard bits, where did the money come from, what is the future vision. A bit Mixergy, a bit Jason Calacanis, but more willing to talk tech as well as business.

Anyone got any suggestions of interesting people, companies or stories as a start point for my research into who to interview?

Post ideas in comments or my email address is at https://news.ycombinator.com/user?id=floobyhoob
Oops honey, by screwing with these genomes I've accidentally created a unstoppable flesh eating bacterium.
This specific CEO had a reasonably easy job/life/career:

http://www.businessinsider.com/life-of-soundcloud-founder-ce...

Both him and his cofounder are paper rich from Angel investments they made (they just got a massive windfall with the IPO of Delivery Hero), by the way, so I'm sure they'll do just fine.
Seems like you could make the same argument about modern C++ or other kitchen sink languages - lots of features, lots of ways to write unreadable code.

I've worked in Scala for the last 3 years and I've found implicits to be the biggest issue. They're hard to debug, it's not easy to tell which implicits are in scope. Things like that.

Being clever is a problem with the developer and not the language. Scala code is dense, sure, but that's not inherently a bad thing.
This is the craziest thing I've written in 2017 but: I sincerely believe we will have consumer fusion reactors by 2030 if not sooner. The work of MIT SPARC combined with graphene manufacture will make this a reality. Combine this with all the investment in battery load leveling and electric vehicles and you'll see a very rapid energy cost reduction and deployment. Probably 10 years once the design is functioning. As to the boats, these reactors are well sized for boats. My guess is ICE Air-travel will be completely eliminated for mass consumption by 2070 if not 2050, replaced by faster cheaper evacuated trains and electric short-range aircraft. The power density of li-ion batteries at roughly 350WHr/liter is not great, I'd wager we can easily get to 700WHr/liter with graphene supercapacitors utilizing a combination of 3D layering and fractal interaction. I've seen an experimental graphene supercap with fractal interaction at 1200Whr/Liter but it had a tendency to explode with only a few cycles. The normal graphene supercaps go like 100k cycles with no degradation, or 30 times longer than lithium ion cobalt (what tesla uses). We are so freaking close to cheap graphene it's ridiculous. That's the technology no one sees coming, it's just about to enter the productivity plateau. /end crazy person talk.
It's difficult for me to believe that they would actually go out of business. Somewhere between the price they would want and going out of business, I feel that a Google/Apple/Netflix/Amazon acquisition is a near-certainty. Not sure how that would work if they don't have sufficient runway for due diligence & acquisition closure, but I'm sure the above companies could deal with that scenario if necessary.
https://www.nccgroup.trust/us/about-us/newsroom-and-events/b... is a good start. You can do some fun stuff once you can see/proxy/modify requests.

If you want to get started, start by poking at something simple (e.g. your own app). Then google as you run into specific issues.
Paredit is great but it is not the same as AST editing, it even describes itself as a 'cheesy imitation,' see https://github.com/takeoutweight/paredit/blob/master/CREDITS
Right, and that's band steering, not frequency hopping.
> compilation times, to method counts, to binary sizes, to performance

besides compile times (mitigated almost entirely by incremental compilation) none of these things hold up. Method counts are irrelevant with proguard and multi-dex (FWIW, most of our count comes from google support libraries anyway). Our binary is around ~5mb. I haven't ran benchmarks but I promise you that http requests, writing to disk, and WebView performance aren't slower because of Scala.
Works perfectly for me these days. It was a little fiddly 5 years ago, but with the newer OS functionality where you can select your phone from the WiFi drop-down (with tethering turned OFF on your phone) and it automagically connects to your phone, enables tethering, and hops online) is like magic. YMMV.
This is shit gear. My Bose QC35 stay connected to my macbook pro and iphone 7 50-60 feet away through multiple walls.

See my comment elsewhere here, I had a set of Outdoor Chips bluetooth speakers for my ski helmet that would cut out if I turned my head the 'wrong' way and I returned that garbage posthaste.
I got the same vibe. Sort of a "hey, it actually wasn't that big of a mistake".

I didn't get the feeling they'd do it a second time if they had a chance to do it over, knowing that Kotlin was about to get official support. (Or then again, maybe they just really love writing Android code in experimental, unsupported languages! And if so, who am I to judge?)
I have actively spent a good amount of my free time finding or maintaining chrome addons to block that garbage. It's the most inane and vacuous product feature I've come across and that's ignoring that it used to be so badly optimised that changing the comment caused a noticeable browser slow down
Another one was RCRD.LBL. Loved their daily mp3s in my inbox.
True say, did a similar thing here that might messily fill in some of those blanks on at least one set of tool options:
https://gist.github.com/patcon/ee96b9bb0f3141b37146#notes

(but it was definitely easier than in the blog post!)
That's the cloud for you.