skysight-inc/HackerNews huggingface dataset:
It certainly can be, but it's not guaranteed. Clean room design is one way to avoid a legally ambiguous situation. It's not a hard requirement to avoid infringement. For example, the US Supreme Court ruled that Google's use of the Java APIs fell under fair use.

My point is: just because certain source material was used in the making of another work does not guarantee that it's infringing on the rights of that original IP.
Consider the alternative where employers can fire you for lying about your employment history. Once you’ve done some union organizing, you’d be potentially unhireable.

ETA: Here's the relevant part of the judicial decision in this case:

> None of these employees [who were fired for lying and used to claim precedent in this case] are an appropriate comparator for McClure, who was never accused of stealing, violating traffic laws, or other criminal conduct. And, even if Respondent could show that the other employees were fired just for lying, and not for the underlying serious misconduct, Respondent could not use that to justify firing McClure because they were all accused of lying about conduct that Respondent could lawfully consider in hiring or firing them. In contrast, McClure lied about his history of working for union employers. Because Respondent could not refuse to hire McClure because of his union background, his lie about working for Deem can’t be used to justify firing him.
Quite a few of the foods seem acidic.
Sometimes I've not bothered to set it up and usually I don't notice.
That's a good point, though you could use some firewall rules to rewrite the port number so that the local daemon is listening on the normal port but accessible via an alternate high numbered port.
Everything you mentioned is immoral. Two wrong doesn't make it right.

If you cheat, to compete you your lies I now have to lie. And it completely breaks the system.

Also, you don't deserve more leverage over other prospective candidate. This is cheating and fraud. It requires punishment.
I just picked up a box of Waffle Crisp cereal at Walmart last week! So glad they brought it back!
If you are running a fleet of thousands of hosts in an environment with auto-scaling capabilities, your swap will never do anything except under extraordinary burst load, e.g. DDOS.

In that situation, swap provides exactly the wrong thing - it attempts to keep up with memory demand by doing a more expensive and slower version of regular processing. That’s a key ingredient in the recipe for congestion collapse.
I'm old school. I usually maintain a swap that 2x size RAM, unless RAM exceed 16GiB, then I usually keep swap between 2x and 1x of RAM. This is particularly the case for mission critical servers. Swap gives me half a chance if something hoses memory.
You're saying that if you as an employer find out that someone you hired lied to induce you to hire them, you should be legally required to continue employing them, as some kind of karmic balancing thing?
All this is so normalized these days that many of the items on this list are referred to with reverence as best practice.

Plus calling these things "sabotage" isn't right even as a metaphor, and IMO confuses the issue. These people aren't on a third-party payroll, they are just self-serving.

No one is creeping into your office in the middle of the night. You invited them over, let them in, watched them piss in the fish tank, and then gave them a promotion and a raise. Now you're surprised everyone is lining up to fuck up the place? As usual the value judgements are just a distraction in matters of economics, look at the incentives.
The piece documents that at least two manufacturers (Data General and Univac) marketed their extended Fortran IV compilers as "Fortran V" -- but it doesn't say whether they actually extended Fortran IV the same way. "Fortran V" wasn't the name of any official standard; the ANSI standard which more or less documented Fortran IV was officially Fortran 66, and ANSI's next version was Fortran 77.
In Germany, there are certain kinds of questions that are not permissible on an employment questionnaire, for example asking whether a candidate is pregnant or plans on having children, union affiliation, etc. However, these questions are often included in the questionnaire and not answering them would provide sufficient signal to the employer and the only remedy would be to sue the employer. So it's explictly permitted to lie in the answer, rendering the questions useless.

I expect a similar line of reasoning applying to this case: The question is about a protected, legal activity which is nonetheless undesirable for certain employers. Asking the question and requiring a truthful answer would undermine the protected, legal activity. Hence an effective remedy is explicitly allowing to lie in the response.
FastLanes Compression Layout: Decoding >100B integers/sec with scalar code [pdf] (2023)
It's not punishable because it's checked by any competent employer for a competitive job. Employee background checks are only start at 1k usd or so, and grabs from data submitted by employers/tax firm/banks/credit card companies/insurance/courts and similar, meaning the employer knows your employer and pay levels pretty much perfectly.

