skysight-inc/HackerNews huggingface dataset:
That looks great!

It's C# though, so I have no idea how to build this under Linux. I also wish there was a Minetest backend.

Similar: OSM to Minecraft[0][1] (there should be another code drop soon-ish, I heard [2] they plan to move the dev effort to GitHub by the end of the year).

[0]: https://minecraft.ign.fr/

[1]: https://github.com/ignfab-minalac/minalac

[2]: video, in French: https://peertube.openstreetmap.fr/w/cLpfr5jWd9SipjJTDKDPmj?s...
This reminds me that I should write down the experiences I remember as a child, including being chased over three miles by half a dozen kids. I finally crossed into an older woman’s yard, she recognized what was happening and asked me inside. I’ll never forget the beautiful polar bear rug in her living room. She got her keys and drove me home.

Lucky for me I sprouted between elementary and junior high, I also got meaner, and the problems stopped.

I turned out okay but I’m sure it shaped me in various ways.
Sweet child, he reads the documentations but doesnt use it. I concur with op, to this day, deleting a fucking file in Windows is an unbelievable chore compared to all their competitors. I tried today, nope, couldn't.

But you dont care, obv you dont use it.
The Casino-Chip Society
Good architecture is key, just building will lead you into pain very quickly.
WFH also means interviews from home. I'm a slender person but am not obviously so in video form. I'm also not especially tall. Again, not obvious. So there are several nice equalizers about WFH that some people don't seem to consider. Anyway, I agree with you that WFH is too good to give up.
It's far from clear that this is the "root cause". There is a good chance any therapeutic effect goes away after larger trials, like every single other drug targeting the same mechanism so far.
Yes, that "not the default" behavior is probably half my problem. I cant count how many days I've lost to trying to track down an issue in a project (trying to be a good citizen!), and then ultimately finding that the issue was already reported but closed by stale bot.
Well, you are going to have a hard time being more in control, unless you invest a significant amount of time and effort to write the app yourself.
Is this where all the stalls during big compiles come from?
You can give people permission to triage and close issues.
> picking only the best images and presenting them

> they removed the worst images and showed the rest

Is removing rejects not a way to pick only the best?
> Anger narrows your focus of attention on what you consider to be the 'threat' or 'obstacle', and anyone who's done technical work knows that the solution is often found by divergent thinking.

This is an interesting perspective. For me, anger sometimes helps me break out of a patient grind on a poor approach to a problem so I can consider more radical, divergent approaches.

For example, week before last, I did a refactoring that affected a few dozen lines of production code, felt good about the change, then ran the complete test suite and discovered hundreds of lines of test code that I had to fix, across dozens of files, because of fixture code that was copy-pasted between files instead of shared as well as rampant use of unnecessary mocks. My patient, responsible side started making the fixes one by one and scolding myself for feeling angry about it, telling myself we're all learning, etc., and this is part of working with less experienced programmers. I guess I'm at a point in my programming journey where for a while now I've been suppressing my elitist tendencies and conditioning myself to accept that it will be my teammates' level, not mine, that dictates the quality of code that we produce, and internally chiding myself for even thinking of it as "shitty code." But this time I snapped. I was too disgusted by what I was doing. I had such a strong "fuck this" reaction that I stopped making the fixes and left my office fuming. I came back an hour later and started consolidating fixtures and rewriting tests. It took me almost a week of unplanned work, but it made me so happy to just fucking kill that shitty code instead of making myself patiently, dutifully deal with it.

I think it was the right thing to do from a team leadership perspective as well. My teammates were surprised at what I was able to do, and now they can see a better way to write tests. We probably won't get that full 4-5 days of effort back in the specific part of the code I was working on, but I am optimistic that future code my team produces will look more like the cleaned up version than the original mess, and the effort will be paid back that way.
The Goal by Goldratt helped me think about optimizing for the end outcome versus sub-optimizing for process steps. (Measure but don’t sub-optimize)

