skysight-inc/HackerNews huggingface dataset:
I rode in a waymo for the first time yesterday, and it was going the speed limit in downtown SF (20 MPH) while cars were speeding around us. It seems like in the future if all cars are driven by robots, traffic would go much slower, maybe to the detriment of intended capacity (the roads still felt really busy, I assume if all the cars were going 20 it would quickly jam to much less than that).
Another version of the same story:

https://existentialcomics.com/comic/189

See also: https://en.wikipedia.org/wiki/Hippasus#Irrational_numbers
Some leaks suggest that 15th gen is achieving these results while consuming 100W less than 14th, but I guess we best wait for some real tests
That sounds horrid.

Adding my own anecdote, I recently drove a rental Camry that had a speed limit detection system out in the middle of Alaska. It didn't do much if I went over, and I was surprised at how often it seemed to detect the right speed limit, but there were obvious errors, and no awareness of construction zones.

Makes me wonder if folks in the future will troll these systems with t-shirts and bumper stickers of 5, 10 km/h (or mph) signs. IIRC, simple flat images already confuse systems on board some Teslas.
Thyristors require you have at least one transformer operate at AC line frequency (50/60Hz). That costs a lot, since you need enough steel to store 20 milliseconds of your total power as a magnetic field. Thyristors are on-off devices (like most semiconductors when used for power conversion), but cannot turn off without zero current, which precludes a bunch of high frequency designs which are better for harmonics and weight-of-steel.

Overall, they were a popular choice in the 90's and 2010's, but I don't think we'll see any new designs installed with them.
This seems useful but honestly I think you guys are better off getting IP protection and licensing out the technology. This is a classic "feature not a product" and I don't see you competing against google/microsoft/huggingface in the model management space.
Some of the elements of this reminded me of a Daniel Suarez book, Daemon. I don’t want to call out which elements in particular because that might be too spoiler-y. Daemon is a super quick and fun read though.
Euphemisms are best changed frequently (2016)
With the end of affirmative action, MIT's incoming class better reflects merit
Whenever I hear the term "pig butchering scam" I struggle to distinguish it from the plain term "scam". Like, as far as I can tell it is simply called "pig butchering" because of the imagery of fattening a pig before slaughtering it. But I feel like in the past we would normally just call it a "long con", perhaps.

This sort of thing has existed for a long time, but this term makes it sound like something that is new or novel. Feels like the media is doing a bit of... "headline engineering", here.
It's a Python wrapper for a popular Java tool.
> If there had been anything wrong with the numbers, it was on HP to identify and act on that, he said

That does not sound like something an honest businessman would say, does it? "Hey, here's our numbers, if you believe them, it's your fault."

Of course, HP during and after Fiorina was an all-out shitshow, so there's that, too. Even they couldn't wipe out $8B of value that fast.
According to this article, it was partially raised, and that would be normal when going into a port:

https://www.theguardian.com/world/article/2024/aug/21/within...
There’s nothing stating the hospital made home leave.
Writer Calc Thunderbird T̶u̶x̶ ̶P̶a̶i̶n̶t̶ Impress
Unfortunately apple autocorrect doesn't know this and I didn't notice until it was too late to edit.
I've had that problem, especially in construction areas temporarily routing around the painted lines. Kinda scary when you feel the wheel veer you into oncoming traffic.
Trust is a continuum. After all, the existence of code reviews is merely a formalization of distrust :-)

I think the policies and culture around code review will vary based on the situation (new hire vs seasoned developer, large vs small team size, minor vs major code change, etc). However, I don't think I advocated anything that would be a bad idea even for high trust teams.

The possible exception would be that a code review "not be a request for permission". If you have structured it as a gatekeeping mechanism, simply ensure a "referee" or "tie breaker" to smooth/hasten the process. Even with high trust/functioning teams you'll occasionally get pointless ratholing in the middle of a review, and both the reviewer and the developer should have a way to cross that divide. And no, a "be mature and discuss it through" will not work every time.

As for stating concerns - when is that ever a bad idea? I didn't come up with it, BTW. I learned it from reading books on effective communications. It's a good rule to live for everyday conversation.
I don't care about any of that: I just want to be able to play video games without running Windows. I'm very happy with the status quo on amdgpu.
I'm tired of fixing customers' AI generated code
What is this shit? Website doesn't say much. And needs hours to load.
Why not use the AppImage or Flatpak version of Yuzu if you want stable libraries.

I don't even remember yuzu having non AppImage releases, if you used AUR you could have just rebuilt the package instead of complaining about manually trying to find the right libraries.

