skysight-inc/HackerNews huggingface dataset:
Where does it explain/prove that "most of what you are doing" is being recorded. That's a really bold claim.

I understand that launching apps pings an apple server to check certificates (for example) but I've never heard much of anything more egregious than that.

The phrase "most of what you're doing" implies recording keystrokes, web browsing history + clicks (and so on).
I checked the math, they are correct.
More lies heheh:

> Atari secretly started a second company, Kee Games, with Bushnell’s next door neighbor, Joe Keenan, at the helm. “We took our number two engineer, our number two manufacturing guy, and every other game in our lineup, and gave it to Kee. We started Kee Games in August, and they were up and spinning by the November AMOA show (the big trade show in the games industry). Their goal was to pick up the rest of the distributors.”

> “We told the distributors that those bastards are stealing our games, and then the distributors would run off and grab the games. We would rag at our distributors’ meetings about [Kee] stealing our games—and stealing our employees no less.”

https://spectrum.ieee.org/atari-alumni-talk-about-the-tall-t...

Isn't that the inspiration for The Giant's competitor in Halt and Catch Fire tv show?
The number of hours per week wasn't even a factor in the original statement. You're trying to drag the conversation off on a tangent.
Well, golang.org does specifically call this out at the top:

> Built-in concurrency and a robust standard library

I think that the joy of Go's async-first design really makes sense most to people who have experienced the awful pains of colored async-await in other languages.
That's just it, they're not getting a "heads I win tails you lose" out of this injunction at all. And they will have to open their purse.

ThedaCare shot themselves in the foot by having to pay lawyers, legal fees, get new nurses, pay for any services they hire out of the new company to maintain their capacity, etc. which is going to cost a lot more than they could've gotten with the counter-offer. Meanwhile the workers still get to work for the new place at higher pay. They are not being enslaved at the current place according to the temporary injunction I read. The new place merely has to help the old one provide medical services temporarily (for which they can, and certainly will demand compensation).

They absolutely should be firing the ThedaCare management, though. They really screwed this one up badly.

The judge seems to be just trying to make sure that the patients of ThedaCare don't suffer for the mistakes of the hospital management. ThedaCare is putting themselves on the hook for plenty of extra costs with this stupidity, and they likely will have to pay significant costs over this for their failures in hiring nurses--and competent management.
That’s not necessarily true. Often, a lack of interdisciplinary engagement can result in easily in theories or debates lasting far longer than they should. In this case, the debate seems to have been confined to medievalists not military historians, and going by the way Wikipedia article it appears that once experimental archeologists weighed in, they were rather critical of the theory.

For a similar example from another field, observe the decades long contention in epidemiology about droplet sizes and viruses like the flu and Covid not being airborne, in contradiction to basic aerosol physics.
Mint a NFT off this comment. /s
We have child support but I assume by ridiculous arrangements they meant were don’t have uncapped child support and it’s also income based not earning potential based.

No getting trapped in a job you hate. No pretending it costs hundreds of thousands a year to raise a kid.
I have to hope that Streisand effect will be similar to the one for non-competes from Jimmy Johns.
It's not just aesthetic, it's practical, too. You can make larger changes that landlords frequently ban.
This is a terrible article.

The proposed bills are clearly directed at vetoing teaching of race and gender issues by manufacturing discontent. It’s not like republican lawmakers are trying to hide it - it was quite literally part of their 2020 agenda. The ACLU is not asking for _less_ transparency in schools, but _more_ transparency and accountability by lawmakers weaponising public opinion.

The case handled by the ACLU in Alabama is about constitutional rights and the separation of religion and state. It’s not remotely the same.
From one perspective Shell has the most to gain from this technology. They are being forced to go green. So that can happen in one of two ways.

1) They convert their entire operation to green energy sources and scrap all their current investments. Meaning a major shift in operations.

