skysight-inc/HackerNews huggingface dataset:
> I'm in favor of duck-typing these words

Hard disagree. A subset of behaviours resembling or even "indistinguishable" from understanding should not be enough to meet the definition.

Maybe some day we will have AI systems that get there, but LLMs ain't it.
Define "pimp."
NASA/openmct:
https://github.com/nasa/openmct
Thanks, that's useful. Might be an interesting write-up or tell / show HN type submission.

I do similarly for some cases. I've written scripts to parse down NOAAA weather reports to something that renders well on a terminal, and have scripts and shell functions similar to surfraw (by now badly dated itself) for doing quick lookups from a shell.

I share your view that most website payloads are rubbish (in one case I'd stripped > 90% of the Washington Post's payload to deliver just article text), and that selective acceptance and presentation makes a huge difference.

Though as much as I use shells and terminals, I still find GUIs useful, including Web browsers, though the situation is increasingly frustrating.
10% is a good percentage, it's been 0% for me. Then again, my best art project has been https://imgz.org, which I knew wasn't really going to get used much by other people.
> If I would have called it learning on a human

But you wouldn't call that learning as a human. If you include a chess manual in the learning corpus of an LLM, but not any examples of playing chess, then the LLM can give you all the rules about chess, but it can't play chess. That isn't learning, that is just parroting.

A human who can recite the rules of chess but can't play chess, would you say that he understands the rules of chess? No, he just know how to output the words and not perform the actions, so there is no understanding there. Same with the LLM, nobody can say it understands these things since you would never said a human understood under similar conditions.
Well it powers https://scrimba.com which looks serious enough. I’ve known about it for the past 6 years, but never had the chance to use it because I’ve only done static websites lately.

I am starting work on an automatic irrigation system that will have a web/PWA frontend and I remembered about Imba which I plan to use this time.
We are not discussing whether sex is a spectrum or not though.
Was the nonbinary person that you talked with undergoing medical transition? If not this might explain their view.
Isn’t that essentially what git lfs is?
Just a few weeks ago I did a one-million-process spawn demo in Elixir...

https://www.youtube.com/watch?v=yxyYKnashR0
> Sometimes

I suppose you could try that, and fall back on full data relaying when it doesn't work. Should save a lot of bandwidth.

Of course, that might be a lot of work to implement, not saying it's easy!
solatic -- I have an existing solution that accounts for a lot of these issues you bring up. Would it be possible to pick your brain? Can you share your email or shoot me an email? lawnchair@lawnchair.net.
A is B is not always a symmetric relation... Also the prose looks like it was written with chatgpt with no edits, their "discussion" is content-less drivel. I would have expected a discussion of this obvious fact any reader (including many here) have picked up just reading their abstract.
I've been doing Prolog without knowing there's a coding guidelines. Thanks.
Indeed I have 3D assets in this case. Would this be done differently in an enterprise that has all kinds of tools to manage specialty workflows? Sure. Do I want to spend my days configuring and maintaining some binary blob / LFS storage system? No.

I’ve migrated a lot of projects from fossil to git eventually, but I dare say they never would have made it that far, had I started out with more friction, including fighting vcs tools.
See also the better known Cobalt Blue and Green Bottle Blue tarantulas, very pretty but not the best beginner pets. They shouldn't be handled and need careful climate.

Other tarantulas are very easy, like Rosehair or Pink Toes. They need little attention, make no noise, are hardy desert climate dwellers, and can be handled. I had a female Rosehair live for 20 years as a beginner.
You act like Java isn’t copying what every other language has had for years or decades. Green threads are not threads they’re just an async system in the existing runtime, they share one or more real threads as workers. They do that because creating real threads requires OS features like permission checking, memory management, cpu scheduling, etc. pick the right abstraction for the work.
>In practice there are many such inputs that will overflow huffman_tables

This looks like the generalized version of the problem...

In other words, you have Software A, it generates a lookup table B which is then used to process an input stream of data.

Now the responsibility shifts to you as a software developer (if you care even a little bit about security/correctness of your code) -- to either assert that:

