skysight-inc/HackerNews huggingface dataset:
I am not saying C++ and all the stuff listed is always safe, just that it's good enough for daily use, including professional use where lives are on the line. As I said before, you used extreme words and made C++ sound like Java applets - something no one ever should use nowdays outside of truly exceptional circumstances (a.k.a. not something as widely used as OSes, browser and the HotSpot JVM).

I'm sure you have seen BS codebases in Java, C#, PHP, Python, etc. as well, I've seen weird interactions with GC in WildFly (I can't comment more because I'm not a Java programmer), spooky action at a distance, globals, using one huge table in a DB to store everything thus missing the point of a relational DB, etc. all in non C nor C++ and it'd not help these things if they were in Rust.

Not all bugs come from the language itself either, some are just true programmer errors. I just google for PHP SQL tutorial (not an English one) and the result is of course pasting input together with SQL to form a query, 0 escaping... Sony had a leak like that. Many Windows issues are pure ignorance like having SMB (that turned out to be buggy, but still) running by default, similarly stuff like misconfiguration, default passwords, Apple's goto fail won't be solved if people are copy pasting code and formatting it badly (unless Rust enforces that, I'm not sure, I don't know Rust yet). Rust will not prevent these kinds of mistakes (maybe the last one if the compiler itself detect inaccessible code and maaybe the SQL one if it marks the variable from user input unsafe at first and cascades that through the function calls to see if it was pasted and passed to SQL) unless it has extremely deep understanding of what's going on.

Additionally, despite all the bugs in Windows there (sadly) wasn't a huge exodus to Linux (which too has tons of bugs and is in C and has lots of programs in C++), it just works "well enough" despite the flaws, there no disaster hanging over our heads.
>Agreed! But they won't provide an easier option if we'll just accept DRM anyway.

Oh sure I think we should break DRM any chance we get and fully support the DVD and Blu-ray reversing efforts. If there was someone breaking the Netflix DRM I'd support that too (and use it probably). But my argument is that just like we should regulate ISPs so they can't prioritize traffic we should regulate streaming services so they can't block platforms. In some jurisdictions we've gone the complete opposite way and started regulating that breaking DRM is illegal. That's the nail in the coffin of content being able to enter the public domain or having fair use exceptions.
> And, with federated identity, you can also run your own, if you don’t trust Google or Facebook login.

Sounds like OpenID...which was kind of a train wreck.

One middle ground could be tighter integration between browsers, sites and password managers. With the right specification, sites could offer a "register with [1Password,KeePass,LastPass,etc]" button which would open the password manager and pre-fill all the fields from a password manager's identity record (i.e. if a user has multiple identity records, the password manager can prompt for the one to use.) If there's a need to choose a username, there should be a standard endpoint for checking uniqueness. Once all information is filled out, the password manager can generate a password based on the site's specifications, post the information back to the site, store the account details and the site's ToS in its database and update the browser page to the success url. There can also be a standard endpoint for password rotation so the password manager can periodically update the password without the user's involvement.

This would still use passwords and for those that explicitly don't want to use a password manager, they could continue doing things the current way. But for the majority of us, it would be just like what you're talking about except that our identities would be stored locally in our password managers, giving us complete control over everything while automating as much as possible.
Juventus’ Leonardo Bonucci in Milan Talks
User prompts for JavaScript from other domains.
You don't want to restrict on any password aspect but this:

Is the password known?

Any sort password is know. There are lists of millions of known passwords.

Better would be to get away from passwords entirely.

NB: I've been checking the xkcdpass utility (available on Debian). Generated 50 sets of 100,000,000 passwords each, comprised of six words (the default), then sorted these uniq, and counted the output lines.

Any duplicates would result in fewer than 100,000,000 lines.

All fifty trials had no dupes.

Took most of a week to run that, on an older box :)
Show HN: Virtual-clock.js – performant highres virtual clocks with timed events
Mainstream political discourse is off limits, unless it presents something of intellectual merit, a new or interesting phenomenon, or has some more than tangential relationship to the tech community.

If anyone else had posted something like this, it would have rightly been flagged as well.
the old presto version of opera had an option to default to user css for the whole program instead of the various sites'. don't know if that's still available in the new version.
Another sensationalized article. They "teleported" a photon which is 1) not an object and 2) not really teleported the way most people think of it. It's basically taking a quantum link and mirroring the properties of one photon to another. It's definitely cool and definitely useful, but it's not like we're taking some small object and sending it to space. It's more like taking a particle and changing the angle of that particle (even though that's not really an accurate description) and observing that the other particle has also changed to the same angle so, for most intents and purposes, it is the same particle (only it's not, it's a photon).

