skysight-inc/HackerNews huggingface dataset:
Which is exactly the point! We tolerate war in the world because we tolerate smaller bad things. If we stop tolerating the smaller bad things, we can build a better society that no longer tolerates the really bad stuff.
I also find it ironic, that from the quote you posted it also sounds like: "no one can stalk you but us".
Depends if the attrition is people you wouldn't want working for you anyway. If not for business reasons, for human reasons.

The kind of backstabbing people to jump at the chance to make a grand-standing against a good employer and get a buyout bonus at a time the company is in the spotlight for BS reasons...
twitter for podcasts.. i think that angle could be huge.
Or Mazda Laputa, or Nissan Moco.
For any of this to be a valid arguement you're going to have to explain why places like Australia haven't imploded.

We have a decent minimum wage, social welfare, and hybrid socialised / private healthcare.

Increase wages and conditions gradually, businesses that can't innovate or charge more will fall by the wayside. That happens.
If so many people are leaving cities, they certainly aren’t leaving Boston given the tight supply and huge increases in prices. However our city is a lot more livable than SF and NYC, in my opinion.
I use a mac every day, but I firmly believe apple has completely dropped the ball with respect to using and interoperating with community software.

They should be sponsoring - officially - non-apple software on their platform because it will make their platform stronger and much more useful.

instead, I've seen:

- opensource.apple.com in decline

- other projects dropped or forgotten over the years (no gpl software after 2, xquartz pushed out to pasture, os support for python/etc very poor, many others...)

- focus on apple-specific languages (swift), frameworks and tools.

- decline in the ability for users to administer their own system

