skysight-inc/HackerNews huggingface dataset:
This article is deeply unserious bullshit.

From TFA:

"At about the same time, Secretary of Defense Lloyd Austin testified before Congress, promising to root from the armed forces supposed cadres of white supremacists driven by “white rage.” Yet neither he nor Gen. Milley ever supplied data or evidence that such cells or movements exist in the U.S. military.

That the Pentagon should foster such ungrounded suspicions of white males—one of its most important sources of recruits—is as if the British war ministers had questioned whether there were too many sexist British Gurkhas in the ranks, or Russian generals had wondered whether there were Cossacks that seemed clannish, or the Indian government had fixated on Sikh recruits as religious chauvinists.

Implying that white males collectively are intrinsically suspect of improper behavior seems a near-suicidal U.S. Army policy, given that the group died at a rate double its percentages in the general population in both Afghanistan and Iraq."

OK, so the brass didn't cite their sources. This doesn't mean such don't exist, and likewise recognizing the very real problem of fascist/far-right white supremacists in the military is not the same thing as "Implying that white males are intrinsically suspect".

Here's a link that indicates the military has a real problem with fascist infiltration, from the horse's mouth, as it were:

https://www.militarytimes.com/news/your-military/2021/01/14/...

"Though the services do background checks for extremist views and will drop recruiting prospects when they find evidence of it, the armed forces has a particular challenge when it comes to extremist groups.

In short, there are aspects of military service “that are of appeal to these groups,” the official said.

“We know that some groups actively attempt to recruit our personnel into their cause, or actually encourage their members to join the military for [the] purpose of acquiring skills and experience,” the official added."
...so only the first usage of `%` counts as a replacement?

What if I need the value to be replaced multiple times, like this:

|> `${%.id}: ${%.friendlyName} ${%.url}`

I'm surprised they aren't going with an idiom like `$1`, `$2`, etc or something like in other languages that have "magic" lambda parameters.
Yup, that's exactly the sort of thing I was thinking. Having a narrow focus means friends know exactly what they're going to get out of the evening, which makes it easier for them to decide whether to attend or not.

Same goes for me too, if a friend invites me over for board games, great, I'm up for that. If a friend invites me over for a general hang out, that could mean the even goes in any number of directions, some of which I'd be less interested in (e.g. heavy drinking, watching sports), so I'd be less likely to attend.
> For most projects CMake is far more readable and maintainable than Makefiles

That's only true for pure C/C++ projects. (I haven't used cmake with other languages so i won't comment on that.). I was specifically talking about the project where there were 7-8 shell scripts to build each intermediate step's target.

When you have to call external commands to build your artifacts, you end up relying on:

add_custom_target()/add_custom_command()/execute_process()/etc..

Example from that Makefile:

$(DISK_IMAGE): $(PARTITION_LAYOUT) $(BOOT_IMAGE) $(SYSTEM_IMAGE) $(HOME_IMAGE)
$(info "~~~~~ Creating disk image ~~~~~")
$(eval PARTITION_LAYOUT_BOOT_START:=$(shell grep boot $(PARTITION_LAYOUT) | grep -oP 'start=\s*\K(\d+)'))
$(eval PARTITION_LAYOUT_SYSTEM_START:=$(shell grep root $(PARTITION_LAYOUT) | grep -oP 'start=\s*\K(\d+)'))
$(eval PARTITION_LAYOUT_HOME_START:=$(shell grep home $(PARTITION_LAYOUT) | grep -oP 'start=\s\*\K(\d+)'))
dd status=none if=/dev/zero of=$(DISK_IMAGE) bs=1M count=2000
sfdisk $(DISK_IMAGE) < $(PARTITION_LAYOUT)
dd conv=notrunc if=$(BOOT_IMAGE) of=$(DISK_IMAGE) bs=$(BLOCK_SIZE) seek=$(PARTITION_LAYOUT_BOOT_START)
dd conv=notrunc if=$(SYSTEM_IMAGE) of=$(DISK_IMAGE) bs=$(BLOCK_SIZE) seek=$(PARTITION_LAYOUT_SYSTEM_START)
dd conv=notrunc if=$(HOME_IMAGE) of=$(DISK_IMAGE) bs=$(BLOCK_SIZE) seek=$(PARTITION_LAYOUT_HOME_START)