A "normal user" wouldn't be using Arch Linux , building their own packages. They would just use the AppImage or the Flatpak.
I'd be more likely to blame the sailplan of the yacht. 56m is a big boat, and the mast was something like 75m, and it was cutter rigged. That's a lot of mast, and you just know the jib and staysail were roller-furled, which means a lot of windage and quite a lot of it up high.

Not necessarily a problem, but bad weather has to be handled particularly carefully.

The lifting keel was definitely there so he could get his look-at-me boat closer into harbors.
There are many correct observations, but Python is owned by Microsoft, Instagram, RedHat and Bloomberg. Google fired the Python team this year, which makes it an attractive work place.
There are some popular videos making spheres using explosive hydroforming, which is quite fun, and much lower tech than explosively forming magnets to avoid the formation of marsenite (sp?).
Thanks for the link. Subscribed!
I wonder what the insider trading laws around this are. If I work for the Fed and am in charge of dumping a ton of BTC at a certain time, I can almost guarantee a price drop, and then likely a recovery some time thereafter. Short, buy, short, buy.
Funny framing of it, but that isn't necessarily how the median works. Consider, what are the median number of fingers on a person's hand? How many people have less than the median number of fingers? :D

Is a fair point that it could be more common than I'd expect. I remember being a teenage driver and we were quite bad. Would love to see data on this.
I think it could only do that in spans of code where interrupts are disabled and purely between values already in registers. CPU state feels like it's in your control, but it's not at all in your control, and even if it was, multiple processes might exist and memory is never in your control.
Chick-fil-A plans to launch streaming service with original shows
We’ve had nearly 30 tornados this year…in New York. One in downtown Buffalo. It’s been interesting
The "in" in "indignity" is silent.
Except it wasn't the same day. Chamberlain died on Saturday, and the yacht sunk on Monday.
The woman who hit Chamberlain stayed at the scene and is known to police. That's not a great strategy for getting away with murder.
Boulder-like 3D-printed homes will feature up to three floors
I like the way you argue.
Your politicans, like Malcolm Turnbull in 2017, believe that the laws of Australia trump the laws of Mathematics, in the context of trying to weaken strong encryption. In at least some areas, they need a better education.
you probably want Rye (as uv is too low-level for now), no?
While this is true for much of Texas. I happen to live in a city that still has a public operator. So we just get more generalized flatter rates. I haven't looked into the details of my plan closely in a while as a result though, so you might be right.

En masse though, it seems not ideal from a cost perspective the way things have been scheduled up until now. I'll give them the benefit of the doubt that it might be adjusted better in the future.
That you can be successful CEO of a bank for many years and still a complete idiot around financial investments or transactions... I'm not sure what it says about CEOs of banks.

> “He said, ‘Brian, I’ve got this money and it’s in cryptocurrency, and I need $12 million to help verify the funds.’

What?
but that'll be at runtime
One can be forced to mindlessly perform ridiculously constricting duties that have everything to do with limiting liability and nothing to do with outcomes, while also caring about babies.
> you can copy software rather easily, but you cannot copy a bridge

You can copy a bridge just as easily as you can copy software: just print another copy of the blueprints. Just change the header from the name of one project to another, and you're done with the engineering at that new site. What's that, the span length is different? The soil is different? The traffic patterns and weather patterns and political climate and regulations are different? Of course they are. And when you copy source code, the use case is different, the hardware is different, the database is different, the inputs are different, the client is different. Every engineering job is custom. Software and bridge. The two disciplines are not as different as you say.

Bridge engineering also undergoes an "agile" methodology as the plans are repeatedly changed during conversations with the client, discovery of new regulations, ground-truthing, etc. Remember: the outcome of engineering is plans, not a finished product.

You're talking about differences in constructing the thing, after the engineering is complete. That's largely irrelevant to the engineering cost.
Moving to a farm doesn't necessarily help:

https://www.agriculturedive.com/news/these-farmers-didnt-kno...

https://www.npr.org/2024/03/28/1241473455/pfas-forever-chemi...
It’s not necessarily fake. I do like helping people.
If you are in a place with very flat/straight roads, you can pass while seeing oncoming traffic. I don’t know how it is in Australia (who are known to have some of the flattest straightest roads on earth) but in Nebraska this is definitely feasible.
Depends on your experience level and willingness to tinker. The bad news is that in my experience, you always end up opening a terminal and fiddling with configuration files no matter what distribution you use. The good news is that if you are OK doing that, you don't actually need that much from your distribution other than the useful trick of keeping itself up to date.

Ubuntu is alright. But you trade off up to date software for stability. And the bi-annual upgrades to the latest LTS are a bit of a PITA and don't always go that smoothly. And you end up running older kernel and whatever else was current around the time they freeze their LTS version. So, for something that is supposed to be user friendly and stable, it actually ends up having a lot of issues and not being all that stable over time.

