skysight-inc/HackerNews huggingface dataset:
I wish I could. I have very little insight. I presume it's some sort of "normal business reasons", but the from my point of view the decision process went something like this:

Me: "It's finished, here are the areas of strength and weakness, and here's where we can deploy the system for maximum effectiveness."

Business: "We're thinking about the best way to deploy this."

Me: "This is how you deploy it."

Business: "We'll think about and get back to you. Don't do anything until we tell you."

Me: "..."

Business: "..."
Diesel subs don’t operate their engines while submerged unless they are recharging in safe waters, so there aren’t any ‘explosion noises’. They have batteries that are used for propulsion, and the Diesel engines are technically generators, as their propulsion system is electric - like a train.
Can Bitcoin be modified to avoid this, or is it over once ECDSA is broken?
> I disagree with that. Haskell is category theory as a language

No it is really not. Haskell only really has one category of any import, typically denoted 'Hask'. There is no builtin way to embed or express arbitrary categories in Haskell. It's not even clear what this would mean, given that Haskell only has one conception of arrow (the function type '->'). In fact, Haskell is so far removed from true category theory that we have to use a compiler plugin (CCC by Conal Elliot) to get anything approaching compilation to arbitrary categories.

Haskell is based on the polymorphically typed lambda calculus. Some decades after its design, some people realized they could use some abstract algebra concepts to help structure programs. You can use these concepts in any language with a sufficiently expressive type system. It is not specific to Haskell
Even if they do, I can live with them having it for 90 more days after the 25:th. If enough people complain about them saying they're "special" to their countries data protection agencies I'm guessing it will lead to some inquiries as to how special they really are.

I think facebook, google and all the other big tech companies have already "war-gamed" this out and I think that they will comply without saying that there are special circumstances as much as possible, so that they can save that card for when they really want to use it.
I wish someone would file suit against both the DNC and RNC for conspiring against the American public and third-party/independent candidates
FWIW, PNG also "fails to protect the length of variable size fields". That is, it's possible to construct PNGs such that a 1-bit corruption gives an entirely different, and still valid, image.

When I last looked into this issue, it seemed that erasure codes, like with Parchive/par/par2, was the way to go. (As others have mentioned here.) I haven't tried it out as I haven't needed that level of robustness.
There's a par2 "fork" under active development - https://github.com/Parchive/par2cmdline

The fork compiled for me this week, when the official 0.3 version on Sourceforge wouldn't. I vaguely remembered par3 being discussed, but couldn't find anything usable. And that's an example of why to be wary of new formats, I guess?
I agree. Wittgenstein had much to say that is relavent here, although he is referenced far more than he is read (unfortunately).
Who said it was OK to be face-recognized at train-stations? I don't think that is/should be right either
It happened in the US long ago for the most part. I often use a tower that is run by someone other than my carrier, but everything just works. This has been the case so long that I can't recall when the last time anyone I know had to think about roaming.

More recently (since 2015) I get free text and data (but not voice) in more than 100 countries around the world. Some countries include voice as well. In short it is coming, if you don't have it ask your carrier why. (odds are it is regulations so get after your representatives and tell them to stop it or you will vote for someone who will)
I'd love for this to get widely adopted if it can remove the pain points around sending images through SMS/MMS. I have no confidence that recipients ever actually receive the images I text them.
> The IRS has offered guidance on bitcoin transactions since 2014 and considers the cryptocurrency to be property, not currency. As such, every purchase, sale, trade, and mining effort is considered to be a taxable event.

Wait. So, cryptocurrencies are not taxed on capital gains? If it is considered property then do people need to calculate their base price, profit and then pay taxes?
It’s possible that this code has bugs that have yet to be detected. It’s a fact that quality is important if it can generate losses. Style may not be particularly important, but reliability is.
whataboutism? sorry, what? i thought taking precedents was standard practice in law...
Hammurabi's code was simple, but did little to deal with edge cases.

One of the reasons that the body of law has grown as large as it has is because of said edge cases.
OCaml users tend to avoid its object system, so while it attempted to fuse object-oriented and functional I don't think we can say it succeeded. F# is, as you say, later.
Germany did yet you don’t see people making a fuss about it. As much as I hate Facebook I think a lot of people just complain about it cos it so high profile. But if you don’t care about privacy everywhere, what does make Facebook special case?
There is https://github.com/scala/scala-async, which is already implemented as a macro, though it is a bit limited
> I am surprised that most of the comments here are actually advocating for navigating Dilbert-style office politics as an effective way of "getting along."

That's unfair. Most people who are advocating for deference when first joining a team.

And the common justification isn't politics! The most common justification is that there are a lot of "unknown unknowns". Therefore, sitting back and learning the social and technical history that led to the current system is actually the correct place to be in the exploration-exploitation axis during the probationary period.

Both for social reasons, as well as for technical reasons.