When you toss in other variables, cmake becomes a lot more verbose/less readable for these kind of use cases.
Other steps in that Makefile were about generating, signing, verifying each of the partition images, fetching keys from the servers etc.. That whole Makefile was 500+ lines, and pretty sure in cmake it would have been lot longer.
The big takeaway from these articles that are coming out should be that baseline estimates are really difficult to do. For any carbon project that is deferring harvest you need to be able to accurately predict what would happen if an area was not included in the project, that is, predict a future that will not occur.

Project developers may use one method to do this, rating agencies may use another method, but at the end of the day we can never actually know. There are so many unknown physical, social, and economic factors that go into whether or not some area will be harvested. This is why we see such huge ranges in estimates of impact.
Ask HN: What makes you passionate about living in this world?
For me, it is to see how far humans progress in space travel and exploration in my lifetime.
Not everyone reads personal email before showing up at work?
Why does maximizing profit have to come at the cost of human misery? I would argue that maximizing profit is a direct result of reducing human misery.
Ask HN: In iOS, why can't I allow access to mic and camera “Only when using”?
For location services, I can specify that access is granted "Never" or "While Using the App". For the microphone and camera, I have no such choice -- it's all or nothing.

Based on targeted ads I get, it's pretty clear to me that many (most? all?) apps that I grant microphone access to collect and sell data about me.

Apple's "pro privacy" stance makes it seem like this would be an easy win for them: let me only grant access to microphone and camera when I'm using the app. Is there a technical reason for not doing this?

My workaround for now is manually toggling access to the microphone and camera per app, as needed. Effective, but terrible user experience.

edit: grammar
So we might somehow create something hyper intelligent/powerful we don't really understand or can't even fathom, but we're apparently going to create it anyway, and then some how program it to want to optimize for paper clips...or it might somehow just come to the conclusion that it should maximize the number of paper clips in the universe for some reason?

All this AI / AGI speculation really sounds like we're inventing mythological like creatures, which is quite interesting when looking back through human history because they've always been part of the narrative at some stage only maybe this time, we might make something like that for real, or we're deluded and in 1000 years people will think we were primitive ancient thinkers, interesting times ahead.
Expo Router – File-based routing for React Native apps
This is all really pathetic because these companies are laying off, likely thousands of, H-1B workers who will have a tough time finding work willing to sponsor in the 60 day deadline. Likely many will be forced to return to their home country.

Trump's policies during COVID had the same effect, and many foreign workers returned to their home country either by choice or because of visa bans.

All of this seems overly shortsighted for the U.S. to throw away top foreign talent.
Employment in the US is largely at will. Only in large layoffs do workers have any rights to notification, and large layoffs are rare, so most US employees expect there’s zero right to notification.

This is a shock to folks in Europe, but when people quit here they generally give two weeks notice, and no one expects you to do any work in those two weeks.

This equilibrium is bad for labor, but very good for capital. Not shockingly, the US is a magnet for capital! The macro term of art for this is “a dynamic labor market”, and capitalists love it.

If you’re wealthy in the US, it leads to extremely generous compensation for in demand functions. But it’s also correlated with a weak safety net.
While there are really shitty places like this, it's almost getting to trope levels on the Internet.

The wait staff/bartenders I knew/know all do it because it was by far the highest paying job you could get. Especially with part time hours. There isn't much else you can do as a college student that will pay any better. And if you are very good, attractive, and get a bit lucky on where you work you are talking white collar pay levels per hour.
It has always been obvious to me that 10x programmers exist and I've been bemused by the backlash against the idea of the 10x programmer.

I've worked with two different people whom I would consider 10x programmers and I might even go so far as to say they were 100x or even infinityx programmers because they just created solutions that a team of normal programmers wouldn't be able to come up with even if they were given the rest of their lives.