If you want to get the best possible experience with graphics, you basically need the latest kernels, drivers, fixes, etc. as soon as they get released. Ubuntu doesn't deliver that because you get stuck on either the yearly or LTS release.

These days I prefer rolling release style distributions. It's just less hassle in the end and not really less stable for me. The opposite actually in my experience. You could go with Debian testing, fedora, and a few other options. But I ended up using Manjaro which is based on arch linux. My reason is simple: the SteamDeck uses a distribution that is based on arch linux. I wanted to run steam on my laptop. So, I figured that using what Valve themselves seem to actively support and invest in makes a whole lot of sense. I've not been disappointed with this so far (three years and counting).

Installing games is easy. Getting things like Gnome, Steam, etc installed via pac is easy. And I can install whatever via snap, flatpak, or native arch packages. More importantly, everything stays up to date and fresh. After three years I have no need to reinstall my laptop because it's fine. Every once in a while I need to deal with some minor issues after some update for which the solution usually is a Google search away. But other than that, Manjaro has been rock solid for me. And besides, I've never used a Linux distribution in 30 years that didn't have that issue.
I wasn't interested in the rotation speed; more the high voltage - I know there are vacuum variable caps for high voltage work, but don't know what the current state of other dielectrics at a few kV is.
Farmers didn't know their land was contaminated with PFAS. Now they're suing
This was apparently a waterspout / tornado; seems like a challenge for any small watercraft. I can only imagine how the wind would have knocked it around.
I use a Mac for ref. Windows is fine.
> I might not always know why I’m being asked, but merely being asked is often good enough for me to come up with some hypotheses. If it’s not, there’s a good chance it’s a learning opportunity: maybe something is missing from my toolbelt, or perhaps some unintended consequence escaped my notice. Being prompted to think about those possibilities without bias may help me learn (or reinforce what I’ll learn) by putting me in a position to retrace my steps and look for other gaps in my understanding.

I'm not at all disagreeing that these things may happen, with emphasis on may. It can all be achieved by the code reviewer saying "Interesting approach. You could have solved it via X instead, which has these extra benefits. Was there a reason you picked Y over X?"

This is a 2-way conversation. In your paragraph above, you're not giving serious enough consideration that it may really be the reviewer who needs to learn something new, and therefore the conversation should reflect that symmetry.

I've often seen (yes, in low functioning teams), the following pattern:

Reviewer: Why did you solve the problem this way (X)?

Me: Because of (outline a simple reason).

Reviewer: But why not Y?

Me: Why Y?

Reviewer: (50% of the time does not give a good answer and merely insists Y is better because of some random article on the Internet).

Note that:

1. The reviewer can't articulate why his method is superior.

2. The developer had to put in a lot more effort in this exchange than the reviewer.

In a better functioning team, it goes like:

Reviewer: Why did you solve the problem this way (X)?

Me: It worked. Why do you ask?

Reviewer: Oh, I thought X would be better. (If I'm lucky he'll explain why).

Me: OK. Moving on...?

Reviewer: (Moves on or sticks to the topic but gives more context).

Both of these are "poor" interactions, compared to the reviewer simply stating up front what his concerns are.
I've known people to get a ticket in this exact scenario. Speeding is not allowed just to pass and will often times get you hit with a reckless driving charge, as well. Especially so if you go 10+ over the limit.

Now, if you mean someone that went less than 5 over the limit, I'm back in agreement with you. But, that is within the realm of speed that probably won't get you pulled over even when not passing?
And that is a positive.

But it's like saying, "here's an (expensive) pill that can help you stop smoking, but we're going to continue pushing you to buy cigarettes with every vending machine you pass and with every ad you see". Instead of removing cigarettes from all the vending machines, making them harder to get, and taxing them so they're more expensive and a new generation is less likely to get hooked on them.

The food system is fundamentally broken, but there's no incentive to fix it because that would mean a loss of corporate profits.
Bookmark? Bah! I've got my browsers trained to fill it in when I write "reg" in the address bar.
Raising rates, can only lower inflation if there isn't large excess cash. The rate raising was also quite a bit of a smoke screen because the money kept flowing via reverse repos. All that changed was who had access to it. The normal borrower can't get unlimited 1 second loads with a 24 hour settlement period.

Raising rates didn't lower housing prices, it just empowered cash buyers to become landlords.
> Any chance you could take a screenshot of what your seeing?

I don't think it's a rendering issue, but sure: https://postimg.cc/ygsNzMhX

