skysight-inc/HackerNews huggingface dataset:
> Finally, any cool tech solutions are welcome.

The cool tech solution to talk about is the fact that we now have the computing power to do facial recognition over all of our cloud saved pictures, so we can just have a collection of all of the pictures you have of that person!
I can see this being useful but boy does it look ugly
For me it tastes a bit metallic, you can taste it clearly if you eat kangaroo meat.
Anyone who seriously sits down and thinks Ballard's prose isn't precisely what he intended it to be needs to read more widely.
Ok I've forwarded the email thread: https://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/m...
I don't care one bit about what Apple users can and can't use on their devices. Those consumers don't want general purpose computers, that want iDevices and Apple is quite right to exploit that market.

If I ever thought this was a threat to general purpose computing I would fight it tooth and nail. But Microsoft is and always has been the biggest threat there.

What I do care about is stupid shit like Apple messages, Air Drop, Air Play etc being locked up Apple stuff. What's really stupid is I can run an Air Play server on a raspberry pi and it works well with Apple devices but not at all with Android. It's utterly ridiculous that these things are locked up. Just let things be better for everyone you absolute fucking cunts. Of course Apple are by far not the only cunts in the world. People will be cunts unless we don't let them. Thank fuck for the EU (writing this as an embarresed UK citizen who no longer contributes).
> to coerce men to do what you want

You make it sound as if it's their god given right to make products as they please but that is not how the law works, and it's a good thing, because without laws we'd end up with stuff that works only in the vendor's best interest and ends up as e-waste sooner than necessary. It is also fair, because society is what ultimately allows these companies to exist.
By this logic, a car salesperson should get the majority of the proceeds from selling you a car. So from a $30k car, $15k goes to the salesperson, $5k to the dealership, $9k to the manufacturer, and $1k to the shipper. You really think this makes any sense?
hard doubt it's bc of old data. It could be a bug in the system, but most probably It's either bc you uploaded from another device/browser or bc of gmail or after the free period ended
Author here, I've forwarded the original email thread for those curious about additional context: https://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/m...
> ... whereas hydrogen proved a nightmare to produce, transport, and store.

"Nightmare"? Really?

The author clearly isn't interested in giving a sobre explanation of the situation but rather in writing a passionate plea for their opinion.
> to make a deliberate break with the tradition

In the monarchical period of European theatre, it was well-understood that the centre was a _pit_ full of hard-scrabble riff-raff. Having a box apart from this was a sign of social class (i.e. _wealth_ and aristocratic connexions).
Nothing wrong with those motivations at all. The maintainer should be fostering new contributors who are doing all this work, who cares if they just want the label. Is the work good or not is all that matters.

And, if getting your code into the Kernel is the only way you get that label then that's a shit system, all the testing and writing solutions "contributes" to the final code, its like the 90% you don't ever see.
It is by no means irrational to hesitate on a new major release of an Apple operating system. MacOS upgrades have caused many people all kinds of issues, for instance a Big Sur update broke a metric fuckton of USB-C hubs and they didn't address it for 6 months.
Maybe it has to do with the relative willingness of users to spend money on apps. Despite being a much smaller market, iPhone users as a group spend a lot more money than Android users. It just isn’t worth going to all that trouble to avoid the Play store.
Does Arch Linux have something like this?
Honestly, if prototype pollution was not a problem for optimization and other things I’d just toss a

Object.prototype.pipeTo = function(f) {
return f(this)
};

