skysight-inc/HackerNews huggingface dataset:
I'm running 32GB system with two browser VMs getting 4G each.

The work VM which is typically connected to Github and work gmail needs to be restarted once every couple of days.

The play VM which would have a Chromium with a dozen tabs open can can take ~20 min to ~1 hour depending on the content in tabs.

I notice the memory leak when Sublime that I run on the host itself
starts dropping key press speed ( I run "xset r rate 400 50" ). Killing VMs or restarting them makes everything go back to normal.

I've ran glxgears for ~2 hours now with no significant leak. I will probably leave it overnight to see if something as simple as it can be used as a leak example.

I'm going to speculate the key is heavy usage of GLX something that only Chromium does as I have left a desktop with an xterm running top for two days and no leaks were detected on a play vm. So it is not just virtgl in QEMU being exposed to the guest, initialized by the guest and interfaced by the guest via virtio, but actually using virgl on a host to do rendering. Maybe virtual context creation/release cycle?

P.S. I originally made this work on my super light laptop ( i7-6500U with 8G ), so you don't need a beefy rig for it although there's a bug in recent Intel GPU libraries used by mesa that sometimes lock it up. I initially attributed it to something I did but it was not:

https://github.com/qutebrowser/qutebrowser/issues/4641

kitty, alacritty, and even Chromium would sometimes lock up with intel iGPUs.

Feel free to reach out - my email address in a profile here. I check it here and there.
It's way better than container runtimes. It's proper security sandboxing and it comes by default on most Linux distributions.
The ones that are formatted to 40 columns in all caps because THATS WHAT THE ORIGINAL APPLE II COULD DO are charming to no end.

http://www.textfiles.com/apple/wiztips4.txt

I wish I was five years older and to have experienced the Apple II bbs era instead of getting an old hand me down //c in the early 90's and not having the cash for a modem.
That’s not a problem with “this”, but a self-inflicted problem from React’s chosen model of reusing class instances. It’s a design choice made by them and not a language issue at all.
> the central bankers aren't thinking about inequality or inflation right now, they're just trying to avoid the apocalypse.

The bad news is that by ignoring inequality, they may be just causing it.
I don't know you or your work. I have no qualms in saying most likely there is someone better than you. I have no qualms in saying that about 99% of the people I know because it's statistically true. To say that others don't deserve more pay or prestige is akin to saying "I will feel bad so don't pay someone better more".
What I learned working with a cheap Kubernetes cluster
Worth noting that due to the size of the Windows repo, they ended up having to extend git significantly

https://devblogs.microsoft.com/bharry/scaling-git-and-some-b...

https://github.com/microsoft/VFSForGit
It dind't, yet at least. Let's see which one is still working in 20 years :)
It's advertising/publishing jargon for the creative bit of the work - the actual artwork and copywriting as opposed to all the other stuff that makes an advert work (tech, publisher, tracking etc). The word has been used as a noun for over 200 years and in this specific context for about 100 years.

https://www.merriam-webster.com/words-at-play/can-creative-b...
Even before arrow functions I just never had much trouble. I had a very consistent way of writing logic. Only ran into scoping issues a few times.
It takes some fussing about but you can do it in more or less the obvious way. I regularly use firefox in a systemd-nspawn container, the only annoying thing at this time is needing root to start the container but there's already a plan for how to fix that and I believe someone has also posted a PR for supporting starting "machines" (in the systemd-machined sense) as a regular user.
Brain Implant Signal Decoder Reversed Paralysis
Consider the support costs involved in dealing with things like broken BIOSes that don't send "switch to boot protocol" command and similar.