That's very different from "put up with office politics". The point is not that you should be likable during the probationary period. The point is that people who go way the hell too far to the "exploitation" side of the axis so quickly are demonstrating poor engineering judgment.

Characterizing that poor judgment as "well I guess I'm just not PC enough" is just icing on the cake.

> The team "criticisms" are to the person who is actually doing his job, instead of the ideas this person expresses, falling at the very bottom of "Graham's Hierarchy of Disagreement."

According to this account.

I submit that it's not even obvious that the engineer in this story was even making the correct engineering decision. Engineers are not scientists:

> In such situation, leadership should have had created a secure context for the team to consider their gaps in process that produce results with reduced quality.

I think the core problem in this story was wasting a bunch of the company's time arguing over a heuristic that's "good enough" in practice. Both solutions would have been "good enough"; the engineer put his ego above producing value for the company.

> Organizations that need to move fast cannot afford such conformism and dysfunctional communication.

Organizations that need to move fast cannot afford engineers spending time to prove they were correct when going with the established heuristic would've produced a good enough result with far less engineering time involved.

If the story included a thorough cost/benefit analysis showing that the change saved the company $N0,000 with N > (cost of engineering time) then you might have a more cogent argument.
i m referring to outrages. before facebook it was net neutrality, before that, something i dont remember. it has become a media pattern.
We built something similar in 2014 for our coworking space, Capital Factory. Slightly different use case though -- to make sure all the founders at the startups working at Capital Factory know who each other are, what they're building and who's an expert at what (so you can get peer feedback/etc).

Since I was seeing dozens of large companies, like Stripe, building their own versions of this, we created a version of ours for other companies to use: https://pingboard.com

Pingboard centers around org charts, and underneath there are rich employee profiles & cross-functional teams. And now we are expanding into hiring planning -- another area that lacks optimal collaboration and transparency inside most companies.
By that definition, they do get it. Because RCS is an improved version of the Messages inbox already in the phone. No need to take any time to adopt and adapt to any new program.
I read it as 250k x 0.0004 / 100

(which equals 1)
Or just import "crypto/tls".
Yes, you have a valid point.

The one I was more trying to make is that a product should not be simply marketed as "a platform for sharing pictures with your friends" if it is actually "a platform for sharing pictures with your friends in exchange for your participation in unspecified and ethically questionable social experiments."

The T&S can stay the same for all I care, I just think companies shouldn't be able to hide behind them when they dramatically oversimplify the nature of the product in the process of selling or promoting it.
So they need profit, which is negatively impacted by costs.
PRs are not getting reviewed. Solution? More PRs. That doesn't sound like the right solution. Seems to me the author didn't bother to get to know his team at all.
They aren't just giving in to your tastes?
Credible defectors.
Oh my the nostalgia, even has the audio of the physical noisy-as-hell HDD! Love it!
Reminds me of "The Jaunt"
> 2 engine aircraft are cheaper to operate per seat due among other things to greater fuel efficiency which can be up to 50% over older 4-engine models.

Why is this true? Is it because of the "older" part - because we've gotten better and designing fuel efficiency? Is it because the engines also increase drag? Is it because the four-engine planes typically don't have to run the engines as close to full throttle, and the engines are more efficient if run at higher power? Or something else?
We will use the sharing economy. Hal has a big system from behind that will allow users to apply and become a Hal so they will be able to reply users whenever they have some time and it will randomly send the questions to the available Hal´s.

There is a lot of people out there without work or doing nothing and now they will be able to literally work whenever they want from any place they want.

Uber, but from your computer, more comfortable, easy and cheap to do it.
>but there's a big difference between using legal loopholes that are available to you and deliberately not reporting things to pay fewer taxes.

Legally that's true, but I think the average person upset about this sees zero difference at all. Myself included, in my opinion using legal loopholes to get out of tax is morally just as bad, if not worse than deliberately not reporting things to pay fewer taxes.
Rust puts you very close to the metal, which can be great for writing high performance code, while forcing you to be very explicit about how you use memory.

This is great if memory managment and high performance are a big concern for you, if they are not you might want to choose a language like Go or Node which allow you to gloss over such details until they really become an issue.

Do not fix problems you do not have by throwing Rust at them, but feel free make the climb of learning it to expand you horizon. :)
CFar: An Automated Code Reviewing Tool at Microsoft [pdf]
You might like this: https://en.wikipedia.org/wiki/Cellular_automaton

I think about time in a similar manner. The delta between point A and point B is the mutation state and point A is the initial state that was mutated into B.
Its often very common that those with the best insights into improving a system also have the least power / knowledge of how to pull levers of power.
Like many things, it depends. As long as one can demonstrate that the icon in question has a clear meaning to a "reasonable person" or "typical user", then use of the icon would likely hold up in court.
you would likely say the same thing about bourbon. then you realize you can mix it in cocktails and that the market will adjust the product for the consumers.

