skysight-inc/HackerNews huggingface dataset:
> The idea was every press would be registered correctly not matter how fast someone hit one, two, or three buttons. So simpler debounce algos were out.

...no ? Only if you care about both on and OFF timing you'd need to get creative.

You can just

* trigger on interrupt

* ignore that input for say 50ms (or how long you want your debounce period), whether by disabling interrupt or any other way.

That way you will always catch it, on the first bounce, the fastest possible way. And as you are "NANANA NOT LISTENING" on the pin, doesn't matter whether it bounces or not.

Same with holding, as long as previous registered state was ON and you get OFF, you just send the OFF higher up the stack, start the timer, and ignore any further input for that duration.

I think that's what your code is mostly trying to do
D is a GC-based C++/Java-like OOP language. People used to call it "a C++ done right", but it was never simple and didn't have any clear edges against its competitors. TBH, one simply should not build on top of C++ - it's a beast that no one can comprehend, and it only keeps growing.

In case of Zig, I think it's a very good modern C alternative. Zig can do what C can do, can interoperate w/ C (e.g. importing C headers), and offers new features that are useful (comptime, slices, error type). It's like Go, but without GC and a large runtime.
Just give up on trying to make google work. Google has definitely not improved. Recently I tried searching "hugginface madebyollin" (with a slight type to hugginface instead of huggingface) and it literally didn't show the obvious result. https://www.google.com/search?q=hugginface+madebyollin. I've switched to duckduckgo and couldn't be happier.
My experience is that the scope is never kept narrow, which is exactly the same that the author is describing.
In polite company you say "The article" or "read the manual" and patiently await your reward, which is their asking "what does the 'F' stand for?", to which you reply only with a condescending look and raised eyebrow(s).

That look of realisation is precious.

I've manufactured this experience once or twice, and it's wonderful.
It sounds like they’re looking in lakes. Could have gone splash without leaving much trace on the surface.
YA, like "New Age" 30 years ago, is not a genre. It's a marketing category.

Marketers built a profile of the buyer they want to target in their minds - a glorified stereotype. The buyers themselves didn't identify with the label.

But the marketers then demanded products tailored to this stereotype. And of course, many authors caught on, and were willing to move towards the marketers caricature of what they had in common, in order to get access.

So there's no co-option here. People are just fighting over a marketer-created niche. The niche is a bad fit to reality (in more ways than the audience hardly being young adults) but it's got enough money behind it that it's not easy to challenge it.
Arbit v. Schneider Electric: Trademark Infringement
> The issue is that IP is a legal creation, so it can only be stolen if it is recognized in the first place

The same is true of all crimes, they are all legal creations. And from what I can tell, China has the concept of IP. They're protective of their own, for example.

It sounds, then, like you're now agreeing that the IP is being ignored, just saying it's okay because China don't want to recognize it.

If not, I will ask again:

Suppose we have 2 IP owners, and 1 has their IP ignored by China and copied, the other has their IP "considered a different standard/not recognized" by China and copied.

_What differences do the two IP owners experience?_

This is the key question I asked before, and I am asking now. What's the difference for the IP owner? I ask because it seems like you're playing with words, not substance.
>how would you have any guarantee that your third party solution would be able to support those...

You could say the same thing about literally any 3rd party software or service you purchase. "Why use cloud services to do anything?" etc.

Sure this thinking will hold for some things, but chances are that for something as standard as billing you're not going to be implementing some revolutionary feature that gets you more customers. On the other hand, if you mess up billing because you rolled your own system that doesn't have many standard options that a mature OTS system would offer it can lose you potential customers, because for months at a time you're stuck building the most mundane and standard things like an annual plan that could be used to better appeal to buyers.

For billing, a one of the most standard things ever for a business, you simply take a small amount of time to survey the OTS options and compare features. Any you know what? There's an excellent chance that buy actually getting a comprehensive look at features offered by such options you will learn about the types of things you will absolutely want to do in the future. Things that, in retrospect, seem like obvious oversights, such as an annual plan. You'll see features like that in your survey and say to yourself "Oh, yeah, that's something we may definitely want in the future, lets put that on our requirement list for a final choice."
There is nothing wrong with self-promotion if, as in this case, it is relevant to the discussion.
He did not say whether socialism is better versus democracy.

He said human institutions have an optimum size. An institution or system that works at small scale is not guaranteed to work at large.

That is not common sense, and in fact many contemporary people believe in scale-free properties of institutions, which have led to catastrophic failures (eg large interconnected banks that all fail together).
An 80's movie dream is playing out for some rural kids, where they stumble upon a smouldering high-tech wreckage and as they explore it, men in suits pour out of black SUVs and talk to them in taciturn ways.

