skysight-inc/HackerNews huggingface dataset:
Indeed. Quite often the situation is this: I'm in code that cannot, under any circumstances, be made async. And I need to call an api, that is async and must stay async.

So basically: you have to call async from a synchronous context. But I think perhaps the article correctly avoids the topic, because in 99% of cases when you think you need to do this, you don't. And having an easy googleable page with an easily copied recipe for doing so could do more harm than good.

In the end it's going to be extremely rare that you can't bend over backwards to refactor your callsite to be async. E.g. you are in a constructor (which is sync) and want to call an async method. The solution isn't to wait on a result, the solution is obviously to not call it from the constructor. And that's the solution even if you have to refactor for a week instead of a blocking wait.

But yeah I agree he could have included the answer, surrounded by big red warning sigs that you probably don't need to, or want to copy it.

Perhaps the key clue is to give the good pointers to solving it properly. Just saying "you have to be async all the way" isn't really helpful. One key insight I got from somewhere was that identifying the async starting points was the key. E.g. for a desktop app, the realization that in 90% of cases your async "root" will be a GUI event, and that these event handlers in the GUI frameworks like WinForms or WPF can be async whenever you want. As a last resort, your main() method can be async.
I don't get the downvotes, it's a valid question imho. For example in France in 2012 they made it mandatory for every car to have 2 alcohol tests (the dumb ones, you blow in it changes color if you're above a certain threshold).

A good idea right ? it's pretty cheap too no ?

It turned out that the lobbyists who pushed for it were also invested in the company manufacturing 90% the alcohol tests for the french market.

https://www.lefigaro.fr/actualite-france/2012/06/27/01016-20...
Jia Cheong Tan is anagram for CIA Agent John. If you consider how much went into planning the backdoor operation, it seems virtually certain it's an internal joke.

And why an Asian name? It's certainly exploiting a psychological bias. Apart from what you noted, the names are much more generic than Ugandan names and IMO it's virtually impossible to track a legend down. And the number of OSS contributors from East Asia is much larger than from Africa. Hence a more normalized/frequent occurrence. And lastly if things start going south, some play on the r-card is always up the sleeve of PsyOps personnel.
A very good overview of the generations of Chinese chips, but I feel like matching performance isn’t really the goal for domestic Chinese chips? Sure, they’d love them to be as fast or faster than western cpus, but ultimately they ensure China is not starved of microprocessors in a war.
Thank you, I wasn’t aware of that change. I’m trying to make sense of what’s going on, and it’s hard to do since everyone seems to be in the can for one political faction or the other, and money printing is something both parties did so people aren’t talking about it.

According to that source the accounting change is responsible for $11.4 trillion of the change. That means M1 really only went up from $4 trillion to $8.6 trillion in two years from February 2020 to June 2022. So we printed more money in two years of pandemic than in the previous twelve years of quantitative easing. How’s that still not the obvious culprit?
Poetry mono repo made easy with plugin
What a great idea! Movie theaters often have arcades, but I wonder if setting up a more permanent multiplayer game in theatre would be worthwhile?
Not a woman, so take this with a grain of salt.

A few years ago, I wouldn't have been very bothered by the privacy implications of an application like this, but for obvious reasons it's become much more prudent to consider them. Were I a woman I'd be deeply troubled to use an application like this, no matter how good, without some kind of ironclad proof of a privacy respecting codebase. Imagine logging patterns indicative of a pregnancy followed by an abortion, and then imagine selling this data to Texan bounty hunters[0] or any other nefarious actor in your jurisdiction. The stakes have become too unacceptably high to use an application like this without knowing with perfect certainty that it is safe to use.

Which isn't to cast any aspersions on OP for developing it. But the game has suddenly become very dangerous, and despite their reassurances, this is in fact a weapon of potentially lethal consequence.

[0] https://www.villanovalawreview.com/post/2229
I don't understand how that is done. Can someone explain to me how to do the same? Whether it is reading the raw image, a particular format or the bytes of the print. Surely it's not like that, like I said I don't understand.
> You can't do auto generation if that generation depends on the output of some units. Generators can not solve that problem.

True

> What a bizarre thing to say. No, that is not just what units are for. I think you are severely misinformed about what systemd is. Units are supposed to take care of ordering accept IPC, define how to handle failures and manage devices.

I mean that part of the point of systemd is that units mostly work out to ExecStart=/usr/bin/binary, and an unit isn't supposed to contain the arbitrary jank one can put into a SysV script.

IPC and the like is an explicit systemd feature, not something you improvise behind the scenes and then expect to work anyway.
It wasn’t just an accounting change. The money supply still more than doubled over just two years.
Thank you, I'll need it lol <3
I agree with your viewpoint. The crux of the matter is not whether to use tiered storage or not, but what trade-offs have been made in the specific storage architecture and what benefits have been gained. Here(https://github.com/AutoMQ/automq?tab=readme-ov-file#-automq-...) is a qualitative comparison chart of streaming systems including kafka/confluent/redpanda/warpstream/automq. This comparison chart does not have specific numerical comparisons, but purely based on their trade-offs at the storage level, I think this will be of some use to you.
> How people could write "public virtual bool Equals(object other)"

Well it was created before generics in .NET one and can't be removed, that's the simple answer. But yeah, making object equality customizable virtually was probably the worst design mistake in C# and .NET. Having to specify the comparer explicitly when creating e.g. a Set collection would have been so much better for quality.

The second worst mistake was defaulting CultureInfo to the system culture (i.e. making methods like float.Parse()/ToString() take the system culture into consideration instead of requiring everyone to pass in the required behavior)
I don’t think manufacturing would end up almost free for any of the newest chips since there are such tight tolerances and high failure rates. At least not for quite a few more years when (if?) there are competing fabs.
I refuse to use it and I can't even view tweet "threads" properly, nor replies or any kind of coherent timeline.... its unusable
Ah that's disappointing, but as a fellow user I too found it too troublesome so I understand that.
What dependencies/limitations are that?
Link btw since it’s on a org: https://github.com/CopilotC-Nvim/CopilotChat.nvim

Re: official version

There was some discussion but the answer is that it’s just too difficult. Our version was reversed from a bunch of MITM and guesswork. The VSCode implementation has a “@workspace” command which involves complex tree-sitter integration, sending off all your code to be vectorized, and uses RAG to get the most relevant snippets. We obviously weren’t able to implement all features. They can get away with this in JavaScript because you can get just about anything via npm. In Lua, most things have to be from scratch. I had to spend a few hours just getting tiktoken working in Lua and even then it requires manual installation. The package management system with Lazy.nvim is very lacking.
British culture is very different from US with regard to race. It took me a long time to understand what the difference was.

In fact every culture I know (directly or am informed about) is different form the others. I wrote a blog post about this: https://pietersz.co.uk/2023/08/racism-culture-different

I do not think people in the UK care about where immigrants are from, they care about whether they compete with them for jobs. This is why some groups of people wanted less EU immigration (predominantly unskilled) and more skilled immigration, and professional people almost universally want EU immigration and oppose post Brexit policies that have allowed more highly skilled immigration.
What's the point in "privacy friendly" if you're backing up to google?
It's almost like GenAI is the ultimate comodification of human connection.

Literally scraping the largest accessible corpus of human communication and attempting to emulate it and placing it as a MITM attack between us.
IMO humanity should just do ASCII and call it a day.
I'm not talking about viability of this, just my wishes.
In fact, EBS is entirely a cloud storage solution and operates as shared storage. It is not a local disk system.
Apple's 'incredibly private' Safari is not so private in Europe
Yes, because a car without safety features can kill people easily
I checked and I think you're correct.

Temu's T&Cs for the UK specifically say that

> You agree that, where applicable, you will act as the importer of the products purchased

-- https://www.temu.com/uk/terms-of-use.html

So yep, on the face of it, this does look like a pretty big loophole.
I bought some Apple Watches (because of reasons). I am wearing one right now. Model 3 (Nike edition or something). I've switched everything off (WiFi, Bluetooth, analytics, the whole thing). It only shows the date and time. The battery lasts 4-5 days.

It's amazing when you shut down the telemetry-battery-draining functionality of devices. And to add some more insult, I am using an Android phone, which ofc don't even try to connect to my watch :)
I believe -and Gemini just confirmed- that they don't work together.

> it depends on a larger device for configuration

yes, the architecture was purposfully made, so that the Watch only collects your bio-metrics, with limited own/independent functionality. They (Apple) does want everyone in the 'garden', so why open it up?
Protesilaos is a legend and I agree with everything he's said on this post.

I myself put all my projects on GitHub because of visibility and the free CI to run tests on Windows/Mac/Linux which is a godsend... but I also normally keep an alternative upstream on all my projects with https://www.opencode.net (it's as easy to do that as adding a new remote with git) so I feel like I have zero dependency on MSFT, all the services they provide to me for free are just "nice-to-have" things. But they are very nice indeed.

The only danger I see is that GitHub becomes so widespread that other tools start only integrating with it (instead of using pure "git" integration). People are saying NPM already does this (I don't know, I don't do NPM)? That's a real danger, but hopefully other projects will have the common sense to not fall into this trap. For now, at least, I feel like that's not been a big problem.
Part of the whole point of holding drills is to show off for the opposing shadows. (the for-satellite version is the elephant walk)
Compressed web phone calls are easy to bug (2008)
Read this about ten years ago. Couldn't find it on HN, though.
That’s what I was thinking. I mean, sure, I’d wish all our code was modern and new, but it’s not. And I can’t just magically make everything async, yet many devs *including MS* think modern code should not offer synchronous APIs. And so I need to call async APIs from synchronous code.
So aim your ire at the distributions who (I agree) cocked this one up. "Take a library dependency to implement basic functionality" is not a systemd mentality, it's pernicious throughout software development - see leftPad as another example.
In my experience, most language developers don't even know how arrays/slices/lists works, or that they are reallocating stuff all over the place in ridiculously inefficient ways. They don't even know the difference between length and capacity.

It's nice to try to create awareness however, but the heap/stack is not the first thing that would come to my mind tbh.
Well, yes. Planned obsolescence and all that.

But what the article describes, and what my experience as a VLSI designer is that as feature sizes decreases, being able to just be able to guarantee a specified lifetime given environmental limits (ambient and die temperature, voltage and current supply including stability etc) is a very hard problem. And is getting harder. Just the statistical variance in the wafer production process steps (amount of molecules deposited) will make migration harder to estimate and handle.

A few SiO2 molecules more or less in thickness of an oxide layer that is 10000 molecules thick is not very important. But when the layer is supposed to be 10 molecules thick, 12 or 8 molecules corresponds to a huge difference in leakage.

So stating a minimum lifetime is what you do. A lifetime where at least 99% (or so) of the device still works reliably. Not to increase sales, but to avoid getting class action suits, having to pay out too much in refund, replace devices etc.
> It's hard to imagine how a working developer can believe that maintaining a platform where anyone can do anything has only upfront fixed costs.

Isn't that how Google Play Store works? $25 once, for life. Presumably revenue is from IAPs and ads.
What is codified as legally fair use is extremely squishy. It's the kind of multi-factor balancing test that lets the courts do whatever they think is right.

The problem is that's also the sort of thing corporations abuse to set bad precedents, by constantly nibbling away at the edges with expensive lawyers, and filing suit against defendants with far fewer resources.

This is why "according to corporate PR, what the defendant did was bad and wrong" should always be viewed with heavy skepticism. They're always going to choose a case where they can try to paint the defendant as the villain. And yet, we know who are the ones twirling their mustache.
China to launch sample return mission to the far side of the Moon next week
Yes, the flat fee per bounty approach was what I had in mind, since the whole idea is to run away from the current fluctuating paid ad costs. I believe having the bounty amount being visible for all bounties allows for transpancy and encourages participation from creators, where they get to pick and choose bounties that align more with them.

Regarding startups not knowing what to offer as a budget, that is a valid concern and definitely something worth considering. I initially thought leaving it up to them to decide was the best approach so it does not seem like we want them to pour large amount of investments into the service. However, I get why something like that would be helpful, It would eliminate the guess work on their side and make the service more intuitive.
Different can be better or worse depending on the user. What makes Vim better than emacs and not just different?
> In March, The Insider, along with its investigative partners 60 Minutes and Der Spiegel, uncovered evidence implicating Unit 29155 in directed energy attacks thought to be the cause of Havana Syndrome

"Evidence" is such a strong word to use for what that investigation revealed, but I suppose it goes a long way of revealing the nature of articles like that
it reeks of Rob Pike ;)
Basically my PoV. The API code itself is the best possible documentation.

