skysight-inc/HackerNews huggingface dataset:
As I understand it, it's more that the mathematical functions aren't specified by the standard.

There is no sqrt instruction. So you stard with a taylor approximation, then maybe do a few rounds of Newton's method to refine the answer. But what degree is the taylor series? Where did you centre it (can't be around 0)? How many Newton's methods did you do? IEEE 754 might dictate what multiplication looks like, but for sqrt, sin, cos, tan you need to come up with a method of calculation, and that's in the standard library which usually comes from the compiler. You could make your own implementations but...

Floats are not associative: (a+b)+c != a+(b+c). So even something like reordering fundamental operations can cause divergence.
>>when I started working in the industry, I realized that it's absolutely exhausting.

It's been this way forever. For every level of the stack. When I started the physical hardware hadn't been settled (coax, ethernet, token ring etc.)

Fortunately when I started we only got paid when we shipped. So we were motivated to ship, not be distracted by rewrites. We were also lucky that as a boot-strapped company we had no managers calling the shots. We made decisions and stuck to them, and it's paid off over the long run.

Of course the product has changed immensely over 25 years - but the core code laid down in 1996 is still integral. We've spent the time on the product, not worrying about the sexiness of the tech stack.

Which is not to say we've ignored the tech stack, it's evolved a lot, but the stack serves the product, not the other way around.

On the other hand we don't have to raise investments, we don't have to attract endless streams of new programmers, we don't have to juice a stock price, so we don't have to appear modern or hip. We can just keep doing what we do, making money, focusing on the value to customers, not being (easily) distracted by the next shiny toy.

And yeah, after a couple decades you learn to see through the hype a bit and distinguish things that are good for you, not just the flavor of the week.
A big part of this in the US is our continued evolution in suburbs: In practice, in person contact with others is a lot more work than historically. This makes children have very little contact with adults other than teachers and their own parents. Even contact in businesses is depersonalized, given this world of chains, large stores and many employees with changing shifts, leading to minimal recurring contact, and interactions that very rarely get personal.

More communal countries, both in Europe in Asia, still have some personal contact: From a pharmacist to an ice cream man, a town or a neighborhood can have community, and with that community come the children seeing those workers as people, and having a relationship with them. When most business is done on foot, people see each other down the street, or in the park, and there's a chance of community. With suburbia an cars, all social contact takes effort: Community get expensive, and few pay the price.
It is strange that you immediately went the criminal route. I was thinking more about fathers who work too much, which is most in my world. They spend far less time with their children than their wives, maybe 5x to 10x. My father had a grueling commute as a child that was 90 minutes each way. What a waste. I hardly saw him during the week, then he was exhausted on the weekends. I cringe every time I hear senior (_ALWAYS_ male) executives say: "I do it all for my kids." Yeah right; work less and spend more time with your kids -- that is what they really want, not another fancy ski trip.
I've been thinking about building a tiny, (relatively) cheap haptic knob. I wonder if this makes enough torque for it to feel right? Maybe with a big stator and a small knob.
I know the answer won't help you, but - from friends recommendations.

If they recommend something great you wouldn't hear otherwise, that's good, and if the game is bad - well, you still have something to talk about
With option 1 you end up in the old meme of

1. Sell 10 barrels
2. ?????
3. Profit

After you’ve sold the ten barrels, now what? There are no more barrels and no more coming since you chose not to drill. You have to shut down and do something else with whatever money you made from the sale.
Sorry that could’ve been more clear. Everyone at the gate speaking on behalf of the airline and/or airport insisted all passengers stay at the gate because the flight would leave promptly as soon as the plane arrived, and repeatedly told us that they wouldn’t stay for any estimated time they had announced.

They were framing it like the scenario you describe, but they held everyone there at the gate repeating this and revising the estimates for more than six hours IIRC. And I guess if they had flown out ahead of that last revised estimate it would’ve been too bad for me and everyone else who felt relieved to go somewhere else for the half hour or so we had to roam around, but thankfully they were just starting boarding when we all wandered back.
Additional discussion from post two days ago: https://news.ycombinator.com/item?id=36443676
Thanks coral restoration volunteers!