TL;DR - Star Trek is still a long ways off.
XFS has gained (some) checksumming and CoW support.

At this rate XFS will end up evolving to add all the features btrfs promised before the latter makes them stable.
An aside and confused this with the Ultra 64 for a second, and thought it would be a story about a Nintendo 64 prototype.

Fun history if you’ve never looked into it.

https://www.gamespot.com/forums/system-wars-314159282/its-fa...
Show HN: TimePike – employees time tracking, simplified
I've had to learn this the hard way as I've gotten ill.

Finding a PCP is different from finding a specialist. For a PCP I'm looking for someone I can have a relationship with, reasonable access/availability, and the ability to make appropriate referrals and coordinate specialists. If you have a lot of complex problems, this is pretty much impossible to find inside insurance. I have found some good, caring doctors in insurance but I either can't get timely access or they can only give you so much time so I have to go to a direct pay or concierge provider. Some doctors will meet with you for 10-15 minutes for free or sometimes a nominal fee if you explain you're not looking for an exam, just interviewing PCPs. Your PCP is the one who will end up doing most of the referrals.

As for the specialists, medicine has become so super specialized. Let's say you get diagnosed with some rare cancer. If you start searching the medical journals and read, you will find the same names over and over again. You can call or e-mail the doctor, explain your situation and see if they'll do phone consults or talk to your PCP.
These are both not reasonable alternatives for all people.

Cell phone data is usually much more expensive and often people don't have a lot of choice on what connection options they have.
Find a large user who feels this is a valuable feature and have them adopt it.

Governments are one such large customer.

Vendors, faced with multiple customers requesting a feature, but with slightly varying specifications, will tend to seek a mutually acceptable spec.
I don't think ext4 has native snapshots. You can use lvm-thin for snapshots. Note that lvm-thin is different from regular lvm snapshots, which are known to be inefficient. RHEL has decent support for this feature, and will even let you set it up in the GUI during installation.
What? So we should blame Uber because some of its contractors are poor? What are you even on about?
You'd also need a keyboard. So...I'm more likely to hit up eBay for a broken complete unit (though I just browsed, and found none with all their keys!). Then again, a red or blue C64 sounds kinda amazing.
SSL was forced by Google single-handedly. Developers scared that https might provide ranking factor, quickly moved to SSL.

As for topic, I would like to see all mails clients rendering emails same god damn way.
Reverse-engineering the Starbucks ordering API
Hi HN,

I built TimePike because in all my previous jobs there was a problem: tracking my working hours and holidays was not an easy task. I was working mostly in Software Houses, but not only. We did not have a proper software.

TimePike is solution to those problems. It lets track working hours, overtime, sick leaves, work from homes, and holidays. You can see who is on holiday today. Agencies/consulting firms can generate automatic reports and invoices for their clients.

Primarily I am totally/passionately focusing on building solution which is super simple to use. Most of tools I have stumbled upon were really way too complicated.

You can try it for free. I am looking for feedback!

Cheers,
Wiktor
i think the electricity use is a bigger problem.
I don't see any real justification here for why it was worth the effort to port the code from Kotlin/Java to Scala other than reusing their "well-established skills with Scala" and "using sbt for our Android app has also allowed us to leverage our unified build system". They're both valid reasons, but they're not so much technical decisions as pragmatic ones for that particular company.

The post states "hopefully I will be able to illustrate how Scala can dramatically improve your experience while developing Android applications". This claim isn't addressed in the post at all however. For example, it states "Scala has a pretty decent concurrency primitive in Future" and explains how to use them, but doesn't say what they offer over and above Java futures or Kotlin coroutines. Most of the post is talking about how they migrated their codebase and any compatibility or technical hurdles that were overcame on the way (e.g. the sbt/Gradle mismatch), not about why Scala was a better choice technically or what benefits it offers over Java or Kotlin. There's no mention either of other practical issues such as the large standard library, method counts, compile times and so on.

The addition of a few strong comparisons would be welcomed. As it stands, the post feels more like "please don't fire me" than "where's my promotion?".
Not the same person, but I have three. I have a roomba for everyday sweeping, a Bissell for actually cleaning the carpets not just sweeping them, and a Black and Decker handheld for the stairs, the car, and other places it's hard to take a full vacuum or a robot.
>So it's alright that companies lie and it's the employees fault for not knowing they were being lied too

Strawman argument
Can you cast photos from the Photos app in your phone?
If that extra $40 a year causes them to not shut it down so fast, I'm all for it :)
One per house, like everyone else!
I was thinking of writing a spec and implementation on a similar thing a few days ago:

Each site would publish a standardized file in a standardized location, and/or add a META tag to the file in each page. The file itself would simply contain the URL to the login page and the parameters that should be passed to it, and the way to pass those parameters.