Not to mention, how else do you see what complex logic might happen in an endpoint?

It seems typespec deals only with extremely simple CRUD APIs, for which again just reading the code would be good enough.

In scenarios where you want to offer the API consuming team some mock, I'd argue time would be better spent providing them with a a json-server implementation (see: https://www.npmjs.com/package/json-server).
Dokploy – Effortless Deployment Solutions
EVERYTHING HAPPENS FOR A REASON.

SOMETIMES THE REASON IS YOU'RE STUPID AND MAKE BAD DECISIONS.

9front System.
Start with macro recorders [0] that let users record and replay sequences of operations. This already exists in certain household appliances, or when making a music playlist. Give them the ability to view and modify the macro code. Add loops and variables etc., and some portion of people will create more complex macros, even if they are no software developers and have no interest in being one. It’s like writing a cooking recipe, people understand that. Apple iOS Shortcuts are also a form of that.

[0] https://en.wikipedia.org/wiki/Macro_recorder
Just installed it. Any tips for what the interesting features are? The one that stood out from the video linked to in another comment was running any selected text as commands.
test it with small cities and preferably outside of US. Hallucinating with street names and directions not worse than other models. Had a good laugh.
Cool to see this here, Anton!

If you can still edit your title, I suggest prefixing this post with "Show HN: " so that it's obvious that you're the author sharing your project.
IIRC Yuzu also monetized.
It never occured to me until I'd read parent comment, but in hindsight it's Glorious(tm):