The Goal: A Process of Ongoing Improvement https://a.co/d/iQGmd23
Everything would be better, but nobody would want to build the platform. Supply chain is a cartel industry and the present cartels aren't interested in new entrants.
> but rather the DOM that makes it so the perception of JavaScript is that the language/runtime is slow.

Not sure what you mean by this. Every time I run something like document.getElementById(), it is very fast.
And why not? They still get paid.
Further ideas

Aside from the FT,

Read the BoE/ECB publications.

Follow topics you're interested in via REPEC https://ideas.repec.org/services.html - see subscription options at the base of the page.

Follow the econ Mastodon econtwitter.net
Nothing short of linear types prevent you from saving the open file descriptor to a variable, closing the file, then using the open file descriptor variable again.
> the non trivial effort to normalize morbid obesity

Musical artist Lizzo:

"Throughout her career, Lizzo has been subject to body shaming. She is considered an image for body positivity and self-confidence. She partially credits social media, and the Internet in general, for changing the narrative around size and giving visibility to overweight women." [Wikipedia]

Also see:

https://headlinehealth.com/lizzo-308-lbs-is-clearly-and-visi...
Vanity Metrics: What to Track Instead?
I generally agree with my interpretation of this article. There's important lessons there on saying no and on avoiding forms of burnout. But be very very careful not to mistake this as a solution to "I don't want to eat my vegetables."

Sometimes we all have to do things we don't _want_ to do, in _some_ circumstances. If you're a contributor or author of FOSS, you are perfectly in your right to say no for any reason or no reason. But sometimes this all happens in a context where you're being paid to do a job.
I think this is a good point - pure JavaScript code is indeed exceptionally fast. DOM calls do have relatively high overhead, and if the change kicks off CSS recalculation or layout, then that can be even more costly. However that's not representative of the performance of the JavaScript language itself.
> I'm not at all the surprised that tuned Javascript can be as performant as pre-compiled Javascript.

Well you must be smarter than I am (which is not saying much).

For my grug brain, an untyped memory-managed interpreted language will be at a significant disadvantage against a typed compiled language whatever the use case. It's a testament to the Chrome dev team's hard work.

It is also possible that the WASM VM has not benefited from as much love as the JS VM.
>>> problem solver

“Applied Engineering Analysis” by Tai‐Ran Hsu, published by John Wiley & Sons, 2018 (ISBN 9781110071204)

Recent discovery. Complete reference in a single textbook. Applicable to any scale: from industrial automation to lunchtable experiments ;)

>>> better thinker

Wolfgang Engel. Decades of books from shaderx to gpuzen. Plus The Forge renderer!

>>> holiday fun

Flea | Acid for the Children (if you enjoy Just Kids, Chronicles: Vol 1, etc)
> Every single time I order stuff is missing, order is MUCH later than promoted, and customer service is awful.

How much of that is Doordash specific though. Sounds like restaurant issues. I could see the underestimate (I believe, at least, with some systems the wait time is manually controlled by the restaurant) as a means to get people to pick Doordash thinking it leads to a quicker meal.
I'd bet he isn't, but I hope they fleece him for the principle of it.
Why?

My commute takes me between 2-3 hours a day, and costs me thousands a year in fuel costs, extra insurance costs (since I need to have commuting cover), and car depreciation.

On top of that, I get 2-3 hours a day less with my family. In the winter that 2-3 hours might actually mean I don't see daylight until the weekend! Plus the stress of commuting, encountering unexpected traffic, etc!

Then at home I have far comfier office (with a much more ergonomic, comfortable, and health-supporting chair, desk, etc), a private bathroom, I can work in whatever clothes I want, I don't have to worry about being in for deliveries, I have a full kitchen and a stocked fridge, freezer, pantry... I could go on all day about the benefits.