Cost of electronics is not everything.
Show HN: Find fast-growing companies to do business with
memset is not required to do anything if the side effects are not observable; this is the entire reason why memset_s needed to be added (and also why __attribute__((packed)) is recommended for anything that is being sent directly over the wire, if this kind of construction cannot be avoided). Compilers often inline and unroll small, constant-size memsets anyways, and since it is not possible to observe a consistent padding in C in a standards-compliant way to my knowledge, an optimizing compiler should be able to legally leave those bits alone.
China Loosens Covid-19 Test Kit Export Requirements
I agree that the lookup map thing looks like very bad advice. I can't see a reason why you'd do something like that.

On topic, it has been my understanding that the React team is moving away from classes for a number of reasons. Not just because it confuses people (although the pattern seems to create expectations that aren't met due to Javascript's weird 'this' behavior), but also because it doesn't have a good pattern for code reuse (as demonstrated by the lack of mixins that used to be popular in React's createClass syntax) and also because it seems to be a suboptimal pattern for compilers.

That said, I've moved on from class components to function components with hooks and I can't remember the last time I thought something would be easier to implement as a class component, even though it is still an option to do so. But that is, of course, anecdotal.
How to write the observer pattern in JavaScript
There is some evidence that big companies (e.g. Ebay) were not wisely spending millions of dollars on Google search ads.

Blake, Nosko & Tadelis, 2015. "Consumer Heterogeneity and Paid Search Effectiveness: A Large‐Scale Field Experiment," Econometrica.

https://econpapers.repec.org/paper/nbrnberwo/20171.htm