* A tie is a long, big(ish), pointy thing that hangs and flaps around in front of you.

* A wedding ring is something you stick a long, pointy appendage through.

Now I wonder if parent commenter just pulled this out of his ass or if this was always intentional...
I still use Acme as my daily driver, with a good smattering of Sam on my vertical monitor for various things. About 90% of my scripts are written in rc or use the tools in $PLAN9/bin (awk, sed, seq, etc.)

It gives me good consistency between Mac and Linux (or WSL), so I highly recommend plan9port as a gateway to plan9 and 9front.
I don't know. I miss my old days on wall St. sometimes. I work remotely from home and most days I'm in t-shirt, shorts and slippers. It's nice suit up sometimes. The only opportunity I get these days is weddings.
go compiles to binary files and libraries. it’s more like c than Java
And people are also telling you that tight integration is not a mandate. Having a bunch of stuff designed to work together does not mean that they're tightly coupled and can only work with their specific implementations.

We've all got confirmation bias, the trick is to be aware of it.
That's what your app creators want, you should be happy for them to have the freedom to distribute their product to you as they see fit.
The guy I was replying to was making a total non sequitur, and I replied pointing out that his comment didn’t make sense wrt the discussion. And now you’ve replied to this… why? I legitimately don’t even understand why you posted that.
I think it's because dystopian situations force people to name things oddly.