And call it a day. It does about 80% of what a pipe macro would do, has instant compatibility with other prototype methods and leads to very simple types. The only issue is that you have to define lambdas to call multivariable functions. D has got this very, very right.
The word "lest" is meant to come after something else. It means "for fear that" or "or else" or something similar. So it's not clear what you're trying to say. I don't know what "very systems" built by "the most evil" you mean either. Is it supposed to be obvious what you're referring to?
I would also add voice control.
That looks more like compose rather than apply (i.e pipe) to me
I have no dishwasher (or rather, that'll be me).

I inherited my pan 20 years ago; it ws in poor shape. I stripped it with caustic soda, and re-seasoned it, which took about a day elapsed. Ever since, it gets washed-up using detergent, and immediately dried. It's as good as when I first seasoned it. I've never had to repair the finish.
There are no differences. You can always substitute one for the other without change in behaviour.

These two are interchangeable:

func f[T any]() {}
func f[T interface{}]() {}

and these two are interchangeable:

func f(x any) {}
func f(x interface{}) {}

Maybe OP means the difference between using an interface as type parameter constraint and using an interface as a function parameter / variable type.
That's next, they were only dealing with one union at once.
I have an old X220. I also have a way older X31 and an X30. One of them has micro-XP running on it. I think it still works.
Try goat meat, you might like that.
Garbage destruction.
You can export the eml of the sent mail
I also highly recommend Extreme Metaphors. It's a collection of interviews with Ballard where he tells you precisely what his writing is about.
Missing Anthropic and how could you possibly forget NVidia in that context?

FANGO?
Previous discussion: https://news.ycombinator.com/item?id=12626314
Why's that company so big? I could do that in a weekend (danluu.com)
712 points | 423 comments
I heard Unreal Nanite built a job queue system on compute threads (https://www.youtube.com/watch?v=eviSykqSUUw&t=1611s), would that help with your use case or not?
In other words, a lot of clueless people entered drop shipping. With huge competition, sale prices declined, constant costs took more percentage.
I think the implication is that it's difficult to read because it's read non-linearly. You first need to start in the middle at `greeting`, then work your way out to `capitalize` on the left, then to `+ "!"` on the right, then work your way out one more layer to the left with `send`.

Some kind of pipe operator can make this easier to read by arranging the operations linearly from left to right (or top to bottom as is the case with this library). Although in my opinion this library has its own readability issues.
How is this "It gets worse"?

iOS has to assume what you mean with play OverCast. Maybe there are other people that wanted the device to play the band? This is such an edge-case which is easily solved by further specifying your prompt.
The generic function is cloning a slice so you need to allocate a new backing array. (think deep-copy)

Here that's just a one-liner that works.

I need to check but I think that if you need to keep the same capacity, you may want to preallocate manually.
re: the bouncy houses and such. Other than kids banging into each other, this never seemed like much of a head or brain injury risk. But watch out for knees! Trampolines with more than one person on them are incredibly dangerous, and bouncy houses seem likely to be pretty dangerous with occupants of widely varying sizes. The specific issue is that the floor may move abruptly and unexpectedly when someone is trying to land, causing a potentially severe knee injury.

If you’re in a bouncy house with kids, consider avoiding any bouncing yourself.
Big disagree. You just clean it out with a brush or something. Maintain your shit. God, imagine if you ever owned the roof over you head or something.

USB-C has the retaining clips in the cable which is a replaceable and sacrificial item. Lightning has it in the device so once it goes the whole device is essentially dead.

So much for "vastly inferior".
He was also stupendously influential in post-punk music - not for the music (Ballard had zero interest in music) but for the lyrics. He supplied the imagery for the subgenre. I wrote about it a bit here: https://rocknerd.co.uk/2016/10/25/j-g-ballard-and-music-how-...
> This is why using experts for advice is great but everyone should still be encouraged to do their own research.

Not everyone is equipped to do this kind of literature review (that’s not research), or have access to all these papers. Everyone needs to be critical and skeptical to a reasonable extent, but this kind of “do your own research” attitude is damaging. People just end up trusting dodgy but authoritative-sounding YouTube videos and blog posts because they cannot read scientific articles.
Ask HN: How do you run integration tests involving third party HTTP services?
Some approaches that come to mind:

- Convert the integration test to a "tighter" unit test which completely mocks the external service, thus effectively not firing any HTTP request

- Run a proxy/mock server intercepting all requests that responds with mock data, thus accepting and responding to HTTP requests. An example: https://mock-server.com

Most third party APIs do not provide a sandbox or a dry-run mode so this is a recurring topic.

I'm using Node.js so if you know of any node-specific tool, it'd be great!
IronSource is the good guy of ad-tech. Anyone that says something else just don't know anything about it. You can ask google security team.

Apploving wanted to merge Unity instead of IronSource because they knew the combined power of Unity/iron and apple will hurt their business.
All the buzz now is due to apploving UniFree project...
An Introduction to LiteStack for Ruby on Rails
If it was taken verbatim, sure - while perfectly fine under the license, that would be a dick move. But you should also note that the commit contains an additional essay or two's worth of analysis and justification, and includes test sign-off from other people. Even if you disregard the difference in code, the difference in commits is huge.

And as mentioned elsewhere, this issue was submitted to security@, triggering a machine optimized solely for resolving issues quickly and correctly for the safety of the user-base, and not one suited for training new contributors. If this was submitted normally, it's quite likely that this would have gotten merged after an iteration or two - which could easily have taken a week or more.
>A single frame of a can of coke in a movie is not generally noticeable but it was proven to have a clear effect.

Are you referring to the hoax from the '50s or something else?
India, Pakistan called goat meat as mutton.
He's just coming up with new terms for old concepts. He's just talking about anti-trust law and anti-trust economics. This is all very well trodden territory.

There's nothing wrong with him doing this and in some ways I appreciate how he gets new audiences excited about these rather staid concepts. He's a teacher in that way, and if he can get more people clued into anti-trust thinking in the technology space then good for him.
"Go on then" or "Yeahh, but you won't" if you're in a grumpy mood.

The difference between being able and doing is infinite.
FBA SKU pooling has completely killed Amazon for me. I used to purchase on Amazon regularly but I just can't trust them shipping me a genuine product anymore. I've gone back to select local eShops, even if the quoted Amazon price is often cheaper.
Nobody is forcing anybody. Apple is free to pull out of the phone market entirely.
I wonder if Apple came out with an Android version of iPhone, would that eliminate pressure on them to open iOS?
Thoughtworks Technology Radar 29
Conversely, I routinely use LLMs to do development tasks now. My last bit of greenfield work, I had an LLM stub out an entire API for it. When I needed to marshal a fairly complex JSON object into a well-defined object in my code, including several validations, due to some security controls, the LLM taught me about a library I wasn't familiar with in this language.

Or, a few days ago, I had the need to run the same CLI commands a few dozen times with slightly differing parameters. Unfortunately, the CLI only exist in Windows, and needed to be called on multiple hosts in a Windows environment. I could probably do this on Linux using bash and/or Python, but in Windows, it was way easier to just have the LLM write a PowerShell script for me.

LLMs aren't the best at dealing with proprietary codebases (yet), but I'm sure that will come. In the meantime, they're really useful for abstracting away mundane work in a way that's much more user-friendly than your IDE probably offers, and they often help me spot issues with my assumptions, as well.
> People have been eating rare or medium-rare meat since forever.

It's not safe, one thing are the bacteries that you can catch from raw/undercooked meat that was not stored correctly, another thing is the parasites, for example https://en.wikipedia.org/wiki/Trichinella_spiralis
This is a great series!

I noticed that the author was using https://github.com/hydro-project/rust-sitter as a parser. Which is based on https://tree-sitter.github.io/tree-sitter/. I've been hearing about Tree-sitter a lot recently, so I dug into it.

Tree-sitter is a tool for generating fast, incremental parsers. In particular, the algorithm is suited towards writing "language servers" for IDEs, which re-parse code incrementally as the user works. These kinds of incremental parsers have historically been a huge problem. It looks like Tree-sitter is an enormous practical advance in this area.

And discovering that there's a way to use Tree-sitter from Rust is fantastic. From the post:

#[rust_sitter::language]
pub enum EvalExpr {
Number(
#[rust_sitter::leaf(
pattern = r"(\d+|0x[0-9a-fA-F]+)",
transform = parse_int
)]
u64
),
Symbol(
#[rust_sitter::leaf(
pattern = r"(([a-zA-Z0-9_@#.]+!)?[a-zA-Z0-9_@#.]+)",
transform = parse_sym
)]
String
),
// ...

