skysight-inc/HackerNews huggingface dataset:
The best approach I can give you? Don't.

If you have a big bang V2 that is incompatible with V1, you've already lost. There should be a V1.0.1, V1.0.2, etc that incrementally gets you to what you would've already gotten with V2 without losing the ability to do each individual piece in stepwise succession. That's essentially what the "strangler pattern" is.

The strangler pattern is helpful, because it forces you to focus on what you piece-wise need to "strangle" -- which usually isn't as much as it looks like at first blush.

The hardest part of most migrations is data model migrations, and the best approach here is to start writing to the new model before you start reading it from the core business logic. By the time that works as expected, much of the pain is done. This takes a long time because it requires a lot of repairing the ship as you steer it, so for the sake of the business, it is best doing it in small pieces aligned with chunks of business value or new feature iteration velocity.

The second part of many migrations is adding sufficient test coverage -- in a lot of cases, this will already be present, but if it's not, you're in for a world of pain. If you don't have enough test coverage of the V1, add that before you try and do anything fancy or you'll end up testing "the long way" (through production outages and late night scrambles to hotfix and inevitable rollbacks).
One possibility is that speed limits are set so drivers are safe/efficient at the maximum observed traffic density.

If the maximum traffic density doesn't happen often, then people can understandably be annoyed when they can safely drive faster most of the time.
Funny how not that long ago everyone used to predict that with the increases of productivity worldwide we'll keep reducing our workload to a point where we'll work just few hours a week and remain just as productive. And it seems that this has happened for a select few but everyone else is working more and more just to afford rent and basic necessities.
Two things happen at the same time:

1. people say that robots are taking all the jobs

2. countries raise retirement age & adopt 6 day work week, because there's too much work to be done

I am not entirely sure, but maybe robots are not that bad, assuming appropriate taxation to fund pensions & 5-day work weeks?
> You just use Mac or Linux without changing anything?

Mac, no. It's almost as bad as windows in terms of having to chase perpetual change for no reason.

Linux though? Absolutely. Nothing changes unless I want it to change. Here's an admittedly extreme, but very real example: I build my parents a simplified Linux desktop setup ca.1996 (neither had any computer experience so wanted to keep it very simple).

Today ~28 years later, my remaining parent is using the exact same setup. The last thing you want to impose on a 95 year old with fading vision is an interface change. So it is exactly what it was in 1996. Through several hardware replacements, countless updates and even distro changes, it is still exactly the same.

This is what user-friendly means. I, the user, own the experience. Neither microsoft nor apple are able to respect that.
Show HN: Designing and Building a self-hosted crypto checkout module
Hi HN, we run a studio for designing + building apps for AI & web3 startups and companies and we wanted to build a self-hosted ERC-20 checkout module. This is the MVP version of it and we still want to add a webhook/listener that updates after payment and triggers other actions in the backend.

This can also be used in a lot of other applications like tip mechanism, a blockchain powered version of BuyMeACoffee.com to fund creatives across the globe.

