skysight-inc/HackerNews huggingface dataset:
I'm a fan of Building a Second Brain too, and I've taken a lot of inspiration from it. In fact, the precise reason I'm working on this project is because "organizing information as a background process" feels a bit too much like navel gazing to me and things are a lot more fun when the process includes interacting and sharing with other people.

The particular way I'm attempting to encourage publishing is an editor that lets you lay out your stuff as a directed graph instead of as a linked list. The reader navigates the graph by clicking on hyperlinks that take them in tangential directions that may or may not converge with the main thread.

The inspiration for this includes those really good conversations you have with your friends where you go completely off topic but in an interesting way, and also the experience of going down a wikipedia or tvtropes rabbit hole that consumes hours of your time.

It's a tough problem because your eyes and ears are only able to process information serially, but concept-space is a complex multi-dimensional snaggle. How do we bridge that gap? The conventional answer is "good writing" but that's really tough to do. Eugene Wei didn't feel up to the task with the ideas in the OP, for example. I'm hoping that by giving people more room to play with how they structure their thoughts and ideas "writing skill" will be less of a constraint on human communication. I definitely don't think I've hit an optimal solution yet but it is a very fun problem to work on and talk about!
I dont think this is true. Creativity happens when you combine/blend prior knowledge. We don't magically create new information without prior meaning.

TikTok acts likes this and the remix is like a blending/combining prior creativity that leads to continuous new creativity.
I have been at talks by their devs. They candidly admit it will never meet the needs (accuracy) to address questions at this level of specificity. Some things will be extremely successful, many (most) will not.

Think of biodiversity as a curve, with a long tail. Will AI on poorly taken images specimens work for the bell? Probably. Will it actually get at the numbers at the tail? Almost certainly not. This is largely because 1) getting at the tail requires intimate knowledge of where to find that biodiversity (the vast majority of iNaturlaist pics are shockingly close to civilization, where diversity may not be) and 2) intimate knowledge, often of internal features or other non-imagable data, so that one can actually record data that fits in the tail.
It's tautological but worth noting: capital is abundant for projects which VCs as a class are already eager to fund. If you have an idea which does not appeal to VCs, capital is not abundant for you.
We might want to highlight this more often that not.

Code legibility is starting to become a primary if not the primary factor for a lot of software these days, because that's what allows it to be maintained.

I think more analysis should be done on why this is for go. Java and C# should be similarly legible, they are not complex languages either. It's possible that go encourages certain paradigms.
Rube? Educate you? You do realize why people are off put by you? I'm happy to engage because I was raised like this. Most people downvote and move on. That is one issue here you need to resolve.

The second, which speaks directly to the concepts talked about, is the idea that "everything in the body is a cell" is a poor analogy to use to try to articulate your idea either supporting or not supporting the original posts concept, and you got salty when called out on it rather than have people simply agree with your "amazing insight".

PS I love this game.
This is really cool! I love seeing GraphQL back in its roots as a way of improving the developer experience for native iOS apps.

From what I understand, this project tries to solve one clear pain point that isn't solved elsewhere: Swift developers can use GraphQL in Swift without writing GraphQL directly. Being able to create idiomatic operations through Swift is nifty to see.

Somewhat interestingly, it seems like to solve other problems, @maticzav is independently following similar paths that the original developers of GraphQL in Objective-C followed. Some of the highlights:

- Using code generation to make access patterns more type safe.

- Creating a centralized set of Type Models, that map 1:1 with the schema the app accesses.

- Mostly separating the GraphQL operations (in this case, as written in Swift) from the models a component interacts with: the components just see that they have a Schema-based Type Model.

I'd personally think about using the query-creation API to produce query (and fragment, once those are supported) specific models for consumption. The problems of both over and under fetching may expose themselves when more than a couple interactions are operating with different views over the same types. I've talked about why Facebook no longer recommends Type Models before: https://www.youtube.com/watch?v=Vo8nqjiKI3A

It's really encouraging to see the recent explosion of ideas for "how to do GraphQL": I'm not sure what sort of synthesis these myriad projects will create for the broader community.
Brewer colour schemes ftw.
"Big Tech" has become an umbrella term which can mean any of the following:

* Big Tech monopolies controlling news and information: Twitter, Facebook, Google

* Big Tech monopolies on Advertising/Marketing:
Facebook and Google

* Big Tech monopolies on Multimedia content: Netflix and Spotify

* Big Tech monopolies on Cloud Technology Infrastructure: Amazon, Google, Microsoft

* Big Tech monopolies on Mobile: Apple and Google

* Big Tech monopolies on eCommerce: Amazon