Similarly, 10x people exist in other fields.

For example, there was outrage at Fusion (a journalism outlet) in 2017 when it was revealed that Felix Salmon was being paid $400,000 as a financial journalist, whereas other journalists at Fusion were being paid $60-80,000.

People made comments like "Fusion could have hired four Harvard graduates with degrees in Economics for the money that they're paying Felix" -- but neglected to consider the fact that Felix Salmon has such a profound grasp on the way markets work and is such an original, grounded, intuitive, and counter-intuitive thinker that you could not replace him with ten thousand Harvard graduates. He simply has singular insight.
Running a Funnel Analysis
That’s like asking whether layoffs at “a bookstore” are interesting
Besides the fact that that wouldn't actually have prevented this bug (which you acknowledge in your edit), /dev/fd/N is a linuxism, so wouldn't work on other unices. And has slightly different semantics than the current implementation, where your changes to the file aren't actually updated in the original privileged file until after you exit the editor.
I think the parent may be missing the trees for the forest here. I am not going to dismiss 'misery loves company' take, because there is a solid psychological basis for it. I certainly would not put it at zero.

Still, I think one somewhat unspoken reason for some of those posts is to indicate something along the lines of:

'hey. i was affected. i am available for x if you need me'

I am not going to give any specifics, but I know when me and my colleagues went through rounds of layoffs and this kind of informal job search helps to help one gain ground.
Wait, design by committee is not a good thing? Gasp

I can only hope this leads to Javascript becoming even more unbearable. Perhaps only this can weaken Google's resistance to WASM.
On Firefox you can right click and then choose "Save audio as..."
Run DMC thought Walk This Way would ruin them: instead, it saved Aerosmith
Ha! That explains a lot, I hadn't even considered it. Yes, a change like that would be massive, and I've just been fighting a guy I made up.
> “Joe spent quite a bit of time talking about the school his son was going to.”

Maybe he was baiting y’all. For the sake of conversation or whatever.

I’ve come to the conclusion the opposite case rules the game. It’s what brings us together that matters and is worth thinking about.
I think the real reason Wall Street made the decision to move US steel production to China is that a Chinese steelworker makes only about USD 12,000 per year, which more than makes up for any costs involved in shipping the steel across the Pacific to the US when it comes to the profit margin equation.

It could be true that there was some domestic monopolistic behavior going on, in that the steel industry's shareholders were blocking investment into research and modern process development, and since they faced no direct overseas competition due to protectionism, they got away with it for a while. Hence your argument about protectionism being a bad policy has some merit, but only if there's no robust domestic competition driving innovation and better technology (see SpaceX vs. ULA as an example of how competition drives progress).

Similar accounting-based cost-of-labor reasoning was involved in not investing in high-grade silicon and computer chip manufacturing facilities within the United States, although the consequences (supply chain vulnerabilities) seem to have caused something of a panic as seen with the 2021 & 2022 CHIPS Acts, which are probably good ideas, though no doubt they could also be called 'protectionism':

https://www.investopedia.com/chips-and-science-act-6500333
Given the same facts, I come to opposite conclusion. To create trust, this business must be conducted in public & must be open access. Imposing any more barriers or concealing the dealings would be actively harmful to the process. Anyone is capable of presenting good data to inform these decisions, to show how & why trust should or should not be given, and that's great, that's how we let in the sunlight.

It is just a mailing list. No one has to take commenters seriously. I found the tone here by the cimmunity to be quite fine. But even if it descended sitnificantly, became much less professional, I wouldnt be happy per se but I would not until a long long descent begin to question the value of the open process. It is up to the reader to figure out what credentials people have; as Kurt said, you've got to do your own searching to find out. That there is noise in the channel (in this case it did not seem to come from the community) is not something we should restrict the processs to avoid; it is something we must allow & be able to be tolerant & resillient to.
A bunch. 343 and Bethesda got hit particularly hard apparently.
Speaking as one who used to host (along with spouse of course) the occasional dinner party, brunch, whatever and now doesn't, there are two factors:

