skysight-inc/HackerNews huggingface dataset:
> Torvalds: [hot take that almost no one else agrees with]

Considering the popularity of vendoring and/or static linking dependencies, I'm not sure where you're getting the "almost no one else agrees with" from.

glibc's hostility towards static linking is arguably a substantial part of why musl has attracted so much interest. Static linking support is explicitly stated as one of musl's core tenets [0].

One can also argue the popularity of containers has in part been due to glibc's dynamic linking requirements, and containers have become the bloated "modern" version of static linked binaries, bundling all the dependencies without eliding all the dynamic linking overhead.

Torvalds is definitely not alone in this particular opinion.

[0] https://www.musl-libc.org/intro.html
I guess it did help you, since you are protected from Google's unpredictable moves.
Interestingly this intersects with https://news.ycombinator.com/item?id=26996972

Content cannot be safe if the tech necessary to deliver it is out of reach for independent creators.

Note that in the Roku thread Google is (IMHO) the good guy, for reasons unrelated to this thread's concern.
What Is Software?
https://pages-themes.github.io/cayman/
Cameo's Hiring Software Engineers
Cameo is a platform that allows users to receive personalized video messages from their favorite people (actors, musicians, celebrities, athletes, etc). And we are on a mission to create the most authentic fan experiences on earth!

We are an early stage startup, founded in 2017, and have been a remote first company since 2020, with employees located in over 33 different states. https://careers.cameo.com/

You will be designing, building and improving APIs, services, and systems across Cameo's engineering teams. Our technology stack is predominantly JavaScript, using Node.js, Express, and React.

Check out all our positions here:
https://boards.greenhouse.io/cameo
If you're doing minimally invasive wrenching on stuff that is in good condition electronics are fine until you have to do serious work to them.

Grafting two engine harnesses together because you can't buy the one you need (because nobody sells that stuff for 20+yo vehicles) will make you want a carburetor.
I'm pretty sure the process can't have payment stipulations like that.
Wow. So if a public domain piece of music (which does not have a copyright) is played by someone and recorded (which does have a copyright) the Google AI has no way to know if you're reproducing the the public domain music (which you are allowed to do) or reproducing the reproduction of someone playing a piece of public domain music (which you're not allowed to do).
Again you're making conjectures and not sticking to facts. The only person attacking a person oppressed by the CCP is the MuseScore developer. He's also the one threatening to involve the CCP. And you're being an apologist for them. It wasn't an alert, nor an attempt to make the plugin legal. The "Otherwise, I will have to transfer information" is a pure and simple threat. And you're the one making excuses for that behaviour.

If this is a real threat then MuseScore really handled it the worst way possible and they should be ashamed for purposefully threatening to endanger a CCP citizen. If it's not, it's just a mafia-style shakedown.

Once again: if you don't see a problem with calling the CCP police on someone whose only personal information we know is that he's anti-CCP, then I don't think we have enough ethical common ground to even continue this discussion.
Proxy Data for Goodreads Fake Users
According to this...

https://www.beckershospitalreview.com/public-health/states-r...

California ranks #31 of 51 in immunizations.
I guess indeed many find it bloody boring. A chore to be dodged if possible. And also when doing some documentation work, because people are so deeply into the subject matter, they feel many things are obvious and need no further elaboration.
There doesn’t seem to be much nostalgia for CP/M either. Most people working on retro projects are more interested in banging bits than working with an antiquated OS.
There is something that feels wrong with this page that I don’t think I experience with other content that uses icons.

I wonder if the human brain is starting to segregate emoji from iconography the way we instinctively don’t look at ads on pages. (Last year I insisted a web app did not have a feature and after conversing with the vendor they showed me it was there, in a little ad-shaped rectangle to the right side of the page. My brain did not let me look at it)
Yes and no. Typical multi-camera video systems can generate data at a prodigious rate. You can "either" put together a RAID system to handle the write bandwidth your you can use a couple of SSDs. The latter is "simpler" the former is more "economical".

That said, when NetApp was trying to sell SATA based filers into this market (which, not surprisingly is VERY cost sensitive) two things became apparent. First, up front system cost had to be minimized, and the vendors of these systems saw disk failure as a revenue opportunity to "roll a truck" to the customer and replace a failed drive.
I'm not. I'm arguing that they're the same situation. I think there are other factors that make the issue of gender reassignment completely unlike abortion, but yes they're both existential. GP was claiming only abortion was and I pointed out that that was logically inconsistent.

