emn13

83 ms·

661.
by emn13 7y ago
HN should ban links to sites with policies like that. It certainly reduces the value of HN. It's essentially spam to anyone here.
662.
by emn13 7y ago
The median UK salary is 30k pounds ( https://www.gq-magazine.co.uk/article/average-uk-salary); it's higher in london, but I find differing numbers depending on where I look. But in any case: Although house prices a
663.
by emn13 7y ago
What privacy-related information was sold to booking.com again, regardless of how the transaction played out? I get the feeling that people are asking Mozilla to simply not deal with corporations at all, regardless of privacy, which is simp
664.
by emn13 7y ago
As an individual, I want "convenience and ease of use". But I'm not blind to the fact that you're going to get shafted because my negotiating position - as an individual - is poor. So I 100% want an organization like
665.
by emn13 7y ago
Just note that the perf loss is 20-40% in their benchmarks, so in your case, you'd need to bump that 4.4Ghz to 5.5-73.GHz, which is a tall order. In any case, the article is worst-case FUD-like nonsense. No idea what the eventual perf
666.
by emn13 7y ago
Heap (over)use by the GC is effectively a scaling factor. How large the underlying objects are remains remains relevant: if your objects are twice the size necessary, the GC will "bloat" that further - and this tradeoff isn'
667.
by emn13 7y ago
Value types aren't "necessary", but they would have been valueable at day 1. The GC heap is simply inefficient; not necessarily because of the GC (which indeed is harder with massive multicore), but simply because of the per
668.
by emn13 7y ago
Thank - I hope I don't come across as too bitter - I really do think there's an upside to all those limitations. I'm just past the exuberance of thinking that because it's so actively developed, that all these flaws are
669.
by emn13 7y ago
Hmm, I do a lot of C# programming, including very language-y low-level stuff, and I'm not sure I completely agree. I appreciate that by moving faster they get more stuff into more hands faster, but they definitely have a lot of hackish
670.
by emn13 7y ago
Without trying to imply some kind of opinion as to Huawei or Trump here: I don't think that's a serious threat. It's one thing to make a lot of tough-looking noise as a matter of protectionism to curry favor with voters thus
671.
by emn13 7y ago
Where did anybody argue that "regulating the internet" is a good idea because it reduces competition for EU-headquartered international companies? Oh well, people say crazy things sometimes. It's definitely a bad motivation
672.
by emn13 7y ago
It may help those two firms, but the point isn't to make these two private entities rich it's national (and union) security: Huawei's existing customers - which exist in the US, but particularly in the EU - must now rely on
673.
by emn13 7y ago
And the problem isn't really limited to links in the response; the same goes for computed links based on keys too. In fact, links in responses are probably easier to update, because waiting for client software to upgrade can take a l
674.
by emn13 8y ago
The handling, or the bug itself? Sound like the damage control is fine (although worrying that they have no way to distribute hotfixes more rapidly than this). The bug in the first place, on the other hand, seems pretty negligent. Not tha
675.
by emn13 8y ago
oh yeah, sorry - that's indeed what I meant.
676.
by emn13 8y ago
Nope, totally agreeing with you! :-)
677.
by emn13 8y ago
I mean, I know you're suggesting the claim has no merit because the poster doesn't know what they're talking about; but you know, even if the poster were a genius with intimate knowledge of the project, a claim like this is b
678.
by emn13 8y ago
That's ridiculous - there are lots of pragmatic xml deserializers available. Not to mention, sometimes you want something like xpath; lack of xpath and lack of validation (schema, whatever) aren't features, they're bugs. T
679.
by emn13 8y ago
I mean, we're not going back to xml anyhow; and xml is considerably older anyhow, so this is a pretty hypothetical case. But I'd posit that most - but not all - of the issues with xml config files have little to do with xml per
680.
by emn13 8y ago
Anybody that wants turing complete programmability in their config file is asking for pain. You can always embed such a language in a string as an escape hatch, so there's no loss of generality in any case, but it's sufficiently
681.
by emn13 8y ago
Didn't know about https://ghc.haskell.org/trac/ghc/wiki/LinearTypes until now; I'm assuming you're referring to that? Neat!
682.
by emn13 8y ago
The value and impact on commercialized surveillance depend critically on the ability to generate large databases, both on the any specific indivual, and on the the number of individuals thus affected. Breaking up dataminers probably would
683.
by emn13 8y ago
I don't think it's helpful to talk about "raw power" in a comparison like this; clearly there are significant type system features Haskell lacks - so this isn't a question of a simple superset. And in any case; what
684.
by emn13 8y ago
Exactly. The fine is basically a token at this point; it's the potential for followup that matters.
685.
by emn13 8y ago
If you use keepass, that'll happily autotype into pretty much anything. Obviously autofill is nicer, but that works even for non-browser apps, so it's nice to have.
686.
by emn13 8y ago
As it pertains to this complaint though, those are all seem less relevant than the issue of well... plain non-compliance? I mean, if they didn't even have a DPO... Still, let's not overstate this "recordbreaking" fine.
687.
by emn13 8y ago
Sure: try to avoid the phone getting hot; don't charge the phone when it's hot; and definitely don't use the phone while it's charging if doing so causes it to become hot. Problematic phones are probably tuned to close t
688.
by emn13 8y ago
That's not true; every manufacturer, including apple, does this. The question is simply to what degree. Battery chargers need to decide upto which voltage level to charge, and at which voltage level to consider a cell depleted; and s
689.
by emn13 8y ago
You say degradation is inevitable, hence implying this kind of degradation is unavoidable. But to draw an analogy: that's kind of like saying death is inevitable, so there's nothing we can do about infant mortality. It's abs
690.
by emn13 8y ago
In general, Li-On batteries don't degrade like this; only design flaws could lead to this kind of behavior.

More ›