2) They capture their emissions in place and turn their emitting sources into neutral (or negative) sources. To be honest, the second is probably easier and cheaper. Remember, the problem isn't so much that we are producing carbon, it is that we are producing carbon and we're ending up with too much in the atmosphere. If we produce carbon and it doesn't end up in the atmosphere then we don't really have the same problem.
>Because it's adversarial. Your choice to use one OS makes it more difficult, in a tiny way, for me to use a different OS.

So I shouldn't be allowed to use a certain platform of my choice because you think this somehow impacts you?

Based on your logic how about you stop consuming water, oxygen, real-estate and food because it's making it more difficult for me, in a tiny way, to get those items.

>You will write software for that OS. You will convince others to use that OS. You will tell your boss to get computers with that OS installed

Please stop making false claims about me. You don't know me buddy.
This sounds like a case of misguided expectations. I like the framework laptop, but it's still very early days and there are bound to be some growing pains along the way. This would be like getting upset that the pinephone, as cool as it is, doesn't work as well as newest iPhone. Of course it doesn't.

If you want a rock solid computer that "just works", but also respects your privacy, just buy a used Thinkpad and throw something like Manjaro on it. You can set up your entire dev environment in an afternoon with zero hardware issues. You can get an excellent used Thinkpad for under $1,000 very easily on eBay.
Reminds me of times when several of us would be standing outside a classroom door, assuming someone else had tried the door and found it to be locked.
I don't think a modern serf would have any of those things, because a society in which 90% of the available human capital is devoted to manual agriculture does not have the available labor to produce any of those things. At least, not for anyone other than the 10% of "lords".
> Three years later, Sarnecka threw the Mount Olympus–themed rejection party in Vickers’s honor—Vickers had finished her Ph.D. in ancient Greek philosophy and was moving on from UC Irvine.

They seem to be doing OK.
Having compared the methods in my own kitchen, I'm also coming around to the idea that the reverse sear is a better method than sous vide, because I seem to get a better crust on the steak (likely because the steak is dryer than what I can remove from the s-v'd steak with paper towels). But, I find this only holds true for really nice cuts like filet mignon. If I want to cook a cheaper steak like a NY strip, I think the sous vide method produces a much more tender piece of meat, probably because I can cook it longer without overcooking it.
azinman2's belief that flat earthers' lives are unbalanced is also freedom of speech, and flat earthers' beliefs do not supersede the freedom of expression of their critics, either. End of story.
100%. I've done just about everything you can do to a steak, and for the past year or so my bulletproof standard method has simply been "set toaster oven to 250, cook steak for 20 minutes until it's 110-115, then take it out and sear it". It's better than the circulator steaks.
Take a look at https://github.com/Attumm/Maat

Maat is much faster then pydantic according to the benchmark of pydantic.
Poverty affords no nets. To be caught by family, your family has to be capable of catching.