Getting easy access to fast, incremental parsing is a huge win. And Tree-Sitter has support for being used from a huge list of languages, not just Rust.
I want nobody to force me to use the hardware I paid for in a specific way, especially if that arbitrarily limits the functionality of the device.

If there were more than just those two providers (say, 10) we’d likely have at least one option like that.
This would be my preferred syntax:

status = greeting+"!" ~> capitalize ~> send

This would need 2 changes to JS:

1: ~> being a pipe operator

2: Calling an async function from within an async function implies await

Without 2, it would look like this:

status = greeting+"!" ~> capitalize ~> await send
Problem is not in optimization but in leaking time.
Have you explored https://github.com/dortania/OpenCore-Legacy-Patcher?

I have used it before and, in my experience and everyone else I know who has used it, the vast majority of time the newer versions run absolutely fine with no issues. Occasionally some newer features don't work, but I'd but confident that 2015/2017 iMacs would be able to run the latest version no problem.
Closest name I can think of is "commitment and consistency". People tend to behave as they have behaved in the past, doing so is both a cognitive shortcut and a source of positive emotion. We go to great lengths to maintain consistency (see also: confirmation bias), and being consistent even in the face of conflicting evidence feels better than being inconsistent but right.

From Cialdini: "Once we have made a choice or taken a stand, we will encounter personal and interpersonal pressures to behave consistently with that commitment. Those pressures will cause us to respond in ways that justify our earlier decision."
Are its unintended consequences in propping up monopoly also good for ‘society’, then? Hate to break it to you, but the topic is a bit more nuanced than ‘privacy good’ ‘ads bad’.
Well put.