And yes, I think not being able to put an app on a device that I paid for is dystopian. I also think not being allowed to repair my own devices is dystopian, too.

If no device had ever prevented a user from installing their own home-made apps, "side-loading" would never have become a thing.

For gaming consoles, I was vaguely uneased by it at first, but quickly got over it because it had always been that way. I never had a chance to put my own game on a game console.

But with general-use computers, including mobile phones, the whole idea really bothers me. I PDAs and brick phones had never allowed people to write their own apps, I might be less bothered by it. But (thankfully!) they did. That cat's out of the bag, and long ago.

Even Google's attempts to prevent "sideloading" bother me at this point. Any warning that applies to side-loaded apps should also apply to store-installed apps because they have shown they aren't foolproof.
In that front I wish their FLASHSTOR product was a 6/12 bay NVMe add in card rather than an integrated motherboard+pcie switch+soldered CPU+soldered RAM. I'd love to just pop that kind of thing into a normal PC but all the ones I've found are either 4 porters or extremely expensive.
I believe that ‘crash the runtime’ is legitimate old behavior. IIRC changes eventually made the default crash on UnobservedTaskException an optional configuration setting and there is now an event they are reported with.
The OCR (optical character recognition) is doing the heavy lifting, essentially forcing the blotches into strings... which then turn out to be valid perl programs
Free-diving adaptations of the Sama-Bajau people
I can see the appeal there, but I can only imagine it's utility diminishes quickly over time as product evolves, and probably doesn't survive past implementation kickoff. Last thing developers love to do is to have to update a spec after having to update multiple tests and server code.

