skysight-inc/HackerNews huggingface dataset:
So much stuff you can learn in the computer science world. For me the blockchain still is more or less a black box, should read a book about this stuff, as it seems to be hyped everywhere ;-)

Thanks :)
One does not excuse the other.
While it's possible to request from Amazon everything that they (claim to) have on their servers from our Alexa devices, it would be better if there was some way to explicitly deafen the devices. I had been using my Echo dot primary as an audio source to my living room speakers. But since it's not possible to know when the room audio is being piped back to Amazon I unplugged it. If there was a way to explicitly not wake to an audio prompt but only to a touch command I would consider plugging it back in... but I really don't trust it. So these days my living room speakers are fed by a very old iPod touch.
I've been using Stretch lately for a project I'm planning to open source in a week or two (a cross platform GUI engine...). Pretty happy so far.
I think it was called "C", by Bell Labs folks.
Cows have it pretty good (especially in my country Uruguay) - I absolutely understand it when you´re speaking about chicken and fish though.

The one ugly part for cattle is the slaughter, you need to have tough skin to work at a slaughterhouse.
very timely, AvE just made a teardown of an AOAS https://www.youtube.com/watch?v=NhZ0D-JRtz0
It's not as interesting as some of the structures in the PDF, but we are working on a problem where we have lots of timestamped data and need to quickly and frequently access the nearest data point from a given input timestamp. We ended up using a tree-like structure but that said, we ended up using whatever tree-like structure was available in the language.
I don’t really understand how that is so. The main FSF Libre software benefits they tout ‘for users’ are only actually accessible by developers. Specifically freedoms 1 and 3, to study and modify and improve the code and share those improvements.

The other two freedoms, to run it for any purpose and redistribute it aren’t in any way unique to Libre software. They’re important sure, but are really just free beer benefits.

Users can benefit from access to better software, but only as an incidental or indirect benefit if developers happen to release it or if they pay developers to do so. In the latter case now you’re in a commercial relationship and arguably a closed model can give users more rights and control they might want, for example exclusivity.

https://en.m.wikipedia.org/wiki/Free_software
>as disappointed as I am with this decision

May I ask why? Them moving doesn't look like an issue to me at least.
Quoting one of my favourite authors, Stephen Covey: “Begin with the end in mind”.

Instead of forcing yourself to finish, better ask: why do you want to do this project? What’s in it for you? Money? Online portfolio? Better employability? How does your work align with your core principles and values? Are you making a tool for saving developer time? Protecting innocent lives? Earning personal profits? All are valid options as long as your core principles are in alignment with what it is what you set out to achieve. Through time, the connection between you as a person and the work you set out to achieve inevitably becomes blurry. However, if a solid foundation of values and principles was made during the inception of the project, you will find it easier to resync your thoughts and realign yourself with your goal after burnout, fatigue or setbacks. Conversely, If your foundation is not solid, you will find it easy to convince yourself that time and effort is better spent somewhere else.

Make a clear vision of where you are, where you want to get and how this project is the key to your success.
> there are quite a few non-dairy creamers that work great

As someone who has tried a lot of non-dairy creamers, I have yet to find a single one that "works great". There's something very characteristic about both the taste and the consistency of milk and most replacement products are nowhere close. That's not to say milk is irreplaceable for all applications, but there's a tendency to over-hype healthy and organic replacement products that try to be "just as good" because we all want a sustainable, healthy replacement without sacrificing anything at all, but belying reality is hardly going to get us there.

Personally, I feel more attracted to the idea that it's better to do something than nothing at all. You don't have to go vegan tomorrow, if people just ate less meat and started thinking about this type of stuff as a luxury and not a right, we would've come a long way. Personally, milk in my coffee is non-negotiable. Bacon for breakfast? Well, I hardly need it every day, or even every week, so I'm open to discuss frequency.
One kind of accusation? Do you mean the kind of accusation in which the only evidence that a crime ever took place is the statement of a single witnesses? It doesn't seem unreasonable that you'd want to investigate the credibility of the witness in such cases. I certainly wouldn't stop at rape accusations.