We could be talking about "Breaking up Big Tech" for 50 years trying to break all of these up. It's kind of insane.
There's a difference between using a struct to represent concepts like program configuration or grouped function parameters, and shoehorning OO-native design concepts like the decorator pattern that need inheritance into a language that doesn't support dynamic dispatch. Much of the bad Go code I see comes, yes, from overusing abstractions and lots of copy-pasting, but most of that comes from trying to fit square pegs like OO design into Go's round hole.
Having worked with a lot of contracted firms that do custom software development and platform customization, let’s not put them too high on a pedestal. What money you save on FTE programmers needs to be funneled right back into management talent to make sure they deliver a quality product (high utility, supportable by next contractor, quality docs, etc). Good management talent is hard to find and not something any government is known for. Consequently, next contractor probably has mondo ramp-up time deciphering what hacked pos the last guys put in with their c-team developers (cuz margins).
I think it's just a difference of perspective and certainly not a dreadful way to live - whatever way you choose to live is fine by me as long as you give others the freedom to choose for themselves.

I personally think that the philosophy of action comes down to desires in every case - any act you take is taken because a tally board in your brain weighed a number of alternatives and came out with that act as the winner. That tally board isn't observable and may contain a lot of factors that you would never consciously place there (see, for instance, physical ticks) but at the end of the day the machine known as you decided that that action was the best to execute.
They have a much higher TDP because you are comparing PC parts that are not optimized for power consumption. Their uncore is made using power-inefficient lithographies to save on cost and contribute a ton to power usage.

They also have a lot more cores.

Per high-performance core, M1 macs are tied or less efficient depending on the workload.
> decreased effectiveness?