I looked into the CSS and removing the "line-height:1.15" makes it massively more readable for me personally. I have no idea about any science of human perception but I think the font is too "dense" with that reduced line spacing. (It's hard to self-observe this but I believe my eyes are slipping off between lines. Character width might be a factor too.)

(To clarify, my issue is with the main text itself, not code blocks.)
Whether to use a branch or a conditional move isn’t really dependent on what the source is doing but how likely the branch is and its dependencies. Simplifying a bit, an explicit cmov is basically telling the computer that the condition is not easy to predict and to not bother. Modern processors will typically do the same analysis themselves and perform similarly on a branch with a slight overhead.
The point of RDF is to raise the problem to the greatest common divisor level of complexity - a hypermedia graph of arbitrary predicates about arbitrary objects.

OWL is a modeling language to describe ontologies, e.g. some constraints people have agreed to follow about how to structure the information they publish in graphs. It can also be considered an advanced schema language.

The idea of a bounded context in DDD is that it is not a good use of time (or indeed may not be feasible at all) to get a single ontology for an entire domain, so different subdomains may be unified by some concepts but have differing or overlapping concepts that they use internally. Two contexts know they are talking about a product called "New Shimmer", even if understands it as a floor wax and the other uses it as a dessert topping.

The two pillars of the semantic web are public data and machine understanding, which IMHO pushes strongly toward the (often unachievable) goal of a single kitchen-sink schema.
One thing I didn't get is if he wired the money to a bank account (and not a random cryptocurrency address), how could they not found the scammers who did this.
> In most (all?) states, he cannot be forcibly kept at the hospital unless he has a court order for a involuntary treatment plan.

That's… not how that works. The _only_ difference between a voluntary stay and an involuntary stay is whether you've demanded to be released yet.

https://slatestarcodex.com/2018/03/22/navigating-and-or-avoi...

“[…]

4. I am seeking inpatient treatment. How can I make sure that everyone knows I am there voluntarily, and that I don’t get shifted to involuntary status?

I want to be really clear on this: in your head, there might be a huge difference between voluntary and involuntary hospitalization. In your doctor’s head, and in the legal system, these are two very slightly different sets of paperwork with tiny differences between them.

It works like this, with slight variation from state to state: involuntary patients are usually in the hospital for a few days while the doctors evaluate them. If at the end of those few days the doctors decide the patient is safe, they’ll discharge them. If, at the end of those few days, the doctors decide the patient is dangerous, the doctors will file for a hearing before a judge, which will take about a week. The patient will stay in the hospital for that week. 99% of the time the judge will side with the doctors, and the patient will stay until the doctors decide they are safe, usually another week or two.

Voluntary patients are technically allowed to leave whenever, but they have to do this by filing a form saying they want to. Once they file that form, their doctors may keep them in the hospital for a few more days while they decide whether they want to accept the form or challenge it. If they want to challenge it, they will file for a hearing before a judge, which will take about a week. The patient will stay in the hospital for that week. 99% of the time the judge will side with the doctors, and the patient will stay until the doctors decide they are safe, usually another week or two.

You may notice that in both cases, the doctors can keep the patient for a few days, plus however long it takes to have a hearing, plus however long the judge gives them after a hearing. So what’s the difference between voluntary and involuntary hospitalization? Pride, I guess, plus a small percent of cases where the doctors just shrug and say “whatever” when the voluntary patient tries to leave.
”””
Another easy thing to do is to avoid drinking bottled water:

https://www.npr.org/2024/01/10/1223730333/bottled-water-plas...
It's really cool! Feels like a timelapse video capture somehow.
Fair that I can't say you should never do so. I'd stand by it as a general safe rule, though? If the road is that long and straight, I'd imagine it also has a rather high base speed limit already.
"The attack appeared to impact business operations at the company's north Houston campus, as well as some global connectivity networks"

Understatement. I think this affects their core systems (heard through the grapevine, of course).
That might be true but only if we know their motives, which we usually don’t. One could argue that any driver isn’t passive aggressive because they are actively driving their vehicle. However part of the passive aggressive definition includes intentionally making mistakes in response to others demands. All of that being said, the difference is subtle and probably not worth arguing in this context.
I have the same concern about those proprietary dependencies, too.
Oh, so that's where "the Grauniad" comes from? I never knew, although I've occasionally used it myself. Fairly sure I first saw it on Usenet in the late '90s, from Charlie Stross.
I don’t really see the problem. If the books are accurate, the accounting treatments to GAAP, the financials audited, the diligence executed faithfully… well, yeah, if they buyer overpaid that seems like a poor business decision on the buyer’s part.
Probably for usage with [the now sold off] HP Records Manager.