A) The software is written in such a way that there are NO possible cases of input data misusing/failing the lookup table, or

B) The software will only be used in a controlled environment (i.e., point to point communication where both communicants are trusted) such that the stream is guaranteed never to contain data that misuses/fails/causes anomalies with the lookup table.

Since B is all-but-impossible for anything other than a small group or office, that is, truly impossible on the Internet scale, that leaves only A).

Thus, the generalized "best practice" for present or future Software Engineering, can be summarized as follows:

If a lookup table is used in someone's software for whatever reasons -- then then the responsibility goes to the software developer(s) to assert that that lookup table functions correctly and for all types or data, OR that the software detects and appropriately handles erroneous data BEFORE it gets to the lookup table...

In fact, if I were a serious security researcher and had the time -- I'd collect a list of ALL reported security vulnerabilities in the past that had to do, one way or another with lookup tables...

Then I'd read through them, one by one, and compare them for generalities.

I'm guessing (but not knowing) -- that there is a pattern there...

Then I'd go through all software that used lookup tables on streams of data in one way or another -- and audit ALL of them for security vulnerabilities.

Now, clearly this is not a task for one man in one lifetime...

This is a "team sport"...

But if I were a serious security vulnerability researcher -- that is the generalized path that I would take...
I wonder how many false positives the algorithm caused.

They also called it an "AI system", but from the article it looks more like a statistical model that assign a risk score to every attribute (age, location, when, duration, ecc) and then do sum/weighted average. If the sum/weighted average are above a threshold, the reservation is flagged.
This is something I learned being in bands. Fame and fortune weren’t in the story, but because we made the music we wanted to hear, I have an album and 3 EPs worth of music that I can listen to and enjoy, over a decade later.
The author doesn't get the most common problem with perfectionism. "Don't let the perfect be the enemy of the good." Perfectionists often give up entirely, because of some perceived deficiency, instead of powering through to the end.

Of course, keep practicing to get better. Nobody says otherwise. But don't stop practicing just because you can't get it right every time. It's the ALL or NOTHING attitude that's the problem, where getting past failure requires SOMETHING in the pursuit of the ALL.
Well yeah, but in things like vehicle suspensions, power station parts, airplanes in particular, etc, failures are most commonly because of fatigue.
The numbers don't make a lot of sense to me. Are all these men cheating on their wives? Where are the 8 other women getting their needs met? Are they meeting men in regular life or something? So why aren't all the men on tinder doing the same thing?
I’ve been using YNAB as of late. Cheap enough it’s a no brainer and it’s really good.
if he wasn't interested, my son would tell me. i might still try to motivate him by suggesting that if he helps me then i'll be done faster and we have time to do something else together that he wants.
Robot ethics: https://en.wikipedia.org/wiki/Robot_ethics

Workplace robotic safety > Hazards, Hazards controls:
https://en.wikipedia.org/wiki/Workplace_robotics_safety :

> There are four types of accidents that can occur with robots: impact or collision accidents, crushing and trapping accidents, mechanical part accidents, and other accidents [...]

> There are seven sources of hazards that are associated with human interaction with robots and machines: human errors, control errors, unauthorized access, mechanical failures, environmental sources, power systems, and improper installation.

LEGO Boost Creative Toolbox has a short mandatory safety lesson in the app.

What's a good robotics safety program?

--

Pybricks documentation: https://docs.pybricks.com/en/latest/

"I Put 44 Mechanisms In 1 LEGO® Machine..." https://youtube.com/watch?v=ykIYP4z-eMk&si=1hh8KvoRxCVamH4y

"Lego Technic Gearing Ratio Calculator Tool" https://youtube.com/watch?v=yUcNnj5NClY&si=hKB-b1pB3HuVM6ed

--

ROS2 docs > Tutorial
https://docs.ros.org/en/iron/Tutorials.html

ROS Industrial Training > Session 1 - ROS Concepts and Fundamentals (ROS2) https://industrial-training-master.readthedocs.io/en/latest/...