- limited ability for users to customize their system (although there are tools for sale, when they're not denied abilities and killed off)

they could do so much better.
Oh man, 100 thousand percent agreed with this. I'm not sure why this seems to have escaped the notice of a lot of the discussion here. If you suddenly are confronted with the fact that the company you worked for isn't what you thought it was, you're left with a pretty significant choice to make. If I had something like that happen to me, I wouldn't have needed the severance to bolt.
Imperialism is bunk and an artifact of a movement predicated on deception, so, there's that. I think the whole critical theory basically lets itself out on reasonable discourse.
> They let this fester - they were complicit in allowing this dumb-ass list to be circulated around the company for years, and when it became an issue, they refused to take any action on it.

After reading the article linked here in the comments a few times - "What really happened at BaseCamp" - I actually think that people who make a fuss about the list are dumb-ass. I mean, it's a list of funny names! Put mine on it, if you want! Anyone who takes offence to it, needs to chill out, forget about woke Pyramid of Hate and stop bothering other people

(for the record, pre-Nazi Germany had hate speech laws, and Hitler did write strong anti-semitic messages in his first book long before coming to power - this idea that "jokes will escalate to genocide" is pure woke fantasy & narrative that they use to promote their cause and bully other people into submission)
Any gap in labor law leads to exploitation by a business owner, anything that can lead to business advantage gets used.

Besides I found really distasteful when I was in my 20s being told that I didn't need the additional money because I didn't have a mortgage.

I don't think we need to rely on employer moralism, so Dickensian.
> Devices aren't built around discrete components anymore.

Huh. Thats news to me. A 0603 resistor is pretty much a discrete component to me. And if it is some other part of the assembly that breaks, the assembly it self is a discrete part (e.g. the microphone of your smartphone might be on a seperate flexboard that costs like 15 euros, which is a lot cheaper than buying a new one).

Yeah things got small. But that doesn't make things unfixable. Missing documentation, proprietary parts you cannot get, gluing in things in without reason, etc. are problems. The size is for the most part managable — and if it isn't, right to repair is also about you being able to go to some repair guy and having your stuff fixed instead of having some Apple employee tell you how you can only buy a new device, and loose all data because they won't even look at it properly. So in short this is about repairability in general.

And if you like to do it yourself, this is totally possible. Even my father managed to swap out that home button for his completely glued Samsung Galaxy S7 edge.

I teach (among other things) soldering at University. Most people can actually SMD solder if you show them how. A student who never soldered before swapped a usb port for an E-reader within an hour of me showing her.
What is the TLDR here?
'Never' is a strong word and doing a lot of work here, and I don't think the counterfactual can be proved one way or another.

I do think your comment here, with an unprovable statement about an immutable characteristic, stated with absolute certainty, would invite toxic political discussions.

Speaking with humility, and honestly trying to improve processes to yield better results, is the type of communication that I advocate for on teams I'm involved with.
>>I want to live in a world where people take responsibility everywhere and not shy away from topics meant to drive morality/politics forward.

This is a problem given that politics is not universally agreed upon and if we can not work together with different politics then we can not have a pluralist society, which increasingly seems impossible as both "sides" of this debate want to sort people with differing politics as "immoral"
Fair. Thanks for the reminder. Should I edit?
> Because one way to read the affair is that one person got upset that DHH as the manager didn't let that person pull a holocaust reference into a debate.

Well it's important to keep the context in mind here: "the holocaust reference" in this case was a chart from the Anti-Defamation League making the case that normalizing seemingly minor bad behavior makes it easier to go on to slightly worse behavior, which now doesn't seem that different from what you're already tolerating, and so on, and so on.

https://www.adl.org/sites/default/files/documents/pyramid-of...

This is not a terribly controversial assertion, in and of itself. Was it a stretch to use it in this context? You could definitely make that case. (I've long been fond of the quip, "If you use a slippery slope argument once, you'll start using it everywhere.")

But I would argue that when DHH acknowledged the list making fun of 'funny names' was a bad idea, apologized, and promised to shut it down, he had the choice to stop talking at that point. He didn't have to publicly chastise the employee who brought up the Pyramid of Hate. He took positive steps toward putting out this fire, but then threw on a match of his own -- and then doubled down on that, publicly calling out an employee who kept at it.

So, if we're talking about DHH-the-manager, I would suggest he maybe didn't do the bestest job of managing here. He could have said, "yes, we'll take down the list"; instead, he went with "yes, we'll take down the list, but don't you think you're being a drama queen about it."
Yes, git bisect.

But what does git bisect require to be useful?

A set of small atomic commits that make it easy to identify which line of code might be the origin of a very subtle bug you're looking for. Squash+merge will not provide you with such history, and make bisecting much less useful.
The U of V Engineering Faculty release is at

https://engineering.virginia.edu/news/2021/04/defenseless
Precisely. I'm not saying it's a bad thing, but it really doesn't mesh with the common bitcoin dogma of a virtual currency free of the ability of governments to interfere with it.

There's nothing stopping governments from shutting it down either. The US by itself could practically take it down alone (or any other crypto) by banning US banks from working with it, or from working with any non-US bank that that deals with bitcoin. No need for a 51% attack, no need to track electricity usage to locate potential miners, just a simple piece of legislation. Or even simpler, an executive order issuing the same ban, stating that bitcoin enables significant financial activity by terrorists & criminals.
Source for this: I used to work there.

> it's 50% better for the 2/3 of remaining employees.

Only in a very simplistic view.

Basecamp runs very lean, ~58 people before this incident, which for the number of customers (large) is a small amount.

Basecamp is going to need to replace ~100% of those people. That means hiring costs, costs for hiring the wrong people, and lack of productivity.

This will most likely cost them more money than they "save".
Edit: my question was answered here: https://news.ycombinator.com/item?id=26999020

Will the second-chance pool be added to the top bar?
bingo.

I think they realized the boss didn't respect them and wouldn't tolerate dissent, and that therefore they didn't respect the boss.

More than about "talking about politics at work".
I get the gist of your response and it certainly has some merit. But I would push back on the black or white presentation of your point - stock allocations certainly do matter, as you can easily confirm by playing with a few what-if scenarios in the past 12 months.

The high-level point of my parent comment was to not run away from market crashes, and instead to buy stocks that are a part of the collateral damage as opposed to those that are directly connected to the root cause of the sell-off. I think this strategy will work regardless of Fed's actions, within reason (eg: the financial system doesn't collapse altogether).
But you have said yourself it's 'bagel' money, it doesn't seem to be coherent to be defending both teenager after school jobs and teenagers in poverty.
Trying to log into a free shell to setup an eggdrop bot for my IRC channel. Had to tickle with a few TCL scripts as well for authenticating with the auth serv, and running a trivia bot in the channel. I was 13-14 years old.
One concern is that this makes teenage employees relatively more attractive and so increases the adult unemployment rate above what it would be with a uniform minimum wage.
Please, define what is a poverty wage, it is important. How much stuff one should afford to avoid being called poor.

What is the change of the model in case of the restaurant? I can see only one, automate the jobs away to reduce the costs, namely replace humans with robots.

But, if we consider these crappy jobs, what about people that are not qualified/able to do any more advanced jobs? People have vastly different cognitive abilities, it is not like we can teach everyone to code. It will not work.
It usually takes me years to find a job I want. That is why I'm always looking.
I dunno. I live in San Diego County. My house monitor has recorded 14 power outages during previous 11 months. Three were planned power cuts, two were due to high winds, and the remainder varied between 3 minutes to over 14 hours where SDG&E could offer no explanation. My neighbor's PV system measured 16 power outages during same period, so my system may have missed some 'glitches'.

I used to live in Anza Valley (Riverside County), where the local co-op lost power at least once per month.

California do not have reliable power. California utilities have been charged with various felonies. California utilities had previously been allowed, by the state government, to increase rates without requiring routine maintenance to power and gas infrastructure.
The Journal of Controversial Ideas Is Here
Terminologically, she didn't change gender, she transitioned. Her gender was female all along.
I think it'll become a case study of removing bad apples to produce brilliant work. Time will tell.
Whatever the intentions of any party the result is a OSS codebase splitting in two because they don't agree on the future of the project. That is exactly what is supposed to happen when that problem arises.
I agree to a large extent. I suppose it’s the voracity that some of these folks have over dictating other people’s words is a turn off.
It saddens me that the top comment here is asserting that all of these people, who were quite vocal on their social media channels, are lying.

I understand that this website is frequented by white supremacists and voting occurs thusly, but it says something about what a toxic community HN has curated that your baseless falsification is the top comment right now.

Shame on you for your fact-free posturing.

Shame on @dang for creating a toxic environment where a dumb speculation from a racist asshole is the top comment. I understand that you think it’s fine that it is, and you don’t care... but I still hope maybe someday you’ll become a decent person.
"Gender etiquette rules imposed by the trans community" sure is a way to frame basic respect for other human beings' dignity.
Circa 1990/1991 in 3rd grade we had a discussion on what programming was. Basically, the recipe/make a sandwich thing. The teacher played the dumb computer that took the instructions literally.

At the same time, in the 1980s and into the 1990s, math textbooks (in the US) often had BASIC listings at the end of chapters. I saw it, asked my dad how to type it into the computer, the rest was history.
A number of their employees were very vocal from the moment the post went live. They expressed how disappointed they are. You can literally hear the despair in two employees voice in a 90s podcast episode where they announce its hiatus.

Basecamp was a company built on reputation, and people joined on that and then the leaders just flushed that all away. Its not surprising that opinionated and outspoken people - the kind of people Basecamp courted - left.
The $500/hr figure is for a 1965 vintage electrostatic "tandem" accelerator with a 10MV max terminal voltage. We mostly make beams of protons, deuterons, and helium. A common use case is making tightly pulsed deuteron beam, and then hitting a gas target filled with deuterium to make neutrons. The outgoing neutrons will also be pulsed and have a well defined energy spectrum, which makes them great for doing experiments with neutrons. At these energies they are non-relativistic, so you can measure their energy through time-of-flight.

The more expensive facility is for making beams of gamma rays. It uses a free electron laser built into a ~1GeV electron storage ring to make ultraviolet laser light in a building-length laser cavity. The laser light then collides directly with an electron bunch and is scattered up to gamma ray energy. It then passes through the laser cavity mirror and on to the target rooms. This is a unique kind of facility because it produces gamma beams with high resolution. It's complimentary to bremstralung gamma beams (often made by shooting electrons directly into a piece of diamond to make them wiggle).

We typically use the gamma rays to study photonuclear reactions. Having an electromagnetic probe instead of another hadron hitting your target allows for alot of simplifications on the theory end and helps theorists to generate testable predictions with less uncertainties attached. It also probes slightly different physics.
Using squash-merge doesn't mean that you can't use long-lived feature branches if that's something that you need for whatever reason.

It just means that you basically have a multi-stage squash merge strategy. We do this from time to time. We only allow rebased squash-merge to master. When we do have a long-lived feature branch for something then this feature branch basically becomes the master for the individual ticket branches and at the end, the feature branch is rebased onto master and merged as a fast forward. It can result in 50 commits appearing on master all at once but each of those commits is an individual small commit just as if they had been done directly with master and the squash-merge strategy. We rebase this feature branch on master very regularly too (once per sprint actually) to keep up to date with master. We also try not to do any long lived feature branches in the first place.
Joke's on you, police don't do that anymore because blm decided holding non-violent criminals accountable is racist.
Getting people to pay for the privilege to wear a tag like a dog. I underestimated Apple's marketing department.
> My sense is that DHH is just a terrible boss.

Interesting. I've read everything posted officially about this by the two founders as it unfolded and I've been super impressed by how well-considered these new policies are. As someone with several decades of experience as an employee, manager and then founder in both large and smaller orgs, I felt these changes were in the best interests of all stakeholders. With the myriad potentially conflicting sensibilities in today's workplace the only fair and sustainable approach is to focus on the work and the customers.

As an employee, these policies would make me feel more respected and safe. I guess the fact that you see it as a sign of a "terrible boss" and I see it as a sign of enlightened leadership is an indication how divided perspectives on workplace etiquette currently are.
And of course, backend services aren't free and they're an ongoing cost. And apps rarely exist without backend services these days.

I much prefer an inexpensive subscription over ads or other approaches to revenue. Especially considering the consumer market has been sold on this idea that paying $10 for an app, even once, no matter how useful, is way too much money.
Yeah “Player Piano” was a good read. I don’t think I really 100% got it when I was 15 but it rings true today still. Might reread it - building a collection of novels for my son in case I die early. And that’s one (as well as “Breakfast of Champions” and “Slaughterhouse 5”) from KV he should read.
Not sure how they got the 3N space overhead for Fenwick trees. If you do it right then Fenwick trees won't have any space overhead (in fact the conversion from an array to a Fenwick tree can be done in place). Though I suppose they might suffer from catastrophic cancellation if you're not careful.
Which exchange were you withdrawing from?
I have always wondered, if it would be possible to make a small enough internal combustion engine so that you could just have it laying around in an apartment, sitting a few feet away from you, powering your appliances or charging a 12V or 24V battery. Dispensing the exhaust through a long tube. If all goes well, complete combustion of propane should yield CO2 instead of CO anyway. An additional enclosure shouldn't be an issue given the generator is small enough anyway.

The smallest propane powered generator I can find is basically still not much more silent or smaller than Honda EB2200.

Imagine a 350W generator that you can connect to a camping style propane tank that you use to charge some batteries.

I played around with setting up such a system with a Sterling engine but couldn't achieve high efficiency.

Surprised to see no YouTuber with the necessary machining skills and CNC equipment attempted to build a mini internal combustion engine / inverter generator.
Our work implemented a similar policy as well because politics was being brought up all the time and it was becoming a nuisance and some employees were basically harassing other employees.

I have no problem with people being activists in their private life but when you go to work, you have to work. You can't be an activist while at work and causing a hostile work environment for others.

I agree with the policy and think every company should do the same. Since the policy has been implemented, our work environment has improved significantly.
Fun fact, early IBM PCs from the 1980s would actually boot into ROM Microsoft BASIC if you didn't have a DOS floppy in the drive. See around the 5-minute mark in this video.

https://youtu.be/e08YtFdwWxE
https://bigthink.com/feeds/feed.rss

https://www.scotusblog.com/feed/

http://feeds.feedburner.com/brainpickings/rss

http://feeds.feedburner.com/68131

https://languagelog.ldc.upenn.edu/nll/?feed=rss2

https://narratively.com/feed/

http://feeds.feedburner.com/researchbuzz/main

I'm sure I have more...
A few thoughts while reading this:

In addition to a deeper understanding of engine manufacturing considerations than I even knew I cared to learn, this article helps me appreciate why people are into engine work.

The perfect tolerances and synchronization of these machines makes me a little ashamed to use the word "engineer" in my title of "software engineer". There is no real comparison of the quality of the result.

And then I skimmed the source, and it makes me think the author deserves that title. It also validates my belief in vanilla javascript.

edit: And later it occurs to me that Mr. Ciechanowski is a true craftsman of software; handmade and built to 1) Be beautiful (and informative), 2) last for years. (The open web standards are the ones that seem to stick around the longest, for better or for worse. (I'm ignorant of the shader world though))
Nothing is built with brick anymore. If you see a newer than 1940s brick house, its a stick frame (wood) with a layer of brick outside it for aesthetics. Also people associate brick with longevity, but as several of my friends in old ass brick row homes, their foundations are crumbling, and are usually in need of serious structural repair. Brick isnt bomb proof like people think it is. Its even more susceptible to long term stress from wind shear.
outrage culture is out of control all over. If it's happening through foreign enemies too that doesn't change the media coverage etc.
Yes, does look better, although looking on an iOS device, which may also have an effect. For example, the font.
Thank you for doing this. This is what I love about HN most - finding interesting content at otherwise hidden(for me) corners of the web.

I visited so many great blogs, that last year, I fell in love with blogging. I started on Twitter, then micro-blogging wasn't enough. So I wrote first article. To make it harder, I set the rule that I have to implement what I write about and make a video(s) about it. This way, I can avoid writing about things I don't understand and keep quality high enough. According to analytics, almost no one read it, but I love it anyway. I can't wait when 20, 30, 40 years from now I will re-read it.
How exactly can stalking protection work with apples claim that the system doesn't provide any outsider or apple themselves the ability to track your airtag?

Surely stalking protection is doing exactly that? Couldn't I take a modded/hacked iPhone and track somebody elses tag all day long from near the edge of UWB range?

Apples original paper [1] said the signals emitted contained no unique/trackable identifier except to the key-holder who could link together all the rolling keys. Yet that can never offer this stalking protection feature.

Have Apple dropped the privacy protections they had in mind to enable this anti-stalker feature?

[1]: https://www.wired.com/story/apple-find-my-cryptography-bluet...
It cannot be understated just how great the two leaders think they are. For the entirety of their career they've been literally telling everyone else they're running their company the wrong way.

They thought this was just another instance of them having a stroke of thoughtleadership brilliance and everyone else is wrong.
Much more common with pushrod engines, where the camshaft is situated close to the crankshaft; less so with overhead camshafts. Though I think some very high-revving sports and competition engines have gears driving overhead cams; IIRC the McLaren TAG F1 turbo V6 (by Porsche) back in the 1980s was one example.