skysight-inc/HackerNews huggingface dataset:
Great question. Read the answers but remember that it's wildly different for everybody. That said:

The life and death matters (sorry):

- Never shake your kid, ever

- Sudden infant death is partly genetic (not your risk/fault), but still: no toys, pillows, plush animals in the crib -> risk of suffocating

The luxury matters:

- Breastfeeding does make a difference. If you can manage, try to do it

- Don't worry. Whatever happens at any point, it's going to be very different soon. Your kid cries a lot / doesn't talk yet / is not dry yet? It will change soon and you'll forget that you even worried about it.

- Adding to before: Don't project into the future. What is now is not indicative of the future

- A lot of things are outside your control. Don't try to control them all, it only grinds you up

- Almost all your challenges are going to be emotional, not rational. Try to invest in empathy, care for all three of your family

- Music is magic. Sing for your kid. Don't worry, it doesn't know or care what good/bad singing is

- Body contact is magic. Hold your kid close to your skin as much as possible

- Some people think kids are inherently evil and need to be broken. Some people think kids are inherently good and need to be left to their own devices completely. Both are wrong: Kids need guidance but want respect.

- Take your kid seriously, always. Even as a toddler.

Obligatory medical stuff:

- The most frequent injuries are toddler fractures (careful with trampolines) and elbow subluxations. When you hold your kid's hand and they fall, try not to pull and twist the arm or the joint will pop out. If it does, don't worry, it doesn't hurt, but go see a doctor within a few hours to pop it back in. The longer you wait the harder it gets.

- If there's a fever and it's really tough, you can alternate ibuprofen and tylenol up to every 3 hours. Take care to use fractional doses by weight. Always have some sort of NSAID in your house.

That's a small selection. Maybe you won't encounter them, but maybe you will, and maybe they'll help.

Having a kid is a challenge, but it makes life much more.
Currying support is orthogonal to how function arguments work. Some languages (e.g. OCaml according to this question[1]) combine named parameters with currying, allowing partial application with any of the function's arguments.

[1] https://stackoverflow.com/questions/3015019/is-there-a-progr...
Hello. I am one of the maintainers. Sorry that we did not spend much time for aws-nuke lately.

Feel free to ask any questions.
Do we know whether that x86 backward compatibility is all that problematic? If I’m not mistaken, it is only used as a “public API” even in current CPUs, and on a microcode level it doesn’t have as much relevance.
I don't think that the goal here is to show a fast and elegant sort, but rather to show that a sorting algorithm that seems like it can't possibly work actually does. That is, probably no-one will learn from this article how to sort better, but hopefully people will learn from this article how to formally prove things (e.g., about sorting) better.
I'm a little amused - I really wouldn't have expected "get a puppie at the same time" as advice for someone who'll have their first child in two months. Particularly coming from somebody who who has been in that situation themselves. But I never had kids, so what do I know!
You sure it was this algorithm and not Bubble Sort?

> algorithmic complexity isn’t everything

Yeah very true. Or at least hopefully everyone knows that complexity analysis only applies to large n, and small inputs can change everything. In console video games it was very common to avoid dynamic allocation and to use bubble sort on small arrays. Also extremely common to avoid a sort completely and just do a linear search on the (small) array while querying, that can end up being much faster than sorting and binary searching, especially when the total number of queries or the number of queries per frame is also low.
WayPipe fulfills the same need and in a modern context there's really no advantage to the way X does it.
Considering that no one with an apple M1 chip is gaming or training ML with it, I'm not even sure what it means that these are supposedly better. What are people even using the extra performance for? Keeping thousands of tabs open simultaneously?
Father of a 9-months old here. Here are two things I recently wrote to a friend who was in your position:

Choreography