To note, luddites' issues were not just losing their job. Let's remember that the earlier machines were very crude, safety was absolutely not in their design, and a worker life's also didn't have much weight. So, the early days of machine assisted production were in inhumane conditions, people losing limbs, kids getting killed in them (less skills needed also meant kid labour was a viable option) etc.

So yes, regulation on how the machines work, how much they get introduced, how the workers are impacted, trial periods to see the impacts etc. should help a lot in all respects. The difficult part being that those all mean putting breaks on profit making.
Fennec(Firefox), Mull, OsmAnd, Librera Reader, K-9 Mail, Termux, Missed Notification Reminder, SecScanQR, Jitsi Meet, Telegram, Element, Aard 2 (Offline Wiktionary)
You don't understand either group.
People also used to get tapeworms and other parasites from eating bad meat very frequently.

Just because people ate it back then doesn’t mean it’s okay to eat it now. Being free of parasites now is expected but was not back then.
And what's your answer to that question for a child you've bred for organ harvest? You're assuming anyone would grant the priors of your scenario.

You just wouldn't breed and farm the animal into existence in the first place.
… and not a single photograph of the actual owl.

(it is a fairly hideous looking sculpture IMHO, so I can’t blame the author for leaving it out)
It certainly would be a form of cognitive dissonance, but that's much more general; I experienced cognitive dissonance hearing the word "nicht" pronounced by a native German speaker yesterday evening, because it wasn't at all like what I expected it to sound like.

"Confirmation bias", where you tend to see what you expect to see, is narrower; but still I think doesn't capture what we're talking about. We're specifically talking about resistance to accepting the idea because accepting it would mean reclassifying actions you yourself had taken from "very good" to "very bad". It's kind of weird that it doesn't have a name -- I'm convinced it plays a pretty big part of human behavior, much more than is commonly acknowledged.
Preventing cheating in Zwift is unsolvable, and I mean not in the classic Red Queen co-evolving predator/prey sense. There are just so many physical hacks Zwift can never sense.
> Because information can only be true to an extent, from a perspective, and for a purpose. If you change the scope and purpose of a discussion and look at it from a different perspective the truth will appear completely different.

This is the worst type of pomo garbage. This is true only in the case of relatively unimportant 'he-said-she-said' type of situations. In most cases, there's a canonical flow of events that can be represented objectively regardless of the 'scope and purpose' of the discussion or the 'perspective'.