I'm sure the landscape has changed since then in terms of there being more accountability (better tools to measure things like ROAI and mgmt demanding stronger evidence of marketing efficacy).
Which is how advertising people speak, no? Horses for courses! (ie it's appropriate to the context as "newspeak" is kinda what advertisers deal in)
> First of all, there is no way the compiler is going to optimize a call to memset(&foo, 0, sizeof(foo)) when &foo is being interpreted as a void pointer. That doesn't even make sense.

that is really dangerous to assume. memset is a compiler built-in in every relevant C++ compiler and the compiler definitely knows the type of the object that is behind your void* and knows if you're being nasty.

e.g. look at this code : https://gcc.godbolt.org/z/xh9BXs

it's UB, and the compiler knows it and inserts an "invalid opcode" instruction even if you try to hide a memset behind a void*-taking function
Developer efficiency is actually harmed by valuing it so much. Developers get into pointless ideological debates about purity and that hurts their efficiency. When good developers have to deliver features in a short time frame they stop debating that stuff and make decisions. They then learn from these decisions the hard way and no one is having an ideological debate any more.
Not the same reputation and prestige.
Covid-19 Drugs and Vaccines Tracker
If you still have the (anonymised) IP addresses I can tell you if the downloads was coming from bots or not.
Yep, he took the time to answer questions from highschool me more than a decade ago and he was very friendly.

I'm glad everyone else seems to have had positive interactions with him also.
Native English speaker here. I had never come across this usage of the word 'creative' before, and even knowing it's meaning now still find it odd and grating in the article. I'm not in advertising though (thank goodness).
You're looking back at those anarchist leanings through two decades' worth of post-9/11 pro-nanny-state propaganda. And in some cases those writings predate the fall of the Soviet Union.

The world was a different place back then. I was 7 in August of 91, too young to remember or have experienced much of the world but I do remember the culture of pre-9/11 internet being starkly different from that of today.
I mean, specific to my scenario, my invariant was "only one zone at a time" and the liveness property was "everyone who wants a zone eventually gets one", so respectively:

1. \A z \in Zones: Active(z) => ~\E o \in Zones: z # o /\ Active(o)
2. \A w \in Workers: \A z \in Zones: WorkerWantsZone(w, z) ~> WorkerHasZone(w, z)

Unlike your scenario, I am checking the spec here. I know that code that properly implements the spec satisfies these two properties, therefore I've proven the spec correct. You can disagree on the importance of those two properties but I've mechanically checked that those properties are always preserved in my finite models, so I know the spec is correct, at least for the model size.

You know, it's really not too hard to get started with this stuff. You can always nit-pick but why not try it out and see if it's useful for you?
FP does not do that.

First of all, there is stateful code and then there is effectful code. It sounds like you are talking about the second, not the first. You can have tons of state and remain mathematically pure.

Where people get hung up is effectful code, or mutable state. Even one of the more hardcore FP languages, Haskell, does not try to abstract that out. Instead it embraces it fully by giving constructs in the language to describe and control effects! This is far more powerful than straight up imperative languages. If anything, writing mutable, effectful code is more powerful in Haskell than in C/C++.

Where Haskell gets difficult is when writing effectful code that interacts with external C libraries and the OS. But this has nothing to do with purity, state, or effects. It really only has to do with the fact that it is designed to have lazy evaluation by default. Which itself has a lot of advantages, but it makes this interaction more difficult as code does not execute in the same order as you write it.

You may find that languages such as OCaml, which are fully functional and have strict evaluation are a joy to work with.
It fares well next to all the other comments saying this article is “pure whining”.
RAL is often used in manufacturing. Our powder coater used RAL colors for example.
I also did this lol. What a misguided, neurotic person I was.
so therefore it stands to reason that other substances can exist that rewrite your mind to make you ineffective at other behaviors
Surviving ventilators, only to find lives diminished
There are two branches of economics. One of them is a science, the other is (politically, economically, and culturally) successful.
I think contractions tend to be less common in American English in general
sizeof will include padding, but there is no need for memset to actually perform a write that cannot be consistently observed.
InLinks Market Trends
Teams has its issues, but compared to skype its amazing in my opinion. Granted, skype is a pretty low bar to compare with, but still.

At my last company, Teams was introduced as a tool besides skype - and everyone was encouraged to move meetings etc. whenever possible over to Teams. It worked out pretty well, after a few months skype meetings became the exception, almost everything, especially if only techies were included, was happening on Teams.

I recommend to give it a serious try, some of it features do suck (notification settings etc. are absolutely horrendous and seem to not properly work half the time) but overall it improved the ways people communicated a lot compared to skype. At least that was my experience :)
It is 35 years since the Acorn RISC Machine chip sipped power for the first time
I see "empire building" as a larger campaign. In some cases, vanity hiring is really just vanity hiring, motivated by noting more than the impulse not to let your peer's headcount pull significantly ahead of your own.
I feel like if they did some decoupling and got rid of the persistent running connection / filesystem stuff for features that did not need it as a mandatory thing that early users wouldn't mind as much. For all I know it actually does work that way too.
Yes it would be nice to add more diverse examples, and I agree with just billion dollar companies it will skew the data. Do you have any sources or link for smaller companies?
> But that's present vs past tense, which is independent of the subjunctive mood.

No, it's subjunctive vs. indicative.

The British form is indicative and past tense, which is not correct grammar under either British or American rules, but is used in common speech.

Replace the verb with "to be", e.g. "the doctor insisted he be here." vs. "The doctor insisted he were here." to illustrate that the past subjunctive doesn't fit.

The past subjunctive is almost exclusively used for hypotheticals, e.g. "If I were rich...."

This isn't hypothetical. This is a mandative statement, so we use the infinitive form of the verb even if the action took place in the past.
That is not in fact a good description of EFail, which was indeed caused by a failure both of the PGP protocol and of GPG, its reference implementation.
I want to add to that the ethereum name service, https://www.increaseo.com/eth-domains-ipfs/ could also potentially play a role in a means to efficiently and reliably distribute public keys in conjunction with IPFS? Seems worth considering at least.
> "We know for a fact that mammals get PTSD after being in highly stressful experiences that they are unable to metabolize."

my otherwise wonderful dog, adopted from a rescue org when she was ~3 years old, plainly has PTSD from prior trauma. she spent the first 3 months with me going through frequent cycles of fear diarrhea, usually in the very early morning hours.