If it does become a long lived artifact, CI/CD must also be a nightmare, having to figure out which commit matches which version of the specification, since the spec is now a distinct artifact from it's documented target, and similar which version of the client. A literal "3 body problem".

On the other hand, if you already have a project template (granted, you do need to fight through all of the various build-time configuration required to get a typescript project up and running) you could probably achieve the same by simply stubbing the API endpoints in code to generate the spec.

If there was an advantage to a spec first model, it would be that any change to the api would be a conscious change, and highly visible. I've also encountered situations where a innocuous refactor (changing a class name or method name) broke the previous builds. But one could potentially integrate a gate into CI/CD by diffing the outputs of generated specs.

Much of my opinion on this subject is based on my own experience using Postman as a pre-implementation spec. But conceptually I see the same problems arising from any spec-first approaches.
Australia to fund $620M quantum computer claimed to be first at 'utility-scale'
Could you explain what JIT would allow? Would sideloading allow this to "work" or would it need OS support?
Well, the point I was trying to make, said in another way is that the initial success of App Store (iOS, in particular) was driven that the fact that , suddenly, users thought that was OK to pay for the software. I think that the (relative) lack of piracy and difficulty for ordinary users to install pirated software has been a key factor in the success of it: "there's an app for that, and I can't easily find it for free".

The other point I was trying to make is that the disappearance of "stand-alone" apps, not tied to a web service, is primarily driven by the fact that, this way, you can avoid piracy. You can offer a free-tier (that would be eaten by the piracy anyway) and sell (say) a synchronize, or additional features tied to a web service (so not printable).

May be it's not the only thing, but that's what (anecdotically) I hear from solo-indie-very small developers.

I fully agree with you on both the current discoverability problem and also with games piracy having a different, may be even not negative effect.
If the compiler would know the stack size, we wouldn't have StackOverflow
Which really means this is a terrible way to emulate games.

The bug list is pretty darn unacceptable for a usable emulator.

You can’t even emulate PAL region games.

It’s a nice novelty that this is built in to the OS but the Linux/Android retro handheld scene is so much more wildly sophisticated than a half-broken command line emulator. Just jump on YouTube and search for an OnionOS overview to see what I mean.
Nice to hear - I googled your watch and wrote you a DM on instagram