The differences are that regulating abortion harms a third party, the woman, while allowing gender reassignment doesn't.
Découvrez l'origine de l'arbre de mai (30 avril et 1er mai, calendriers païens)
Most likely it will hurt your career. Typically you want a niche technology that is growing rapidly.
OP, I’m super curious as to what inspired you to ask.
Like some have suggested, the automated system should only be an input for a team of humans to then review and consider. They should then contact the potentially breaching party and get some feedback as well as doing some due diligence to check if the complaint came from a proper right holder.

Yes this costs money but it is the only way to do the job without being a scumbag and a general burden on the world.

Furthermore it should cost the person sending a complaint somethings to file it, which then is refunded if the complaint is found to have merit.

Lastly, some of these steps could and should be skipped if a particular account or multiple accounts determined by some other means to be the same person are repeatedly found to be in violation.

Similarly if a person keeps making unfounded accusations the refundable fee might increase in steps.
Yeah, it tells us that we're wronger than we thought. If FTL is possible, just knowing that will push research in that direction.
If there is no official diagnosis, would it be ok for journalist to amateur diagnose her? Afaik, that is not considered acceptable.
Sidebar Menu Using HTML and CSS
I agree a noticed that too. Even excellent kids in kindergarten with me could barely read and write, let alone make something of that quality.
This. As a technical writer, this is one of the biggest pain points of the job. While writing the documentation, valid questions will come up regarding design decisions, but no one has the answers.
This doesn't change that the shortages are caused by processes with infinite appetites. The demand grows with the supply, for hardware used by cryptocurrencies. To me it looks like the polar opposite of sustainability, which is distressing.
> Even today the United States is either at the top or near the top of education spending per student

And the US is dead near the bottom in social spending. As a result American schools are asked to do a hell of a lot more than other nations.

American teacher salaries are higher than overseas but, by US standards, teachers aren't paid very much. In the US salaries are high but social safety nets are non-existent. In California it's even more extreme because the cost of living is out of control (arguably because of Prop 13).

> little to show for it in terms of results.

Curious why you think that.

The UCs are the envy of the planet and, before Jarvis, they were free. People bust their ass at IIT, Tsingua, or ETH Zurich then fly over here for grad school at UCLA where they ultimately land jobs at American companies. Why you'd want to defund this process I have no idea. Seems like the kind of thing we should be aggressively expanding.

For K-12, unlike most of the world, US schools have been educating more and more people from different ethnic backgrounds. It's no secret that blacks and hispanics do worse on standardized math tests and when you mix them in with the rest of course average scores go down. But when you slice by ethnicity both groups individually have been improving.

> someone, may be at the administrative levels, is obviously profiting.

"obviously" you should be able to point to who it is
OP trying to pump their Safemoon bag.
Documentation seems to follow two principles. It’s either (1) never complete, or (2) always outdated. As a general rule, you can always rely on it to never have the information you need, or to always have incorrect information.

Joking aside, documentation is great but it needs to be treated as importantly as the code itself. Treating documentation as a feature, rather than an afterthought or side effect, will allow it to get the funding and attention that it deserves.
I'm not misunderstanding. Features are merely attributes. Whether they are virtuous or not is irrelevant. A turbocharger, whether good or not, is a feature.

My point is that features may have maintenance cost, they are not in of themselves a maintenance cost.
I'm with you re: "pay more if you want more applicants" but this does not sound like a situation where the jobs are economically unviable.

When I was a student in LA in the mid-2000s I lived on basically this amount of money, inflation adjusted. I couldn't afford a one-bedroom, so I split the cost of a three-bedroom with two friends. This was a very common arrangement for people well into their late 20s, especially people in creative professions like writing.
Sure, but the grandparent alludes to the fact that what they think of as great now can easily change by the time they enter the workforce - and, given that we're talking about engineering jobs that usually require a degree, it will take some time.

Additionally, these people don't have much work experience. A lot of ideas - such as open offices, work from home or skipping documentation - feel fine until you've worked with them and found their drawbacks. It might work for some, but it does not for a lot of others.
That could have as much to do with the contemporary social environment as it does with actual decisionmaking. Sex among youth is down overall - even pre-pandemic, iirc.
When I was at Google they had a mission statement that went something like "Organize the worlds data and make it available." But the reality seems to be it was "Seize the world's data and hold it for ransom." The latter of course being the better business model.
Yep, and that's why being sympathetic and able to put yourself in the shoes of an outside reader are very important soft skills for a programmer.
There are a remarkable number of commenters saying no, documentation isn't hard actually. One question for those commenters:

How do you test your documentation? Properly test it, ensuring that it answers many kinds of questions for those who are new to the topic, and who haven't already been working on this project for months?

If you're not testing it, then how can you consider it done? Would you do the same with your software?