Yes, because the public conversation about vaccine effectiveness is very simplistic. The first-approved vaccine, the BioNTech/Pfizer vaccine, was developed in Germany and the development subsidized with >$400mio German government money. Its success got a heap of media attention, owing also to easy access to the BioNTech founders and their human interest potential (the company was founded by Turkish immigrants, Germany's largest ethnic minority).

"95% effective" is the gold standard everyone knows now, and accepting anything less, to people, feels like they will miss out on their only chance to get "the good one". They want to feel safe, not 70% safe. The latter sounds like Russian Roulette - 30% chance to get sick just the same anyway?

The reality of course is different - it's not a binary will get sick/won't get sick, but also a "how sick". My own understanding of the medicine is also limited (I would love if this prompts an insightful comment explaining efficacy!), but AIUI almost anyone would be far safer wrt/ getting seriously sick on AZ than remaining unvaccinated.
It's not that easy. A new language starts because a set of developers has a problem, however that doesn't mean that others share that problem or agree to the choices and solutions made. Rust seems to be in a good situation where this worked for large parts, but many languages came and got no or only short attention.
I've seen plant identification groups, and the thing is that a blurry picture of half the thing is not conducive to accurate identification.

When these are correctly identified, it's often because the person has a particular investment in that exact plant. So if the expert on irises or two-stripe bumblebees is offline at the moment you might get crickets, or wild-ass guesses.

There is something about video that makes it easier to identify things. The object feels more three dimensional, I suspect, which makes it closer to field identification.

That said, we use camera 'traps' for very shy mammal species. I wonder if we could tune those systems for bees. (A fox or cloud leopard might run if the camera gears make noise, but do bees give a damn?)
It's all terribly simple: https://http.cat/
Perhaps I'm a minority, but I got A LOT of value from my investors (both pre-seed, seed, and series A). To the point where I'd consider them core partners in my journey of building the business.

I know Aaron isn't saying that the investors don't matter.

But when I think about why VCs hate going through an auction-like process, at least part of it is human nature. Like, we're about to work together for a long time. Let's not start off by commoditizing what we each bring to the table. I understand the POV that 99.999% of what VCs bring to the table is the literal commodity of cash... but if you have good ones, they really can help.

In our case, we had multiple term sheets for our Series A so I was able to optimize terms and get the partner/fund who I thought would add the most value but at "market" on the other terms. "Market" being what was on the other term sheets. That seemed to work OK as a softer way of actually doing the auction.

The real point in all of this is that if the VC's value-add is true, then you shouldn't NEED to discount things because of that. If it's real, then they should be happy to pay 'market rate' to invest in you, and the impact of their other value will be that together you build a better business, which is more valuable to them too.
The one all the cool-kid execs are using these days is "lean in to" as a replacement for the boring "focus on". As in "We're going to be leaning in to Cloud and Chat Apps this quarter in order to grow our investment into execution and innovation..."
I am not in Texas, so a couple of questions for those who may be affected by this story, because I've been wondering about this:

1. If you are on this plan, what is your visibility into current prices for electricity? e.g., are there any alerts that you could have signed up, even if you hadn't before?

2. Have you been bitten by unexpected high prices before, perhaps in the summer?

3. Prior to this event, would you say you saved money overall with Gridly?
> As we vaccinate the people at the highest risk of hospitalization, the correlation will change: Numbers may stay very similar, but hospitalizations should go way down.

Then we'll know in 2 weeks to change the policy and account for it.

Note that vaccinations will *also* cause the %positive and case# to decline. USA is approaching 15% vaccinated at over 95% efficacy means that you'll have 15% fewer cases (as well as 15% fewer hospitalizations later on). I'm not convinced that cases will become desynchronized with hospitalizations: my expectation is that vaccination will cause a decline in both case# and hospitalization#, roughly in proportion.

But if case# and hospitalization# become less correlated, then it won't take long (~2 weeks to see the first effects, maybe 4-weeks to be sure of the effects) to see such a split in the time-delayed correlation.

-------

EDIT: Why the downvotes? Today, there's a new study being pre-pub'd that shows that Pfizer's mRNA vaccine is ~90% effective at stopping the spread of the virus (https://thehill.com/policy/healthcare/539783-pfizer-vaccine-...).

When you have a vaccine that's both 90% effective at stopping the spread and 95% effective at stopping hospitalizations, then the spread and hospitalization numbers will both go down severely (that is: #cases and #hospitalizations reported both go down).

This assumption that #cases and #hospitalizations will become "desynchronized" isn't necessarily written in stone. Its possible both numbers drop down dramatically in the coming weeks as vaccines are distributed... indeed, its highly likely IMO.
The real question IMHO is "does the library change impact the protocol itself"? Because last time I checked, gRPC the protocol didn't evolve that fast. Now, gRPC-REST bridges are a different thing...
The only major cons to rust imo are the slow compile times, the steep learning curve and the immature ecosystem.

You can solve the first hurdle with better hardware (for the same price as our usual specced macbook pro, I opted to custom build a beefy workstation with a 3790X).

The second, you just solve with time. I remember when I first started with rust I hated it. I was working on a native project, and felt like it would have been easier to do in C++. But internally now we have more mindshare and knowledgeable folk who understand Rust - this has helped tremendously in onboarding engineers to the language. Also, having a working editor (via rust-analyzer) and the quality of compiler error messages have improved significantly in the past few years.

In terms of immature ecosystem, I think the rate at which the ecosystem is advancing is incredibly promising. Tokio hit 1.0 in Dec 22 of last year, which will finally put an end to the dependency upgrade thrash we've had to deal with. Going from tokio 0.1 -> 0.2 -> 0.3 -> 1.0 has been a journey. But with 1.0, finally, libraries will have a stable API to target, so we won't have to worry about this much for a while. Additionally, in the following months we intend to start funding critical open source rust projects that we use to ensure their success.
> "Pro" is just a branding, not a class of machines designed for specific tasks with any specific guarantees.

I agree, and to be fair, there are plenty of professional use cases that are totally serviceable with one external monitor and 16GB of RAM. Not every professional is a YouTuber or big data engineer.

I can't speak for anyone else, but I do like it when the name of a product actually means something, because it gives me confidence in the honesty of the vendor.
I have done some reading about people who got convicted wrongfully. Being released from US prison is an extremely bureaucratic and slow process where nobody seems to be willing to apply some judgement. As long as the process was followed everything is fine even if it’s blindingly obvious that the person is innocent.

Getting into prison is easy but getting out is really hard and will take you years even if everybody agrees a mistake was made.
This is not the case. The very first Zen laptop parts were far ahead of Intel.
I don't think that's the main issue. I think it's that the general assumption is that Moderna vaccine is about 90% effective and AstraZeneca about 60% effective.

I don't know how well you can actually compare these 2 numbers and if those are even the most important numbers, but that's part of the problem: Most people only look at these numbers and that's why they would prefer the Moderna vaccine.
This looks neat. It's a great presentation, but it's terrible for SEO. People will still need that content on individual URLs. Does this support that?
> Discord has never been afraid of embracing new technologies that look promising. For example, we were early adopters of Elixir, React, React Native, and Scylla. If a piece of technology is promising and gives us an advantage, we do not mind dealing with the inherent difficulties and instability of the bleeding edge. This is one of the ways we’ve quickly reached 250+ million users with less than 50 engineers.

this sounds like a recipe for disaster in every other company i have worked with. are Discord's engineers just THAT good or is there something else going on here?
:facepalm: Wow. Trying to do too many things at once this morning and totally misread the numbers. Edited my original post. Thanks for catching.
> You are denying Pol Pot killing 1 million Cambodians was "genocide".

No.

> As I said even by your legal definition the Chinese are not committing genocide against the Uyghurs.

Counterpoint: They absolutely are.

https://www.npr.org/2020/07/04/887239225/china-suppression-o...
It's not really the subject of the discussion, but since you're here and interacting with people: would it be possible to ask the UI/UX folks if they could finally make the built-in shortcuts configurable (and deactivable)?

It's really weird that such a game adjacent piece of software completely hardcodes shortcuts, especially when so many of them either conflict with or are near-misses for common chords, especially for very disruptive actions like starting voice calls. Even more so as it already has configurable keychords, just not for most of the useful stuff.

Also they should fix the labelling around these, either it's just not working or it doesn't work reliably, but trying to override built-in shortcuts via the configuration (in order to disable them) has never worked for me.
Not quite sure why you answer that to my message since the only Ed Banger in my list are Justice (last release in 2019) and sebastiAn (2019 too). The others I listed aren't part of that group.
The problem with go here is (a) garbage collection, such that rust likely wouldn't have needed any unsafe outside of well-known libraries; and worse (b) when you need to do stupid C shit in go, there's no `unsafe` to contain it; it just spews over the rest of your code.

"Principled policy and software design" is exactly what's needed to get rid of memory bugs in C too! So we can conclude that these things are impossible, or else we would not need memory safe languages in the first place. Since it's increasingly apparent that go requires these mythical safeguards after all, it's safe to say that it is not a memory safe language in the useful sense.
At the same time, in college we are teaching our students Java and C++ because that's what companies expect our students to know. Half our CS curriculum is in Java. The students I teach loathe C and C++ and want to learn Rust, but we won't teach it to them except in an experimental elective that won't count toward their graduation. So it's hard to say how many young programmers out of college actually know these "new hot languages".
Who broke America from undisclosed ivory tower locations
There's also the unfortunate belief that "earth was created for our use", which blesses the exploitation of all available resources.

This idea has floated around since well before industrialization, but the negative effects were localized until then.

So we're simple reproduction/consumption machines -- and that is our highest calling. Woe be to those who would disagree.
When I saw the headline of this article on HN, I assumed Aaron Harris was starting a new venture capital fund called "Abundant Capital" after leaving YC. How ironic that the article is about how "new funds... seem to launch on a daily basis"!
And yet, the software may save more than a million dollars in admin costs. And as soon as the most of the bug are worked out, it can operate less of those payouts. Don't let perfect be the enemy of good.
Must be awful - to lose someone from covid over the last 12 months would be bad, but to be so close to the finish line....
Like you said there are questions of efficiency, but hardly any questions of effectiveness. By clipping in and being able to muscle around the full rotation might burn more calories, but it does allow you to push out more watts. Try climbing a 10%+ incline clipped in vs flats. You might be more tired at the top of the hill clipped in, but with flats you'll likely spin out and be forced to hike your bike. Regarding this study, I don't think form in cycling can be trained on the typical trainer. You'd need a rocker plate and something raises/lowers your fork to perform any of the movement that outdoor riding requires.
It is a general rule that you can fall back to. Like all general rules there are exceptions, but those exceptions have to be explained. If you do not use boring technology, you will pay a price, so you really need to think if the price is worth it.
I’m tempted to subscribe, if only it weren’t so comically expensive.
No. React/TypeScript is too productive for our project engineers.

But we do write our perf critical stuff in the client in C++/Rust! For example, our entire video capture pipeline is in C++/Rust (the meaty bits in rust, some glue in C++ to interact with WebRTC.)
> Walking/running/driving with headphones is likely unwise

Driving while wearing headphones is outright illegal in France, [0] and some US states [1].

[0] (PDF) https://www.rospa.com/rospaweb/docs/advice-services/road-saf...

[1] https://drivinglaws.aaa.com/tag/headsets/
Depends on where you live, in the Midwest the peak was more around Halloween in October. You can hardly find Thanksgiving in any data (and then you probably have to squint and ignore proper statistics) By Chirstmas/new year things were clearly in decline. Other areas of course have different results.
There's an Adam Curtis documentary on the subject, The Way of All Flesh (1997) which seems rather good. Interviews with many of the people involved.

https://www.youtube.com/watch?v=R60OUKt8OGI
This very easily refuted, then no creativity is possible because who was going to create the "first knowledge"
None of those problems cited are the problems of the inmate/ex-con. It's the state that is choosing to go ahead with implementing buggy software affecting people's freedom, it's the state's duty to make things right.
I've done both, but mostly I use it to speed up the debugging of JS issues.

I'd consider adding a GIF or video of the flow to connect with a dev.
Good point. I'd edit the title of my submission if I could to include 20%. Doesn't appear I can do that now.
Mainly it means somebody else can spend your money and can get you in trouble you can never get out of.

Imagining the other is yourself, and not just somebody else with all your memories who looks like you (whether you are the original or the copy) is the first mistake everybody makes, thinking about it.
Adding a 100+ amp contactor and two way communication to every existing meter will add a lot to the cost of the equipment required at a user site.