the industry will do fine
> Why are people so intent to bash sombody else's language choices?!

Partially it's simple tribalism. But part of it is also the rational awareness of the opportunity cost of investing in a language other than the author's preferred one. The more people using language X that I don't like, the fewer people using my preferred language Y. That means fewer libraries I can use, docs I can read, bugs that get fixed, etc.

Language ecosystems aren't entirely zero-sum, but they aren't totally orthogonal either.
Absence of malice is nice, but what should be considered more highly is the absence of care.

Remember, this error probably will get people killed.

A rapid & public sacking may not reverse the error, but will have at least some preventative effect -- some people learn from the mistakes of others.

Of course this should not be the only step, and they should also add processes & procedures to help make it more difficult for this error to get through again (default to no names for sources?, second set of eyes asking for every source?)
They kinda did exactly that. GTalk became Hangouts which is no longer quite XMPP.
Life is too short to spend trying to fix a team when you don’t have the power or political clout to do so. He should have left at one-half of this blog post; the story up to that point should be sufficient to convince anyone you want to work for that you had made a simple mistake in judging the opportunity and moved on.
I don't think lack of technical expertise to fix whatever needs to be fixed is what caused Google's demise in the messaging domain.
> I've been blown away with the MS/TS speed of development

TypeScript broke my code for the past year on every new release.

---

Scala evolves a lot on each new version. There's a big difference between 2.10 and 2.12, the current version.

Dotty is a big change. That it ships in 2020 that's OK. Shipping it any sooner is risky.
Perhaps they needed you to elucidate the risks or possible downsides?
For instance, there is no point in refactoring a piece of code that never needs maintenance. In that case it is good debt and it already paid off.
Even if EULAs were easily understood, they are still ultimatums: you either take it or leave it with no room for negotiation or repercussions for demanding far more than the product could reasonably ever be worth. There is no motivation to ever write these in good faith. There should be a general federal law to protect users and businesses from malice, privacy laws (similar to CAN-SPAM,) and a ban on all other end-user license nonsense.
For the same reason you don't need to have every single steak and every single carrot analysed to a molecular level. After all, each individual steak or carrot will be a little different from every other. People who know what they're doing has found that mixtures of certain substances within certain parameters are just inherently safe and there's no point in a lot of histrionics around this.

> Who decides what the library of safe ingredients are?