Sometimes that's the case, but all to often your family breaks the net in an attempt to catch you and end up homeless as well.
Every time I think about this problem (whether it's clicking-drag to re-order, or click-and-swap as described here) I always wonder if there's some smart "box packing" algorithm that will just distribute the elements with some "suggestions" (x,y) about where they should fit and let the algorithm place everything.
I would love to see a demo to feel the UX. I'm not fond of drag and drop and really want to test the click and swap.
There is no definition of a fetus where it's totally equivalent with a child.

And I guess you don't have kids if you imagine attachment to a fetus is the same as to say, a 1 year old child.

Anyway, I don't want to discuss abortion, so feel free to monologue if you so wish.
Mounted infantry did not fight on horseback but rather traveled by horse and dismounted to fight on foot. They had access to horses but did not develop coordinated horse-mounted combat tactics or armament.

Edit: Wikipedia has a good overview if you Google the term. My guess is that proper horse mounted combat requires far more intensive and consistent training that could typically only be undertaken by a noble or knightly class with no other real responsibilities. Whereas anyone with access to a horse could fulfill their (rarely exercised) martial duties as infantry.
Nope, here are the lyrics:
https://genius.com/Loituma-ievan-polkka-lyrics

And since you asked for it: https://leekspin.com
What are the odds that's a non-bias, accurate retelling of the event? "Here I was, just working super duper extra hard..."
If you use the reflection package in Go, the dead code elimination optimization step does not run if you use reflect.Method to look up a method because you can use reflect to reach those methods and the linker preserves the possibility.

Unfortunately, almost every large client library has public methods AND references someone who calls the reflection method somewhere, so in many cases you get the full tree of dependencies.

It’s unfortunate because any one dependency can bring in reflect and trigger the behavior. It hurts large generated method libraries the most since you usually only use a small subset.

See https://go.dev/src/cmd/link/internal/ld/deadcode.go line 318
That is a very good point - I never thought of it that way. Old Nokia phones are indeed built incredibly well.

Perhaps and "build quality" and "premium feeling" need to be separated. I suspect I'm not the only one conflating the ideas.
What did that camera set you back (or did you get it some other way)? Their page only says "Call for pricing", which usually means it's going to be outside my hobby budget hah.
oh yea! great point, I forgot about that. I am using PiAware to handle the decoding so I do have an Enterprise Account. I will have to check if I can make API calls for free.
Are you sure you're on the right website?
Wrong bottle. It's all about A1 sauce.
If you lack expertise enough to say if a simple explanation works, you lack expertise in complex ones too, and should probably stop trying to guess what's right based on very weak signals. Which was my original point.
The thing is that the economy cannot go up and up forever. One of these guys will always be correct, and if you say something a couple of decades then you are bound to be right eventually.
Haven’t yet gone down the SV road myself. I intend to buy the equipment and start playing around some time this year.
> The native clients offer much better performance on every operating system.

Background blur uses significantly less CPU in Google Meet running as a chrome/chromium tab, than in native Zoom Linux client. Besides, Zoom Linux client also makes some arbitrary decision that my more powerful i7-3720QM is not qualified to have background blur enabled, while my less powerful i5-8250U is allowed to do so. Background blur works just fine with both CPUs in Google Meet.

From your POV, perhaps Zoom product/engineering is doing a good enough job. From my POV, what we have is a crappy Zoom Linux client and a half-arsed Zoom web client. And if corporate wants to give everyone Mac and Windows machines only, just so its highly paid engineers and highly paid product managers can share their screen over a Zoom session, who can argue with that logic?
I think SQLModel actually exists precisely so that you don't have to do that. According to [1]:

> That class Hero is a SQLModel model... But at the same time, it is a SQLAlchemy model... And at the same time, it is also a Pydantic model

[1] https://sqlmodel.tiangolo.com/#sqlalchemy-and-pydantic
1. Bonds generally aren't there for returns, but to manage risk. When rebalancing (±5%) they end up being a form of 'dry powder' to buy equities during down turns.

2. While they may dampen returns (but also dips), one has to examine how much risk is actually needed to meet financial goals. Sure, more money is generally better, but not necessarily at the cost of other factors.
Does the Sun Cause Earthquakes?
> It does depend on where in the US you are or how your company handles remote compensation.

Yes, if you go to work for Albertson’s instead of Google prepare to be surprised

But honestly that’s the point of the post. If you are a SWE in a low pay company realize that you can make $300k+ by switching companies

Can everyone earn that ? No
Can you? Maybe

Sometimes that is enough - motivated individuals will use the information
I've done the same tests with ribeyes and strips and, in a triangle test, you can't tell the difference between a circulator cook to 54c and a toaster oven reverse-sear cook to 45c (both followed by a hard sear). I really can't see much reason to circulate steaks anymore; there isn't even really a convenience win to it.
I have been using this Docker image on my Pi and it has been rock solid once you get it setup:
https://github.com/mikenye/docker-piaware
A short term, high dose prednisone treatment restored enough kidney function for my sister that she is no longer looking at a transplant or dialysis.

Bi-weekly, 5mg doses of prednisone to treat chronic pancreatitis have extended the life of one of my cats going on 5 years now, and greatly increased her quality of life in her senior age. The same dose occasionally treats another cats intermittent IBD that otherwise, before treatment, would eventually progress to triaditis and hospitalization.

Yes, it has side effects, and patients should be made aware of that. But acting like it's something that should never be given is ignorant at best. It is cheap, widely available, and is a first-line treatment for a number of conditions.
Nobody said you shouldn't be allowed. But it does impact other people, and those people are also allowed to comment on it, or even put social pressure on you.

I'm not going to respond to the sentences you added after I posted this comment, because I don't think they add very much.
From another essay by Scott Alexander:

> Suppose you have a target that is half red and half blue; you are aiming for red. You would have to be very very confident in your dart skills to say there is only a one in a million chance you will miss it. But if there is a target that is 999,999 millionths red, and 1 millionth blue, then you do not have to be at all good at darts to say confidently that there is only a one in a million chance you will miss the red area.

> Suppose a Christian says “Jesus might be God. And he might not be God. 50-50 chance. So you would have to be incredibly overconfident to say you’re sure he isn’t.” The atheist might respond “The target is full of all of these zillions of hypotheses – Jesus is God, Allah is God, Ahura Mazda is God, Vishnu is God, a random guy we’ve never heard of is God. You are taking a tiny tiny submillimeter-sized fraction of a huge blue target, painting it red, and saying that because there are two regions of the target, a blue region and a red region, you have equal chance of hitting either.” Eliezer Yudkowsky calls this “privileging the hypothesis”. [0]

> There’s a tougher case. Suppose the Christian says “Okay, I’m not sure about Jesus. But either there is a Hell, or there isn’t. Fifty fifty. Right?”

> I think the argument against this is that there are way more ways for there not to be Hell than there are for there to be Hell. If you take a bunch of atoms and shake them up, they usually end up as not-Hell, in much the same way as the creationists’ fabled tornado-going-through-a-junkyard usually ends up as not-a-Boeing-747. For there to be Hell you have to have some kind of mechanism for judging good vs. evil – which is a small part of the space of all mechanisms, let alone the space of all things – some mechanism for diverting the souls of the evil to a specific place, which same, some mechanism for punishing them – again same – et cetera. Most universes won’t have Hell unless you go through a lot of work to put one there. Therefore, Hell existing is only a very tiny part of the target. Making this argument correctly would require an in-depth explanation of formalizations of Occam’s Razor, which is outside the scope of this essay but which you can find on the LW Sequences.

[0] https://www.lesswrong.com/posts/X2AD2LgtKgkRNPj2a/privilegin...
One of the things she talks about is the problem of scientists trusting other scientists. I wonder whether trust is the right way to put it, or if a lot of the time it's that they're afraid to speak out against colleagues for fear of reprisal. So many of these domains are small enough that everybody knows everybody else, and bad blood can poison people's careers.
I feel the same way. I'd prefer to program an SQL database in SQL.

What I personally do these days is to write migrations as normal (sql files for the "up" and "down" steps), and then have a `go generate` step that creates a randomly-named database, applies each migrations, and dumps the schema into a file that gets checked in. A test assures that the generated content is up to date with the rest of the repository. This gives you 3 things:

1) PR reviewers can see what your migration does to the database in an easy-to-read diff. (A tiny bit of regexing needs to be done to make PostgreSQL dumps compatible between machines; it puts the OS name and the build time in there.)