I set up a nappy-change table that folds out on our bathroom wall. That was a bit of a coincidence but I am really happy that I put it there. It's the perfect spot with access to the sink, the washing machine and the nappy bin. It's worth thinking a bit about because you will be using it during the middle of the night, holding the baby with one hand and needing to throw out the diaper with the other, followed by cleaning up nasty stuff all over. And you will be doing this in a sleep deprived state, with a baby screaming into your ear, making it feel like a military stress test of sorts. The same applies to bottle routine -- if you are going to sterilize them, are they easy to get from there to drying to usage etc.

Stress

One thing that is at the same time super frustrating and a huge relief is that the stress keeps changing character. Every time you think you've found a routine, suddenly the trick that used to work for calming down now seems to do the opposite. But conversely, the thing that was the cause for tantrums is suddenly not a problem at all, and might even trigger smiles. I try to keep this in mind every time I do something for the 14th time that is really annoying.
Sometimes it's faster to implement certain features in another languages and deploy it as microservice instead of fighting your primary language/framework to do it. Deploying microservices in k8s is as easy as writing a single yaml file.
IMHO:

- Process: follow it in order when you want result X, all steps need to be completed, each time every time. Routine stuff.

- Runbook: follow it in order when X happens, some steps may not apply depending on the situation or you may need to adapt. Non-routine stuff.
China has their infamous five year plans and for 2025 they have a goal of suppying 70% of their own semiconductor demand.

So it is pretty much given that we will see high-end Chinese CPUs by then.
Especially people who might think they can get vacations cheaper through one weird trick.
I recently had to look into Go for an interview and the question you just made it's on a lot of people's minds however I'd say Go and Rust have different user cases so the answer, like always, it depends.

I'm unfamiliar with Rust, so I'm mostly going to address the little I know about Go. It's a great language if you want low memory consumption, concurrency and a fairly simple codebase - the language is minimalistic and C-like so it tries to shove complexity away. I'm someone who hasn't touched anything with pointers in ages and really loved it.
Docker, Kubernetes, Terraform and from what I've heard a lot of Google services are being developed in Go, think about what they have in common and if you have a similar use case or you specialize in backend and devops then GO for it.

However people are reporting that Rust is coming to the Linux kernel soon so it seems like a solid choice no matter what you pick.

I think I have a similar background to you and learning Go definitely made me a better programmer and it barely took any time.

