skysight-inc/HackerNews huggingface dataset:
Show HN: Tawazi – A Python library for parallel execution of functions in DAGs
Tawazi is a lightweight, pure Python library designed to simplify parallel execution of functions in a Directed Acyclic Graph (DAG) structure.

Several features include:

Integration by decorating existing code.
Automatic concurrent (or parallel) execution management.
Easy task scheduling without dealing with low-level concurrency primitives.
Thread safety.
Lightweight.
Python 3.7 -> 3.11 support.
Asyncify IO Bound sync Code.
Extend the original DAG by composing it with smaller DAGs.

We built this library by iterating a lot on user feedback, since the first users were our own colleagues from the R&D team, who used the library when developing the API codebase ! We tried to make it as generic as possible, so it wouldn’t just be tailored for their needs but for everyone’s. But the downside of developing with a fixed user base is that we tend to focus on their requests and having other users would be a blessing to get other points of view. This library is pretty battle-tested since we’ve been using this library for almost 2 years in production now !

As our job develops APIs that require long calculations and each API call requires running many heavy computer vision deep learning models encapsulated in functions, that depend on the result of other functions and so on. The crux is that as functions don’t take the same time to run, parts of the code could be run while other parts wait. As this can naturally be modelled as a DAG, we decided to write (and open-source !) a library enabling easy parallelization of such workflows.

Open sourcing our work has always been something we had wanted to do and this was the perfect excuse to do it ! Any critic/feedback/questions is absolutely welcome and encouraged (and will mean a lot !) and we’ll try to address those as precisely as possible !

Matthias & Bashir
Hi! Thank you for your kind words.

> The easier the tool is to use, the harder it might be to monetize... but there are so many applications of a tool like this

I am in favour with you! That’s exactly why we've started developing our Dynamic Staging Environments platform. It will integrate seamlessly with CI/CD systems, enabling to generate, create and maintain stateful components of your services more efficiently.

One key insight we’ve gained is that this type of software introduces new responsibilities across the Dev, Business, and Security teams within a company. This can result in complex processes and interactions. For example, changes to schemas often require approvals from both the security team and service owners, which can slow down workflows. That's why I really appreciate how Bytebase (https://www.bytebase.com/) tackled this issue—by providing a platform that combines GitOps for stateful resources with business logic in a streamlined way. We should be looking in this direction.

Important Remark:

Current design of Greenmask fits well with future plathform. We remain committed to focusing on simple utilities, as they are essential—especially for small businesses. These tools serve a critical purpose by solving problems quickly for smaller companies and for individuals who need a solution that works ASAP.
Did you skip the first sentence

> acknowledging improvements in global bandwidth like everything else
A lot of people here seem to ramble about this, apparently without ever having actually used Passkeys themselves: They are nothing like SSNs, driver licenses or other static IDs. A Passkey is generated per device/site combination, where the client holds the private key, the site receives the public key, and the user can optionally share their private key among user devices depending on their client software. That's all it is. How are you "screwed", and what does it even mean "they don't work perfectly" for you?

What's more, passwords work well for a much smaller percentage that has learned to use password managers. Everyone else is subject to regular breaches, and suffering. This is a problem Passkeys get rid of entirely. There is no good argument against using Passkeys over passwords. Not one.
I feel like there should be some kind of exception for proprietary code that's published in good faith. Though I'm not sure that could work if the company wanted to stay in control of the code.

It's not ideal if the way the software was written was itself illegal. Still the advantages of having it out in the open seem to outweigh the benefits of litigating all license violations.
But they also do that
A free tool for making textures via StableDiffusion
A very cool one-man project. My friend who runs a game production company generates meshes in Luma Genie and then makes the high Rez textures and normal maps in stableprojectorz.
The fascination with “intelligent design” is cherry-picking. The is no shortage of “unintelligent design” in the natural world.

Take humans, for example. You can block your trachea and die through the simple act of eating. An intelligent (and omniscient) designer could have avoided that by better designing our overall our overall structure.

Or take the fact or ear bones are modified jaw bones. Or if you believe in intelligent design, ask why our intelligent designer thought it wise to link our jaw to our ears so that it’s hard to hear things when you’re chewing.
And yet UAE a country without any technical knowlage built them in a cost effective way and quickly.

In fact, any country that has built them in mass figured out how to do it cost effective and quickly.

The reality is, its only not cost effective and quick when a country only builds a single reactor as a vanity project to keep the industry alive.

No country that seriously tried to quickly increase production with nuclear has failed.
There are email obfuscation and managed challenge script tags being injected into the RSS feed.

You simply shouldn't have any challenges whatsoever on an RSS feed. They're literally meant to be read by a machine.
I can try to reproduce but don't want to go through all the steps every time in case things go wrong again. Is there a savepoint/export/import kind of feature?

