skysight-inc/HackerNews huggingface dataset:
Right. After 1945, the Soviet Union didn't suffer war on its territory - it exported it abroad instead, from Korea to Hungary, Czechoslovakia, Vietnam and Afghanistan. Proletariat of all countries, unite!

Meanwhile, the economic conditions in 1985 were just as broken as in 1945. I know because I was there, as a brainwashed oktyabryonok, being sent to stand in a bread line with a talon (a rationing ticket for bread). In Moscow Oblast, the most prosperous in the country.

The level of naivete and pedantry in this whole discussion is amazing to me, on so many levels.
Change is the only constant.

Adapt.
I've been trying to figure this out and just end up being more confused.

One issue is that song's use of "ye" seems to be from the 1750s, so about 150 years after the KJV usage, which in turn was somewhat archaic. English changes.

Another is how https://en.wikipedia.org/wiki/Ye_(pronoun) says:

> In Early Modern English, ye functioned as both an informal plural and formal singular second-person nominative pronoun. "Ye" is still commonly used as an informal plural in Hiberno‐English and Newfoundland English

So it's possible that the KJV uses "ye" only for formal singular second-person, even if was also used more widely used for informal plural, and as that informal plural became more widely used, it became the go-to way to translate the Latin, which is in plural.

And then I read https://www.etymonline.com/word/you?ref=etymonline_crossrefe... and my eyes roll up in confusion.

Most likely I misunderstood the text I copied from the KJV entry, and "ye" and "you" are both plural forms?

I give up.
I think it's the whole etiquette of "Don't discuss religion or politics in polite company." If you really passionately believe in some political figure or religious thing, that's great. Other people don't, and I'm hosting a party for everyone to have fun, not just for believers. So, for the sake of getting along, leave it behind. Surely even passionate people can avoid talking about these topics for the mere 2 or so hours they spend trying to have fun!

I nearly had to throw someone out of a pool party being hosted for a bunch of 10 year old kids. The kids were all having a blast, but Mister Politics just couldn't stop talking about and inserting his political views. In this particular case I was in agreement with him, but it doesn't matter. This shit doesn't belong at an event that's supposed to be fun.
Do you have any good resources on how to manage this?

I've run into similar history management problems with `screen`.
Working with something that uses an ES3-like level of the JS language, it's actually painful not having some of the conveniences added in the past decade+.
One of the many values of a good communications team is that they communicate in both directions. They’re not just mouthpieces for the company, they know the customers and users and market as well. A good comms team will tell the company when users are confused about something; a great comms team will tell the company _before_ users get confused at all.

By shutting down the comms team, Musk isn’t just saying that he doesn’t want to play by corporate communications rules, he’s saying that he doesn’t want to _listen_ to anyone, either.
First time travelling to California ages ago, I had to try how fast this rental car went on a Hwy in the desert (close to Death Valley) with not a soul around. Downhill it went quite well. Then towards me on the right just a few meters about ground an airplane was coming towards me. WTH? It took me a while to realize that this must have been law enforcement. I went mostly by the rules afterwards and didn't receive a ticket.

Another time, many years later, I got carried away a bit on my m/c near Mojave. It didn't take long for a cruiser to follow me and flash his lights. After stopping the cop called in his mic ("I got him"), presumably to a helicopter in the air. Don't recall, whether I got a ticket then (over the years I got more stern warnings than tickets).

Not long ago, going on Hwy 25 there's a long straight stretch between two hills where it's really tempting to go flat out as there is (or used to be) very little if any traffic. Shortly thereafter a single engine air plane was approaching me left of the road at very low altitude. I was actually wondering whether it would clear the trees in its path, until I realized that he meant for me to slow down ;-}

Now I have a Prius and no such worries.
I read this because I was confused why a system-on-chip was a controversial subject... It got more confusing until I got to the second paragraph where it was actually defined :)
The fact that you compare having a drink thrown on you or getting hit with a sprinkler to this attack shows how little you understand the situation. The water is not the issue. The issue is that this man treated a vulnerable woman with absolute contempt and set out to hurt her. Maybe you don't have enough empathy to understand how that feels, but the rest of us do.
Apache httpd uses subversion.

That's the only example of a well-known project I could find that's not directly related to subversion itself. I'm sure there are others, but all the other ones I could recall have since migrated (usually to git).
Yeah, google doesn't have that. So it doesn't affect your life.
The problem with 10x programmers, and I say this as a 10x programmer, is that once you realize that you're 10x as efficient and effective as your colleagues it can lead to cynicism. You quickly realize that everyone around you is also making big bucks working at FANG while they work on their handful of items each sprint. Rather than destroy yourself, you can outperform everyone by operating at 2x efficiency. Perhaps this is a combination of cynicism and age.