However, I think I'd prefer to see a court, rather than just the police, decide what data should be obtained/requested and how it should be used.

I suspect that in some of these cases the police think it's a hopeless case and are looking for a justification for dropping it. They are perhaps thinking: if this person really wants us to prosecute, then, OK, we'll do it, even if it seems hopeless, but if they won't even fully cooperate by letting us examine their phone then we really can't be bothered any more because we've got lots of better cases to be working on.
Bitbucket and Bitrise: Configuring Continuous Integration for an iOS App
I was going to roll my eyes about stuff no one will ever hear of, much less use in their day job, but there are some really relevant structures here. Finger trees, cache-oblivious structures, R-trees, etc., just to name a couple from a random page or two. The "why they're worth studying" summaries are gold.

Thanks!
You're right.

They were both released extremely close together, and I don't remember why I associate Mercurial ideas as being something Git learned from. Maybe I'm wrong about it.
So what would you do then?

If you don't like it, don't present pale echoes of criticisms we've already seen (not listening to 30 years of language design...), tell us what you would do instead, because the answer is non-obvious and there is no one 'right thing'.
How can you make moral judgements about "social justice" and its advocates/opponents, when you can't even define the term in your own words? I appreciate your instinct toward open and polite dialogue, I just don't see how that can work on a topic you can't propose a definition for.
Having worked with contractors in the US, there are some added legal cautions where employers for especially software contractors to not setup too long/close of an engagement. But, in general many contractors will end up working for a larger contractor house which carries your vacation/healthcare etc. They of course take a cut to do that. None of them are exemplary, but some are less terrible. An arrangement of a cooperative of contractors and even whole mini teams could control more of their own destiny would be interesting there.
... and people ask why browsers are so complicated.
Presumably this "new standard" GP mentions would be codified into law. And the law would still be 'paramount.'

I think procedures to effect expunging records follow the requirements of paper. If you have tens-/hundreds- of thousands of paper files, a law to require physical removal of the specific convictions is burdensome to whomever maintains the archive. A law that simply dictates ignoring old convictions under certain circumstances is bound to be misused (whether intentionally or unintentionally.)

Since we're now in a digital age of keeping these records, I believe that automating the 'deletion and cleanup' of files under specific conditions is laudable.

Addressing your comments about 'only charged ... but suspected of': this reeks of discrimination masquerading as safety. If you can prove it, charge the suspect and give them their day in court. If you can't prove it, a LEO's own suspicions have no place in the decision making process of other cases.
So we can take over the galaxy.
Drinking an entire coffee in three minutes is bad for your body.
I'm curious how many people didn't buy these but got them for free as part of some other package (like renewing service on Verizon). Personally, I won an Echo Dot at a programming meetup but haven't had it plugged for over 15 months.
This sort of misses the point of influencer marketing.

You wouldn't _see it_ unless you subscribed to the influencer. It wouldn't be a "random" influencer _to you_.

Everyone has their role models, their influencers. It's hard for us to understand how others could like some influencers - and they probably to ours. But everyone has their own influencer - and they influence.

[Edit] This is not a defense of the products influencers sell. That's independent of their persuasive ability, often.
Typically vegans don't eat Honey so most do care.
There are a lot of vegans who don't eat products with Palm Oil in them because of how bad it is for habitats.
I agree 100% that its not the same but its also not Vegan.
yep, "think of the troops" is just as emotive (and patronizing) as "think of the children". Unbelievable that people repeatedly fall for it.
Well most of them don’t live on “ranches” for one.
The beet juice makes them "bleed", but more than that, it gives them the color of beef. And it turns brown when cooked.
Perhaps worth starting with Merkel trees before digging into blockchain implementations.
Cultural revolution was a political maneuver by Mao to suppress his competitors, he won that battle, but not the war. People he sidelined came back in power after he passed away, the biggest one being Deng Xiaoping.
As a young boy I certainly cried when reading that book.
Yes, this is a great point.