There's nothing that can be offered that would make me want to work in-office.
Ooh, LiveView pattern implementors! I have a question -- I've been tinkering with a custom Phoenix LV client in my 'shop time', so I wanted to ask: are you doing your diffs on a string-based representation, like they do in the internal Phoenix LV protocol? Or are you sending the DOM patches?

In the phx protocol, their diffs depend on having split the render into a tree of 'statics', 'dynamics', 'components',
and on each change, that structure is patched, and needs to be recursively zipped to a string, parsed into a DOM, and patches computed against the previous DOM.

I've been playing with a new client as a way of understanding it, and it's definitely a certain amount of work! Fortunately computing 'what needs to change to reconcile 2 html-like DOMs' is a project that's been wrapped into libraries a few times in a few languages (phoenix relies on other people having done that too, via the 'morphdom' library in JS, and Dockyard recently open-sourced an ergonomic Rust library I'm using in my client).

So -- it's a lot of client work, but it optimizes for bandwidth. Cool.

But I've wondered if there could be any benefit to optimizing for granularity of patches, and simpler clients -- by sending 'just the patches', ie the list of DOM operations that cause the desired end state. My intuition is that the bandwidth 'cost' would be prohibitive, because the list of patches required to perform the morph could be quite large for a change that appears small in 'what string has changed' terms. (maybe harder to debug, too? lots of trade-offs)