That said, I think most of the time the difference between 1x and 2x-5x is putting in a tiny fraction of additional effort. That can be as simple as taking the time to sit down and read all the docs and whitepapers you might get inundated with on a new project as opposed to skimming through and then later complaining about everything being so complex like most engineers seem to do.

At a financial firm I worked at, I spent the first few weeks mapping the code out class by class on a notepad. It was extremely tedious but by the end of the second week I could speak intelligently about how the components interacted (on a massive trading system). For most engineers on the team, there was no sense of intellectual curiosity in this regard. Instead, most engineers I've ever met are very siloed and concerned about their small (relative) slice of the stack -- whether that's a feature, system, or product.

The key to being 10x is your methodology and mindset and that carries over to any experience. I've been 10x at finance, at FANG, in low level dev, and even measurably 5x on a language/stack I had never used professionally and had to learn from scratch (not easy, C++).

I think the key to executing at 5-10x is a careful protection of your most valuable asset, time. By examining how you structure your work, how you approach problems, how you approach "getting stuck" and reaching into areas of a problem that are unknown, as well as how you get distracted, you can find areas that are time sinks.

But in the end, I don't think being 10x is worth it unless it's for your own startup. There's a point in life where, as I said earlier, you get a bit of cynicism and realize you can work at 2x and get just as many accolades. You grow a family and a life outside of work and suddenly 2x is plenty and you can spend the rest on yourself or the people you care about.
It absolutely is, but time and time again TC39 has followed few champions over the waves of people favoring F# pipes.

It's incredible to me TC39 would rather have this monstruosity over F# pipes which are actually pretty similar to how most pipes work and read in most functional languages including unix `|` one.
...or the opposite.

the VAST majority of people who have taken LSD under reasonable circumstances have an incredible, life changing experience.

I personally know 100s who have, not a single one of them regrets it.
Wouldnt the poor trade in value dovetail with environmental values? The increased real cost is likely going to discourage you from trading in (where does your old one go?) and making do for longer.

Side note - maybe what the author wants is to lease a mac instead of purchasing? I guess some people do that with cars and trade up every few years.
Many such cases. Every major company (FAANGM) talks big about being all-in on AI, but when you use their products in your daily life, stupid stuff like parent's map example is glaring.
It wasn't just pay for fewer ads though it was supposedly going to be pay for algorithmic upranking, extra say with reports and in polls, and many other things.
The purpose of a union is to level the playing field between the many workers and the few boss, by sabotaging their attempt to "divide and conquer".
I'm sure there's worse hiding beneath the covers of some apps you use on a regular basis; e.g. Teams, Office, most AA/AAA games, etc. While Electron is far from optimal, just because a great app is built on top of it doesn't make that app any less great.

As an example, although I do have a prejudice against Electron based apps myself, that doesn't prevent me from using VSCode, which itself is based on Electron. VSCode is pretty great, and I'm not going to not use it simply because it uses Electron.
At the risk of sounding like an HN contrarian: I find it fascinating how many projects reinvent the wheel with a complex solution for something that's already easily possible, while introducing all sorts of limitations and security issues.

This seems like a repository of—hopefully verified—NodeJS scripts, and a standard library of common tasks, presented by a slick graphical launcher. The appeal seems to be that it's cross-platform (yet no Linux?), and that users can write their own scripts.

But... Other than the standard library, which might be useful, all of this is already possible. Just write your scripts _in any language_ and launch them via the universal launcher: the command line. Or, if you want to get fancy, use any number of script launchers, like rofi on Linux.

I'm curious to know what this tool does differently or better than what's currently out there.
This reminds me of the time on Something Awful that radium banned the one user that was using WebTV.

> About 91% of visitors are on Windows. Mac users make up 5% and Linux is 2%. The other 2% are permabanned IRC trolls browsing the forums with a text-based browser written in Ruby on OpenBSD. Oh yeah, we have one guy using WebTV but I banned him because WTF.
I agree.
web browsers need to become a service in the OS that can securely be shared. Electron apps are crap until that happens.
Show HN: IPyflow: a reactive, dataflow-aware IPython kernel
IPyflow is a new Python kernel for JupyterLab that understands how variables and cells depend on each other, making it easier to reason about notebook state. It adds opt-in reactivity, so that pressing ctrl+shift+enter triggers execution of all cells that depend (recursively) on the current cell. Furthermore, with its `code` function, you can see exactly what code is needed to reproduce a given variable.

I started working on it after watching the famous talk "I Don't Like Notebooks" by Joel Grus, and, anecdotally, I like notebooks just a little more when I use this kernel :)
Despite making up only 57.8% of the population, white Americans collect 92% of benefits from investor tax breaks.