Are there already coral restoration drones / RUVs?

Is there a SAR Synthetic Aperture Radar -like imaging capability for mapping coral health; with sensor fusion? https://en.wikipedia.org/wiki/Synthetic-aperture_radar

Sensor fusion: https://en.wikipedia.org/wiki/Sensor_fusion

"Bacterial sensors send a jolt of electricity when triggered"
https://news.rice.edu/news/2022/bacterial-sensors-send-jolt-...

re: sensor nets:
https://twitter.com/westurner/status/1612605800576335874 ... ansible-OpenWRT, [DuckLink] LoRa, MEMS wave power

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

#Goal14: Life below water: https://www.globalgoals.org/goals/14-life-below-water/

#SDG14: Conserve and sustainably use the oceans, seas and marine resources for sustainable development :
https://sdgs.un.org/goals/goal14

Do coral fragments have to be planted ashore or could they be ~transplanted by a drone?
But, he tried. He made a conscience decision. That part matters most -- his intent. He did it for love.
The US still does a ton of nuclear energy and weapons research. Policy is generally made by the people doing the actual work - who influence politicians - than by the politicians themselves. We live in a high technology society, and make a lot of policy based on scientific R&D. There is plenty of populist rhetoric, but aside from that the Western world is largely run by scientists and technologists, for better or worse. Nuclear power will never not be on the table as long as humans have nuclear capabilities.
This script sometimes break the normal flow of interactive type pages, so I don't think it is that applicable to all pages. Great thinking though!
No, I'm in Costa Rica
Can you share a little more (anecdote) about what this means to you? <<As someone who grew up on shitty side of that research>>

Was your dad mostly absent, over-working, or what? Or emotionally invisible?
> XML is the future

That kinda happened, just not in the way everyone thought.

In 2023, JavaScript XML is the most popular way to develop web applications, and a common choice for mobile and desktop applications.

---

EDIT: JSX/React/React Native, in case that wasn't clear.
Is there really a difference between a multimodal vs a text LLM + stable diffusion?
1. Pooling is trivial to setup with servers. In fact, pretty much all clients like Knex and Prisma does connection pooling by default without an external dedicated server.

2, 3. The promise is that serverless APIs can be deployed on the edge for improved latency. The edge does not matter if your data is centralized. So you're adding complexity without the benefit of speed.

4. One of the most important aspects of any web app is load speed. Sure, you can say that serverless is better for scaling but who cares if your web pages are randomly adding 3-5 seconds to the loading time.

5. Try pointing your mobile app to Vercel's serverless APIs that are built inside Next.js. Makes no sense.

6. The most common way people use serverless for webapps is through Vercel's FaaS or some other similar FaaS. That's what I'm focusing on. Not confused. No, FaaS does not have more predictable pricing than servers.

7. It is. I just outlined why it is. Even if you want a simple cron job or a simple persistent queue, you can't do it with serverless functions.

8. You're building your entire stack on a FaaS like Vercel with Next.js. It's not as easy to switch hosts like using Docker. I don't know if you were doing development during the Zeit V1 days but one of the main criticisms of Vercel and newer versions of Next.js is now it makes it hard to switch hosts. Whereas, being able to switch hosts easily is default in a docker setup.
this was also 2 years ago, at the peak of the madness. These days it's far less likely to get that kind of money.
There are huge barriers to entry. A marginal barrel of oil might “cost” $1 coming out of the ground. If you use 50 barrels refining it and getting it to market, you can still make a profit if that barrel costs the end user $51.
He died in US prison because he was committing large scale fraud, specifically by claiming to be selling a miracle cure for cancer that didn't actually work.