The vast majority of documentation that I see these days is bad in multiple ways. Most common is lack of coverage for important topics or cases, and I'm not even talking about things like "why this product is built this way".

I'm talking about stuff like:

- An API providing all kinds of methods for manipulating "Fribblers", and when you look at the Fribbler class it just says "This is the primary class representing Fribblers." No idea what this means or how it fits into the wider API? Good luck!

- Parameters or properties appearing in lists without any explanation of what they mean

- ... and that's assuming those parameters are even listed at all, which (often) they're not

- ... especially when those parameters appear in other parts of the documentation. "This method will work asynchronously unless you've passed the "borgle" attribute to the Fribbler constructor." There's a borgle attribute?!

- And this is all just for basic usage of a product. Want to contribute, or run tests, or anything else? Nothing.

Documentation needs usability tests, same as anything else which is primarily designed to be used by humans who may not have seen it before. But it's hard enough getting proper UX testing for the product, let alone its documentation.
Writing docs isn't hard, but maintaining a well-documented ecosystem is quite difficult. The aim of docs should be to limit reverse engineering time, or at a higher level should provide direct impact on velocity of a given team member.

When I first started out I would keep big centralized documentation stores. If a project had a dedicated wiki then I'd use that, but if that wasn't present I'd throw together something on my internal note taking like Obsidian. The downside of centralized and detached documentation is that it's hard to check per pull request if it's been updated, so it relies on regularly fallible human processes. Second, code and architecture tend to drift, and it's difficult to stay on top of that drift with a centralized doc store.

I then gravitated towards in-repository documentation. I'd open up a /docs folder and either include a static site to be run locally or configured to run on the web. I haven't seen a ton of downsides for this approach other than that it will skew respiratory metrics if you keep them. Changes in the docs folder can be prompted and checked for in pull requests.

The only potential downside is when your software spans multiple repositories of different types. A deployment repo here, code repos there - have one store of your documentation in the application repository means you treat most (if not all) other repositories as generic and document them as such so they neatly fit into your software docs.

None of this even begins to touch on documenting inline, which is fairly key to maintaining good code. For all the churn and hand-wringing I see about when to document which is often phrased as when not to document, this is the chief barrier I see software engineers hit their head on. When you're working on a package / module / library it's easy to substantiate lots of implicit context that's easy to admit during this process. I follow this pretty loose framework:

- document inputs and outputs

- document error conditions

- document package purpose, intended use

This direct documentation should then be backed up by more implicit documentation like variable / function naming conventions and tests. Testing is all about maintaining contracts; not attaining "coverage". Though it is possible that tests are not only reinforcing trust for end users; I do generally trust tests in PRs but only so far as I know I won't break my users as opposed to being "bug free". Really thorough testing that instills my confidence involves other methods like fuzzing.
Again, musescore may already be involved with the CCP for contractual reasons. Basically all companies who do business in China are involved with them in some way. These things happen for reasons beyond their control, e.g. an investor sells everything off to foreign investors who then change the terms. If you're being careful, you have to assume they are already compromised. I don't apologize or make excuses, it's just basic safety. My view is that if this person is really worried about threats coming from a government, it would be wise to take those threats seriously. Github profiles are public, so it's not exactly hard for them to find this information.

Edit: I agree with you that if this musescore developer is lying about that, then that would be wrong of them. But I don't think I have enough information to make that judgement. So I think that's where we're disconnected. At least for open source projects, my view is to take any and all potential legal threats seriously until the matter is resolved with the lawyers.
Three Monsters: The Path to Self Growth
That doesn't make the engineers feel clever, though.
Exactly. These are all check-able facts (not, e.g., allegations of secret dealings or something). The fact that he works in the industry is what allows him to write this compactly; it's not proof of correctness.
Semver is a second-rate coping mechanism for when better coordination systems don't exist.
We claim credit for the combination of letters that we call a short story, or even for a slogan ("I'm loving it."). We claim credit for a short song, or many other combinations of atomic components.

The fact that I can't do it means, to me, that there is creativity involved. Creators deserve rights. That's fair enough, it seems to me.

I was looking for a site where creators had generously made some available under a Free license.
> This phone doesn't have the latest and greatest software/hardware (version locked at iOS 12), but it does its job