(Self promotion ahead, skip to last paragraph) I even made an article[1] that's an introduction to Go where I talk about everything that seemed interesting to me and I follow up with a small project, it's meant for junior to mid level developers that want to start with Go or are undecided. Perhaps have a quick look (it's been well received and featured in Hashnode).

Overall I'd highly recommend learning Go, it was a breath of fresh air for me after working mostly with Node and Spring Boot. If I had to make a backend system, depending on the requirements, Go would definitely be a top choice for me.

---

[1]https://bognov.tech/introduction-to-golang-build-a-mini-twit...
The fact that this can be solved using LiDAR, just seems irresponsible to not
I guess to pay devil's advocate here the question you need to be asking is if it would still be worth it if a loved one was driving your Tesla and they crashed because your Tesla drove them into a train.

Even if Tesla Autopilot was significantly safer than a human driver I know I would still struggle knowing a love one died because the AI in my car decide to make a really stupid (albeit unlikely) decision. Right or wrong, human error is something we've always tolerated in society. If you're using a power tool and injure yourself, so long as there is nothing that can be reasonably done to make that tool safer, it's on you. But if once in a blue moon the tool malfunctions and injures you, that is something we don't tolerate.

It seems Autopilot at the moment exists in this in-between place where the driver assumes full responsibility so all situations are considered human error even if the AI is clearly malfunctioning. The more advanced autopilot gets the more we're going to have to question whether it's reasonable for the driver to expect autopilot to malfunction and take full responsibility for their car's actions.
You both might enjoy an Australian TV series called "Curiosity Show".

It is science / technology focused and aimed at kids around your daughters age.

They explain a lot of fun sciencey things, puzzles and magic tricks that can be made at home from very easy to find parts.

The YT channel has over 1000 short videos : https://youtube.com/c/CuriosityShow

It was made in the 70s and 80s yet much is still totally relevant today. Even the occasional thing that is out of date might be a fun history discussion.
You are probally the exception.

A guy I know said the tech is so good you let your guard down.

He said there are days on 101 around 4:30 when he puts his sunglasses on and closes his eyes. He knows he taking a calculated risk. He's in bumper to bumper traffic.

He also said their were times he let the car drive home, with one eye open because he was tired.

With tech that good, I can see where drivers let their guard down compared to a guy in a old truck with a clutch. A vehicle he knows inside and out. A vehicle that needs his constant attention because of the sketchy alignment done years ago. Plus--he just can't afford a fender bender, or worse an ever increasing frantic fine. Hell--the stress of the old car might keep him more alert? Kinda like being in the woods when you know it's your wits, or a bear might tear you apart?
Related: https://news.ycombinator.com/item?id=31932250
I have had several clip+ses over the year, and the one thing that died every time was the onboard flash (which prevents the player from booting at all). I resurrected my last one where it was only corrupted and not dead, but I did not have other issues otherwise.

Now I am using an hiby R3, which is quite clunkier, but allows me to choose between microsd storage and streaming from the phone in high quality, while also having 2.5mm balanced IEMs (kind of a gimmick, but I like their sound a lot).

edit: and of course being able to finally ditch USB-mini is great.
This is so ridiculous. A Zoom background does not "make a space your own." I feel like people who write this crap never played Second Life. They forget that all of this has been tried and failed! Big name brands spent millions to create "land" in the SL metaverse and it was all a waste. It has no value.
I think learning to "think with your hands" is not a recognized academic skill, but yet there's something real about it.

If at all possible, teach her to ride a bike and to actually be able to get around on one if your locale is suitable for it.
is, not was.
I don’t see why the distinction would matter to the people it should matter the most to, Apple’s customers.
All deck and floor screws are also Robertson in my part of Canada. I've seen drywall screws in both Robertson and Philips however.
As a company it made sense to develop their own desktop experience instead of relying on the default experience provided by Gnome, since the majority of developers in control of Gnome are Redhat employee or ex-employee or affiliated to Redhat in some way, and Redhat is their main competitor.
One thing about this video that caught my attention: around 14:40, Tesla is in the "forward" lane, but it tries to make a left turn. While I agree that this is against the rules, my experience with driving around a big city is: half of the human drivers would try to do the same, if they accidentally ended up in the wrong lane. So, if Tesla is using data captured while human is driving, can it pick up bad habits as well ?
Just the other day I updated Adobe CC and it prompted me to install yet another daemon to check for original Adobe software.
I used a Comma 3 (somewhat close to FSD, just simpler) and I found that it allows to you look forward in time more then you normally would. Normally you might be looking at the first 50ft for issues, now I find I'm able to expand out to 200ft and look around more for traffic.
Terrible article. It’s basically a negative yelp review masqueraded as some sort of financial analysis. He’s essentially a pissed off ex-customer that on one hand complains that they don’t pay the drivers enough, but also complains that the service is now too expensive. The article is utter garbage.

If you look at Uber’s drop in valuation, it’s commensurate with the drop in all tech companies. In fact, the article is seemingly singing the praises of DoorDash but Uber is down roughly 50% since Nov 2022 but DoorDash is down 75%.

And there’s nothing new that this article brings. Same old “Uber shouldn’t exist” meanwhile it’s set to become profitable.
>>Their skill lies entirely in breaking laws in a way that allows them to make more money than the fines they pay.

Almost like AirBnB's model.
5 lessons I learnt after coding for 10 years
It's adobe. By the time we understand it, it will be cancelled.
The Boeing 787: Broken Dreams – Al Jazeera Investigations (2014)
https://xkcd.com/1053/

Today is a good day then!

There is, for lack of a better term, "folk knowledge" and technique even for simple tools that someone has to explain or demonstrate. I've been lucky and had people in my family pass their experience on to me but I've also made a lot (a lot a lot) of mistakes ruining things and breaking tools.
Sure, but would you go as far to claim that X phone is so much better in battery, Y has no chance of catching up, when X just put a twice as big battery in their phone?

Like we just don’t know how much node size alone matters in the picture (or in the analogy, whether the improvement is only due to the bigger capacity battery vs better energy management at other places)
You would sue because there's a sign that says "win this car" and nobody will win that car. As I said, it will get thrown out, but if a few people would do that, it wouldn't be worth the mall's time to deal with them.
"being unemployed" could also be a euphemism for "i sold my startup for $100s of millions"
> We ended up porting everything to k8's. That was a long & arduous process but it gave us total flexibility at significant cost savings. The benefits were great, but not everyone has access to the engineers/skillset needed to be successful with k8's.

I think the argument from most people advocating against using k8s from the get go isn't so much that you'll never need it, but more that it's better to pay this cost later when you have a demonstrated problem that needs to be solved, even if it's a bit more expensive (and I would bet that the total time expenditure isn't really all that much more moving to k8s later, it's just in one chunk instead of spread over your history).

By deferring the cost of building more complex infrastructure:

- You can use those resources to advance your product (arguably some companies that have hit a wall with PaaS vendors may never have gotten to the point where they outgrew those vendors if they spent more of their time on infrastructure vs. company value)
- You'll have a better idea of what you'll need and where your scaling hotspots are going to be if you've already encountered them. Building infrastructure that allows for flexibility in a few key areas is infinitely easier than building infrastructure that can scale in every way imaginable.
- You can potentially take advantage of new technologies if you defer the decision to when you need it. It would be silly to assume k8s is the final word. If you wait a few years, things will have evolved and you gain the advantage of using those few years of advancement rather than cementing a choice early on.
Which line has the Killswitch?
I remember I heard about Adobe moving into the CMS business in 1998 or 1999.
I'm glad they finally got around doing it . . . ;-)
> After the first main loop, the first item will be the biggest item in the list.

> The inner loop, as it always starts from 1 again will gradually replace the bigger items with smaller items, and so on.

I think the "and so on" is the point. To put it more precisely, I think that anyone (with a suitable familiarity with the tools) can prove formally that "after the first main loop, the first item will be the biggest item in the list"; but I think that it might take a bit more work to prove the "and so on" in a way that satisfies a formal prover.

(As to the intuition—I can buy that the "and so on" part is reasonably intuitive, but only at a level of intuition that can also believe wrong things. For example, just always replacing bigger items with smaller items doesn't guarantee you'll get a sorted list!)
There are no changing tables in the men’s restroom. Well, sometimes there are, but I can’t tell you how awful they are. Quite filthy and often in questionable mechanical shape… just keep telling your wife this. Have your fellow fathers tell their wives this.
Ask HN: Thoughts on free (no $) but closed software
What is your opinion about software that has no fees but isn't open source either, in terms of adoption? Suppose its shown to be very robust, would you use it in commercial usecases if its MIT licensed? How about non commercial but "critical" usecases like part of personal tool set (where your output might or might not be part of larger professional work)? I know I haven't specified the type of software, just wanted to abstract a potentially distracting info, but would your decision depend on it?
+1 ... rockbox'ed sansa clip+ is the best, except for one thing: browsing. In every other way, it beats all the other options i've seen.
Of course. It's not a seismic shift; it has some advantages in some dimensions.
I agree. This was just a write-up I promised the Twitter thread.

https://twitter.com/CiPHPerCoder/status/1538574970011500546
Oh man, they're not using lidar? I had no idea, that's crazy they're just putting cars on the road just cameras and AI. Jeez.
Correct. My mattress does not surveil my financial activity to the Government, or operate as an extension of law enforcement. Nor does it act as a form of power projection by being something to which access to it is centrally controlled for the sake of sanctions.
> The problem with this sort of argument is that it sets up a straw-man, without describing what you should do instead. Kubernetes could be better - of course - but what better approach is the author recommending to use instead?

The article explicitly advocates for high-level PaaS tools as an alternative to Kubernetes.
That is definitely true, but you can't reach any conclusion on the cost of the x86 baggage by comparing different process nodes. It has way too much influence on the end result to be ignored.

In a few months we will have both AMD and Apple on the same size, so we will finally get some idea of how the baggage compare then. It won't be a long situation, Apple will relatively soon after release a new on a smaller size again.
And yet, to me it sounds like NIH since it's a pretty standard stack; couldn't they just get something like google app engine and get all of that from day one? Because did any of those things mentioned result in a more successful company?
Had a feeling a reply like this was coming. Could you help me understand a bit more about why C would be a better place to start and how it’d lead to me growing my skills in core areas vs something like Rust or C++? I hear about C++ and can’t wrap my head around the benefits of going with something like C that has less features. I recognize I’m asking what will help me grow/learn and am saying, “why use this if x has more niceties?” but hopefully you can humor me. One thing I hear a lot is that Rust is the language for the next few decades, and while I’m sure C isn’t going anywhere, I’d be very curious to hear from someone with more experience about why C would be the way to go here. I’ll admit I’m intrigued as I used to have a professor in college who was a wizard and did everything in C — especially since a game I like from 2001 has an active modding community so long as you know C/ASM.

Explicitly: I’d be curious to know what the “cleaner strokes” are.

I also have never even heard of an FFI so thanks for starting my next research binge! I always thought two langs could interact once they’re both compiled to machine code, but I’m guessing i took that for granted and that C does that heavy lifting..
Worse: it's like driving with an alien driver. The teenage driver at least shares your language and some "human" cognitive patterns with you. You may communicate with it, you may receive its feedback, and you may even understand when he struggles with something so that you pay more attention to correct him (i.e. because it's highly likely he struggles at the same places you do)