Seriously though, these jets sound terribly overpriced for how unreliable they seem to be.
Copying others’ successful strategies is probably something that has existed since before apes even evolved into humans.
This is an ad by a company that sells billing systems. This is what ads look like now.
> Godot needs a whole lot of work (..)

There you go!
I'd love to hear them!
How to Make an Origami Stablecoin
Great tip! Seems like this adds the query param "&tbs=li%3A1", so this might be something you can configure as an extra search engine in firefox. But then I am a happy kagi customer, and I was just thinking that I can't recall the last time I had to do a !g to find something. For me, google search si pretty much dead. I only use it now when on someone else's pc
I shipped a product that used both SQLite and XML files.

One of the improvements that I made was moving a few tables that contained small amounts of data to xml files. Because these files were small and rarely written; it simplified the data access layer, and simplified diagnostics. (I made sure the files were multi-line tabbed xml.)

For "technical" people who needed to diagnose the product, asking them to crack open a SQLite database was a huge ask; but for the major part of the product that used SQLite, it was hands-down better than XML files. (An older version of the product used XML files. It had scalability problems because there's no good way to make an incremental update to an XML file.)

The advantages of XML, specifically, a human-readable format; really only work for small files when the design of the schema is optimized for readable XML. Unfortunately, the need to always rewrite the entire XML file, and the "complexities" that come with lots and lots of features will quickly erode XML's biggest advantages.

IMO: A "lay" person needing to muck around with the internals of an office document is fringe enough that learning to use a SQLite reader is an acceptable speed bump. The limitations of XML + Zip, when it comes to random writes in the middle of a file, just can't be overcome by Moore's law.
I imagine the only limit would be finding a VR game that has enough stress, and playing it for long enough. Most people probably wouldn't willingly play a VR game that stressful for that long.
Tasting a difference in grind size does not equate to fine particles being “bitter” and larger particles being “flat”, nor does it result in a slightly uneven grind being “better” than a more consistent one…
Sadly the law of salvage is only part of maritime law https://en.wikipedia.org/wiki/Law_of_salvage

Hills of south carolina are out of its juristiction.
I've built several billing systems and managed a team that built a much larger one, and it's not that hard, but it does require an attitude and attention to detail that a lot of people lack.

E.g. one thing that worked well in the systems I've worked on was to break things into small state transitions, very firmly document the allowed states and their transitions, and log every transition to the database. Wherever possible (anywhere that didn't interact with external API's, and sometimes even when they did) we'd aim for state transitions to be idempotent. When they weren't, we'd seek to reduce the non-idempotent call to an external dependency to just that call as a separate state transition.

When something very occasionally went wrong, we could trace things in detail, and pinpoint it, and most of the time we could safely replay transitions around whatever went wrong until we could see what had happened.

It wasn't difficult to build these systems that way, but it was tedious, and something where it's easy for people to be tempted into shortcuts.

As for scaling, you spit out events for rollups, and can shard invoice generation. We handled millions of revenue on a machine far less powerful than my laptop today. Scaling really would not have been up there for me.

To #3, maintaining old pricing isn't generally that hard. Very few people drastically change how they account for usage, which tends to be the most complicated billing scenario. They tend to change amounts and periods and thresholds, which should be data, not code.

With respect to a team, I agree. One of the places I worked on billing was Yahoo. At the time it wasn't just one team, but several - my team (responsible for Europe) existed largely because the European finance and product teams didn't trust the US payment services team to take their requirements seriously enough and so wouldn't let them near the European premium services... Billing isn't something you want to do yourself unless it's either a core competency or you're big enough to have to deal with that kind of bullshit.

(As for size of teams, I've built a billing system with 2 people, but I've also worked on billing systems managed by 50... You really want to have a good idea whether you're likely to end up towards the former or latter before you go ahead...)
For now, this seems to work: https://www.google.com/advanced_search but, given the pace at which Google "improves" things, I don't have much hope that it will last.
We don't have children starving in schools
I'm sure many folks, including me, would be willing to help Vlad organize a private acquisition if he suddenly had some pressing need to sell.
The trick is that 99% of the engineering expense at cloud providers is to enable weird multi-tenancy use cases and scale to obscene size. You don't have to do either of those if you run your own hardware - your infrastructure can be quite simple.
Yes, but irrelevant here. Basically any shell access means you've changed from preventing remote code execution to preventing privilege escalation, which is much harder.
Surely they knew that it would become a programming language in its own right. That's the fate of all such statically typed languages which give you type-level power but that aren't dependently typed. (Of course dependently typed languages might end up with other languages like its own tactics language.)
Elevator in my apartment is like that, so annoying
ShadowDragon: Lets ICE Monitor Pregnancy Tracking and Fortnite Players
Funny you should say that, since:

a) the Ukrainian forces were saved by the Minsk agreements[1]

b) it was both Merkel and Hollande that said they tried to buy time using the Minsk agreements[2]