I wonder if there any other statistics like this we could discuss here (those shared with the intent to malign the values, motives, or behavior of a particular racial group), or if they would be immediately flagged.

This comment itself will be flagged for merely hinting at the discrepancy.
Seems to me that someone "stole" it from F#. F# probably also take this idea from some unknown (to me) language. Here a similar idea in C++ https://www.fluentcpp.com/2019/10/18/piping-to-and-from-a-st...

This is generally a weakness of text based programming languages, that you cannot easily express graph flows like:

/ B1 \
A>-| | -> C
\ B2 /

|> operator only solves the problem for non-branched flows like A -> B -> C making them more readable by removing nested calls.

In theory you can create something similar using JS OOP by attaching e.g. map/use(func) methods to every prototype:

function use(func) { func(this); return this; }
function map(func) { return func(this); }

and then:

(1).map(n => n+1)
.use(console.log)
.map(n => "n = " + n)
.use(n => console.log("str = $n"));

Introducing a new operator instead of a library is a huge effort. I don't think this proposal will succeed, especially that current custom operator support in JS is nil.
No, but unlike Twitter their advertiser tools are at least halfway decent.
to all the people who claim this, i wish there was a RemindMe! feature to check back in a few months

People who have invested years of their lives writing thousands of tweets aren't giving up investments so easily. This is like real life investments or relationships, it takes a lot to break them
For context: I believe large slaughterhouses use CO chambers to slaughter, but those chambers are relatively expensive.

I've worked in a family member's small meat processing facility, and they offered slaughtering for hogs and cattle. The method there was to use a captive bolt gun - basically a gun, but instead of propelling a bullet from a cartridge, it used .25 caliber blanks to push a metal piston ~6" out the end. It was quiet enough that no hearing protection was required.

The process was basically:
* animals in queue were kept outside, in a covered holding area, separated from the kill floor by a concrete block wall
* a chute door was manually opened to allow a single animal into the building
* the animal was killed by placing the bolt gun on the head, driving the piston and parts of the skull into its brain
* the carcass was raise with a winch and hooked to an overhead rail system.