i can only guess that she was treated badly by a very overbearing/masculine person in tight quarters, based on her uncontrollable fear reactions, which almost always happen at home. outside, she's generally friendly toward women, mildly curious/cautious of kids, and fearful/cautious of men. we've largely worked through the diarrhea, though sometimes it triggers if she thinks i'm mad at her for any period of time, even if i get angry for reasons totally unrelated to her.

she still sometimes exhibits extended bouts of panting, scratching, and self-nibbling as she tries to regulate the autonomous fear reaction. distraction, petting, hugging, and other countermeasures sometimes but often don't work in calming her down. it still breaks my heart every time, even 2 years on.
Worth of note that this was also possible with MASM and TASM back in the MS-DOS days, and other 16 bit home platforms.

Hence why PC Assembly was so much more fun than dealing with it on UNIX derived platforms.
If you mean the history graph, try gitk (part of the git distribution, but you may need to install a separate git-x11 or similar package).
The TLDR states that the current state of modern development prioritizes developer efficiency over all else, and that user experience is way under valued.

My problem with this isn't that it places value on user experience, it is in the premise that developer efficiency is prized above all else. Deploying an app today is just as hard as it was 15 years ago. The only two things that jump out in recent memory that made a very sizable difference on developer experience were Heroku, Github, Docker. Setting up a hello world with react and a basic API takes me a day or more, where as 10 years ago with jquery this was an hour or so. Deploying an app with K8s is google scale, but takes me a week to do, forget debugging something in production.

If we've been prioritizing developer efficiency at all costs we've failed pretty massively. I personally love the idea of optimizing a lot for developer efficiency because we can do deliver more value to others at the end of the day, but there's a lot of shiny new stuff that has some reason for existing which is definitely not developer efficiency.
That's very helpful. But I'm talking about people with a special ability to remember everything after reading it once. My brother is someone like that and it's insane how much he remembers details of things that happened so many years ago.
Agree, what is going for Nix is that is a valuable tool and is very versatile. NixOS is just one application.

From OS point of view you no longer need:

- Kickstart

- Ansible, Saltstack et.al.

- Custom package repo for custom packages (if you need to customize something)

There are other areas too:

- create common developent environment, makes sure every developer has exactly the same tools installed with exactly same versions, so no more "it doesn't work on my machine"

- build system

- CI/CD

- packaging (as mentioned, you no longer need artifactory, instead you can have nix cache)

- there is also potential to use it for IaC, there's NixOps, but currently this is maybe the weakest part of Nix, it only covers deploying a box, but if you want to do something more complex, like autoscaled service it gets in the way. It is great for developing a new image though. There are terraform integrations, I didn't try them yet, might work better.

- you can configure local developer machine to use build system for local builds as well. If caching is configured, then once code is deployed it will already cache good build so it doesn't need to redo it

- for personal use with things like home-manager it can replace dot files as do more, you can have the same environment each time. Let say you change job and get a new laptop you can have it quickly set up the way you want it
>Worse, I keep seeing security issues brought up to the systemd devs and then tossed aside with "well, just don't do that" or "how is that even a problem". It's not pervasive or constant, but it's steady enough to be worrying. Obviously not every security issue raised will be top priority, but it concerns me how much of my systems are being subsumed by a project that seems to prioritize "do all the things now" over "do things securely".

I would be even harsher than that. It's not just security issues that earn "don't do that" from systemd devs - it's everything that doesn't fit their narrowly imagined use cases. You don't even get "do all the things now" - you just get "do this particular thing now". Generally with no regard for POSIX. And if you want the old behaviour back, expect to boil the oceans. Exhibit A: https://news.ycombinator.com/item?id=19023885
Sometimes rust-analyzer stops working. It seems to be related to how many projects you have open. I wish there was like a ui that would allow me to disable it for some projects and enable it for others.
Onestly, I always found all git interfaces (gui or text based) from just ugly and useless to totally counterintuitive.