--

MoveIt2:
https://moveit.picknik.ai/main/index.html https://github.com/azalutsky/MoveIt2Docker

--

RoboStack > Jupyterlab-ROS, Jupyter ROS
https://robostack.github.io/JupyterRos.html
> It’s just too error-prone, there’s too many things… You just have to always quote everything.

Sorry, but this seems like a very silly, petty argument. There are other reasons to not like today's pervasive use of YAML, but this is not a very compelling one imo.

The same is true in XML, practically speaking, there just isn't another option - everything must be quoted or wrapped in tags.

So just ... use quotes in YAML. You can force it through a linter [0] if the optionality is what you're hung up on.

[0] https://yamllint.readthedocs.io/en/stable/rules.html#module-...
I did read the article you linked. It does touch a little bit on potential benefits of having databases managed the same way the services using them are, and integration tests that include the database.

However, I’m still scratching my head how any of that is better or not possible with a Postgres installation that is outside of kubernetes. Let’s take out the management part of databases themselves - assume a managed database service like RDS POSTGRES. why would one want to run Postgres on EKS over having their pods on EKS talking to RDS Postgres?

I feel like I’m missing some technical reason/advantage that makes all these people choosing to run Postgres on Kunernetes with operators and what not.

What does Kubernetes bring to this table over a separate Postgres that dont run the risk of kubernetes interfering with the reliability or operation?
As someone who formerly lived in email marketing, the onboarding flow for a trial signup was usually a 7-day flow, 2 emails on the first day, the first was very transactional and automatic for activating your account, the second one was still automated, but a few hours later, and from me (the developer of the product) providing my personal email for any questions. Then one email per day with a tip on how to use the product effectively with mini-case studies from customers.

This converted at 9-15% depending on time of year and product. We built a lot of micro-SaaS offerings.

Our conversion before we did this onboarding multi-touch email approach was closer to 1-2%. These onboarding emails really do work with get a customer engaged and using the trial instead of signing up, and forgetting about it because it was free.

After that, if they converted, they would be moved into a different flow with a less frequent emails (weekly or monthly depending on the product). If they didn't convert, we had a second flow that would lead to an extended trial or discount which would convert another 3-5%.

Effective trial marketing is very important to sign ups. Our "marked as spam" and unsubs never went above 2% because we were providing value in our emails for a customer who signed up for a trial for a reason.
If Fossil is so against deleting commits, what do you do if you've accidentally committed sensitive information that cannot live in any form in the repo?
There is a certain amount of Stockholm syndrome built into the current acceptance of async programming paradigms.

Linear code is far easier to reason about, but that is easy to forget once someone has become accostomed to thinking in async constructs.

The thing is, there are only so many things a person can mentally juggle. Removing the consideration of a whole dimension of issues means the developer can take on more useful complexity.
I mean "massive resources" is just de rigeur across the chip industry now. The hard in hardware is really no longer about it being a physical product in the end.
All that's happened is that the audience has changed. Ownership of your device does and did matter - just not to the wider market that's now being served by the Bambu devices. The market couldn't have grown to this point without the open source printers, I'm convinced of that. And I strongly suspect that there will always be open source printers out there, and they probably will have feature parity, and they probably will be a bit more expensive, and people will say they have "failed" because they only hold a small percentage of the market, but you know what? The market will be ten times the size. Not everyone has to like the thing for the thing to be viable.

In a sense Prusa are already proving this: they're not really competing on price, and they can't build printers fast enough to satisfy demand.
Also, green/virtual threads are overrated, IMHO. Just make system threads, it's not nearly as bad as people think, and it is a lot easier. You will likely want to cap max stack size (so that unintentional large stacks cause crashes instead of using up unreasonable amounts of memory) and perhaps tune a few other things.
And we have a project named Corrosion: https://github.com/corrosion-rs/corrosion
It's also hardly a billionaire. Engineers are solidly middle-class.
That's a good point. Delete the repo and start over I suppose? W/ git wouldn't it possible to find and restore that info anyway? Guess it becomes what do you care about most at that point.
What these 0days teach us is that if you are a person in the crosshairs of powerful adversaries you have to be super-paranoid and reduce your target surface to as small as possible.