I think a tutorial regarding basics such as how to find shortcuts, do's/dont's for new beginners might help.
> principles > wild market

Your principles will be gone by the time the 10th company starts to sue you for a public disclosure you did in good faith.

There's a reason why nobody wants to use their real name and creates new aliases for every single CVE and report.

Principles are discrepancies with the law, they don't exist. If the law dictates a different principle than your own one, guess what, you'll be the one that is in jail.

Whistleblower protection laws are a bad joke, and politicians have no (financial) incentives to change that.
Those 20 poorly written plugins make a good amount of money though, which is why many of those plugins' creators and affiliated "wordpress influencers" also do an outstanding job pushing the sentiment against more integrations into the core.
It's worse than that. This guy takes a void* function and casts it to a char* function, then passes it a char**.

void (*name)(char *ptr);
typedef void (*name_func)(char *ptr);

void target(void *ptr)
{
printf("Input %p\n", ptr);
}

char *data = "string";
name = (name_func)target; // Illegal: casting fn that takes void* to a fn that takes char*
name(&data); // Illegal: passing a char** into a function that takes char*

Before someone mentions qsort(): the comparator function really is supposed to take a void*, and inside the function, you re-cast the void* argument to a pointer type of your desire. If you don't do it in that order, you're using it wrong.
I think both: there absolutely will be f-ups. And the Vogtle experience will have tremendous benefits to the AP-1000s that follow.
It breaks the assumption that Chrome is sandboxed and something I do as a user including installing an extension will not have an impact outside of Chrome. A new process outside Chrome to call your own and do whatever you want with.

You're on Windows? Download a binary, create some WMI triggers and get executed at every boot as the same user (requires no elevation for same user, if Admin, you can get NT_AUTHORITY). If you find something to elevate to Administrator you could also patch the beginning of some rarely used syscall and then invoke it and get a thread to yourself in the kernel. These things tend to almost chain themselves sometimes. At least on Windows it feels that way.

Also the user doesn't have to navigate to a specific URL in the final form, just needs to open devtools after installing the extension.
That site is truly scary...
> "Don't take this the wrong way, but I don't think you understand Adams."

