skysight-inc/HackerNews huggingface dataset:
Chiming in as a data point even though I didn't really "quit".

I was a pack-a-day smoker for about 20 years. Quit and started lots of times.

I replaced cigarettes with a nicotine vape (salt nic) about a year ago and haven't looked back. I still consume the equivalent of a "pack of day" worth of nicotine. I still get the rituals and sense of "stepping away" that I used to have.

I liked cigarettes in the same way I like coffee and probably would have been happy to smoke indefinitely if I hadn't had kids and it wasn't so incredibly harmful.

It's unfortunate that vaping is not "zero harm", but in my life situation I believe it's been a major harm reduction that would have been very, very difficult to achieve otherwise.
Conflict of interest means you can never be sure why they recommended X, not that X was recommended with malice aforethought. That's precisely why it's such a thorny issue. People with malice aforethought are relatively easy to root out compared to people who mean well, but can't quite get it right for reasons no one can quite put their finger on.
Having the designs itself can only carry you so far. You also need the fine precision tools, materials engineering, software, etc in order to build sophisticated machinery.

China is advancing quickly but they can't make up 200 years of industrial headstart by the west in 20 years.
Not if he is giving the standard advice everyone in the industry gives. There are lots of conditions where the standard expectation is that "people like you don't really get well" and "symptom management is the name of the game." It would be considered malpractice to even tell people with certain diagnoses that you will shoot for curing them.

This is not a fair summary of your previous point. You previously implied that a psychiatrist will maliciously give information they know to be against the patient's interests purely to continue a financial relationship.

In this second post, you have walked back your irrational and ridiculous claim from "a psychiatrist will give you bad advice so you pay them forever to" "a psychiatrist will offer you evidence and science based advice that doesn't lie to you about your condition or future and instead seeks to give you the best options or advice that evidence teaches us can help"

Sure, that sounds great to me. That's why you trust an expert.

Now you seem to be mostly upset that a specific mental illness or condition isn't curable and may be permanent as the result of damage or pathology, and are blaming humanity's best experts for not having a panacea for your troubles.
There are a lot of startups trying to intermediate between small businesses and customers. They often start by providing customers for your business, and then will try to add more value-add tools into your pipeline, so that you are dependent on them (things like ecommerce platforms, CRMs, etc)

As a small business, work with them at your own risk - they promise to drive demand to your business but will take your margin as well since you won't have a relationship with your customers.
In my example it was proximity as in 'same city' and price was not the limiting factor. No-one would sell the land. Of course in the US you have a lot more land to go at!
Jaw-Dropping Second Life Sim Inspired by Blade Runner, Other Cyberpunk Classics
I practically grew up eating that thing, though I also find mitubishi's maroon pencils to be popular too.
I didn't want to pin the downfall of Nortel completely on the IP being stolen and being outmanoeuvred in deals.

During the dot-com bust they also lost a bunch of money selling carriers equipment on credit and that is when the tough times and inability of the executives to right the ship began.
Can you recommend any books for the more advance uses you stated?
I’m currently going through MOOCs and most courses seem to focus on the language itself as opposed to why the language is useful.
Sure, we can do much better. For example, how about we recognize that bodily autonomy is a fundamental human right, and that includes deciding what to put into said body?
Yep same in Australia
> Bricking your iPhone for a week-plus is not the equivalent of popping a party balloon or a short dose of UV light!

You totally misunderstood my comment.

I mentioned popping a party balloon because it could also disable your phone. And UV light because it can also destroy certain electronics. But sensors that can pick up little bits of UV are normally not set to warn about it, and that's perfectly reasonable and not "disturbing".

We can use a different word if you want. You think it's a [significant] problem and I don't think it's a problem. Is that better?

I'm not here to die on the hill of word choice. I disagree with your underlying opinion.
News Agreegator you shuld try
Israel silent as Iran hit by computer virus more violent than Stuxnet
It has no fuel to reorient itself or push itself anywhere. What would you do with it?
You forgot about the HanaHaus in Palo Alto, which unfortunately makes coffee at the same speed of all other Blue Bottle locations.
I haven't walked anything back. An awful lot of people are woefully misreading what I said in a much more negative light than I intended, then acting like I changed my story when I try to communicate about the issue.

It's probably best for me to walk away at this point. Most of the remarks here do not strike me as good faith engagement.
Here's a few ways of thinking about it:

1. Escalation, the instinctive response of angry humans, is generally a bad idea in international relations (or any relations). I once read a veteran practitioner express it this way: 'The job of international relations is to prevent a B-level problem from becoming an A-level one'. The U.S. and China, for example, have a very large number of interactions on an enormous number of issues; if someone retaliated every time they were unhappy - and then of course the other side would re-retaliate - that would be all that was happening, lots of treasure would be wasted, war would be risked, and positive things wouldn't get done. That doesn't mean that you do nothing, but you need to respond in a way that doesn't escalate the situation - it's not always easy to thread that needle, but that's what the professionals are there for. Another reason retaliation is bad is that it puts the other side in control of your actions - they can provoke you into doing what suits them, when it suits them. You want to act at the time and place and using the means that best suits you, not dance to their tune.

2. The U.S. does take action against them, but not in public. This helps prevent escalation - the Chinese government isn't publicly challenged and forced to respond.

3. Espionage is, in one sense, like a state of war. The U.S. is already doing all they can to shut down Chinese espionage and to spy on China, and vice versa. China isn't breaking any rules in the context of espionage (AFAIK), and if the U.S. could do more, they'd already be doing it.
Another use case is dealing with tokens that assume globally synchronised clocks such as JWTs and Kerberos/Active Directory. Ideally all clocks would be perfectly synchronised but things happen.

For example, you might have one container that’s exchanging JWTs with a micro service that should be using AWS’s NTP servers and another that’s joined an Active Directory domain that should be using the AD NTP server. Right now you either need to run them on separate machines or expose yourself to interesting problems if clock skew happens.
thanks for pointing it out
I've never known Amazon to ignore customer pain once they're made aware of it. We'll see what happens...
This exchange is a wonderful example of why amateur/anonymous advice shouldn't be automatically taken as better than professional advice! You are both filling in the blanks with your own experience and biases.
Thank you, I enjoyed it greatly. Freedom of expression (one's right to express one's beliefs) is not freedom of speech.
And in many implementations you have several options for weakness on hash tables. While not required by the standard, weakness is a very powerful enhancement to hash tables. (Weakness is the kind of thing programmers could add themselves if CL had a MOP for the garbage collector.)
I'm more of a (.)(.) guy
As someone who struggles with basic meditation, but believe in it for the long haul, I'm curious why you stopped meditate after seeing such insight? Do you have ambition or hope to take it up again? Or do you feel that you don't need to?
In the legal profession which is prestige driven, relationship based, artificially supply constrained and very lucrative, you would fear for your career over most else especially if you're lower on the totem pole.

This creates a perverse set of incentives to hide all misbehavior even if you're a victim of it.

So I don't know where you're getting this idea that lawyers would automatically defend themselves in those kinds of situations when the incentives are heavily weighted towards ignoring the situations and moving on.

As a software engineer in the tech industry though (especially at a place like Google), you can tell your employer to fuck off and you can find a new high-paying job tomorrow.
I loved reading books but i realized for myself that a book is a tool for reading. I like my kindle very much.

I have even ripped books in half to read the first half first and than the second because those books with 1k pages are horrible to read.
> Also, having "clock slew" be a matter of perspective—with processes that can handle leap seconds seeing them happen instantaneously; and processes that can't handle leap-seconds, seeing slewed time—would be nice.

I imagine there might be some really interesting (for meanings of interesting that include shoot me now) and hard to track down bugs as you deal with inconsistent clocks not just across systems within a network, but processes within a single system.
I actually prefer buying used books because of the patina of them being worn.
You've illustrated the problem in anecdata: Nothing in what you said indicates that cannabis causes his episodes.

It is just as likely, given the description, that the sequence that results in an episode includes the prompts that trigger him to medicate with cannabis.

This is why we can't use personal experience to make public policy.
His money is in real estate investments. Might not be tech VC, but an investor is still an investor.
William J. Murtagh, American historic preservationist, dies at 95
Disclosure: I work on Google Cloud.

As I replied in a sub-thread, I think Intel's marketing diagram [1] is probably useful to help separate the Optane flavors. This is about the "near DRAM" variant.