2) You have the full database schema in an easy-to-read form. I open the SQL dump all the time to remind myself of what fields are named, what the default values are, etc.

3) Unit tests against the database are faster. Instead of creating a new database and applying 100s of migrations, you just apply one dump file. Takes milliseconds.

In general, I think that database migrations are fundamentally flawed. The database schema and the application should have a schema version that they expect, and rules for translating between versions. That way, you could upgrade your code to something that reads and writes "version 2", but understands "version 3", and then apply the database migration at your leisure, and update the code to start writing "version 3" records. But, nobody does this. They just cross their fingers and hope they don't have to roll back the migration. And honestly, I don't think I've ever had to roll back a migration, because they're so scary that you test it a billion times before it ever makes it to production. But, that testing-a-billion-times comes at the cost of writing new features, and the team that only tests it 999 million times no doubt has a horror story or two.
I don't think you or the replies to your comment are addressing the parent point. It's not a game where something is "allowed" or not. They are saying that they suspect most people would not be able to themselves demonstrate that the earth is round, and that their argumentation would end up relying on faith. Whether such reliance is "allowed" is irrelevant

(This made me think of a kind of inverse example that came up recently: I had made a point in an online discussion and offered an argument for it in my comment. Someone replied and said they looked up what I was talking about and didn't see anything about what I'd mentioned, and so didn't accept it. The disagreement was not about the merits of the argument, but that they couldn't find that argument anywhere, and so apparently instead of considering it, they just rejected it as invalid. I've seen more variations of that recently, the whole "citation needed" thing, where people think that an "authority" is automatically necessary vs just thinking about what they were told and deciding if it does or doesn't make sense)
In my experience, this sort of thing breaks down when you have a large production database that requires carefully crafted migrations to avoid affecting the existing system and taking too many locks.