There are not 'multiple truths' and there are not 'alternative facts.' There may be differing interpretations of why people did the things they did and it may be hard to determine what actually did happen but, at the end of the day, things either occurred or they did not occur.

We cannot accept weird split realities.
Heh, my solution exactly the same. 20 years of photos, and so far I pretty happy with this structure.
Very good. A step towards the proper concept of computer security.
> They are acting immorally by restricting what users can do with devices they own.

It is not immoral. They are open and upfront before you buy the device. I personally buy an iPhone because of the walls.

Keep in mind a village/castle with protective walls is not a prison.
I just take pictures and share them via Whatsapp with my wife/other family. I know they are not the best quality they could be, but I am fine with that.

I don't know how it is backed up. It feels great, not knowing.
Lamb is very robust actually. It can be cooked rare or slow cooked and anywhere in between and still be delicious because it’s often fatty and marbled.
At some point you need to get the memory for your pool from somewhere, for example from malloc [1], hence you can safely set the type of the raw memory by writing into it. You can also change that type to some other type, by writing other stuff (so you can reuse the memory). You can also write metadata to it between uses. What you cannot do is having overlapping lifetimes for different types.

Making sure that you respect all the underspecified, obscure, and often contradicting rules is not easy, so if you prefer to disable strict-alias, you have my sympathy. For the most part is useful for high performance numerical code, and less advantageous for typical pointer chasing stuff.

From the practical point of view, the safest way to implement a custom allocator is to make sure that the compiler can't see through it, so separate compilation and no LTO and/or launder your pointers through appropriate inline asm.

[1] but other 'anonymous' sources, like mmap, would also work in practice.
macOS Sonoma: Game Mode
Nordic skiing too in north of europe.

The main reason it has the biggest exposure is because it is one of the sport that fights the most against it. The amount of testing and openness to this subject is just on another level to other sports compared to say soccer, rugby or tennis where there is so much money on the table that every possible scandal is shut down.
The compiler knows the size of statically allocated buffers and can be told about alignments with:

__attribute__((aligned(N)))
__builtin_assume_aligned(P, N)

Is this information sufficient for correct code generation?
Thank you for your interest! It wasn't too hard to be honest, the actual tradeoff is that the shared object must have been built with the same version of rust that was used to build the runtime(see https://github.com/nbittich/adana#plugins)

for the way it's loaded, it's like in nodejs with common modules:

my_lib = require("/path/to/my_lib.so")

or for standard lib:

fs = require("@std/fs")
I’m of Cuban/American descent. Consequently, I grew up primarily on a diet of BBQ and roasted pig. However, after moving to Spain, I developed a penchant for the tender piglets from Segovia. Initially, mutton and other lamb dishes were a challenging taste for me due to their robust flavor. However, with time, I’ve come to appreciate and even relish it.

Currently, we own a small flock of sheep, which we mainly keep to graze on our property’s grass. This not only ensures a well-maintained lawn but also provides us with financial benefits. We offset the cost of their upkeep by selling the yearlings. Moreover, a local resident benefits from their milk in exchange for assisting in their care.

Having said that, over the years, lamb has grown on me significantly. Now, whenever I host a BBQ, mutton is the star of the show. Guests never stop singing praises and eagerly anticipate the next gathering. However, one aspect of cooking mutton that I find challenging is the lingering smell. It necessitates thorough personal hygiene measures, especially for my children and dogs. Cleaning the BBQ after use is essential to prevent the overpowering aroma from lingering. For those with beards, the scent of mutton can stick around for days. My solution? I opt for a clean shave post-event.
There is a proposal to add the pipeline operator |> to the standard that works similar to what you have here.

https://github.com/tc39/proposal-pipeline-operator
Basically a cross section of the, to cite Marxx, non-capital owning class os citizens. Aka, the vast majority of us. Only difference today, parts the groups thatbmade uo the Luddites back then are now actively cheering in those developments.

Change isbinevitable, and in the long run society usually benefits as whole. The transition period is the problem, and on that front we are making no progress what so ever right now.