If the position isn't worth those prices for a background check, it only a fast food job where the only thing that matters is the Employee does as told.
On that slope nothing should considered immoral.. if one kills we can all be murderers..
Not really. If there’s no swap, then at some point programs will just die when you run out of RAM. Once things start going to swap regularly you might notice a slowdown and have a chance to do something about it rather than kill a process unexpectedly.

For server workloads, you probably never want to use the swap, but it’s safest to have it enabled because you don’t know which process is going to get killed when memory runs out. You can monitor for swap usage and tweak your settings appropriately.
TIL "garden leave", a period of time when you are mandated to be out of work. Thanks.
Möbius Strips Before Möbius: Topological Hints in Ancient Representations [pdf]
Really? I was under the impression that was an OpenAI limitation, which they eventually worked around by deploying their own models.
You can read more about the motivations and options for integrating nuclear power with thermal energy storage in this great 1978 ORNL report too: https://doi.org/10.2172/7213843
Habitat destruction for wild animals? Lab meat would also be nice.
Yes, it would definitely be more performant to move it outside of the transaction :) good catch
Disabling swap is recommended on k8s nodes, since the idea there is to schedule workloads to use up the actual RAM/CPU of the box.
I'm curious, what kind of software would care about that?
According to the ruling, yes, given the public interest as stated, in protecting the right to organise.

This is broadly similar in principle to laws like those in many places allowing one to not disclose spent criminal convictions.
The context here is salting so it would likely be omitting prior employment or education/training. I personally think this is completely reasonable in all cases.

Non-salting example: over a decade ago I omitted an entire year of professional experience as a PHP developer when trying to get hired as a Python engineer, because I didn’t want to get pigeon-holed as “PHP dev who can maintain our crummy legacy PHP codebase nobody wants to touch”.

Anyway it would be extremely problematic if employers were entitled to full and complete honesty from applicants but had no equivalent obligations from their side. If businesses had the choice they’d pick the status quo over mutual transparency.
> If that has to be punishable, then job listings with false or misleading information should be too.

Currently, it's symmetrical. If either side lies, the other side can exit the contract with no notice, and may tell others their story.

> Also, saying you’re hiring when you’re actually not.

This would be nice and very actionable. Perhaps requiring a company to say how many resumes they've received, candidates they've talked to, and how long its been open on job listings could save everyone's time.
‘Secure’ == unable to be compromised.

You seem to be saying ‘secure’ == ‘compromises are able to be fixed’.

Which doesn’t fit any definition of secure I’m aware of.

Every one of those things you mention has been compromised, and then fixed, at various times. Depending on specific definitions of course.

And that is what we see publicly. Typically figure on an order of magnitude more ‘stealth’ compromises.

For a compromise to be fixed, someone has to notice it. Exposing machines to the Internet increases attack surface dramatically. Allowing machines to talk to the Internet unmonitored and unrestricted increases their value to attackers dramatically.

Without careful monitoring, many of the resulting compromises will go undetected. And hence unfixed.