As a small businessperson, I find it's critical to be aware of the different strengths and weaknesses that come with being big or small, and to leverage them to your advantage.

My favorite one-liner about the difference is: small companies make it possible, big companies make it cheap.
Coz it was orchestrated by Mao mainly to persecute Liu Shaoqi and his kind by the hands of the people, Liu was of important position in the party and soured his relationship with Mao over the Great Chinese Famine.

The prolonged struggle affected a lot of high officials, including the Xi family, the Gang of Four was eventually deemed the culprit by those who survived, and "rectification" ensued .
In South Carolina Boeing produces 787 Dreamliners. The 737 Max is produced in Washington.
Enlighten yourself. I have to post here with a throwaway account after my other account got shadow banned for not being PC. 99% of HN are sheep. Silicon valley is blinding you all. Logic is going down the drain. Diversity in mental illness is taking over.
Same. I tried the impossible burger recently and was pleasantly surprised - it's as good as meat in my view. As a moral matter I will never eat meat when the Impossible variant is available.
This looks great! I've been using Yoga in my Rust UI framework via the yoga-rs bindings, and this looks like a nice pure-rust alternative to try using instead.
Also discovered by the company he is talking about in the parent comment (Boots).
I can "buy" a cow from a local farmer and they will raise it and slaughter it and deliver all the meat butchered from the cow. It provides nearly a year's supply of meat, at much lower cost than buying similar amounts from the grocery store. If more people followed suit of buying local farm direct then the whole thing would be better off.
> What interests me about this Finnish subculture is that it's perfectly cloned the "horse culture", just without any actual horses. It's very close to a cargo cult. Possibly Finland is too cold to have a regular horse culture?

I assumed this was why the hobbyhorse culture was female -- whatever the reasons are for horses to be a female interest, hobbyhorses are an imitation and necessarily target the same demographic.

Horses are expensive; it seems natural to me that enthusiasts who don't have real horses might be drawn to an imitation.
but if you go look up the definition of "vegan"

Oh, hell, no. I'm not looking to Webster's to define my lifestyle choices. You want to get all legalistic about it, knock yourself out. But don't set up a legalistic strawman and then proceed to beat the stuffing out of him.
It assumes a lot of costs are fixed, and do not scale with income. Software is weird like that.

Double the 500k R / 250k P company without more expenses, and you now have 1 M R / 750k P. Double the 1M R / 100k P and you now have 2 M R / 1.1 M P.

Especially if a firm can come in and do a round of layoffs (Replace support with outsourced, fire marketing, replace devs with outsourced).. it would be pretty easy to get the margin really really high for a few years, which is all they may be looking for.
Apache has a few big hitters, yes, but for dozens more it's been more akin to a tomb than an incubator. I really believe a large part of the reason for that has been their dogged determination to stay off GitHub.
Yes, it's sad on many levels. Never heard of a billionaire farmer though. Maybe Purdue (chicken)?
Huh. So can you script Friendface so that it sends out pre-scheduled posts? Dead me could really mess with people that way.

Now that I think of it, it would be an interesting hobby to build a virtual you that does things on Facebook.
Just a fair warning to anyone thinking about backing anything on Kickstarter: You have absolutely no legal recourse to against a company that doesn't deliver your goods. You pay Kickstarter, Kickstarter pays the company. Kickstarter is the only one who can enforce their terms against the company, and they're notoriously famous for refusing to do so. There is a long list of Kickstarter campaigns where the founders just took the money and ran. Even ones where the founder appears to have all of the best intentions fall apart.

Not saying to never back any croudfunding, but know what you're getting in to. From what I've seen, you get better odds at a casino.
> sometimes the stereotypes were the opposite of what they are today.