For example, with Postgres some indexes have to be performed with "CREATE INDEX CONCURRENTLY" or "DROP INDEX CONCURRENTLY", which cannot be done inside a transaction. (Also, a "CREATE INDEX" like this can fail halfway and leave behind an invalid index that must be manually deleted.) Whether this must be done with "CONCURRENTLY" or not isn't something the tool can know.

In some cases, a change must done in multiple steps. For example, if you change a column from "NULL" to "NOT NULL", you have to provide a default value. Updating the database with a default value can in fact be a huge operation that might even have to be done in multiple stages to avoid locking rows for too long. There's no way to easily express this in a DSL. M

Then there's the database support. A tooo like this needs to support a huge range of features. Postgres has extensions (CREATE INDEX ... USING), special index operator classes, functional indexes, partitioning, and so on. I've seen many ORMs or SQL adapters (ActiveRecord/ARel, Squirrel, Goqu, Sequelize) try to be smart with how they let you build SQL from high-level code, but they all fail to cover all cases. (Recently I needed to do "ORDER BY CASE ... END" and was using Goqu, which has support for case expressions, but did not support sorting on them.)

So while a tool like this might be good when you're just starting out, for a "real" app you want to avoid this sort of automation, because the tool is almost certainly not going to be smart enough.

I'm a fan of non-magical tools that let me just write SQL migrations, like dbmate and Goose, because that gives me full control. Having a tool to magically figure out the diff isn't super helpful, because I really need to know the diff myself when writing the migration, in order to make it predictable. It's simply more convenient to specify the order yourself.
If you add a laser pointer, you effectively built a low cost anti aircraft weapon. Very cool
Then there is a huge problem with how we publish Science... Decades ago, sharing all these huge datasets would have been quite difficult if not uneconomical.
But nowadays there is no reason left for not publishing the data and hopefully get academic rewards for that...
I have seen huge amounts of data not being digitized and lost because of this ownership mentality...
Wsmoses/Enzyme: High-performance automatic differentiation of LLVM
I think it might depend on the period, but mounted infantry uses horses for travel but fights on foot, while cavalry fights mounted.
Oh! that is a great idea. I am already tracking the camera's azimuth and elevation so I could probably composite everything to togther.
As a side note, Andorra has a single telecommunications provider for the whole country.
When faced with this problem, I wound up using normal SQL migrations to set the DB state, sqlc to generate the SQL boilerplate (https://sqlc.dev/), and I wrote a little tool to generate the HTTP handler boilerplate for these tables.

Not all-in-one, but this approach has been really effective in a large codebase.
What is the utility of the project? Any use cases?