[https://www.cvedetails.com/vulnerability-list/vendor_id-1902...]

[https://www.cvedetails.com/product/47/Linux-Linux-Kernel.htm...]

[https://purplesec.us/security-insights/space-x-starlink-dish...]

[https://www.pcmag.com/news/account-hacking-over-starlink-spa...]
The black and white lady is nightmare fuel for me personally.
Thanks for pointing that out!

Looks like they've gotten a permit to start construction in Kemmerer, Lincoln County, Wyoming last May: https://www.nrc.gov/reactors/new-reactors/advanced/who-were-...

Edit: this would be for 840 MW thermal (I assume that means 840 MW worth of heat, which is then to be turned into electricity and perhaps district heating): https://www.nrc.gov/reactors/new-reactors/advanced/who-were-...

Looking into India's plant, that is apparently entirely independent of Terrapower. Sounded a bit like they got a permit to build there sooner but no:

> designed by India’s Indira Gandhi Centre for Atomic Research (IGCAR) based on the success of IGCAR’s 13.6-MWe/40-MWth fast breeder test reactor (FBTR), an experimental sodium-cooled fast reactor that has operated since 1985 [...]. The 500-MW PFBR got its start in October 2003, when the Indian government set up a wholly owned enterprise [...]. Construction of the reactor began in 2004. [...] delays stemmed from funding deficits, procurement delays, operational challenges, technical difficulties, and the geopolitical impact of the Fukushima accident.

Much further down the article, also interesting:

> At the end of 2016, Russia put online the 800-MWe (2,100-MWth) BN-800 at its Beloyarsk nuclear plant, a sodium-cooled fast reactor project that [this magazine] recognized as a pioneering Top Plant in 2016. The BN-800 reactor was, for the first time, fully loaded with uranium-plutonium MOX fuel in 2022. In December 2023, it was preparing to begin pilot operation

China also has an experimental reactor, Japan is working on one, Canada started planning one in 2022, three European counties in 2023... nuclear isn't dead?! We're actually getting safer reactors that can eat spent fuel, even if they're a bit later than one might hope for? Cool!
I wasn’t aware of that. I haven’t had any issues and the swamp cooler at my place is old. It’s very dry here, but I guess if you were to not run the cooler for a while the water may sit and you could see stuff start to grow in it. If the water is running 20 hours a day I’d be skeptical that anything would settle there but I could be wrong. As soon as we stop using it for the season I drain the water out of the reservoir.
If you need constant latency you already need to avoid allocation altogether after the start of the program (among other things) so swapping should never occur in the first place.
Sourcing HALEU has pushed back their schedule. Whether or not domestic supply is able to come online is a big risk for them even with the USG putting resources behind it.
I wanted to read more about the interesting part!
Here’s a case where calling the boss names is protected converted activity.

https://www.nlrbedge.com/p/wall-street-journal-is-mad-at-wel...
Beyond Clean Code: The Optimization Spectrum
CVE-2024-4947 V8 incorrect AccessInfo for namespace object causes type confusion
What is this about then. Obviously you can omit stuff on your resume. I take offense at adding fake experiences.
Depends on the workload characteristics. If there’s a chance one request could balloon into a huge RAM consumer, you want to be able to survive that without running out of RAM. But if you are hitting swap regularly across your fleet, it’s time to tweak your scaling parameters. But if you never ever hit it, you may be overscaled.
The Dutch trains (the rolling stock) are a joke for such a rich country but I love everything else about the Dutch railway

And yes overall everything in the NL seems better quality
Why? Are they spam pages?
Most people think of swap as "emergency memory in case I run out of memory" and while it's true that it can get used in this way, it usually serves a much more critical purpose in your OS's ability to reason about and use memory.

For a good article on why this is true for Linux: https://chrisdown.name/2018/01/02/in-defence-of-swap.html

I believe that most operating systems are going to make use of memory in a similar manner.

With that said, I'll turn off swap on devices that have unreliable storage. (Anything using an SD card)
Free for nonprofits/hobbyists and €500 as soon as you use a piece of software commercially would be very reasonable. But charging the same from someone who doesn’t make a penny as from a company making millions doesn’t make much sense.
At the time the Kinetic Energy Interceptor (KEI) was expected to work, the plan was to scale that up. The idea is that some sites would be defended even in a saturation attack where it would be unlikely that Russia would devote enough ICBMs to a single target. There have been attempts to restart it with more lasers. Even now it’s seen as a matter of time - believing the hype from Lockheed and Raytheon. I hope it is only hype but maybe enough lasers could work. I would hate to find out it doesn’t work the hard way.

I could tell back then (>20 years ago) that cheap drones were the future but doing a bad job on expensive things provided job security so no one was interested in doing a good job on cheap things. I quickly switched career to big tech.

Some decision makers in the US are oddly ok with getting nuked so long as they can still call it a win, one single American and no Russians. Suburban sprawl was encouraged as diffusion was seen as a survival strategy. Then you have Baptists that see nuclear holocaust as an essential part of the rapture so they can go to heaven without dying and be with their resurrected relatives. A really dangerous belief held by plenty of people in the military.

I’m of the view that it’s only a matter of time before space is militarized, especially if Trump gets elected again. And if we do that then Russia and China will want to do that as well. I am assuming their base on the moon plans are a cover for launch capacity investments to get nukes into space.

People in the military think about the ‘unthinkable’ all of the time. I think the current framing of nuclear exchange as unthinkable is only done as part of the wests propaganda to allow the west to push red lines harder than what would be otherwise permitted.

As per realpolitik, nation states are immensely paranoid and often think if we don’t do X then Y will and with that can justify doing some truly awful things. Dr Strangelove is less of an over the top satire and more of an oddly accurate portrayal. Even the ability for a first strike nuclear attack by a military commander without presidential approval was accurate despite being classified at the time, I wonder if someone leaked the idea to Kubrick as a round about attempt to show the world how nuts it is in an effort to get popular pressure to apply political pressure to fix it. Have they fixed it, I don’t know but either way they would tell us they have and keep the truth classified.
No mention in dns0.eu, which is what I use and also hosted in the EU.
It's possible to be technically competent and kind. They're not mutually exclusive traits.
One doesn't even need to be kind. Just don't be an asshole.
You should look up the aerosolization of patterns of toilet contents when toilets are flushed.
Many people still use the traditional Japanese toilet or western with no bidet. There is often options. Plus not everyone likes to use a public bidet.
Well yes but you certainly can’t become a lead if you’re getting mad at people. At least in many situations you can’t. And yes you could quit, but the job market isn’t the best right now. And sometimes the jobs that pay more require dealing with less competent people so sometimes there are tradeoffs.
Sure swap isn't helping, but having random processes being OOM-killed isn't either …
That's local site prep permits. Getting an NRC permit to be able to start construction of the reactor itself is the real rub.
On servers, unless you have a very fast SSD dedicated to swap, all swap gets you is waiting an extra long time to figure out that the operation you're trying to do is going to fail anyway. The number of tasks that need just a little more RAM after exhausting the dozens to thousands of gigabytes modern computers have are vanishingly few.
Your “perhaps unsurprisingly” itself seems to be an ad hominem fallacy, if you are keen for writing to avoid them.
I have to say: It's really annoying that some idiot who wrote a book in the 90's has resulted in everyone redefining "nice", when they should have invented a new word.

As far as the English language goes, what you define as "kind" is also "nice".
One of my main goals with the book was to "democratize" architecture, to make it accessible and relevant to every developer. As the cover blurb says:

"It democratizes architecture. You may have software architects at your organization — indeed, you may be one of them. Every architect I have met wishes that all developers understood architecture. They complain that developers do not understand why constraints exist and how seemingly small changes can affect a system’s properties. This book seeks to make architecture relevant to all software developers, not just architects."

In hindsight, my book hasn't been very good at that but perhaps it was a stepping stone on the path. Michael Keeling's book Design It: From Programmer to Software Architect does a better job of saying how developers can engage with architecture ideas. I'm a personal friend of his and a huge fan of his work. His experience report [2] on how to democratize architecture is what I aspire to do.

[1] Michael Keeling, Design It: From Programmer to Software Architect, https://pragprog.com/titles/mkdsa/design-it/

[2] Keeling and Runde, Agile2018 Conference. Share the Load: Distribute Design Authority with Architecture Decision Records. https://web.archive.org/web/20210513150449/https://www.agile...
It's pretty good for say, 3-6 months.

Long enough to reset, not worry too much about health coverage, and if timed right.. not miss out on a bonus cycle. It's also short enough that you can interview and get a job offer from a company willing to wait for you. Often you can negotiate a signing bonus at the new shop to make up for compensation you may lose due to deferral or bonus cycle.

The firms trying to force 18 month terms are also some of the highest turnover shops. Arguably you'd need to demand a 50-75% bump to take the role since on the way out the door you are going to miss out on 1-2 bonus cycles. The term is so long you likely need to quit before finding a new job too, and then kick off interviewing in the last 6 months.
I imagine Fujitsu did everything they could to put only loyal management on the stand.

They did call the Fujitsu chief architect, who is now under investigation for perjury for his efforts (and I also imagine Fujitsu are less going to try to throw him under the bus and more have a tungsten bus dropped on him from orbit)
From the WHO report:

> This is in the context of increased population mixing following a period of reduced circulation of GAS during the COVID-19 pandemic.

The article is merely restating the WHO report and not adding any new political takes. The downvotes are because the comment is incorrect.
Of course your code should live up to requirements and be correct, for it to be good - The requirements can also be performance requirements.

If you have a list of maximally 10 elements that needs to be sorted and you opt for quicksort over bubble sort in a context where bubble sorts time/space guarantees perfectly solved the requirements, well, then you absolutely wrote bad code.

This is what a more senior developer understands, where a junior would jump in and write worse code.
Funnily enough a lot of Bidet toilets in Japan have a suction function for this reason.
Being from Louisiana we have so many interesting existential problems here.

The dead zone, Old River control structure, increasing hurricane sizes, barrier Island and coastal erosion, giant levee systems managed by corrupt/ incompetent bureaucrats, cancer alley.

And all that's just the environmentally related stuff and not the social stuff.

My theory is that all of this stuff makes it a terrible place to invest which keeps land developers from coming here so the culture is awesome.
Very cool concept! Is it software engineering focused, and do you have to invest in sales or marketing to get clients?
Kubernetes insists that you disable swap. The reason is that swap messes with the accounting of memory usage. Kubernetes expects hosts to have a very direct action memory reservation. Containers have a memory request; if they are over this request when memory pressure hits, they will be killed. Because the swapped out pages are not included in the memory accounting[1] you can end up in states where nothing is over the request, even though you theoretically haven't overcommitted. This requires falling back to true random killing, which is to be avoided.

It's also based on observations of performance - for many moons, the performance hit of swapping was bad enough that it was never worth it to run two jobs concurrently that didn't both fit into ram together. The exceptions weren't even exceptions. Disk thrashing was a serious impediment and way to slow your whole fleet down.

Now with fast flash being so common, swap is probably actually a good thing for many workloads again, but only "many", and SREs would prefer you make that explicit by using memory mapped files for data that's of random utility, so that the OS can manage that pressure for you, understanding that those files don't need to be fully resident.

[1] This is an oversimplification that I don't remember the real truth of off the top of my head
An interview with AMD CEO Lisa Su about solving hard problems
Section 117 is irrelevant — it grants archival rights to end-users for computer programs. It doesn't make claims about servers or legal third parties.

(Although it is relevant in disproving your point: I can pay an archival service to back up data I legally have the right to view, even if the backup is then on their server, and despite the service being a different legal entity than me. And they can give me a copy of it later, too.)

> You could conceivably make "ublock origin except it's a proxy run by a third party and we modify the website on the proxy", I'd agree that that has the same problem as a service like perplexity (though a different fair use analysis and I'm not sure what way that would go).

So, running a local LLM version of Perplexity that does exactly the same thing is legal, but Perplexity is illegal, because "a third party legal entity has the data"?
it's like a seat belt. If you never crash your car you are OK with instant death if you do so anyway. I prefer seat belts, even though I also prefer not to crash my car.
There is nothing or any hint about that quote being politically charged at all.

You just making up things in your head.
https://effect.website/
We use port knocking and haven’t had a single hack attempt in many years.