For those curious, the miracle cure was sitting inside a special magic box he claimed would do something with your "orgone energy", which was like that orgasm/organism joke but posited as a real thing his device could help you with.
Not just similarity. It also includes all other possible relationships if you want, such as order, connectivity, etc.
How the Moon Is Making the Days Longer Each Year
I highly recommend I Don’t Want To Talk About It by Terry Real or The Will To Change by bell hooks (which extensively cites the former) on this topic. We don’t talk enough about the harm patriarchy inflicts on boys and men through emotional neglect and detachment.
While having support for Lightroom proprietary format and edits would be a nice way for existing photographers that are vendor locked into Adobes software it is a Herculean effort for very little real benefit. The photographers that were lulled into "live lossless edits" with (the free for ever beta of) Lightroom already made the choice to be hamstrung by and having their edit being locked into Adobes format. They should accept the loss and render exported versions of their edited images. It is a fact that XML sidecar edits are not portable or suitable for archiving.
Even coyotes help control deer populations.
I spent my recess in the school library reading Tintin and Asterix!
Dang! I should of mentioned those in my comment.
Not a single word on bureaucracy… the single driving cost issue is the lack of industry of scale and vastly different regulations in each state.

Learning how to do nuclear means learning how the french did it in the 70s. You need knowledge sharing and expertise in the construction of these things to achieve nuclear within time and budget.

The first reactor is always going to be a colossal failure because, but essential to know where the problems are.

But with so many nuclear startups I fear all investment will be dispersed into a range of different approaches, none of which will achieve what is promised. This will be the final nail in the coffin for western nuclear.
Multimodal can refer to a lot of different types of models, but feeding LLM text into stable diffusion definitely doesn’t count.

LLaVA is the first one that comes to my mind, it takes images and text as input and outputs text.

There’s an unreleased version of GPT4 that can do that same thing.
For a fine vocabulary, read 137 books
Broadband ISP Customer Satisfaction Ranked Second Worst, Above Only Gas Stations
My home nas and via zfs send the off site nas from my parents.
Especially if you take into account that humans have just arrived in the Far North. That was a quick march south...
Honestly, why bother about the wider world when this provides an excellent filter for those both principled enough to quit Twitter and competent enough to join Mastodon? Sure, you'll have a high false negative rate (i.e., some great folks won't join), but the people who do will probably be more interesting to you than the average person.
What do you mean by duress? Children are captive by their parents. But captive != duress.
> There is plenty of populist rhetoric, but aside from that the Western world is largely run by scientists and technologists, for better or worse.

Germany says hi
Liberation is generally not peaceful is it
All the trustifatians I knew in college were happy to ridicule other religions without knowing some of the crazy shit they were poseuring.
While I agree with your take about society, I disagree that boys have less space to be boys. Boys will be boys, no matter what the world does. There will never be a shortage of boys who want to throw rocks and jump in mud until their feet get stuck.
Considering how many embedded devices are in use, a lot of which are 8 bit microcontrollers with minimal RAM, designing systems that way would be irresponsible. There probably are some systems that don’t have an embedded use case that would (Eg. Encryption for live video) but not everyone is connecting to the internet on the newest iPhone.
I’m unsure why this would be compared with Actual Budget or CRDTs in the README.

The issue that CRDTs are solving isn’t simply getting the bytes from one device to another, it’s ensuring that conflicts are merged in a sane way, which this project doesn’t clearly address. Simply syncing a DB across multiple devices won’t help if your app isn’t designed to handle data conflicts.
> But a lot of it, I can admit, boils down to sheep shaving.

AKA Yak shaving[0], which I am... unashamedly fond of doing

>> There are yaks to shave all over the stack, and I go where the yaks are.
(quote is from my github readme)

> When you start figuring out how you'd implement codebase 2009 in stack 2023, and then actually doing it, that's golf. It's all good, it's educational, but it's downright immoral to sell that to a client and drag them through it.

I definitely agree that selling this to a client when you've told them you'll do the minimum to update the codebase is immoral, but if there is value in updating, then you should expose them that value.