The rail system was used throughout the operation, from slaughter to when the carcass was broken down into parts. They didn't have enough employees to always have every workstation in operation, so there were freezers throughout the area that would be used to store the carcasses while slaughtering was taking place. Basically each one would be skinned, dressed, and stored in a freezer. Once slaughter was complete, there'd be a similar setup to break the animals down into quarters or large cuts (depending on the customer's order), and yet another to butcher from quarters into packaged cuts like you'd find in a store. Making finished products like sausages would be another workflow still.

My understanding is that this operation is pretty typical of small meat processors, and every one that I've visited seems to follow a similar pattern.

From an empathetic perspective, it honestly seems fairly optimal to me. Yes, the animals are uncomfortable because they're in unfamiliar surroundings, but they're insulated from the sights and sounds of the kill floor until literally moments before they're killed. I don't think oxygen deprivation is necessarily any better in that respect. I suspect it's more easily scaled, requires less labor per animal, and cheaper overall once a certain volume is reached.

ETA:

To be clear, I am not making a political or moral statement here. My background is very different from most people that I've encountered in tech, and I'm only sharing my experiences here to contribute to the conversation in a way that I expect isn't possible for most of us.

I assume that most people reading HN haven't spent time in places like this, much less spent participated in the process.
Making it smaller does add physics based safety features that couldn't be achieved otherwise.
Ngl just join the pro capitalist instance then?? Make your own pro capitalist instance?? It’s not like capitalism is a minority sentiment, you’ll surely be able to find plenty of supporters for your network…
This is a tricky area. Do we legally protect access to unpublished APIs or only published, supported APIs? If there is no API, should we legally require an API? Should the API support 100% of the services operations or may it only support some subset? What if the API is unprofitable, can the business reduce the set of operations supported or remove it entirely? Can they even release a new version of the API and retire an older version?

What, exactly, are you asking for when you say that "accessing APIs from 3rd party clients ... should be legally protected"?
One of the big ones Buffer [0] do not believe that they will be impacted this may not be an issue [1]

[0]: https://buffer.com

[1]: https://twitter.com/buffer/status/1616418191718207488
Wait until you read the gun free school zone act, which seemingly makes it interstate commerce merely to be on a public property proximal but not on school property, no matter you have no intent to interact with the school or the school property in any way.
"cvs add image.jpg" and then discovering you can't just do that 2 years later after a fresh checkout was fun.
“What’s so beautiful about creating products is that saying it in a poetic way, if you have that passion it naturally starts waves and those waves connect people. Then you don’t know where it’s going to end up, anything can happen, but if you don’t do anything, if you don’t write that text, if you don’t draw that picture or design that object, you can’t expect anything to happen. You need to start that chain reaction in life.” - Jesper Kouthoofd, founder of Teenage Engineering
> A lot of the time, the jobs (ie: iPhone assembly, AI related) are highly sought after

This description alsp applies to mining toxic substances by hand and high-end prostitution.

The artisan cobalt-mining by hand is relatively popular, and kills you withing 10 years. It is not difficult to explot desperate people. I dont think we should be whitewashing it
A quick google search shows varying numbers between 74k and 120k for median software developer salaries in the US. 54k seems quite low, where'd you see this?
A rocky past haunts the mysterious company behind the Lensa AI photo app
Yeah if you're good and have the resume/experience to back it up, you won't have any issues getting great offers even in this market. Great candidates are not easy to find in any market.
This is opposite in every way from my experiences above, including my direct experience being one. Especially the “rely on the team” - I think you’re confusing hero programmers with 10x programmers. Hero programmers leave husks of teams and shoddy code in their wake as they rampage through a career of self interest. A 10x programmer is a force multiplier for the team and spends their energy unblocking the team and driving a high standard for quality and ease of improvement. That’s essentially how they accomplish 10x the work, even in their own work. Because the team functions well around them friction to effective productivity is much lower.
> But even granting that this is true: congrats, you've just found the worst part of giving these intermediate steps a name!

Yes. But given that people would usually put you on a stake for naming function bake() because it doesn't tell anything about what the function expects or returns and bare minimum about what it does, this use case scenario is what happens very often, because naming your function in a very informative manner is very important because they are a part of the API.

If you really have functions like bake() or pour() in your code esp in weakly typed language then for the love of God, yes, please name the variables that you pass there and get from them always and as verbosely as possible.

Don't get me wrong, I'm very fond of naming intermediate things too. And with helpful IDE it can even tell you the types of intermediate things so you can better understand the transformations that the data undergoes as it flows through the pipeline.

But sometimes type, that IDE could show also automatically in |> syntax is even more important than the name for understanding. VS Code does something like that for Rust for chaining method calls with a dot. Once you split dot-chain into multiple lines it shows you what is the type of the value produced in each line.

My personal objection to naming temporary values too much in a pipeline is that it obscures distinction between what's processed and what are just options of the each processing step. But I suppose you might keep track of it by prefixing names of temporary values with something.

> Or maybe you want to just start with the unnamed nested or chained calls, and when you need to read or debug or refactor or test your code you pay the "naming things" price tag at that point.

Yeah, that's usually what I do. I start with chains and split them and pay for the names as I go.

> That's often the first thing I do when I come across code with a dearth of names, I just give everything a boring, uncreative temporary name, and then I can do whatever work I showed up to this code to do.

I'm also splitting and naming stuff in that case and checking types along the way. But I prefer that to encountering the code named verbosely and wrongly. Then I need to get rid of the names first to see the flow then split it again sensibly. Of course I don't usually commit those changes in shared environments. Only in owned, inherited ones or if the point of my change is to refactor.

Granted that chaining class member accessor mostly covers up this problem of naming intermediate things if you use classes. That's why we even survived without pipe syntax. But since we would like to move away from classes a bit to explore other paradigms maybe it's time?
Please, leave the accusations of rhetoric to one side. Your post could equally be described as the tired rhetoric of climatologists but it's unproductive and shallow.

Also. Please think very carefully about what they are saying because it makes no sense.

If weather stations are moved today that doesn't change temperatures in the past.

Moving individual stations is rare and climate change is by definition a wide area phenomenon. Occasional station moves shouldn't be having any effect on general global trends, yet the data is altered in ways that change long term trends.

Recalibration means adjusting your instruments to improve the accuracy of future observations. It isn't a word that lets you arbitrarily change recorded data. By definition, if you believe your instruments were badly calibrated in the past, it means that past data is unreliable and shouldn't be used.

When scientists aren't sure a measurement is reliable they're supposed to add confidence intervals. If the dubious data was from the past they should then retract papers built on that data, as the foundational data is no longer trusted. Climatologists never do these things.

Temperature data is now being changed for every month in recorded history, every month. There is no scientific justification for that possible. If they can't be sure what the temperature is today, or last week, to such a great extent that historical documents about the past now completely contradict present claims, then they can't predict the future.

There is no methodological claim that can change these things. Science requires basic standards or else it is meaningless cultism.
I'm really not sure what point you're trying to make here. Every example you gave is someone "managing" at their own expense. When an immunocompromised person gets sick from a rave, no one else suffers directly from that. Of course you can "manage" that way up until the moment you die. You can't get upset when society changes and some of those people decide the expense of "managing" isn't worth it any more.

I mean, come on. Just think about this. We've heard so much of this over the last few years like "some people died from the flu before, so you should accept you likely may die from COVID." Would you really say that to the face of an immunocompromised person?