With one exception: the only good git ui that I tolerate for its clearance is the eclipse egit plugin

https://www.eclipse.org/egit/
I do this as well — "Upgrade from image b1257 to b1262". As a bonus, you can tell every tag that doesn't fit the b-then-a-build-number naming convention hasn't come from CI.
The problem with this entire piece is, it’s based off the premise that consumers:

A) have unlimited time and memory to research every decision they make and store all that information

and

B) will make rational decisions based on said information

Both are so obviously wrong it makes me wonder if the author has ulterior motives.

Being published under the brand of Yale Law Journal gives the words more authority than they deserve.

The author clearly doesn’t understand how modern search engines nor modern advertising work. The positioning of the information you see on Google (SEO) is advertising.
That would be trivial to spot. Not the case with hooks.
I think that's widely understood to be 'sort of true'. Not necessarily a literal knot, but a geometric property - like what I mentioned, where integrating around sees a net divergence/curl/etc in any reference frame. That's the reason that QM doesn't predict exact locations for particles: the discontinuity doesn't have a location, it just exists in a region.

(I don't exactly understand if this 'is' a knot, in a sense. I guess it is.)
I did appreciate them detailing these costs.
Show HN: Goodnight Zoom – Remote storytime with isolated seniors
I think the question asked by the author at the end was already answered by Snowden.
But excellent for affiliate link abuse. :]
The Meta Engineer
I don't like to build applications that are 100% coupled to a framework. In my ideal world, Django (if it is being used) is just one puzzle-piece of my application.

Then again it will depend greatly on the surface area of your application. A small app will do fine with a single configuration file or the DJANGO_ approach, but a larger application deserves its own config.
That immediately rules out GCC and Clang…
Yep, there was even a library making the rounds recently that leverages them: https://crank.js.org/
It's interesting that both you and the other commenter took the second option for a dismissal of the grieving person's emotions. Which is not, and there is no indication in the text that it is one. It does acknowledge the pain (also by explicitly sharing a personal experience) and then proceeds to reframe it into some common occurrence that can be overcome in due time.

I think the keyword here is "common". Negative experiences become especially bad when they're perceived as unique, extraordinary. Framing them as normal facts of life helps dealing with them (think of support groups: they reframe personal experiences that might feel uniquely terrible into normal experiences inside the group).
> And in some cases those writings predate the fall of the Soviet Union.

That would explain some things, then. Indeed, those writings have a lot more in common with the pre-Soviet "nihilist" movement than anything relating to anarchism as it would be understood today.
Keep in mind that Rust was already trying to figure out what the language itself was supposed to be and even if the whole lifetime analysis would work once they landed on it as a possible solution. Making a compiler suitable for an IDE from the beginning is much harder (but can inform language design). If you compare the output from rustc 1.0 to any recent version you will see how much of the work needed for a production compiler is at best tangentially related to what people consider the raison d'être for a compiler.
What does that graph let you do that you cannot do now?
Advanced React Patterns: Lessons from the OS Community [pdf]
Could you not see the $4 disappearing on the GP scenario?
ImageNet Classification with Deep Convolutional Neural Networks
please change the title of this to remove the 'beware the gif' part if it doesn't have anything to do with the vulnerability really
What I'd like to know is how whether it's possible run GUI applications in their own containers. From what I understand about X, if a GUI app runs in the same context as the DE, it will have access to all other windows, the clipboard, etc.

That makes me think that Xephyr is mandatory in order to run an app in a container, but I haven't found a satisfactorily easy way to do so. Would systemd be the easy solution I'm looking for?
No we need services to aggregate and to network them. A good federation of services would be good.
Interesting, I wasn't aware that there was a such distinction in British English between the two. Thanks for sharing.

I would use the second sentence for both cases. If I needed to distinguish them, I'd probably add something like "last week" or something to clarify things.