For example -- moving a client to AWS might not make sense, but if they're maintaining on-prem infra and paying tons of money for an application that would actually cost less as a single ECS service (or App Runner, these days)... Then maybe you should upgrade their stack a little bit.

In the end it's your job as a consultant or an employee (if you're high level enough) to introduce change that will make the company better, if you see an opportunity.

Tech stacks crumble underneath their own weight, and if they're bad enough, become business risks. If it's humming along, easy to maintain, and isn't riddled with security holes, then great!

[0]: https://en.wikipedia.org/wiki/Yak_shaving
Well this was apparently an unusual situation. Everyone has been waiting politely for hours, quite a few passengers and staff seemed relieved to have someone speak up and demand some relief, and when the flight left around the time of their final estimated delay it was calm and full of the same people I’d seen for hours preceding.

A lot of the folks around me seemed to resonate with “you can’t hold us here indefinitely” and the staff response was very agreeable. I don’t like that I expressed it angrily, but I don’t think anyone in this scenario took it as vinegar, just saying what many people had already been thinking for hours already.
To fuel society's never-ending addiction to unsustainable exponential growth and efficiency.
I prefer $PROJ/config/ (or even /settings/) -- this is self-explanatory. $PROJ/.meta is not a standard practice and would be confusing (what's so meta?). Why use dotfile naming? That's just old practice that no longer needs to be used. We're not hiding anything (and why should we?). Configurations should never be hidden.

I feel like the main reason why dotfiles exist is because they typically got put in your $HOME and that would just litter your file manager's view.
This is a pretty low-grade reactionary ism. Usually without saying so directly the effort seems to be to lambast, to shame & berate. But it does spend a good three paragraphs catastophizing & melting down over Javascript & left-pad.

> We were told to stay on top of the most modern ecosystem, and by that I mean dealing with compatibility being broken every two months.

Some people just want to be ornery & cantankerous.

The article can be not wrong about saying there's too much hype, marketing, and rationalizing that we know real answers. Fools with certainty are everywhere. But it can still be wrong & have a jerk attitude. That we still have to figure things out & can be wrong or overadopt is not some horrible flaw. It doesn't mean we can skewer all these ideas & crap on them like this cavalcade of schlock.

So many of these various ideas do keep reoccurring, keep having real use. XML is reborn as jsonld which has some great uses. Isomorphic JS is alive & well in the new server side react craze. GRPC and Kubernetes and dozens of these other techs provide a normative baseline that let many teams work together where before we had anarchy & disorder.

There's some good messages & ideas here. We do need to iterate & refine & assess value. But also this is a conservative paean. A back to the land, just simple code ideology that is so appealing, that let's folks look down their nose & reject assessing technology fairly, that doesn't allow for valid complexity. Rakishly anti-elitist, thinking itself better for being such a smart source of truth only because it can smash other works so effectively. Be more liberal & open minded, not so fixed: accept that most of these things have some really good morsels or kernels that have value

Modern software is a couple decades old. Of course we are still refining & learning. Most of the things here have provided real value & informed where we go next, happened for real reasons. Some will fade, but many of the ideas will reoccur, will be better more creatively worked in or worked together in more cohesive wholes. This is a great amazing process, we happening live, in a young industry. Absolutely, beware of hype & bandwagons & marketing, of anyone who would tell you this is the way. For we don't know, and we have a long road ahead with many unexpected turns to figure out where computing's truest values lie. Stay young, stay hungry, and stay a bit foolish.
> Maybe, as a culture, we should emphasize MORE the health of the family, of the duty and honor it brings to raise kids and less on the "perfect" romantic relationships of the parents?

That ship has sailed. We live in a culture that not only has doubled down on the idea that the happiness/romance of the marriage is far more important than children, but even tells us that the marriage itself must dissolve when unhappy or this will do damage to those kids.

Imagine going to work and telling a coworker that your marriage is a disaster, but that you and your wife are considering staying together for the sake of your kids. What would your coworkers say? Do any of us know anyone that we believe might tell us "hey, that's a good idea, and I hope it works out that way for you"?

It shows us where our priorities as a society and culture lie.

Even if someone could intellectually admit that this assertion of mine was correct, it has inconvenient implications. The larger culture war around us relies on the idea that children simply aren't important to a marriage.
FWIW, after using serverless technologies in both AWS and GCP for years, I think the cloud vendors have largely fixed most of the issues you're complaining about. Few examples:

1. Amazon provides things like RDS Proxy, which is essentially a hosted version of pgbouncer, and Aurora, essentially a "serverless postgres" - no need to manage your own server for connection pooling.

2. Cloud vendors have largely fixed the cold start times through a variety of means like min scaling of 1, warming requests, and functions that can process many requests simultaneously.

3. I don't get your point about not being able to share an API between web and mobile. I do this all the time.

4. When it comes to vendor lock-in, GCP for example offers Cloud Run, which will essentially just spin up any Docker container you give to it.

Managing your own servers can have a huge cost, and this can be an especially large cost for a small team. For example, does your business have any SOC 2 or other compliance requirements? Being on serverless as opposed to being on, say, your own EC2 instances, means a huge amount of work (e.g. ensuring servers are always patched, ensuring they are configured securely, ensuring you have permissions configured correctly, etc.) can be offloaded to the cloud provider, who is frankly much more likely to do it correctly than a small startup team.

If anything, I think GCP's CloudRun is awesome and the real future of serverless. In my mind it has most of the benefits of something like kubernetes with about 1/50th of the complexity.
I don't think that I have there something worth transferring, but I just wanted to check and close the account. But I know people that have a lot of their life savings there, and that is why I shared this situation. How it can be trusted if they can even let transfer the funds out or give a proper explanation?
This post seems unnecessarily harsh.

would require women to choose better mates

Or: Men should pay and do their fair share?

Then:

How many women are out there with three kids by three different fathers?

Let's turn that around:

How many men are out there with three kids by three different mothers?

Sadly, a lot. And few of them are pulling their weight in term of parenting and financial support. I'm not talking about the Elon Musks of the world.

Custody laws typically place all the power in the hands of the mother

Multiple other posters have noted this is highly location dependent. This may have been true in many places around the highly developed world in the 1990s, but no longer.

most mothers are fine with the father having minimal contact

Ridiculous. Most mothers would like the father to much more involved. Divorce or single parenthood is hard enough.
Thread: “BLADE RUNNER was released 41 years ago today”
You can get some of properties you describe with the behavior most people would want via a combination of anycast, some route exchange protocol (probably BGP), and ECMP.
It's easy to just mark XML off as one of the many fads in tech given how many there are.

But I think it's much more worthwile to dive into the particulars of why it failed. While they're all fads, some of them share commonalities that, in hindsight, I think we can say were major catylsts to their downfall.

With XML, it failed because something like JSON was much simpler. Time and time again I see people saying that json+comments would be the ideal format. Time and time again we see that people prefer simple solutions that they can get jump into easily. Maybe certain problems don't require solutions with those traits, but anything with sharing data among a diverse group of consumers does.

The XML ecosystem with things like XSLT, Xquery,etc, were elegant, but also overengineered and clunky. I would even say that markup itself with closing tags were more annoying than just closing brackets.

Software is still so young... I think it's good that we tried and learned something from it in the short term. Maybe one day we'll get a proper standard with all the right data types that becomes the defacto solution that people learn it even if it's more complicated.
Show HN: Free PDF Watermarking and Compression
Sorry that’s a valid point, my point is that I’d like to not have my data sold in the first place,
Believe it or not, I'm going through my third read-through of his entire works right now (yes, even Cratylus).

But the question still stands: What is the job?
Well, turns out you don't really need large antlers either, but the deer just won't listen.