1. Kids (older than the "small and cute" stage).
2. Out of practice due to COVID! Worry about the virus is pretty low now, but in the meantime the clutter has grown, social connections have weakened, and the longer you don't have a gathering the less confidence you have to organize one.

The kids thing has multiple angles. One is that with all their stuff the house is a lot messier than it used to be, so much more intertia to make it presentable. Another is than active social life exists to fill a need for companionship that is just not as strong when you have multiple humans around you 100% of the time. The third is that the social crowd's growing kids have the same effect on them!
I have never seen evidence of this at all. Maybe reconsider your own biases.

I do think the quality has fallen overall at Ars Technica though. Particularly on their car articles, which for a long time now have been just regurgitated press releases filled with lame industry speak and no critical analysis. I also don't like that they are recycling Wired articles so often rather than posting original content. Great articles like this one are becoming less and less common.
How are these two stories linked?
I wasn't arguing that it was a good idea, only that it took place in contrast to OP's claims.
WebAssembly is just what you want, a second "modern" language that works in browsers. It hasn't reached 100% of its potential just yet, as there are some things missing for that (like DOM access) but once the language is feature complete, I'm sure most languages will have some sort of "Lang to WASM" tooling that'll allow you to write React apps in Ruby or whatever, if you so wish.

Stuff like that takes time though, so if you're antsy, you have two options: get involved, or wait patiently.
For sure. Assuming you have a few friends to start:

(0) Reach out to everyone. Everyone. That old college acquaintance you just noticed is in your city? Get coffee/happy hour. You never know who's looking for more friends.

(1) Encourage people to invite/bring their friends when you organize something. Hit up one friend for happy hour/food. "You've mentioned [coworker] a few times before - would he/she want to join us?"

(2) Host (implied) large group gatherings. Easy to say "come over, and bring whoever!" I like sports, so I host for the super bowl, World cup, March Madness, etc. - but could be anything. Throw parties for other peoples' birthday/going away/coming-to-the-city. Advance level: some bars are often open to "hosting" an event - they'll just rope off an area if you promise X people will show up.

(3) Host recurring events. Board Game nights, poker nights, dinner parties, wine club, etc. Great way to deepen relationships.

(4) Start group chats. Much easier to maintain a relationship with 4 group chats than 20 individuals. If one can't get critical mass, post the plan in another.

(5) Be actively welcoming. Make a point to intro yourself to new people/social stragglers on the edge, and greet people by name when they show up in a new-ish space (e.g., my friend brings his new gf to a board game night; she doesn't know many people here; stand up and say "Hello Janice! Great to finally meet you. How has your week been?"). Forge connection, don't just co-exist in the same space.

I'm sure there's more...
It'd be socially unacceptable for me to criticize participants in the special olympics, but I'm pretty sure that they don't control me.

That quote is from a neonazi who wanted to argue that jewish people secretly controlled the world because antisemitism is no longer socially acceptable in most circles.
I think the comment OP explained it pretty well.
It's less of groupthink, and more of betting on this side is the optimal choice.

Bet on permanent growth
- growth is permanent: You're a hero
- growth is temporary: Sucks, but you just do some layoffs

Bet on temporary growth
- growth is permanent: You're fired
- growth is temporary: You're righ! But so what?
When you take an immediate hard stance on defining a water spray as assault, it's hard to take you seriously.
> That seems like it's the worst of both worlds: ugly externally visible identifiers

Sometimes the external identifier is needed due to interaction with external systems, so it isn't really your choice as the DB/app designer.

>, record bloat,

Depending on the DB, the opposite can be true. In SQL Server if the integer key is the clustering key, which is usually the case for a table's primary key then you may get a smaller DB then using a UUID alone because the clustering key is included in all non-clustered indexes on the table (so the 4 or 8 bytes saved by just having the UUID and not also an integer ID is quickly lost to a larger amount of bloat).

> and having to roundtrip to the DB before you know the ID of a record.

For internal use you should just use the integer ID for the most part, the UUID or similar being for external references.

Unless of course the UUID is for security purposes (making enumerating records impractical for instance) in which case you'll be using the UUID in your own application directly. In these case you shouldn't look up the ID, just query by the UUID. Usually you are wanting to access the base record anyway so that isn't an extra JOIN, and if you are just referring to child tables (so wouldn't need to reference the main entity if not looking up the internal ID) the extra JOIN is usually insignificant, pulling back a single row, compared to the latency hit of a full round-trip to lookup the ID separately.