I just don't have the energy to try it that way too, hehe, on the off chance that my intuition is off base and it'd actually help improve things (simpler clients, and maybe the bandwidth hit wouldn't be too bad?); it'd require deep server changes as well, when up until now I've only been writing a client. So I was curious what approach y'all are taking.

Prior/related art in the Rust space: I know there's a non-Phoenix liveview project, 'dioxus', with a generic DOM liveview implementation that several clients have been created for, by making a state machine that operates on that list of generated Patches; however I don't know what that one sends, whether DOM patches directly, or Phx-style diffs that need to go phxDiff -> zippedUpString -> dom -> morphPatches -> applyToDom.
Those patterns will only work if they also reduce calories though. The vast majority of people who are normal weight in the western world will have a mixed diet and their body is not 'going crazy'.
The exercise that was cancelling, including being hung up on twice during the process, is why I’d never go back.
I disagree, they are just not necessarily associated. Less intelligent people have problems too. Children constantly throw tantrums, for instance.

I do agree that overthinking and the high neuroticism that usually comes with intelligence will lead to an unhappy life usually.

Contentment imo requires understanding your insignificance in the universe and having strong values to drive your behavior. Usually that means not being a workaholic, though I'm sure that isn't true of everyone.
> It could also be the well-known effect that "weaker" (physically or mentally) people are more likely to be bullied.

Dang, I was going to post this suggestion as a joke (because “proof that weak people deserve it”—get it?).
OK, if someone abandons open source project and claims to be developing it then I see a problem.

(though open sourcing project and not accepting PRs or even issues is fine, if it is actually maintained)
They already trust each other anyway. They have contracts. And you wouldn’t supply shipping containers to Maersk to ship from here to their destination if you didn’t think you could trust them to do it.

So centralization would have always worked. At Maersk, or some industry trade group or something.

They never needed a blockchain. It was just the cool word of the day to make them hip.
The article mentions that you can't use FPS as a yardstick for performance if you're already getting "max", but there is a way around this.

You can measure the frame start and end time (duration) and divide 1000/average duration over 1 second. This will give you the render speed even if that's not the actual number of rendered frames.
> If PRs and issues truly will be ignored, then that really needs to be explicitly stated.

No it doesnt. No one owes anything to you

> Because otherwise, why even open source or release it?

Because they can.
I think their business model rests on:

1. Stomping out Grubhub and similar with massive spend.

Then...

2. Somehow profiting off of DashPass
This might also be related to end-of-year slowdown and budget cycle exhaustion for companies whose financial year (FY) aligns with the calendar.

There is still hiring happening between US Thanksgiving and the New Year but so many people are off (and some companies have time-off mandates!) that all internal processes slow to a crawl.
>probably saved countless cavemen from being eaten by lions

Though the laughing hyena found a way to game the system...
The Bank of Canada lost $522M in three months – here's why
I bet that came down as strings coming from the filesystem, or user for that matter might be in a language that requires UTF16 to properly be used.
Eh, as a burnt-out maintainer I have to say I can understand the use of stalebot and don't begrudge people using it at all.

When I started my project, I had the attitude that I'd be better than all these other maintainers. They flaked out but I'm just that much better that I'd never let the project wither.

But over time the backlog of things you're just not going to get to, or don't have enough information but you don't have time or motivation to go through composing a reply, begins to cause a genuine psychic pain. To the point you can't even open the repository because it's a reminder of all the ways you're failing.

So I think it's good advice that maintainers should use stalebot, because the alternative is a dead project.

Sure, it sucks that the issue you put time and effort into gets memory-holed but you're owed nothing for the time, as TFA says, fork it.

Edit: Even manually closing as wontfix is that much more work, you're asking for every issue in the backlog the maintainer does the emotional work of deciding that the issue is unsalvageable from their perspective and takes a manual action that will potentially get people mad at them and now they have to deal with being flamed. Closed issues are still searchable and preserved in the issue backlog, they don't disappear forever.
I'm a FT subscriber, and I can also recommend the Neue Zürcher Zeitung (https://nzz.ch/english).

They tend to have excellent data-driven reporting, and substantive articles.
French baguette gets Unesco heritage status
A rather unimpressive collection with the exception of the IBM and NeXT logos. In particular I always hated that OS/2 logo--so boring and now I know who to blame. The Westinghouse one actually ages pretty well.
Absolutely. The business of turning $1.00 into $0.95 (or less) must stop.
>lots of people will lose jobs

Isn't employment at highest rate ever? At least that's what I keep hearing.
The unit economics never made sense. None of the founders of these companies could ever explain how these things were supposed to be profitable without the hand waving. And it was up to everybody else in the company to make them be. Speaking from the first hand experience. So I too can´t wait for this gig economy bubble to pop.
There are fewer than 100 million shipping containers in use today. A database of all of them, their location, their destination, and what they contain is not even "big data." this is a mole hill built into a hype mountain with some crypto jargon.
Interesting. I use brave search on a daily basis and when I can't find what I'm looking for, I use !g as q last resort. For dev inquiries google is still king (Brave search is getting better and they're focusing on crawling SO posts).

Google is focusing on ads and it's really hurting them.
Oh yes, the proverbial wise young people who understand the world better. Not being able to be genuine on social media when they spend a large proportion of time "socializing" there clearly can't do any harm. In no way can this bring about a distorted view of reality and of what people actually think. No, not a chance, young people are savvy about these things.
POSIX does not work this way.

When the last directory entry for a file is passed to the unlink() system call, the file is removed from the directory hierarchy.

However, the data on media will be deleted only after all open file descriptors are closed.

One exploitation of this feature that I have seen is the SQLite temporary tablespace, which is created and immediately unlinked, ensuring that it will not persist after the program terminates.
>Build a real business. If you can't be profitable without eliminating all the competition by undercutting them then jacking up prices, then you shouldn't exist

This was a major part of the playbook of Standard Oil; I would consider them a real business.

>The business model of these so-called unicorns is effectively a Ponzi scheme

"Ponzi scheme" has been thrown around flippantly lately, and I think your comment is perfect example of that.

I think it's a safe assumption that significantly more people order food from local restaurants than they did before DoorDash existed. So they did create a real market with a real product. It's not a 'box' that SBF would be proud of.

>but the sooner gig companies like Uber and DoorDash collapse, the better.

This I agree with, but for different reasons. These apps price their services artificially low by charging high fees to restaurants, underpaying drivers (forcing them to live on tips), and by- at times- subsidizing prices with investor money to keep them artificially low.

Overall, I think it's a crappy business model that doesn't deliver much value. But that's just my opinion.
No one said anything about the purest..that would be tasteless.
Let it crash does't solve these problems. Let it crash solves random disconnections, machines dying and being replaced by others, unexpected network partitions and processes being killed because OOM.

I would be surprised if you write unit tests for these cases.
Maybe this is too simplistic, but pretty much no one is happy. Everyone has problems, even if those problems seem minor from another's viewpoint. I'm not sure smart/stupid has much to do with it.
I recently got hooked onto Munger and his thoughts. Fascinating.

Read this and heard his speeches, took detailed notes and am going through berkshire's annual meeting recordings since 1994 and it's surprising how many of these concepts reflect in warren and charlie's decisions, answers and thought processes.

I'm going to be spending more time on this.
> However, I do think maintainers, issue reporters, and contributors equally deserve clear and respectful communication and that, further, the burden rests on the maintainers to clearly communicate initial expectations.

Why? No they don't deserve anything. Unsolicited communication is unsolicited.

>GitHub provides the ability to disable issues altogether. Just do that if all you want to do is release a personal project as open source only.

Why should anyone bother. It doesn't mean anything
Blaming it on the person if you're in America is mostly wrong. HFCS and sugar is in literally everything. It's super expensive to buy healthy food. You have to drive everywhere so you don't get the exercise.

Can weight loss be done with food only? Sure. Is it affordable or attainable for the average american? Not really.
Some people have a strong sense of justice and love taking down people they see as cheating their way to success (this is often people who aren’t as successful as they thing they should be but aren’t accurately recognizing why). If you saw this going around social media, it might be easy to assume the creator made a serious amount of money or used it to get a good job. The more popular something was, the latter that group gets and thus the higher the risk of that group reaching a critical mass of disturbed people who escalate (often riling each other up).

Sadly, this also follows existing class, race, and gender status levels. If you’re an attractive white guy from an affluent background you are more likely to skate away from something like this without consequences. The further off you are from that, the more likely you are to encounter some sicko who thinks they’re putting you in your proper place.

Social media makes all of that worse because it provides instant gratification for everyone joining the pile-on and it allows them to feel like part of a large group even if they’re a small percentage of the total population.
> had there been a will for "collaboration" (and in many cases there should be)

The problem is, collaboration is seen by many as a danger to their business: common standards make it easier for clients to, sorry for the pun, jump ship; transparency / auditability makes it harder to hide internal fuck-ups and as a result provide an incentive for customers to jump ship.
Fair enough, I build json rest apis in Crystal, then someone else does the js/css front end.
I'd wager heavily that the vast majority of their support are also contractors / vendors.
IMO the Economist's version of "progressivism" has shifted to be more aligned with the World Economic Forum's version of "progressivism". Some might even say, in lockstep with the WEF at this point. IMO the newer brand is more aligned with the Third Reich's version of progressivism than the version I grew up believing in which is a generally non-invasive benovalent advancement of the human race.

One might do well to research the roots of "progressivism"; it's a very nice sounding word with some really evil origins, and the confusing thing is, it's evolutionary existence across decades has states where it was more good than evil.
It's because DoorDash didn't want to be a courier service, they wanted to run arbitrage on restaurant food. The courier service was just a way to get you to use their app with their prices.
Wow, this is really fantastic. Thanks for sharing.
> What happens when the coupons and discounts dry up?

Their growth stalls and they fire 1,250 employees as they rethink their business plan starting next week.
Graded Go Problems for Beginners

A bit of a cheat answer. The book here represents the game of Go. I found getting into this hobby helped in problem solving other areas of my life since it exercises analyzing many branching paths.

There are often too many possibilities to try every one, so it requires intuition to narrow down the good options, and then you can visualize how it might play out.