In my opinion (as a Brit who isn't an expert on Douglas Adams, but has read his books) the person you replied to was completely right and it's you with the misunderstanding.
Thank you! I’m really happy that Greenmask meets your expectations
The speed of light is constant as measured from any observer. This has been verified experimentally to a very high precision and motivated the development of special and general relativity.

Otoh there is no requirement for a wave front to have the same frequency as when it started. A gradient in the gravitational field can cause a gradient in the gravitational redshift and thus "parts of photon" can very well have slightly different frequencies. If you recombine the paths and have the photon to interfere with itself, the interference pattern will capture the shape of such a wave function as affected by the distortion in the gravitational field.

IIRC this is the "standard" way of thinking about what's going on although marrying quantum mechanics and general relativity is still a work in progress.

If you buy into another theory that involves a variable speed of light, I'd love to hear more about what exact theory are you talking about since it seems to me that the burden of proof is on who makes the most extraordinary claims.
This is the kind of extreme internet Libertarianism that's dangerous in the real world. Not practical or concerned with extreme poverty through inequality, but preferring to fight on first principles, like all tax being theft (not your claim, but equatable).

I'm less concerned about the definition of fairness and more concerned about real human suffering.
This is an unexpectedly excellent article and incredibly well written.
This is not a rant, but a well laid-out description of something a widely used software ran into as a result of a change in the compiler they use.

The #ifdef they had in place was a bit hackish, but I wouldn't call it abuse. It is a typical construction for C to do stuff like that which in general isn't without risk, but they have used it without any problems for years. The whole point of the blog post is to start a discussion whether sth. like this should rightfully be flagged as "unexpected behavior" or not.
And We Finally [we think we] Know Why
> it's priced on demand and supply like anything else

You should complete the sentence: “It’s priced based on demand and supply in legal markets like anything else.”

There are, of course, other markets where things like this are traded, but that’s a different story. That said, I think the author is free to negotiate further with Google if they believe it’s worth it.
I know how they technically work.

I was referring to how 99% of people have (or can easily get) an SSN, license etc., but for 1% it’s absolutely impossible for various reasons, so any flow requiring one for non social security or tax declaration purposes is an unnecessary obstruction to them when other alternatives exist.

Don’t ever believe that passkeys will always stay strictly optional. As soon as something works for 99% of potential customers, the 1% can be deprecated for efficiency/security/… purposes.

And I’m even not anti-passkey or anything, I personally like them and will take them over SMS OTPs any day. But they’re just not done yet, and I really hope they get done in a way that works for everyone before they start becoming mandatory in some places.
Or to autotrigger. That's how they do for backstabs in team fortress 2. Just go around and have it trigger immediately when it'd be an instant kill.

Demomen on the other hand use an aimbot so they can hit you with those parabolic projectiles in the face, even if you're behind a wall and they can't see you at all.
I've been doing that for years using the Calibre app. No problems so far.
No idea about CSGO but Dota 2 already does this (another Valve game).
> Then you have mobile apps that just don't run if you don't have a google account, like chatgpt's native app.

Is that true? At least on iOS you can log into the ChatGPT with same email/password as the website.

I never use Google login for stuff and ChatGPT works fine for me.
EV battery prices to fall by nearly 50 pct and near ICE parity by 2026
Excellent writeup and work, reading this made me be right there along with you in the excitement buildup thoughout the discoveries. Thank you!

Well deserved reward!
Firefox Is Now "More Than 75X Faster" Running WebAssembly
WooCommerce is owned by Automattic, so that won't happen. Owned as in, the trademark and the place in the plugin directory. Automattic bought it some years ago.
This decision is forced by it being hard for most English speakers to pronounce Vyacheslav.
> control flow graph contained 132856 basic blocks

That is a stunningly large function. I've looked around the onnxruntime sources and can't find anything like it. The largest C file is under 6000 lines. Does anyone know what function it's referring to?
> name(&data); // Illegal: passing a char* into a function that takes char*

I assume this is just a typo in the article. He probably meant `name(data)`.
not true. if you make a repair, you're liable for it. if you do your job well, there's no reason that would mean more of a business risk than the OEM takes.

If, on the other hand, you do a rush job, then yes you're very much on the hook.

If anything, this makes repairs/reuse of devices more interesting to the consumer, since you know that some basic level of responsibility (read: liability) is taken care of.
Vite uses esbuild only during development, in the build it uses rollup.
Girls hitting puberty 2-3 years younger and being assumed as being more 'responsible' as per traditional gender roles from about the age of cognition.

This is non-withstanding the Western Educational premise of treating 'misbehaving' boys as 'broken' girls, as opposed to facilitating them in a mutually acceptable learning style.
Not OP, but by booting M1 from external thunderbolt nvme you lose less than 50% of benchmark disk throughput (3GB/s is still ridiculously fast), can buy 8TB drive for less than 1k, plus can boot it on another M1 mac if something happens.
If there was "max mem, min disk" model, would def get that.
"what percentage of grandmas would lose their life savings if they stumble across this bug" is the metric I use to determine severity.

And in this case, it requires a chain of unlikely events. The user tricked into installing an extension (probably not one from the store, which is now particularly hard on windows). The user tricked into opening devtools.

It's gonna be sub-1%. Certainly still worth fixing, but nowhere near as bad as a universal XSS bug.
So the sharing economy is when a company profits off the free labor of others. I mean, they could have hired couriers, but that would be more expensive.

Got it.

And no, as the history behind the 2018 movie 'Green Book' taught us, the real sharing economy, as is something other than labor exploitation, has older roots.

The Negro Motorist Green Book was a guidebook published 1936–1966 for African-Americans to have safe road trips during the Jim Crow era. Some of the information was voluntarily collected by U.S postal workers who gathered the information while on their routes.

> In a world with the Internet, cryptography, and the blockchain

BLOCKCHAIN? How old is this article? Ahh, February 14, 2016.

Well that didn't age well.
>For whatever reason

The reason is that you won't bother to pronounce Vyacheslav so Russians have to use a short version of their name.
Drew popped up on this thread yesterday saying that he'd "read most of the report".

We can now ascertain that this was a lie and an attempt to mislead, because it's clear from the accumulation of evidence that he authored it. While writing and editing this document he would have read every word, not just "most of" it.

He is also keen to congratulate himself by not-so-humbly announcing that "the depth of this report is astonishing".

Knowing that the author has engaged in such deceptive sockpuppetry casts significant doubt on the document itself. How much of it has been written to mislead the reader and misrepresent the facts?

https://news.ycombinator.com/item?id=41838124

> I've read most of the report and it's got a lot more than "last time". Speaking as someone who has done a lot of my own research on Stallman's bullshit, the depth of this report is astonishing. The allegations it makes regarding the conduct of the rest of the FSF is particularly alarming.

> I think you should at least skim it before you comment.
The question remains whether this price drop - if it actually is going to occur at all - will be forwarded to the end-customer. Right now, the high prices of EV compared to ICE is one of the main roadblocks for broader adoption of electric cars.
What dialect is he using that has “plus” vs “+” and so on?
Certainly, not all Christians are pacifists, and not all pacifists are Christians.

But, to my mind, pacifists choose to not fight back by definition, or that would be violence, so their prolonged existence is only possible because other social mechanisms hold back violence which would destroy them. Interaction with these mechanisms may be the point of holding a pacifist position: say, a monk or a nun may have a higher moral authority because of a declared personal abstinence from any violence, and hence indirectly incentivize lay people to protect them.

Of course there are people who call themselves pacifists but admit a right for self-defense, but only not organized or military; such a position again is only possible when someone else would partake in a defensive warfare and protect them.

Abstaining from aggression while being ready and willing to respond to aggression with full force, lethal when required, looks to me like the most logical "lawful good" position. It has a chance to produce an equilibrium when multiple parties live in peace for a long time, and any violent deviations are quashed.
So aim for at least 64GB of memory?
Surprisingly painless, in my experience. Vite is good.
It's not well laid out. The examples are malformed/illegal and the ifdef thing is stupid.

The author admits to not being a C undefined behavior expert and yet acts like they might know better than a tool made by such experts.

Looking up the rules and verifying the shown snippets takes at most 30 minutes at a leisurely pace, the author could have saved themselves the embarrassment.

I'm not going to write a blog post about how I didn't expect a color spectrometer pointed at the sky to say "BLUE" because I thought it might have been purple, "although I'm not an expert in wave lengths".
> Then you have mobile apps that just don't run if you don't have a google account, like chatgpt's native app.

That's not true, I use ChatGPT's app on my phone without logging into a Google account.

You don't even need any kind of account at all to use it.
It's Time We Kill JavaScript Dates
That happens on sideloaded books that belong to the same device as well, at least on my Kindle Scribe. These books disappear occasionally, and I have not found a consistent way to make them reappear in the UI. Sometimes they return on their own, other times they do not. Interestingly, their files remain on the Kindle’s file system.
Awesome writeup. Always interesting to read what Daniel has to say.

I think the fact that it turned out that he was wrong (and UBsan was right, as usual) is a great testament to the shortcomings of C.

Lots of people - both inexperienced and very experienced - celebrate it for being "simple" and "close to the hardware", but the truth of the matter is that it is precisely not close enough to the hardware for people who _know_ what the hardware is doing to be able to do what they expect, and it's too close to the hardware to be able to be able to ignore it.

Lots of experienced C programmers (and - guilt by association - C++ programmers as well) run into UB because they have clear expectations of the compiler. I.e., they know what the compiler should generate, more or less, and C is just a convenient notation. But compilers don't live up to those expectations, because they don't actually compile your code for the hardware. They compile it to the virtual machine abstraction defined by the standard, which very often works differently from any real architecture, and then translate that into machine code. Even though there is basically a single set of semantics that every single "relevant" (mainstream) architecture implements. This is a holdover from when C had to target architectures that are 100% irrelevant today.

Everybody's favorite example is signed integer overflow. In both x86-64 and ARM64, that just works - two's complement is the only relevant implementation, so there's no issue. But `int` in C and C++ is not that.

Almost every single common UB pitfall has reasonable behavior at the assembler level for every mainstream architecture, and almost every single niche architecture.

C gives you the illusion of being close to the hardware, but in actual reality the hardware is several steps removed, so if you want to leverage your knowledge of the hardware, calling conventions, assembly, or other low-level details, you have to go out of your way to work around the C standard.

(Aside: We need new languages to tackle this, and I coincidentally happen to like Rust. Lots of people coming from C or C++ are irritated and frustrated by Rust, but 99% of the time it's because Rust gives you a compile error where C would give you UB. This is one example of that out of thousands.)
Qwen2.5-Coder: Code More, Learn More
Some of the biggest pros and cons of Kindles vs Books:

Pros - Lightweight, I can even fit it into a holder on the side of a chair or bed so I don't have to hold it.

- I don't have to physically manipulate the 1000 page book to try and get to certain pages.

- No dust.

Cons - I can't tell you the authors or names of most of the books I've read on it. When you have a physical book you're confronted by the book and author's name, along with an image to burn the combination into your mind. As a kid going to the library I knew whether I had read a book just from the jacket.

- Amazon shenanigans.

- Battery won't last forever and you'll need to replace the whole unit.
"Very intense people" -> Borderline evil sociopaths.
"Things in category 3 needs to exist" mmmmh no, and reading from a "philosophy grad, rationalist heavy" that those are "morally thorny" questions tells me that he should have studied something else...
It's a shame the GitHub repository got attacked by the kind of sexually frustrated perpetually-teenage crowd you normally see on 4chan.

On the other hand, Radionomy's clear incompetence over the years sours me. Having the IP for all those years and laying it to waste, culminating in a half-assed attempt to open source it. It pains me to say as their intentions may be good at least in part, but one has to let Darwin get his way too.