I hope you do not browse the Internet on it, since a lot of security bugs are probably not fixed in its browser (and you're not allowed to install another one). So you put all your data on the phone at risk when using the Internet.
It's really important that manufacturers start responding to cryptocurrency induced shortages with auctions.

The demand from the cryptocurrency users will be extremely high until they've spent a particular amount in total. They can do that with 1000 units, or with 5000 units.

Obviously auctioning off units would be bad for having predictable prices for retail customers but that is irrelevant if aggressive miner buying is buying up all the supply.

Moreover, shareholders at the manufacturers should be demanding it: they're leaving money on the table.
That's because minimum wage isn't actively pegged to a cost of living measurement, it's manually adjusted from time to time (ostensibly to be inline with cost of living). That manual adjustment is slow and decoupled enough that there's no runaway feedback loop.

If you legally define the minimum wage as a formula instead of an absolute number, and that formula includes cost of living, you can create a runaway situation.
Is it too late to carve an exception for a site with basically no images, that loads bunch of frameworks?
Does PeerTube have ads or monetization?
That will only work for a select group of viewers. Waiting a day or even a week isn’t a huge deal for me as a consumer, and I’m familiar with it because Patreon people often put their videos up in patreon earlier than their YouTube ones.
It seems odd to me to simultaneously hold the view that luck is the dominant factor and advantages (like being lucky once) are incredibly important.

If advantages are important doesn’t it follow that advantages like intellect, wisdom, or courage might be decisive?
I'd like to think that the masks are just because they had to film these now, and that the actual plan for when people return doesn't include them.
https://www.revelist.com/pop-culture/olympics-body-shaming/1...
> The answer is why the hell am I being forced to figure this out?

Because the decision is made before CSS loads and is parsed, so the browser doesn’t know any of this.

Don’t get me wrong, this frustrates me endlessly as well, but the reasons for it are clear. Delaying until CSS has been parsed would slow down image loading.
Did anyone learn from that post or the comments on this page? I'm struggling to extract any value, everything is sensible, but a lot of it is opinions, open to interpretation and high level "its a judgement calls". I don't think any of it is useful in practice. Not much was backed by evidence or science.

My perspective: Always just do it. If you're good enough to succeed you'll succeed, and if you're not good enough, you never were gonna succeed anyway. Of course, you need to be scientific in your approach, but nothing on this page is scientific. Apart from my perspective ;)
I think many would argue things have gotten much better for a majority of the world's population. We still have a ways to grow as a society though.
Something the author didn't dive into - which is very important - is the audience of said documentation. In my 20+ years documentation is pretty much essential, but there is definitely a skill in documenting for a particular audience:

* Internal, non-technical users; what does the code do, why was it written, who currently owns it, when should it be run, how to run it, and what to do in case of failure. The more accessible, brief, and direct the better.

* Technical users; this is your README that usually doesn't need to be updated all that often. What is this code for? A quickstart for install/loading, dependencies, and the bare-bones set of functions, arguments, etc.

* Fellow implementers; the above README, but likely with a few additional notes of how the code is (high-level) broken up, and where to go for the most common things. This is where documented code is really good as well. I usually find the best code comments have always been A) NB: here's a drawn-out explanation of why the code does this, it's for a reason, do not question the code first unless you understand this and/or the above reason has changed, and B) in the future, you may want to do X, in which case you'll need to do J, K, and L and update M. Comments like those have saved me (from myself, even) so much grief and time.

* 3rd party users; this is where real documentation gets to be a monumental PITA and any company worth its salt will hire a technical writer or two. This is a very different skill than what's required for any of the above.

The biggest concern I see brought up again and again with documentation is that it becomes out of date quickly as soon as it's finished being written. This needn't be true. Internal documentation is just enough info for whoever is using it to know what it is, how/when to use it, what to do if it fails, and who to go to for more information or help.

Honestly though, the biggest problem with documentation has always been where it lives and how it's edited. Is it all repo READMEs and markdown? Are they google docs? A wiki/confluence? This is always where the breakdown happens. Programmers are comfortable with just being pointed to a repo and text files, while non-programmers want WYSIWYG docs somewhere central, which is the last place most programmers even think about. Wikis/confluence attempts to be a compromise that (IMO) no one likes. This - like task tracking - is a unicorn of software development.
Unless I’ve misunderstood something, no DMCA notice or counter-notice has been sent.

Instead the copyright claim is purely via YouTube’s content ID system that detected the supposedly infringing audio before the video was even published, as the YouTuber states in the video linked. The company claiming the copyright sought to monetise the “infringing” video for themselves through this content ID mechanism.

I would argue that, while YouTube says it cannot arbitrate copyright disputes, if it continues to allow supposed copyright holders the exclusive right to decide whether something is in fact their copyright, they are arbitrating the disputes, just in a completely one sided manner, and the creators beef should be with them. If they were actually neutral, they would instead allow the DMCA system to work as you said.
Why do you assume the gender they tell people isn't their legal gender? Some jurisdictions allow changing it.

Do you keep track of people's names? Their partners' names? Their jobs?

Did you ever think someone was a different gender when you first saw them? What did you do after you realized?