Then, your browser/password manager could simply perform a request in the background, and log you in completely automatically. This solves all the hassle of finding the login form, locating the fields, auto-filling, typing some characters if the change wasn't detected, handling single-page apps, etc.

This could later be extended to signing up automatically. It would make having strong, unique passwords for each site the convenient alternative.
FWIW, I use git inside Dropbox for my personal solo projects. I don't want to have to use commits and git's remote syncing mechanisms to share in-progress code between my desktop at home and my laptop. I want to be able to pick up exactly where I was on the other machine, including my git staging area and local unstaged changes. It works perfectly for this.

I do occasionally get Dropbox-level merge conflicts for tmp editor/IDE files, but I can't recall getting any for source files.
Agreed. I think it makes them look a bit complicit to not make their stance front and center as they did for SOPA with the blackout. I understand that companies don't want to get involved in politics, but, this is something that directly impacts the future of their business.

Long term company health ought to be interested in maintaining net neutrality. Those seeking short term profits would prefer the ability to gut existing company reputation in order to line executives' pockets. I believe Google is still long-term focused, but their lukewarm action here gives me some doubts.
Would you say Kotlin is still experimental though? Scala appears to have a 10-year headstart, but time isn't everything.

I use F# and found Scala to be a breath of fresh air after getting sick of Enterprise-y Java, but haven't had the time to venture into Kotlin.
I wouldn't be so fatalistic. While I personally find some of the ideological currents behind Trump abhorrent, his rise does prove that a huge grassroots movement focused on a specific goal can generate results.
AI powered robot lawyer for the poor launches (1 min video)
I've never seen Haskell people (I'm relatively fresh here, 2 weeks, as evident in my lack of fitting into echo chambers) and Haskell is entirely different beast so that's different, especially if they were okay with F#. Rust is pretty much claiming to be doing same stuff in same niche (efficient native code) as C and C++ except better, it's like reverse of Haskell vs. the world except F#, it's Rust vs. C and C++.

I wasted an hour and a half or even two here today as well, I at least got a reply from a Rust core team member who responded to me (yay), was nice enough and told me the community rules disallow wars, that's something I'd not get otherwise, but still, this feels very very unproductive in the end...
Or more specifically, not pour random fluids into your butt for some mystical health benefit. Only for pleasure.
The problem is this article is making general statements off of their specific use case. Like this complaint:

> Simple things were made harder to develop. React was created to make DOM changes fast, really fast, so you will have to use React functions to make use of this, some of which you will not be familiar with (because React has a different architectural style)

It's utterly meaningless. What it really sounds like is they didn't understand React, didn't research what using React with jQuery would entail (given by the fact that they couldn't make it work), and didn't bother to learn the (relatively small) React API. React is not hard.

Then this gem:

> React is great, but only if you want to develop a simple application where the UI should not be consistent across different technologies

Is _completely_ incorrect.. React is used at enterprise scale by many companies to develop all sorts of complex apps, and surely many of them have or had existing systems coexisting side-by-side.
>If you're not making enough money on that, charge me more for the bandwidth.

There's no such thing as "enough" money, only "more" and "less". Holding last-mile delivery of Netflix's content hostage for a ransom payment gives the ISP more money. So if they can do that, they will.
Disneyland Resort uses photos to eliminates hand stamps to re-enter its parks
Yeah but they should show that in the recommendations, not just when I'm at the product page.
iPhone 8 May Feature Rear-Facing 3D Laser for Improved Autofocus and AR
My point is exactly that a subjective first-person experience is self awareness. The root of all conscious experience is an awareness of own awareness, a sense of our own senses, the difference between them, etc. I would challenge anyone to come up with a definition of conscious experience that does not, ultimately, boil down to a form of self-referential sensory input.
You're not wrong.

Before 2015, there was really nothing stopping them from doing it aside from consumer outrage. But as time goes on, large ISPs have been making more and more noise about "internet fast lanes". There have been several incidents of them throttling sites like Netflix in secret. So while they previously adhered to defacto-net-neutrality via informal gentlemen's agreement, the likes of Comcast are no longer acting like gentlemen.

Without net neutrality, it will get worse. Especially since ISPs are also cable and phone companies who are justifiably worried about how the internet is increasingly affecting their cable and phone revenue.
I think this is only really worth the headache for security issues. That said:

- HSTS

- DNSSEC

- IPv6