> I stick to UUIDs … with the exception of where there are justified … performance reasons not to.

A perfectly valid approach.

Though it does vary by DB, and what looks like a smell to someone with most posgres experience is often the more efficient method elsewhere, so you need to take that into account when looking at other projects (or working on your own if support for varied DBs in the backend is desired or a requirement).
While pipes are great in Elixir I think it’s important to look at the total cost to adding any new syntax in the context of the language that is considering them.

In the JS ecosystem, idiomatic nested function calls are read from the inside out. And in most cases that is highly readable because a single layer of nesting is all you need.

This proposal flips that on its head, so you have to retrain yourself to read code in a new way based on the presence of a |>. That adds significant cognitive overhead, especially in code that isn’t well written or that is already complex.

Your example looks nice, but also just as nice is the .then() syntax you could have used.

Now we’ll see code bases with both styles. You’ll have some team members who love pipes so much they’ll never call a function the old way doing x |> console.log and the rest of the team doing console.log(x).

Sometimes, limitations are a good thing.
I don’t think allowing your competitor to use your own data against you is ‘anti-competitive’

Old Twitter was just not a very well run business.
This is very disappointing. I'm kind of amazed that they think this is a good business decision when there are massive numbers of paying customers with mountains of python code using boto3. I imagine much of that code uses the resource interfaces since they're easier to use.

This isn't some fringe feature they're deprecating; the official documentation uses these interfaces in its examples; they're literally telling you that's the correct way to use the library and then the next moment they're telling you it's not.
I don't see how you think those two facts are related to each other at all. What does cash on hand have to do with if a company truly believes in recession?
Why do you think it's not?
That's pretty standard practice in journalism. You have a source (e.g. google employee) who you develop a relationship with over years and learn to trust — this is called a trusted source. They tell you something that they have seen first-hand , so you rely on that to be true.

Depending on the standards of the reporter/publication and the impact of the claims being made, you might try to verify the scoop with one or more additional sources.

Considering the guy is self publishing on Twitter and is not currently a reporter at a well respected publication, I'd bet this is just based off of a single source.

The system isn't foolproof but it works pretty well most of the time
> Neither seems very good to me, and the |> version doesn't really seem "less bad".

For me the piped version seems way better, way cleaner, with cleanly separated processing steps.

I don't like nested steps because for nesting multiple arguments functions your expression tends to grow in both directions and parts belonging to the same step tend to end up really far from one another and clearly distingushes them from data that's pushed through the pipeline.

% is short so it keeps parts of the same processing step together.

This syntax also enables you to express which part is the data to be processed, what are the processing steps and what are additional parameters of the processing steps.
I think in a way, MSFT is only doing fine because all the alternatives are doing awful. Google, Apple, Amazon, they're all not exactly at the top of their game. Also MSFT is in a huge dev. marketing campaign phase, so we as dev probably are exposed a lot more to their charm offensive than the rest of the population. Our perspective might be biased.
Oh wow, TIL about `Kernel.then/2`. That definitely works around the syntax problem.

An aside, the implementation is kind of amusing. It almost seems unnecessary for this to be a macro but maybe the compiler can optimize this a bit more? I would expect TCO to simplify of my "simple" implementation of

def then(value, fun) do
fun.(value)
end

https://github.com/elixir-lang/elixir/blob/a64d42f5d3cb6c327...
A lot of fascists in this thread, to no one's surprise.
> It makes me really question the judgement of the people that are working on this language

Only now?