Super excited to have started this anyway and open to feedback, thank you.
First Bitcoin and now AI.
I understand the point. It’s one in a long line of such enabling tech — all leading to the same outcome.
Thank you! The code is unlikely to be released (it's built upon Meta-internal codebases that I no longer have access to post-internship), at least not in the form that we specifically used at submission time. The last time I caught up with the team someone was expressing interest in releasing some broadly useful rendering code, but I really can't speak on their behalf so no guarantees.

IMHO it's a really exciting time to be in the neural rendering / 3D vision space - the field is moving quickly and there's interesting work across all dimensions. My personal interests lean towards large-scale 3D reconstruction, and to that effect eliminating the need for traditional SfM/COLMAP preprocessing would be great. There's a lot of relevant recent work (https://dust3r.europe.naverlabs.com/, https://cameronosmith.github.io/flowmap/, https://vggsfm.github.io/, etc), but scaling these methods beyond several dozen images remains a challenge. I’m also really excited about using learned priors that can improve NeRF quality in underobserved regions (https://reconfusion.github.io). IMO using these priors will be super important to enabling dynamic 4D reconstruction (since it’s otherwise unfeasible to directly observe every space-time point in a scene). Finally, making NeRF environments more interactive (as other posts have described) would unlock many use cases especially in simulation (ie: for autonomous driving). This is kind of tricky for implicit representations (like the original NeRF and this work), but there have been some really cool papers in the 3D Gaussian space (https://xpandora.github.io/PhysGaussian/) that are exciting.
> try to find a way to do it incrementally,
I would make it a hard requirement.

If you can't do it incrementally, it's going to fail. Corporations rarely have the attention span and staff tenure to make that kind of migration work.

Even if it takes a year of pre-work to get to a point where it can be done incrementally, it will be the only way it gets done.
> without all the contortions and schnookery involved in "telling a story" in our marketing-besotted culture.

This is probably the only story I've read on here that didn't reek of self promotion or self aggrandization, or even a "I did this so you don't have to" -- it was the kind of story you might find on Blogger back in the day. Exceedingly rare now.
Yes! Speed difference is dangerous. So yes the difference in speed between vehicle and stationary objects it can hit (trees, poles, parker cars). On highways without a divider the danger is from incoming cars as that will double the impact speed. On highways with dividers having speed different from cars around you can be dangerous because it means either you are changing lanes to pass often else others are changing lanes often to get around you.
> Running clusters of VM/container/instances to “scale up” to transient demand but leaving largely idle (a very, very common outcome) then an event oriented rewrite is going to save a big hunk of money.

If you're using k8s, HPA is handled for you. You just need to define policies/parameters. You're saying as if rewriting an entire app doesn't cost money.
One of the best textbooks I had to read for my degree, back in the 80s. The appendix containg the Minix source code was my first exposure to a large body of well-written C code.
Latitude
At my local fine-fare (80s uk superstore) they sold computers in a 'concession' stand.

They sold Jupiter Aces. Wish I had the money back then to get one!
Your understanding is correct!
A lot of internal web apps with low TPS can be easily ported to Lambda using these adapters. They should be the main use case IMO.
Design patents have a 15 year life. I'm a great lover of books and arts in general, but I'm not clear on why ownership rights in some creative endeavors should be massively privileged over others. Can the families of authors not write books of their own, or engage in other economic activity?

What about the families of people who toil over creative work and don't hit the jackpot? There are many fine writers/artists who never gain more than a niche audience while garbage sells big. Go to a bookstore and look at the history section, pseudo-historians like Bill O'Reilly are given more shelf space than serious historians. To be frank I almost exclusively buy from used book stores for the last decade because nonfiction offerings in chain/non-specialist bookstores are so bad. Vendors of used books tend to select for quality rather than popularity.
It would take a miracle for us to stop wasting energy on nonsense.
> without consequences.

Also look up "blue skin colloidal silver."
clang does have pragma clang fp to enable a subset of fast math flags within a scope
Full title: Why going cashless has turned Sweden from one of the safest countries into a high-crime nation
>Selling to Private Equity is almost never what any founder would have wanted, as their job is to slice and dice, "cut the fat" and sell the pieces to different highest bidders.

Depends on the founder, I'm happy that the OP decided to look after his workers, but there's no loyalty in business.

Many founders would just look at the largest payday and be done with it.

I guess you can have a George Lucas moment and criticize the new owners for destroying what you made, but you're sitting nice with your profits.

OP comes off as someone who was already really comfortable, and the business appears to of been profitable.

But it would have been a completely different story if they were losing money, at a point you might just have to sell the company for parts and cut your losses.

Maybe offer some of the lifers generous severance packages.
https://archive.org/details/msdos_SimCity_1989
> Sadly he doesn’t actually understand communism

Maybe you can cite examples of it working?

It's legal to start a commune in the US. Why not give it a try? Report back to us how it goes!

> conflates collectivism with being “anti freedom” (lol)

I do, because collectivism means you do not own the fruits of your labor. I bet you'd be outraged if I helped myself to some of your stuff that I decided you didn't need.
Reading just the syllabus, I was surprised to see no mention of accountability. Quick Ctrl+F searches for "accountability", "appeal", and "review" gave no results. "Reputation" appears, but in a section rather harshly titled "Herding and Conformity", about the reputations of the people not trusting algorithms, not the people making or deploying them.

In my own experience, human forecasters and decision-makers tend to be much easier to hold accountable for bad forecasts and decisions. At a minimum, they stake their reputations, just by putting their names to their actions. With algorithms, by contrast, there's often no visible sign of who created them or decided to use them. There's often no effective process for review, correction, or redress at all.

The fact that high-volume, low-risk decisions tend to get automated more often may partly explain this. But it may also partly explain general attitudes toward algorithms, as a consequence.
Productivity has increased substantially over the past few generations. Longer working time just captures more of that productivity for the benefit of the employer. This is a continuation of another trend over the past generations, to have increased productivity over a much larger segment of the population (more women joined the workforce) and yet the benefits of this were mostly captured by the employers, at least in the countries where this was more thoroughly documented and didn’t suffer any upheaval or regime changes to influence the numbers (e.g. the US).
The number one reason for shutting down an investigation is when the government already knows the answer, but has no acceptable solution to it. In this case, possible reasons include: (1) prions, with a possible spread into the soil and plants (2) neurotoxins like BMAA etc. from seafood (3) brain eating amoeba.

If it's #1, "god help NB" because short of incinerating the whole region with a hydrogen bomb, there is not much else that can be done.

If it's #2, neurotoxins from seafood, stopping them will decimate the local seafood industry, ergo taxes and exports, so the government has a lot to lose by taking action.

If it's #3, the government would still be on the hook for inadequate water purification.
Companies of a certain size have always had this power, that's why they pit countries and states against each other when setting up factories and offices.

However in this case Apple are not going to pull any models from EU markets, that would be an own goal ceding the entire region to Samsung.
There's one in the Cambridge computer museum: https://www.computinghistory.org.uk/det/1332/Jupiter-Ace/

Steve Vickers, one of the founders of Jupiter Cantab, was my university lecturer back in the 90s. He taught a very obscure course in mathematical structures, and in a sense was both the first and last (a decade and a half later) to teach me computer science. Previous comments: https://news.ycombinator.com/item?id=23760382 https://news.ycombinator.com/item?id=26375986
Their code base is also weirdly convoluted, with many crates and files just proxying over to others. I've read and written a lot rust, and haven't seen this style really. Could be nothing but its odd.
No amount of automation has ever seemed to result in a net reduction in work to do thus far
70mb is insane and not at all the standard.

There's a reason why Vite has a default bundle chunk warning of 500kb.

There's really no reason it should be that large. If you just lazy load each route your chunks should distribute into manageable size pretty much automatically.

It sounds like you may also have a bunch of dependencies. Which can happen in a native app, but in a web app as you know you'll have limited resources so size is important.
If the container has any dependencies, and they change, a lack of change quickly becomes an escalating liability. I’ve heard the “fixed is reliable” arguments for decades and have never seen anything that would justify the widespread failure to keep systems patched.
“If we work together, we can unlock AI’s game-changing abilities to help create the net zero, climate resilient and nature positive works that we so urgently need,” Microsoft said in a statement.
> This way I am explicitly exporting the dev environment without relying on the fact that everything is in order in my .env file (another approach would be to have a .env.dev file)

What did you find lacking with the .env.dev approach? (Or if some tool doesn't support .env.dev could always symlink .env → .env.dev)
Not surprised. They probably treated treated bloggers like Press 15 years ago, so…
Did you read the cited articles or are you basing your assertions only on this Web article? There might be a lot of detail on the evidence in the cited articles which are just not mentioned here.

It's somewhat ironic that you throw around a speculation that everything is speculated without actually trying to look at the possible evidence yourself.
In Blender, dithering is enabled by default. First of all, it's not exactly true, that 8 bits per channel make it so banding is unnoticeable - but it's very hard to notice; will depend on the area of colors (darker/brigher, redish/bluish...), but also if you dither your gradient in the image, and the image is further processed, the dither will help avoid banding after processing. Of course if you want to process an image, don't save it in just 8 bits per channel, but sometimes you don't know the image will be processed, or choosing the format is not up to you.
>How can we be sure of this?

It's theft. How many people, no matter how altruistic, will feel truly zen seeing their own idea copied by people who care nothing about thw craft making money, exploiting other labor, and otherwise making the world a worse place?

I argue less than the amount that at least want a steady living at the bare minimum. Something many struggle to achieve.

>why is the current model assumed to be the best, when it is based on a lot of outdated assumptions (e.g., physical copies)?

Because I've heard no better alternatives?

We don't need to throw the baby out with that bathwater. In increasing orderof viability: Implement UBI so artists don't starve guarantee an easy trial for proper compensation (which may still be pennies for thieves) if/when their art is stolen and makes hand over fist in money, or reduce the current time of exclusivity. The concept of keeping some time to benefit from your ideas exclusively isn't a flawed one, it just needs tweaks to the idea, or a fundamental shift in how humans survive in the modern world.
> all scientists and military use it too,

That's hardly true. Even if it was it's not a justification for forcing people to change their common parlance.

Also, if you really want a temperature scale, you'd have it referenced to absolute zero so it's an actual ratio quantity. So, a lot of "scientists" use Kelvin or in some cases Rankine.

> ignoring rest of the world

There's a conversion factor. We don't keep it secret. We're not "ignoring" the rest of the world, we're just operating in a mode that most convenient for us.
It'd definitely not something I can relate to. My parents will leave me nothing, and have spent most of their life taking from me.
Don't stop it yet, we need more stupid LLMs.
1. Remember Murphy's Law
2. Have Rollback option
3. Keep things todo on go live date to a minimum. You would be surprised lot of the risks can be mitigated before the date of change.
3. Greece's unemployment rate is almost 11%.

What a bizarre situation.
As a SDET, I suggest lots of testing.

Assuming V1 and V2 offer users the same functionality, there’s a bunch of tests you can offer. The best one IMO is oracle testing where you do something on v1 and v2 and check they do the same thing. Preferably roll out to a subset of users such as via a canary deployment and make sure you have a rollback plan.
I led a painful migration a couple of years ago and can share some tips.

It's not clear whether v2 is already in production somewhere else. If it is not, you better wait until 1) the v2 data model has really been finalized and in prod and 2) key resources can be made available to the migration team. We were forced to begin the migration before the new product was complete and it was just plain impossible. We had to start all over every quarter.

- Migrations are very difficult to estimate. Any optimistic estimate will bite back. Hold off as much as you can, and ensure appropriate buffers if you really have to.

- ensure that the 8 clients have an identical v1 data model (tables, constraints, etc). If that is not the case, remember you will run n migrations, not 1.

- You need a team with knowledge of both v1 and v2 data models, as well as business domain know-how. There are many decisions that need to be made and you need the right people to be around.

- Not everything has to be migrated. Trying to migrate 100% is a common mistake: engage with the customers to understand what's the minimum that legally and operationally has to be migrated, especially if the v1 system has been in production for many years.

- Data migration is a iterative process, and the last thing you want to is to manually QA every iteration. You need to develop tests that will provide a reasonable data integrity assurance.

- Dashboards showing data migrated, failing/ok tests, remaining tables, etc. help communicate status and track progress.

- Customers will need to be involved during the whole project. You need them to commit to making people available that can quickly answer questions to unlock you dev teams. ideally, you want to create a single team. Make sure that decisions are traced and versioned.

- Performance matters. Discuss the performance requirements upfront. Our process was very, very slow and we found out a bit too late that the customer would not tolerate such down time. Also, discuss "when" ok to migrate, how to rollback in case of failure, etc.
Ripgrep is recent and written in Rust, but it does not describe itself as modern, even if some apects of it are.

Its interface is designed to be an almost drop-in replacement of grep, which makes it "old style".

I think software can be old style, modern, or neutral. Most software written today aims for modern, it seems logical.
HH70, the first high-temperature superconducting Tokamak achieves first plasma
"While the 40-hour work week is still officially in place, employers are permitted to require staff to work up to two unpaid hours per day for a limited period in return for more free time."

This is kind of a wild quote from the article. WTF? two hours unpaid work per day?

"A supplement of 40% of the daily wage will be paid for the sixth day of labor."

It's unclear to me if this means they're receiving 100% + 40% for their sixth day, or if the sixth day is 4/10th the normal wage?
People have different gut/intestinal flora which affects the amount of calories digested from different foods.

There are actual studies on this:

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC10368799/

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8291023/

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7463616/

We all know that one person who can eat literally anything and is still fit and that one person who sees an ad for ice cream and gains 5 pounds (hyperbole of course). According to these studies it's the difference in gut microbiota that's the difference here.
Even if that were true, it’s not the case that all products have PFAS, so it’s not the case that Colorado would not have access to dental floss.
Isn't Greece's unemployment rate the highest in the E.U.? Yes, they may be "low-quality" workers applying for jobs, but if a company can't find "high-quality," they must make do.

How did we lose the art of training new hires?
I've seen one once at a HamFest or something.

There are kits out there to make your own though:

https://www.tfw8b.com/product/minstrel-4d-turbo-jupiter-ace-...
It’s odd that no one installs these in the US!
If Robots/Ai allow us to extract more value per hour worked, it will unlock more work that wasn't worth doing before.

Paradoxically, efficiency generates more available work, not less.

The amount of work to be done is not finite.
Having danced for around a decade, I would say the hand positioning example is a bit reductive. The most obvious example is that there's only one variant of "both hands crossed over" - while it's true that the hands might only fit together one way, the things you can do with the hands depending on what arm is on top varies significantly.

Having said that I'm pretty excited about the topic and what the author can do with it.
Scaling to 0 means me being able to deploy each branch/PR to a whole, fully separate environment without it costing too much. As soon as you do that everything from testing migrations (via database branching), running full end-to-end tests (including the full infra, db, backend, etc.), having proper previews for people to view when reviewing the changes (like for example the UX designer seeing the whole feature working including the backend/db changes before it going in) just falls into place.

If I don't scale to 0 I'd prefer to work on dedicated hardware, anything in-between just doesn't give me enough benefit.
> At least he’s getting the downvotes he deserves in this thread.

Feel free to downvote me all you like, Taylor!
I’m sorry to hear about your experiences. It might not be the nicest thing to hear, but I would recommend getting a job in any field that can support you and your family, and looking for a dev job afterwards. I’ve had trouble finding a job too and that’s what I would do if money was tight.
I just read kill it with fire [0] that describes a methodology for legacy modernization projects (which should work fine for any migration). Highly recommended! It would have served me well as a guide before I went in to the large migrations I’ve operated in my career.

[0]: https://nostarch.com/kill-it-fire
@fastmath in Julia is telling LLVM (basically) the same thing. I think the only difference is that Julia doesn't think rsqrt(x)*x with Newton iteration is a good way of computing sqrt
Yes the kids these days call it being “Him” (or whatever third person singular pronoun you may refer to)