in that order. I think for a long time, governments had no interest in pushing security and encryption because that would prevent them from mass data collection. I think minds are starting to change around that: poor security is much more likely to be exploited against a government rather than used in its favor (plus all the real criminals now have much better opsec these days so mass surveillance is much less effective).
Vast majority of hosting companies don't offer LE.
Scala has been around longer, sure--but it's also a bunch of stuff that doesn't really work well together and I'm still not sure that most (not all, by any stretch) Scala programmers really know how to write a program in Scala that's there to be maintained over the long haul. It can be done, but the pull of the super-broad feature set seems so strong that most of the developers I know personally, including me, write code that's awful to read two months down the line because it's dense and featureful and so very clever (note: very, very pejorative; the line about needing to be twice as smart to debug code as you need to be to write it applies here).

Kotlin is literally Java plus sugar. That's all it is. It encourages doing the right thing through stuff you could totally do in Java but nobody does because it's awful to write in Java. And, TBH, for the 90% case that's pretty great. There's no Shapeless in Kotlin--but that's a good thing, because Shapeless encourages developers with skill but no taste to do awful things and inflict them on, say, me. ;)

So, no, Kotlin's not experimental. Because experimental is a mindset, not an alpha/beta release stage.
But some companies actually come out of that, especially when they've built valuable assets. It took a long time before it seemed like Facebook could be turned into a profitable business from being a plaything. But the fact that they were sitting on this growing social graph gave people enough faith to believe it might be worthwhile to give them some more rope.

At least that's the way I see it -- maybe they started monetizing effectively earlier than I recall.
The keywords here are "whenever he needs to".

Are there verified nuclear warheads on verified trajectories from verified origins?

Does the US President need to retaliated?
Not really.

Properly hedging requires constant adjustment of the steak to lock in the "winnings" and replacing the losing company with a different one that does similar things but has better management.
I don't know if the problem is infographics or just not providing enough nuance and context. Some examples:

- I showed a friend this who didn't know what IFTTT was and he balked at the results before understanding what IFTTT was. Since the percentages were too high. Understanding Ifttt made the footnote of who was surveyed make sense. They had seen it before, just didn't understand it.

- "46% say they're more likely to ask their assistant for information over their smartphone". Most of the users have Alexa devices. Alexa is pretty limited in what it can help you with. For my daily briefing of news from specific niches/publishers, weather, and one or two other things, it is great and I too prefer it to using my smartphone. But for most other things, your smartphone is likely to be much better for other information.

An example of basic information I tried a few months back: "How tall is X companies building in Y City?" I chose 6 corporate buildings in 5 cities. Alexa didn't get any of them. Siri and Cortana were 50%. They differed on one of them. Google got all but one. I can't find my notes on it now, but one example was asking the height of the Comcast building in Philadelphia.

--

I guess my point is, this infographic is great for the specific niche of Ifttt users who have already connected with at least one voice assistant. So that's great for home/tech enthusiasts with some spare money. Ifttt does state in the footer who is surveyed, but footer is footer. The rest of the infographic is what pops out at the average person. I have no clue if this infographic actually shows anything or just helps out Ifttt marketing.
I program in Clojure more than in any other language. That doesn't change the fact that I feel a stronger incentive to avoid local variables than in any other language I've used so far. Also if I wanted to tackle this issue with a macro I'd probably have to make an alternative to `defn`. That's a great way to invent a dialect of Clojure nobody else will be familiar with.
The problem is the economics of the Internet today. Most sites are ad-funded. They need to maximize pageviews and time on site. The recommender is a huge part of accomplishing that, and it simply won't be tuned to any metric other than maximizing revenue. The solution would be to reskin popular sites with recommenders that had other objectives, such as retrospective satisfaction with time spent. Unfortunately sites know that if they give up control of the UI through an API that is open, they will lose money when people do things like this.

I really think we're entering a crisis here where sites and apps that are engineered to maximize corporate metrics are leading people down horrible paths of addiction, and psychic stress as they spend their mental energy resisting temptations constantly thrown at them.
To be honest, I was all-in on "screw JavaScript" until ES6 came around and Babel became stump-dumb-easy to deal with. I've found that just getting things done has gotten a lot easier in modern JS and TypeScript is a powerful tool (though working with React/Redux directly with it is kind of a pain in the ass; I tend to write React components in ES6 just so I don't have to what-the-hell-am-I-doing-with-my-life my way through react-redux).
I have multiple wallets. I have one I take on business trips that contains my work ID, American Express, business cards, etc. All stuff I normally don't carry with me. I have an everyday wallet with cash and my bank card and stuff I need everyday. And if I'm dressing up, I don't want to ruin the lines of my suit so I have a far slimmer wallet that just has my ID and space for one credit card.

I mean I'm not accessorizing with the latest seasonal fashions, but there are utility reasons to change the kind of wallet you're carrying for different purposes.
In turkey pedestrians do not have right of way. So on zebra crossings, you have to wait until the cars stop, they don't have to stop for you.x