No such luck with this ridiculous software. An incoming train that any human (with normal sight) would have no problems to detect? The car drives right into it. You literally have to pay full attention during even the simplest of situations because there is no way to understand how this piece of software actually thinks, much less to predict how it will misbehave.

Today it's an incoming train that's painted white, tomorrow is a cricket on the road that causes it swerve onto oncoming traffic, or a small paint chip on a traffic sign that causes the OCR to read "speed limit 200" instead of 20.
That was really good, thanks for sharing. Answered my questions on the deliberateness of all the design decisions I noticed and even the ones I didn't... Which is probably what makes for a good design.
Multiple [dupes] https://news.ycombinator.com/from?site=sfconservancy.org

Parent has linked the heavily discussed one
Yes. People bandying about "legacy x86" instructions miss this often. This isn't much different, conceptually, from Apple's Rosetta, except it's provided in microcode automatically rather than a discrete transform you need to run once and cache. This is very convenient for broad x86 backwards compatibility (e.g. I can run a Java 1.4 JVM and StarOffice or a libc.so.5 to play Unreal Tournament 2004 just fine on my 5900x). Can I run x86 apps, even ones from the last couple years on an M1 with no questions asked? Well, we abandoned local dockerized development at work because Docker for Mac's qemu couldn't hook into Rosetta and qemu alone couldn't handle JIT'd instructions from a jvm11[0]. Maybe that changes with the new MacOS version and the next version of Rosetta (there seems to be a Rosetta that works like qemu's binfmt_misc translators for Linux), but it's been missing for 2 years so far and caused me to do a bunch of work on remote dev capabilities in the meantime.

[0] Let me stop you right there before you suggest I recompile 15 years of operating systems, third party toolchains, and internal tools for ARM and then rebuild every intermediate container just so we can work around Rosetta shipping without necessary features. I know that you can ship a whole parallel stack of containers with ARM but that's not feasible in the slightest for anything but the most trivial use cases or entirely greenfield projects.