Correct, and this is the reason for which I qualified my statement. They do, however, apply to the section where western "horse culture" as is being debated arose.

I commented on some of this already, and don't want to pollute the comments too much. Link: https://news.ycombinator.com/item?id=19780759
My takeaway from the last 30 years in computer science is that errors are not exceptional. They occur often and should be accounted for near the code that generates the errors.

Exceptions and return values are both sub-optimal. Exceptions encourage drastic actions for non-drastic events (exit the program if an HTTP server is transitently slow). Return values encourage ignoring the error value, and then wondering why your program broke. Special types that wrap error values or exceptions cause the same problem; when you want to defer something, your code becomes contaminated with the error type (f(x) returns an error, g(x) calls f(x) but doesn't feel like dealing with the erro, so now g(x) returns an error... and all the way it goes up to the top level.)

Overall, I don't see a grand unified solution to this problem. We should make it possible for functions to declare everything that goes wrong so that recovery can be more easily tested. No language does this; they often merge vastly different errors into the same type, so the programmer is powerless to understand the possibilities. Consider two database errors; "syntax error" and "transaction aborted, retry it". Typed error systems typically condense that to a "database error", but how your program should handle the two cases are vastly different.

Anyway, I'm happy with the way go works. If I don't explicitly know how to handle an error, I wrap it with a tag and return it. When I look at the alert / error logs, I know which codepath caused the problem and can investigate. For cases where I know how to handle an error, I can explicitly deal with it (yes, often with strings.HasSuffix to find the one I know how to handle). That is all I really need. If it were an exception, the code would be basically the same. So I think it's a red herring to complain about values vs. exceptions. Neither system prevents you or encourages you to write correct, robust code. If we want to do that, we need completely new tools.
My go-to comparison for pro wrestling is stunt performers, since most of stage wrestling is stunt performing wrapped in the aesthetic of a fight. It may not be a "real" competition, but it's certainly a skilled and physically strenuous performance.
Humble Book Bundle: Python by O'Reilly
I have a very simple GPU abstraction in Pathfinder that has to manage lots of these objects, and it was easy and natural to get them to work. Sometimes I have to throw in a reference count here and there to make sure things are destroyed in the right order.

If the model doesn't fit perfectly into Rust's ownership system, I usually just do the checks dynamically and panic, or accept logic bugs (but not memory safety bugs), if things go wrong. Is that admitting failure? Perhaps. But it's also just choosing my battles. I'm trying to keep my code clean and ship, not prove it correct. Memory safety problems are pernicious enough that it's worth significant effort to rule them out, but almost everything else is a judgment call.
This is an extremely odd call. Also, how the hell am I supposed to prove anything here? Where do you even get data like that? That's my whole point, that this seems like some dude on the internet making some wonky proclamation. You want quality discourse? Then the person making such a claim needs to provide some receipts or else everyone else has to work twice as hard as he does to keep up with his bullshit.

I'm not making any claims about where vegetarians do or don't live, and it seems pretty bold to throw something out like stating where most people of such a diverse group live.
>Just let them be. And they will let you be too.

I think this is the point of contention. I don't think the type of person I'm describing will 'let you be' if you make an argument that falls outside their worldview. And the tone of the resulting debate is more often than not fairly toxic. The result is just more division.
Maybe in a debate club. If you're having a casual conversation, though, the emphasis is usually on having agreed upon facts and keep the discussion going.

Asking for fact-checks is fine, but it's also exceedingly annoying to try to build up a point while people who don't know what they're talking about disingenuously stand around demanding you validate every single statement or axiom you want to make. That's a common rhetorical style on the internet, and it seems it's very often designed more to exhaust and bore the person being questioned than as a way to improve understanding.
There's probably a difference between whole carbs, and the majority of what is available today in the market (refined and processed carbs). That probably plays a role here.
The headline's referent in non-video form: https://en.wikipedia.org/wiki/Straddle_carrier
Here in a small American city, fountains are seemingly coming back into vogue
That's the 0.5 Elixir developer. Let's face it: It's easy to become a poor Elixir developer, but those capable of becoming a good Elixir developer such that it's worth the cost of effort to train them, are uncommon.

As the CIO, where the buck stops, I learned Elixir well enough to write my own Genserver-like implementation from scratch, and thoroughly enjoyed it. I wanted to be able to understand the code base. But I am still a far better Python developer than I will ever be an Elixir developer. It's all a question of time utilization.

Due to the modular nature of our integration, it's relatively easy to move from one platform to the other, one module-at-a-time. And in the end, the cost of getting a new Python-based platform up-and-running far outweighed the cost of trying to retrain Python devs.
There's an interesting anti-meat psyop going around, coinciding with rising meat prices (Canada).
PetSmart’s online business, Chewy.com, files to go public
Gamedev, but even then actually implementing the data structures is rare. And nothing outside of geometric/parallel data structures listed towards the end.

I've had to use a concurrent priority queue once (locking a regular priority queue was too slow, dropped in a concurrent implementation), implemented kd trees a few times, and I've used half-edge once (a cousin of quadedges). Mainly doing graphics work.

Often the naive data structures work better because there's less indirection and it's easier to vectorize. In my case, depending on how much GPU budget you have available, you can also just scrap the CPU implementation and throw it in a compute shader.
Hmm, a good point I didn't even know to consider. I'm over here in the Apple camp thinking that such things cost $350 a pop.
I think its valid but difficult to argue that military arms procurement is not by and large a reasonable example of monopsistic negotiation (I hope thats a word :). But that it is debatable goes to show how its not valid to treat an abstract model like monopsony as though it is a factual encapsulation of certain business or issue, which is dishonest to avoid, as the parent comment put it.

Absolute monopsony might be a very threatening thing to absolutely profit orientated business, but in practice here nationalised public services like Health need have no interest in forcing their commercial suppliers slowly out of business with unsustainable deals. The position could be abused if it was arranged as such but if a Nation were to choose that outcome, it would make more sense to nationalize the suppliers promptly rather than slowly degrade their value.
Accelerate Supercomputing in the Cloud with Cray ClusterStor
Is that different from something like this?

fn main() {
let list = &[0, 1, 2, 3, 4, 5, 6, 7, 8];
let i = 0;
let j = 4;
let k = 8;
let iter_ij = list[i ..= j].iter();
let iter_jk = list[j ..= k].iter();
let pairs = Iterator::zip(iter_ij, iter_jk);
for (a, b) in pairs {
println!("{}, {}", a, b);
}
}
In the "easy" path, you're neglecting the lack of standardization in the "attach/upload" step. For some projects it might be as simple as "create an account on their bug tracker and open a new bug and attach the patch", but for others it might be "dig through their website to find a mailing list, dig more to figure out how to subscribe to that mailing list, send email". and then you might: "get a bounce because the patch is too large", or have to "repost because your mailer posted the patch in-line instead of an attachment, which corrupted it", or...

As much as I hate centralization, especially when the central entity is a for-profit corporation running closed software, often that ends up giving you a standardized experience that makes things easier. "Easier" doesn't have to mean fewer steps; I agree that the GitHub workflow you describe isn't simpler, but if you've done it a few times, it's mechanical and you don't need to think about it. GH even provides a command-line tool[0] that lets you avoid most of the click-around-on-website steps.

[0] https://github.com/github/hub
How do local farmers fall into the mix? I buy a cow every year from a local farm - they raise and slaughter the cow and deliver the whole thing butchered and packaged. I much prefer this to anything I could buy at the grocery store.
I don't know if that's entirely true—I followed him on twitter for a period of time before and after the sale, and post-sale his tweets got more and more unpalatable. Perhaps you're right, and he didn't change at all, but at the very least the public persona that he expressed changed.