The FDA, as well as their counterparts in practically every single country in the world. This is not controversial.
You said [Scala] it's by far one of the language I hated the most. If you don't want to start a flame-war maybe you should change the tone of the comment.
It's nearly impossible. Here's just a few situations that are unclear (no i'm not asking for advice, nor do I think HN is my personal CPA)

1. You buy into an ICO and it exit scams

2. You get staking / masternode payouts (but don't sell them to $ or another coin)

3. You trade futures - can you use Form 6781?

4. What's your cost basis on a futures trade if not (selling/buying bitcoin with borrowed bitcoin)?

5. You receive funding/interest payouts on an open leveraged trade

6. One of your coins forks

7. You have trades on a DEX with no downloadable history

8. You have trades on an exchange which no longer exists

9. You are awarded coins as part of an airdrop to holders of (other coin)

10. You get hacked (are you sure you aren't faking that to avoid taxes, citizen?)
I've got the other set - the beach!

http://shop.cooperhewitt.org/p/3953/evan-roth-solitaire-deck...

(high five)
The advantage of the blockchain is that we have well tested clients and api already, dealing with ID, logs and sync, with a huge number of nodes.

And you do need trust for distributing software.

You can't use git, it's hard to sync automatically. Torrent is a nice transport, not a db, and can be use to sync blockchains anyway, why make them exlusive ? And using any distributed db would exclude the field tested solution on millions of wallet that prove to work, and the api that is alreay well supported.
This appears to be about people who filed taxes through Credit Karma, not normal users. You need to file your taxes somewhere, and Credit Karma is probably the best free option available.
Rust excels at giving you fine-grain control over how your code runs. This was important to me recently, when I found I couldn't prevent Go from using threads:

I recently wrote the same UNIX PAM module in Go, Python, and Rust. I started with Go because I enjoy writing Go and the Go compiler can generate shared libraries. Go didn't work out because Go's use of threads resulted difficult-to-debug conflicts with the use of fork(2) in sshd - after realizing that the issue was related to threading, I found that you can write PAM modules using the excellent pam-python [1] package. The code I wrote in Python worked great, but I really wanted to generate a module as a stand-alone shared object binary, so I re-wrote the code using Rust, which worked great.

Footnote:

1: http://pam-python.sourceforge.net/
It depends on the use case. Our work primarily revolves around extending Spark with custom pipelines, models, ensembles, etc. to be deployed into our production systems (petabyte scale). Scala was really the only way to go for us.
Does that draw any distinction between paying and non-paying customers then as far as their rights? I see tons of "you assume all risks" sorts of Terms of Service, but I have a feeling those are likely just there and don't do much.
TypeScript has a comparatively easier job because the type system is unsound. They can add new type features without needing to be paranoid about a hole in the system or a usability pitfall because the tools don't rely on types for correctness or optimization, and because users can easily cast to "any" or otherwise work around an annoyance.

When you want the whole system to actually deeply rely on the static type system, it needs to be much more robust, and that takes a lot of effort.

I'm not trying to minimize what the TypeScript folks are doing — it's a really nice, well-designed language. But the complexity required to evolve an optionally-typed language is closer to that of a dynamically-typed one than a statically-typed one.
Will Disney destroy the movie theater?
>Most places have shut down their 2G.

Citation? I haven't seen this to be the case in California - at least on Verizon.
From my own experience talking with CEOs, I really think that will continue to be the case. If you're asking them to accept a large concrete loss now to prevent a hypothetical even large loss at some point in the future, they won't care.
NYC blasts broadband competition shortage as it pursues suit against Verizon
I'm curious as to the reason for storing bookmarks. It was a feature long ago, before search engines became so powerful. So what exactly is the use case now?

This guy on the Pinboard google group reached TEN THOUSAND bookmarks. For what reason exactly? https://groups.google.com/forum/#!topic/pinboard-dev/JKSUpO6...

Here's another user with A HUNDRED THOUSAND.

https://groups.google.com/d/msg/pinboard-dev/JKSUpO67cuA/7Hd...

Ooh, that looks useful, thanks! (I’m approaching the 100k bookmark barrier, and I’m well-behind in tag maintenance over the last couple of years. Thank goodness for full-page search of my archives!)

- Lynne

That sounds like a manual search engine to me?

I tried many times to manage bookmarks in various forms, and it just turns into a giant list that you never revisit. Cathartic to just delete them all.

It sounds like a utility for people who hoard things in general.

Thoughts?
I was amused to read recently that, thanks to having an ancient Yahoo! mail account, I am now subject to binding arbitration when I have a disagreement with a Yahoo! spinoff called "Oath." Also, I cannot participate in a class action or jury trial. That should work out well for me the next time they leak all of their user data.
Her web site is "kare.com". She's done icons for Apple, Microsoft, Autodesk, Facebook, Paypal... She's still doing graphic design.

Good icons are really hard. Most icons suck. Open source software icons especially suck. Open source people just do not seem to get communication through graphic design at all.
Beer in The Netherlands just declares how much fat (thereof saturated), carbohydrates (thereof sugars), protein and salt it contains.

That's exactly analogous to Coke. Basic nutritional information that doesn't cover trace chemicals or the brewing process.
I wish all mobile sites were as beautifully designed and spaced as this one.
Yep. His house is in Pensacola, FL. So the interior walls are stained pine board (FL panhandle prized by Spain for pine timber & naval stores). Exterior is clay tile with an air gap to prevent interior moisture build up. Steel roof.
Do you cross-build any libraries?
I keep promising myself one of these but I can never choose between them. :-)
Sure thing, we've gone with a representative image caption from the article.
1. Market prediction -- given basic demographic data, and publicly-available or easily acquirable information like when the person's house was purchased, what their credit score is, etc., how likely is this person to want / need your product, and is it worth spending a salesman's time on them?

2. Data entry. We took a picture of this customer's utility bill / bank statement / receipt / whatever. Now do we give it to human to identify relevant fields and manually type them into a spreadsheet, or do we have a computer automatically extract the business-relevant data? Or, heck, maybe that's too complex, but can we at least have a computer help--automatically filter out bad images, do perspective correction, highlight areas of interest, etc.? (This sort of thing is actually used in, e.g., digitizing census records; we don't trust handwriting OCR to be good enough on its own, but we trust it to automatically highlight relevant fields, in order, and provide a first-draft guess at the transcription to assist the human transcribers).

I could probably come up with a few more if I thought about it for a while, but those are the areas I've actually worked on recently.
Eco-Socialism or Bust
5G's main application around the world will be more capacity, a good thing for telcos

Or companies that want to break the residential broadband monopoly in a local area. Personally, I'm counting on TMO to kick Comcast's ass in my town. 5G would be a complete success if that happens.
Do you believe that the law is infallible?
> Scala's for/yield has surprising behaviour ... because it doesn't have a categorical grounding

Not sure what you're talking about, but for/yield is syntactic sugar for map/flatMap, just like the "do notation" is in Haskell. Of course it has theoretical grounding, because it wouldn't work without flatMap being the monadic bind.

> mixing lists and sets

Again, not entirely sure what you're talking about, but if true, it's entirely unrelated to for/yield.
Migrating an API Gateway from Flask to Django