If you are James Bond and you want to have secure communications with M, you are better off using a custom appliance type mobile device meant only to do that one function and nothing else. You will have to rely on anonymous 3rd-party burner devices to leave messages encoded in pre-agreed sequence of rotating geo-locked codebooks on random message boards. Any less opsec and you are toast!

If you are a normal human-being using connected digital devices normally, then you should assume anything you put on those devices is already stolen. If you want to keep things truly private, keep it off digital (paper, old-school analog tape etc). Then, at least they will have to physically steal it from you – which, depending on the situation, might be much harder for them, but not necessarily much safer for you. So, you lose either way.

Only real way out is to have well-functioning democratic governments with strong transparency and checks and balances with strongly enforced privacy laws to protect its constituents from both domestic and foreign adversaries and strong support for initiatives like Citizen Labs.
Also doesn’t support recovery questions. As someone who generally enjoys safari, the password manager could use some love. Integration across devices is good though.
> If your medium is a mobile device, then you don't have that much "side" to put the notes in, so you have to get creative another way (you also don't have the same "hover" semantics as on desktop).

When I designed my site (https://two-wrongs.com) I figured you don't have to get creative at all. A person reading on a small screen will likely want a more condensed text, with less of the semi-relevant asides.
I'm not a fossil user but https://fossil-scm.org/home/help/purge
Harpoon – Trace syscalls of user-defined functions, using eBPF
Harpoon aims to capture the syscalls (as if they were fishes) from the execution flow (the river) of a single user-defined function.
Use an autoformatter with formatting rules defined and committed with the code so your team never has to argue about code style again. It shouldn't even be possible for that to come up in code review since it should be an automated check.
In this case, whether it's an identity-is or a "is a member of the group".
Are Wild Animals Just Like Us?
Why have a goal?

Oftentimes it is the journey that is the most important, not the destination.
That's one shitty CEO change away from "your AMS will only work with our filament" and they've already sold you the hardware to do it.
I am not a big direct Chez Scheme user, so that was news to me. Thank you! There is this tool that apparently makes it easier and creates a single file.

https://github.com/rschardt/chez-exe
In principle, I think so, but there a lot of technical barriers to learning how to actually make the structures you’d need to do it. (I haven’t read the actual paper because of the paywall)

From my understanding, there are (at least) 3 factors responsible for the high strength

- nanoscale geometry, basically the can 3D print nanoscale truss structures

- nanocrystalline base metal. There are established methods for fabricating bulk nanocrystalline metals [0], but doing it in an additive manufacturing process at bulk scale I think is a totally open question

- they’re getting extra strength from residual porosity in the metal grains (the pores pin dislocations, stopping one of the principal deformation mechanisms [1]). This is a well known phenomenon, but getting uniform nanoscale pore structure sounds really hard, especially in a bulk metal, and extra especially in an additive setting

0: https://en.m.wikipedia.org/wiki/Nanocrystalline_material#

1: https://en.m.wikipedia.org/wiki/Dislocation

1b: https://en.m.wikipedia.org/wiki/Zener_pinning
This is awesome! I wonder how feasible is it to include TG in Apache Sedona (https://github.com/apache/sedona)

Although Sedona runs as a distributed system, but TG may speed local in-memory geometrical computation for each worker node. Let me know your thoughts!
(2010)

Previous discussions:

https://news.ycombinator.com/item?id=2524422 (86 comments)

https://news.ycombinator.com/item?id=19006036 (247 comments)

https://news.ycombinator.com/item?id=27736980 (127 comments)

https://news.ycombinator.com/item?id=31696940 (73 comments)
Like I said, If you have any independent journalists you think I should check out to get educated, then I’m all ears.

I can give you dozens no problem.
> With IPv6 privacy extensions, your address changes regularly. This seems like an improvement.

Eh… If I was a company that wanted to use IP addresses to fingerprint users, IPv4 vs IPv6+privacy extensions both seem identical to me. Multiple requests from the same IPv4 address mean “someone, perhaps more than one person, from the same household/wifi”. Whereas multiple IPv6+privacy requests from the same /64 prefix means the same thing.

ie. You just consider the first 64 bits of the IP and can assume the same amount of information you already would assume from the IPv4 address. Just ignore the trailing 64 bits because it’s expected that they’ll be randomized/shuffled even from the same client.
Inasmuch as I've read, and that's mostly 60s/70s stuff, most stable escalation theory is based on messaging and red lines.

I.e. identifying a future possibility and loudly proclaiming that if (and only if) it happens, then this nuclear action will take place (and stop there)

Essentially, trying to avoid surprise and uncertainty by tying specific actions to reactions, with the hope of avoiding runaway escalation-begats-escalation scenarios.

Which is notably the opposite of what Russia has been doing, which is more along the lines of "If the West pushes us too far... they're in for it", which is more the kind of bluff you'd make if you never intended to actually escalate (because you create the fear without establishing any requirements to escalate on yourself).
Prime shipping is almost worthless these days. The good stuff you actually want to buy isn’t on Prime. You know what’s on Prime? Knockoffs from QZEEVLO and YAAOUIE brands.
I like that git allows rebase, as long as it is only done in prs or local. Rebase in the sheets, merge in the streets.
Everyone who knows anything at all about mining knows that "owning a mine" (any kind) says nothing whatsoever about the wealth of the owner. It's quite common to put more money into the ground than you ever get back out.

I've known several gold mine owners over the years. To be blunt: none of them had a pot to piss in. Some of them made enough to get by, but that's it. Others had to subsidize their mines by working in town part of the year.
Just thinking aloud here... So functions already (typically) have a bit of prologue for setting up the stackframe, where they juggle rsp and rbp etc. I wonder if you could change the convention for that into something that basically does RequestStackFrame(SIZE) for some known SIZE. RequestStackFrame could then either grow the stack linearly or get memory in some entirely different region depending on what is needed.

Though doing such a function call for every tiny little function is a bit excessive of course, I'm thinking maybe the compiler should track for every function how much stack it will need in the worst case (usage for the function itself + max of usage for the functions it calls). Functions that use memory below some threshold just grow linearly, while those that use above it will go to the trouble of requesting memory. Now this idea assumes that function calls happen in a DAG, it breaks if functions can call themselves or each other in a cycle. But that's actually a good realization maybe. Like a recursive function should perhaps always explicitly request stack space. Security and robustness benefits!

What about libraries? Ideally library functions would be annotated with how much stack space they need (as a side note I have long thought that C-headers are inadequate for specifying how a function should be called. Not annotating stack space requirements one deficiency here!). Absent such annotations, I suppose we need to go with the status quo of making some guess.
I never used D-lang in any production application.

But for an IOT prototype where the executable size and performance were very important we benchmarked D also along with Go and C#.NET Core.

I made the same prototype in Go, C#, Java(GraalVM Native Compile) and D-lang. The results were surprisingly positive for D-lang.

Best Peformance -> D-lang, next Go and then Java(GraalVM), C#.NET Core.

Executable Size -> D-lang:500kb, Go: 2.5 MB, C# : 11MB, Java(GraalVM):8MB.

Our major concern with D-lang was lack of dependable(tested) standard libraries.
The "learn form your own mistakes" phase must occur at some point, regardless.

You may or may not be capable of learning from the mistakes of others; which is the prime reason for listening to others. The other reason is gathering ideas for things to do; and it sounds like you've already got that covered.
For me it’s the elixir/erlang OTP library. Main point being - wherever I worked each team invented their own bespoke solutions and approaches to the problems solved with OTP, and it turns out we had battle tested building blocks all along, had we bothered to look back
And, thankfully, newer computers have virtual memory and page tables, which means that allocating a large stack only costs one page of physical memory until you use it.