[1] https://en.wikipedia.org/w/index.php?title=Battle_of_Debalts...

[2] https://archive.ph/c4ZVK

[3] https://kyivindependent.com/hollande-there-will-only-be-a-wa...
VSCode with the devcontainer and docker is great on Silverblue.

I've been prototyping some developer workflows with friends here: https://universal-blue.org/images/bluefin/developer-experien...

So far the major patterns are vscode with distrobox, vscode with devcontainers, vscode with devpod, jetbrains toolbox thing (which just runs everything out of the home directory, the OS doesn't care).

And then devbox/nix and homebrew in ~ is also an option if you're into that.
But from the perspective of anyone that isn't a networking expert, there is no real problem, things just work and there are no real issues. Networking folks found ways to extend the runway and all other tech people see is the occasional article like this and then they forget about it again five minutes later. I don't even see the effects of the cost of an IP anywhere. I guess it's there, but I don't notice. No regular person even knows what ipv6 is.
https://jbshaldane.org/index.html was pretty interesting too.
Sure, that's one line and then you're done. And only if you care about very old (WinXP) or deliberately obnoxious (OpenBSD) platforms.
You need schmitt trigger input to do it properly and most microcontrollers don't have it.
Geoffrey West, Scale: The Universal Laws of Growth, Innovation, Sustainability, and the Pace of Life in Organisms, Cities, Economies, and Companies:

Fascinated by issues of aging and mortality, West applied the rigor of a physicist to the biological question of why we live as long as we do and no longer. The result was astonishing, and changed science, creating a new understanding of energy use and metabolism: West found that despite the riotous diversity in the sizes of mammals, they are all, to a large degree, scaled versions of each other. If you know the size of a mammal, you can use scaling laws to learn everything from how much food it eats per day, what its heart-rate is, how long it will take to mature, its lifespan, and so on....

Recently, West has applied his revolutionary work on cities and biological life to the business world. This investigation has led to powerful insights into why some companies thrive while others fail. The implications of these discoveries are far-reaching, and are just beginning to be explored.

<https://libgen.rs/book/index.php?md5=0899C2F4CD20BF73FC1E150...>
But that's not based on evolution/biology anymore.
/etc/shadow was born not because /etc/passwd had a plain text password but because the hashes became crackable and /etc/passwd is a public read file. Linux has never had them. Here's the man page indicating encrypted passwords for Unix v7 /etc/passwd release in 1979: https://man.cat-v.org/unix_7th/5/passwd
Could you give some specific examples? I'm interested as someone dabbling in game dev in caught in the endless cycle of engine debates.
I built a billing system for a web hosting company in PHP, almost 20 years ago. This was for a few hundred users. There were a couple of edge cases, but nothing incredibly challenging.
> How then does your gardener get his truck to your house? Your DoorDash driver? The elderly woman on a fixed income who needs to get to her doctors appointment?

The whole idea is to reduce peak demand. Your gardener doesn’t need to go downtown at the same time as office workers, so they are unlikely to be affected since they’re going to your house rather than your office and they can show up at 10am. Similarly, getting breakfast from DoorDash across town is not a human right - you can order closer to home or pay market rate for use of a couple hundred feet of public space to haul your burrito.
I thought most of what’s for sale in a typical supermarket now in Europe or America is more or less on consignment anyway, and manufacturers sign complex agreements with store brands regarding shelf placement, height, length, and price.

How much do retailers actually control the price of what they sell, except their own brands and bulk produce?
fortunately in the low country.. there really aren't hills just marshes and wetlands, but in all seriousness it would be a pretty cool salvage for someone
What Is Federated Machine Learning?
https://archives.sonophase.com/music/1484849167

I'm searching for songs like Anotherclock by Parcels.

The first one is this ambient electronic song, the next is some reggae, which don't feel very similar to Anotherclock to me.

How does it determine acoustic similarity?
That something can be Turing-complete in the worst case doesn’t mean that you hit those worst-cases on a frequent, or even occasional basis.
Would be interesting to know the precise number of requests that Telegram replied to in the Netherlands. And also where else in the world this has already happened. I.e. according to NDR research, the German federal police BKA handed in 202 requests in 2022 and telegram answered 64 of them, handing over user data in 25 cases.

(Source: https://www.ndr.de/der_ndr/presse/mitteilungen/Ministerium-b...)
The problem isn't that Unity is changing their pricing model, it's that without warning they have changed their terms to a highly volatile pricing model that is holding game developers hostage.
Don't you mean something like [A+B+C] ≃ [A]×[B]×[C]
I doubt I'll ever attend but it's a great initiative. I might blog about it just to spread the message.

> what's your domain name?

Lives at https://manuelmoreale.com
Fine instead of Freaking is much nicer.
Fileless Remote Code Execution on Juniper Firewalls
Well, you can - you can have a policy that forces payments from a select group. Some users will complain when "No, you cant pay with 2 chickens every 3rd full moon", but that is too bad.
Well one thing an OTS solution accomplishes is it makes costs and capabilities very clear to product and marketing. When you have an internal team doing something bespoke to your organization it is viewed as much more malleable.

If the third party solution cannot support the billing system devised, or will support it for a large cost, companies are more likely to choose things that are more in the box.
I love this.

Well down the road of this journey myself:

https://www.frankcaron.com/blog.html

Working on killing a lot of JS, albeit my 10 year old Bootstrap theme still has a bunch that's not really necessary.
> Rust’s type system ended up being Turing-complete anyway. It seems like it fell into the same trap as C++ templates

I hear it is a common trap.

https://aphyr.com/posts/342-typing-the-technical-interview
That document is not a proposal, it is a problem statement. It goes without saying that IPv4 only clients - every single one of them - would need to be upgraded in some fashion to support a larger address space. The issue is how to do that while remaining incentive compatible.

The only way to remain incentive compatible is to remain administratively compatible, and that is where IPv6 as presently constituted fails dramatically by requiring two independent network configurations to be maintained for the better part of a century, without giving anyone an incremental incentive to maintain the second one, leading to a hold out problem.

The public switched phone network has gone through major upgrades and yet at no point did someone say we are going to throw out all your existing phone numbers and require you to get new ones, or require you to have two independent and incompatible phone numbers that you put on your business cards, have two phones on your desk, or a phone with a mode selection button depending on whether you wanted to call a new style phone number or an old style phone number.

And that - from an administrative point of view - is the fundamental problem with the deployment of IPv6 as we know it. Dual stack now and for decades to come. Dual stack anything is not incentive compatible and should never have been done. The proper solution is single stack everything with capabilities that are dormant until they are deployed on a global level as part of the normal upgrade process in an administratively compatible fashion so that no large scale administrative intervention is required now or at any time in the future.
Set theory might seem almost mundane in many cases, but it's really powerful to express certain solutions in a very concise way. I've refactored code into much simpler code by just thinking about it in terms of set manipulation, vastly reducing the number of classes/tables necessary. Operations became self-explanatory (it's "just a set").

It also gives you a good foothold to realize whether the solution works or not into the future, a bit of a barebones formalism. You get to play with it in math terms before writing any code. This particular refactoring became the only thing in the codebase that didn't need to change as new requirements came along.
Then don't put an irrelevant citation if you don't want to play the game.
One is peer reviewed, another isn't, so it's like comparing results from a self-reported against an academically measured study.

The availability of Windows source for partners is nothing compared to how many educated eyes are on the Linux source at a given moment.

Of course none of this matters because the BSDs are more secure than both but they wouldn't pick them over Windows IRL anyways. Why Windows are preferred is a matter of business and not technology. This is a long topic and if you were in Usenet advocacies you know what it's all about. Support, logistics, number of trained people in the market, certifications, so on and so forth. Linux doesn't have an easy fight there.
- "Mount Blue Sky is the highest peak in the Mount Evans Wilderness..."

https://en.wikipedia.org/wiki/Mount_Blue_Sky

Is this an oversight?
author here. That's a really good observation kornel. Rust's philosophy of avoiding post-monomorphization errors at all costs is usually sung in high praises (followed by a ridicule of C++ template errors) - but it comes at a cost. And when you stray away from the declarative way and start plastering const generic bounds everywhere you really feel the pain.

Anyways, I think engaging in this topic as a community is super important. Cause that's the only way to push PLs forward and explore this massive space.
$1.2T to OPERATE the F-35 program, yikes! I would love to see the TCO figures on an F-35 (or not). US Military budget concepts have always blown my mind.
My jet-plane brings all the spys to the yard.
If you've tried blender last before or around version 2.5 or so I can heavily recommend giving it another go. Much less stuff is hidden behind hotkeys, and the interface in general behaves more like you'd expect it to. I can't overstate how wildly the blender UI has improved since then.
FlatBuffers – an efficient cross platform serialization library for many langs
Crypto != intelligence. But the people that said the former did may have been lacking in the later.
I think it's more "learn rust" than "use rust", and nowadays a lot of partly written learning projects are published on GitHub. A lot of the similar "learn C++" projects happened earlier and either stayed private or are quite good by now.
That's simply not true. The US military only has primary radar coverage over a small fraction of the country. (Air traffic control primarily relies on secondary surveillance radar.)

Only the weather satellites in geostationary orbits provide near real-time imagery, and they lack the resolution to spot something the size of an aircraft. High resolution images come from spy satellites in highly inclined low orbits which provide only intermittent coverage of any particular location. And they can't see through clouds.
Your People and Blogs newsletter looks great. I just signed up!