While the blog post highlights running SAP HANA (SAP's in-memory focused database), you can use them for whatever you want. The persistent part is that it's persistent across reboots. The hope is that this might make it easier to have tiered database/caching systems, since the gap between DRAM and this new "memory" is much closer than say DRAM and SSD.

[1] https://newsroom.intel.com/wp-content/uploads/sites/11/2018/...
That's nothing; EBCDIC has it in its very name.
Can anyone compare this to unbound?
Show HN: SliceUp - building the world's fastest time series database in Rust
We want to share that we are ambitiously building the world's fastest time-series database... and we're using Rust! It's called SliceUp and it's already significantly faster than the current fastest - kdb (http://kx.com). We still have a lot more query optimizations and novel features that we want to add to make it even faster.

There's a small demo/tech intro video of our database on our website (http://www.sliceup.co) that shows some query examples and its speed compared to kdb.

Rust is the key ingredient to achieving our goal of being the fastest time-series database. The killer feature for us is Rust's algebraic data types that can express query syntax trees and pattern matching to analyse queries for optimisations - while still being a systems programming language to build such low-level software.

We would like to thank the Rust community for all the great packages and libraries that we've used.

Your feedback is welcomed. You can sign up to our private beta via our website if you're interested to have early access to our private beta.
What do you mean by relevance here, could you elaborate?
Think of them as two separate products, and then mentally invert the branding: "CloudWatch" (and the rest of its umbrella) are really sub-products of "CloudWatch Events."

How did that happen? Accident of history:

First, CloudWatch Events was built for internal AWS usage.

Then, CloudWatch was also built for internal AWS usage (EC2 health checks, fed by the event stream!)

Then, CloudWatch was exposed, since people need to be able to configure those health checks and provision them in CloudFormation and such. So, they had this "monitoring" service—may as well slap together a logging dashboard and stuff. (And then forget about that as soon as the MVP is done, because writing their own equivalent of the Elastic-Logstash-Kibana stack was never AWS's intent.)

Then, after SNS came around and there was somewhere user-controllable for the raw CloudWatch Events events to be routed to, CloudWatch Events could be exposed, too. It got the sub-name because they had exposed the higher-level CloudWatch product first.

If SNS came about before CloudWatch, then probably it'd just be CloudWatch Events with a set of suggested "one-click launchable partner AMIs" for ingesting+indexing+searching/analyzing your AWS event data, and no first-party dashboard at all. And "CloudWatch" would remain an internal feature to power health checks without its own branded dashboard; just an unbranded presence under other services' dashboards/RPC endpoints/CloudFormation type hierarchies.
I wish we had a public database of outages / postmortems somewhere that anyone could contribute to, so that each of us could move from his own slowly acquired experience to more thorough statistical data.
Does such thing already exist?
The exceptions are 'real', but they're fuzzy, they change over time, and they're not in the constitution itself. They're the opposite of 'specific'.
David Bull has a great youtube channel about japanese woodblock printmaking that I highly reccomend.

https://www.youtube.com/channel/UCKSrgKjevPmNZxCAyTZP5cQ
How open source hardware increases security
An interesting part of this project was dealing with artist names. John has done a very good job normalizing all of this data in a graph which can allow others to discover related works and even merge otherwise distinct aliases.

A subset of this problem emerges from the transliteration of name kanji. Romaji is not always handled consistently, especially in historical contexts, and name characters have their own rough history around digitization of han character code points.

One of the first steps was to adopt name indexes to help with normalization but beyond some of those databases, it's been very interesting to see the graph analysis approach work with a combination of computer vision technology and carefully crafted apps to help archivists and researchers in these communities work together to combine their own data. This is a great example of what technology can do for a community if the intersection between people and technology is done well.
So it has its origins in bullshit. Great.
I had a boss once who attended a 10-day silent retreat. He spent about 2-3 hours a day texting and emailing me. I chalked this up to him adhering to the letter of the law but not the spirit.
I never said it was automatically better. Where are you getting this nonsense? I only indicated that there are situations where one might want to hear from an uninvolved outsider for perspective and this is one reason why "amateur advice" in newspaper columns can have genuine value for some people.

Anyway, I'm done here. This entire discussion is completely off the rails from my perspective.
Thank you and all the others for your sharing. Nice to have some honest opinions.
Ok, I hear you. But I think my usage is ok. The purpose of prohibition is to apply a criminal status to an otherwise non-criminal. And without that law they are innocent, no? Or how else should we describe the status of said citizens without the existance of prohibition?
Obvious benefits of the internet: communicate instantly with anyone anywhere in the world with any interface that can be digitized.

Obvious benefits of blockchain:
You can get tons of free money from idiot investors? You can hide wealth from the tax man with private fiat? You can forget your bank account number and never be able to access your money again? You can have a database that takes ten times as much electricity to maintain? There are so many benefits!
I came back to add: One of the things that just popped into my mind that Calcite has that we don't is query planning. Obviously since MQL was developed in house we didn't get any optimizations out of the box. We've since added a layer that processes the parse trees looking for optimizations and while it isn't quite query planning it has yielded some significant performance gains (or rather poor performance mitigations, haha).

I'd imagine getting this for free from Calcite would have been really nice.
Roger Alsing (Johansson) did this in 2008:

https://rogerjohansson.blog/2008/12/07/genetic-programming-e...
OK, so who are you referring to as the "single centralized power"?
Financial Update: October 2018
> ....a hacking group calling itself the Syrian Electronic Army hacked an Australian domain registrar

> In early December 2013, prosecutors said, members of the conspiracy used the same tactic to hack the Australian registrar again, this time to hijack domain names of one of the targeted technology companies.

What's with that registrar, don't they learn from their own mistakes?
> when you get an error, the error is far from its call-site, and the truly helpful information that I could've had in the stack trace is gone

I'll grant you that one. Languages with non-strict evaluation (or tail calls, or inlining, or extensive use of macros) rarely have useful stack traces. You can see what was being evaluated but not necessarily how it got there. The ability to leverage the stack as a debugging aid is a feature of certain runtime conventions more applicable to imperative programming paradigms than to functional ones. In modern Haskell there is a way for functions to receive extra information about their call site as an implicit parameter, which helps with error reporting. I'm not sure what tools Clojure might offer along these lines.

I will point out that tracing the source of incorrect or corrupted data is no less of a problem for programs written in strict, imperative languages. Functional programming adds to this by emphasising functions as a form of data, and non-strict evaluation carries that still further by treating all data as closures. On the other hand, strong static typing limits the kinds of runtime errors which lay hidden within those closures to a manageable set (assuming a pure functional language like Haskell).

>> Either way, making eager evaluation the default is a form of premature optimization.

> I don't see how that's true - it's the default way CPU's operate on the silicon level.

That's not really true, given the existence of speculative and out-of-order execution. In any case, how the CPU operates at the silicon level has very little to do with whether a high-level language optimization is premature.

> Millions upon millions of lines of non-lazy code have been written and put into production and they perform real, valuable work.

I'm not disputing that, but it's beside the point. Code which has been prematurely optimized can still "perform real, valuable work". It just may take a bit longer to run or require more resources to develop (for example by being harder to reuse, requiring more code to be written to accomplish the same result).
Erik was rather hostile online, but his technical abilities were quite high and his opinions well-researched. I met him once IRL (as did many Lispers when Franz paid his way to the Lisp conference in Berkeley in (can't remember which year. PG was a keynote speaker and McCarthy was holding court in the hallway.) Erik seemed perfectly polite in person. To me anyway.
I really wish they would go so far as to get a Kibana-like front end and expand CW to ElasticSearch levels of UX.

In the end, I really appreciate the ELK stack, and if you can either use ElasticSearch for other things, or have enough logging to justify a cluster, it (ELK) is a great option.
>I'm done with this conversation since you have bunch of strawmen you really want to fight.
Just wanted to chime to compliment this gracious exit, it's easy to waste time online arguing with these types.
Aha - it wanted GPT and also the 64 bit version.

Thanks for the pointer.
I made a simple roguelike for Ludumdare not too long ago. Here's the code: https://github.com/kraln/rougish

Simple, but fun :)
> if you really think all controversial speech is funded

Not what I said at all. That Russian grassroots propaganda campaigns exist certainly does bear up to scrutiny.
After my time with Scala, I think that if I need a heavy type system, I'd look to Haskell. And there are certainly classes of problems that I would choose a type system, but the general case isn't nearly as strong as I though it was before seeing them used in anger.

So, in the following, I'm not ranting at you, but I am saying I see lots of arguments for types that jump to QED without nearly enough evidence, with the "everybody knows" kinda explanation. And you happen to have put a handy list right in front of me when I had time to respond.

> ... difficulties with refactoring, runtime errors, needing lots of test coverage and not scaling well to large teams and codebases.

I was really impressed with Scala when learning or toy projects, but every time I saw it in production it was pretty horrid. Small, technical refactoring was taken care of by the IDE, but large scale refactoring takes the same amount of thought as before, but now there's 10x as much code to understand first.

There were less runtime errors, but not much less, and I saw a lot of code that didn't error, but didn't get done what it needed to.

When it comes to scaling to large teams, I saw lots of "The compiler says it's ok, and the tests pass, so commit!" where the code didn't make sense! The old thing about write code for programmers to understand first, and the machine to understand second...

Outside of certain specific situations, I just haven't seen the benefits outweigh the increased code weight and slower time to market.
"Couldn't" is a bit unfair. The article seems to imply that it wasn't from a lack of trying, but a lack of interest, and a company only took on the challenge after the issue became considered an issue of national pride and came to light.

The numbers given suggested that it cost just over $17 million to import the pen tips to manufacture 38 billion pens. Which puts the cost per tip at $0.00045/piece.

It's not hard to see why manufacturers wouldn't bother creating a process and tooling for that if it already exists.

More importantly, the article put emphasis on the idea that once the government complained about it, something was done quite quickly. Which is completely different story to a military jet engine, which is being researched, funded and developed by government-linked organizations.
One would have to walk into that expecting to "lose relevance". I can't think of a 12 month period, save 2001, where checking out for a year would put one much behind on relevance. FB is still FB, Twitter is still Twitter, still arguing about the same shit we argued about thirty years ago on usenet.

You will, however, have to learn all new javascript frameworks before you go back to work.