skysight-inc/HackerNews huggingface dataset:
SPOF is something that you have to make trade-offs for and decide what you can cope with.. How much work to maintain a parallel infrastructure _just in case_ GitHub goes down for more than an hour once or twice a month? How many people actually are in the position to pivot their entire company processes around this failure case?

It can't be "remove all SPOF or you aren't doing your job". How many offices are resilient to continue working if the building power goes out?
With a lot of force anything is removable

A direct reply to that tweet shows the Apple documentation stating that they consider it non removable by the end user

https://twitter.com/aaron_bukovsky/status/150500134118950502...
> "manufacturers are responsible for 100% of everything that happens when automation is active" will stifle tech development

That's... technically true but not at all an acceptable explanation for anything. We don't just go ahead and do whatever we want to "speed up innovation". All kinds of abuse constantly gets bundled under the "only way to innovate" umbrella.

If a manufacturer advertises a feature and even charges money for it then it certainly should take responsibility for the feature working as expected and for the fallout from any failure outside of user control. The customer insures against things that are their own doing, or simply cannot be assigned to someone (weather?). The company pays for it's mistake directly, not via "market forces". That's why companies don't get out of such lawsuits by just claiming "innovation" and "the market will deal with us".

"Driving" is absolutely core to a car. It's not a GPS where the manufacturer can or should be able to just say "we take no responsibilities for the outcome of a GPS or (self)driver malfunction".

If the insurance on your car suddenly triples because the stuck accelerator pedal caused accidents, you're now left with a car which is not only terribly expensive to operate but also impossible to sell because the expense follows the car. All because of something the manufacturer caused. And that will also stifle innovation in all kinds of ways.
Call your doctor's office, tell them that all CPAPs are currently facing major supply shortages. Get them to reissue the Rx for "*pap machine capable of range [x-y]mmH20". It should be ready by the end of the day.

Then go buy anything you can. If you're a mouthbreather at night, get a full face mask and a humidifier.
Up until recently, I was the steward of a large, distributed, and profitable app that used no containers. The infrastructure was managed with packages and puppet, and it worked well.
Why PureNix?
50% sparsity and rated at 700W. The new DGX is 10kW!
Yes. To pile on, if you're playing a First Person Shooter (FPS), you want at least double the Hz. It makes a difference. Additionally, there are other factors that gaming monitors offer such as brightening darker areas that are around a brighter area.

But in general, this monitor, though it's impressive, does not have the features needed for gaming.
Even if you do unsubscribe successfully, they will periodically re-add you and send you marketing spam without your permission. I've unsubscribed from emails from cfmarketing@cloudflare.com so many times over the years. I've even sent them emails asking them to stop, but they just ignore me.
I've had the 5K LG 27" monitor for about 5 years now and 4K monitors just look blurry now. Feels like you can count the pixels even though you can't.

Reading VSCode off this monitor feels like reading analog text on paper. It's amazing for eye strain. Really doesn't feel like you're staring at a screen all day.
What was the methodology around asymptomatic covid cases and cardiac outcomes?

This seems like a sensationalist claim.
Yup. After all this isn't downtime, its "degraded performance":

> Git Operations is experiencing degraded performance. We are continuing to investigate.
> Speaking of which, shall we start a discussion on climate science? ;-)

Here's a Monty Hall explainer. Will a plane on a treadmill take off? When you shower, do you explicitly wash your legs? Did you know that 0.999...=1?
This is why I have a comically large 43” 4k which I operate at 1x. It’s roughly the same density as a 27” at 1440. High DPI is nice and all, but I’ll take more space to work over pixel density any day.
Don’t obsess over this. It’ll distract you and stress you out, which comes with its own health risks. None of us get out alive anyway. Go live as healthy a life as you can, find happiness, and help others when the opportunity presents.
You don't really ever need >60Hz for editing though. You're working with 60fps, at most, but even more likely 30fps or 24fps.
Many years ago I worked at a place that deployed thousands of bare metal servers. We were effectively running our own cloud before the cloud became a thing.

The way it worked was simple. We created our own Red Hat variant using a custom Anaconda script. We then used PXE boot. During OS install this script would call back to our central server to provision itself. You can do that a few ways. If I recall, we baked in a minimal set of packages into the ISO to get us up and then downloaded a provision script that was more frequently updated to finish the job.

This is still a fine way of handling horizontal SaaS type scaling, where you do a sort of white labeling of your service with one customer per VM. Swap Postgres/MySQL for SQLite on each node and everything is just stupidly simple.
Any fudge factor with a continuous effect on the output that covers the range of interest can be used to adjust a given output to an output of choice.

For dark matter, one of the problems is that any given instance is allowed to have whatever amount of dark matter gives the output we want. This makes the math work out great, but weakens its predictive power.
A more accurate headline would be "it spares 93%–97% of people," though the interview meticulously omitted almost all quantifiable information. The hazard ratios in the paper smitty1110 cited https://www.nature.com/articles/s41591-022-01689-3?s=08 are mostly 1.49–1.85, which as I understand it means that people with covid were 1½–2 times as likely to experience the condition, pericarditis or stroke or whatever, than thr control group. The exceptions are things that normally happen only once in a lifetime, like cardiac arrest (HR=2.45), so we're still talking about a tiny fraction of people.

This justifies the statement in the paper's abstract, "Our results provide evidence that the risk and 1-year burden of cardiovascular disease in survivors of acute COVID-19 are substantial," but (unless I'm misunderstanding the paper) shows that the interview headline is an irresponsible, sensationalist lie.
> So essentially I'm interesting in knowing how people find ways to reproduce the value these technologies offer, what they instead rely on, which things they leave on the table

It's interesting that you're not interested in what they get by not using containers...
It’s been here. Two weeks ago it was 10-20% of new infections. Now it’s half, but the new infections is down 20% over the last two weeks. Compare to Omicron in a similar time frame - Say December 7 to 21. Entirely different situation
If you're referring to cases of myocarditis caused by vaccination itself, the cases are negligible: 2.3 per 100,000 [1]. Compare that with the apparent near-certainty of heart damage (and likely brain damage) if you contract COVID while being unvaccinated, and the decision to not get vaccinated is not just selfish but self-destructive.

[1] https://www.nejm.org/doi/full/10.1056/NEJMoa2110737
depends on what kind of scale.

I used to make online games and our gameservers at launch were in the order of 100,000 physical CPU cores and about 640TiB of RAM spread across the world.

But we did this: On windows, with a homegrown stack, before kubernetes was a thing (or when it was becoming a thing).

With the advent of cloud we wrote a predictive autoscaler too. That was fun.

I don't work there anymore, and they moved to Linux, but they're hiring: https://www.massive.se/

You can learn a lot from a technical interview ;)
Looking at the title, I am sad to see the discourse in research sink to this level over the last few years (well, I think so – perhaps it was already at this level before?).

Honestly, it's hard to blame the author(s) for using such a clickbait title when Governments across the world have done precisely the same thing by trivializing the effects of a largely unknown disease, banning public health measures, or declaring the lifting of public health restrictions as a "Freedom Day".

I don't have a great solution for this – perhaps just that we should all tend towards discourse that is a bit more dry and phrased in terms of data; and steer it back to that phrasing when required.
This is something that even the Docker core team is not entirely clear on (either they understand it and can't explain it, or they don't understand it).

The RUN command is Turing complete, therefore cannot be idempotent. Nearly every usable docker image and base image include the RUN command, often explicitly to do things that are not repeatable, like "fetch the latest packages from the repository".

This is all before you get to application code which may be doing the same non-repeatable actions with gems or crates or maven or node modules, or calling a service and storing the result in your build. Getting repeatable docker images usually is a matter of first getting your build system to be repeatable, and then expanding it to include the docker images. And often times standing up a private repository so you have something like a reliable snapshot of the public repository, one you can go back to if someone plays games with the published versions of things.
I‘m called a principal engineer in my organization (I know that can mean everything or nothing) I like to use code review requests and sometimes gates also to put a fence in front of my ego. Also this is a great way of sharing knowledge. I had great sessions where questions about X and then answers verbally or in text suddenly put stuff into different perspective. Sometimes I realize that my solution might be to complicated or an more generic, performan, (paste fancy adjective to describe your code here) is easy to achieve.
Okay,so what's a better way to do error handling?

Returning an Either<Result, Error> is pretty much the same thing conceptually. Either you propagate the error or you handle it.
Thank you so much for Appwrite! The community on Discord is very helpful and the self hosting guide is great. Very unlike my terrible experience with Supabase who seem to do their best to cripple the self hosted option
California solved this by making speed limits not specified explicitly by the CVC unenforceable if they aren't backed up by a traffic survey. This will still result in places where the speed limit drops and local enforcement may try to profit from the drop. However, it stops local governments from reducing the speed limit arbitrarily for the purpose of creating a revenue stream.
I had chest pains for the first time in my life in 2021 and I’m in late 20’s. Doctor couldn’t find anything. Felt much better after a month. But it came back after getting a booster.

I had COVID confirmed in 2020 with no such issues. For me, as far as i can tell, the chest pains are more correlated with the vaccinations. I’m rather grumpy at the idea of getting additional boosters.
Or it could be that you just became old and don't want to learn new things anymore ))
1Password 6 for Mac won't fill or save in Chrome 99.0.4844.74 or later
The inspector is a chartered engineer, and is liable if your building don't confirm to the fire code.
It depends. Are you at work/university? Then that is a different Microsoft account than a personal Microsoft account. I think. Some Microsoft login screens won't let me log in with my work account even though they look the exact same as other Microsoft login screens.

The mind boggles.
Mind if I ask why you would really like to do it? It sounds like you view programming as just a job. A lot of the people who work on this stuff in their free time just view it as a hobby that they do for fun, not as a second job (although there are people like that, too). Why would you "like" to do something you apparently don't enjoy, and apparently would only do if you got paid to do it? I'm not being snarky, I'm honestly asking.
In this case the hedge was going the other way. They hedged their real long position with short futures. The market broke and they were in a position where they were losing money as the price of their real asset was sky rocketing.

This is because of the natural limits of hedging short positions.

Circuit breakers aren’t designed to protect traders from betting too much, they are designed to prevent the market itself from breaking in unforeseen ways.
Do remember that television got its start as a vertical medium. Mechanical TV scanned vertically in the days of the Nipkow disk.
> Native UTF-8 in memory makes character indexing a non-constant time operation

The only reason that Java's UTF-16 has constant time indexing is because they use a braindead definition of character which is "UTF-16 codepoint".

If you want constant time character indexing you need to go UTF-32. But obviously the downsides are too great for most users. So in practice everyone uses UTF-8 because it is usually the most memory efficient.

Plus it turns out that character indexing isn't actually that common of an operation, so it is really the right move for almost every application.
That article is such a classic. 77 years later people are still trying to build what he described there.

I was sniffing around with GitHub Projects (beta) in the browser network tools the other day and spotted "memex" in the private API URLs they were using!
I'm not much into video editing, but is it not useful that 120 hz is a multiple of 24, while 60 hz is not?
>There's no need to sacrifice in resolution very much either.

I'll never understand why the display industry went went with 720/1080/4k/5k etc. (And the camera industry with another, but I digress) — but:

4k: ~8.3 megapixels

5k: ~14.7 megapixels

That's a huge difference in resolution.
Vanilla Conquer Is a Port of Command and Conquer for Amigas
A good memory might lead you into evil? Are you being serious?
What you're asking for is an essay on comparative devops architectures, with a focus on k8s alternatives. I think what you'll find is a lot of ad hoc persistent systems that tend to drift over time in unpredictable ways, and take on the feel of a public lobby if you're being generous, a public restroom if you're not. So what you're asking is really a sample of these ad hoc approaches. What I think you'll find are a few inspired gems, and about 1000 bad implementations of K8s, Docker, Salt, Terraform and all the rest.

The case that always interested me is the service that can really fit on one machine. Machines are truly gigantic in terms of memory and disk. Heck, I worked at BrickLink which ran on two beefy machines that serviced 300k active users (SQL Server is actually quite good, it turns out). (A single beefy server is a really great place to start iterating on application design! PostgreSQL + Spring Boot (+ React) is a pretty sweet stack, for example. By keeping it simple, there are so many tools you just don't need anymore, because their purpose is to recombine things you never chose to split. I can't imagine why you'd need more than 16 cores, 128G of RAM and 10T of storage to prove out an ordinary SaaS. That is a ferocious amount of resources.)
Python should really have done this for 3.x. The breakage thanks to using the system default locale is hard to overstate - PYTHONIOENCODING winds up being a bit of a PITA for writing cross-platform code.
> The idea disparate outcomes between genders are "fair" isn't supported logically or evidentially

Can you link to a prominent CRT advocate speaking up about white men getting harsher sentences than black women? Otherwise I don't believe you when you say they don't consider this fair. The times I have argued about this they always start bringing up culture or genes to explain the differences, never that men are less privileged under these circumstances.
It seems incidents like this with the big providers are becoming a lot more common. Wonder why that is
The VESA local bus is dead, let it go...
Github is a platform that comes with all platform-related risks, i.e. operational risk of having the whole development and SDLC lifecycle blocked, creating a vendor lock due to using some unique github features, inability to rely on third-party dependencies hosted on github.

There are a couple of strategies one could rely on to mitigate the risk of github downtime:

- create a map of features between github and competitors, find the common denominator and risk accept anything that is unique to github but viral for your business/product;

- maintain a primary self hosted instance of gitea/gitlab/sourcehut and use github as a mirror;
- use github as a primary platform, maintain mirror with public gitlab and switch to gitlab in case of outage;

- if github is used beyond its primary purpose(git hosting) put some efforts to maintain the same features in gitlab/gitea/sourcehut, i.e. use CI features of both platoforms and push releases and artifacts to both of them so that end users have the choice.

- separate concerns and not go all in with github as a platform for the whole SDLC and project management and instead use different tools/platforms for different purposes.

Yes, it takes more time for the initial setup but it quickly pays back.

The above applies to those cases where your products need to be hosted publicly.
Unlikely, similar to anything else you throw in the recycling bin.
No, but I think how people express themselves to future colleagues on a mailing list says a lot about how they think.
Indeed, neutrinos appear to not be completely understood, https://en.wikipedia.org/wiki/List_of_unsolved_problems_in_p... -> ctrl-F
I just tried Nix yesterday for the first time in order to play with reactivated. Was surprised by how simple it was to get it running. Made me think that perhaps containers are not as indispensable as I thought.

And reactivated is awesome, by the way. I just worry about how brittle it will be as both Django and React evolve.
I used Lofta. They were much more interested in selling me their CPAP machines than explaining the results to me. (I was so borderline, CPAP would not be the first treatment anyone would recommend.)
> Not sure what you mean by higher kinded monads

The FP term of art I was forgetting yesterday was: algebraic effects. Hooks as a whole are trying to model algebraic effects. Algebraic effects are still raw and new in a lot of FP languages. They are hard to reason with even in research languages designed entirely for testing algebraic effects work. The one time I saw an example of trying to model algebraic effects in Haskell it used a half-dozen or more GHC extensions including GADTs on top of monads. (GADTs applied to normal types create higher-kinded types. "Higher kinded monads" was a bit metaphorical, but not the worst description I could have come up with for how algebraic effects looked to me how I saw them modeled in Haskell that one time months ago.)

I wish what React was trying to do was just dumbed down Arrows or Observables. From what I understand of how things like React Concurrency and React Suspense are built to work they are doing a lot more reasoning under the hood about the hook effects than just the raw arrows would imply. I think it is an interesting big swing. I also realize that using ideas from way out in Research Land in a non-type-safe language is a huge risk and liable to create a lot of footguns (as it has).

> I'm not a fan of the pure JS implementation the react team did, I wish they went the compiler way like solidjs did. It results in an API that is close enough to react and works faster and without gotchas (or hooks rules).

I have mixed feelings on this. Pure JS has some advantages. While hooks as they exist offer some footguns, they also allow for some flexibility when you need it (sometimes, very rarely, you do need a closure around a local variable that is not intentionally in the dependency graph). Admittedly right now a lot more people are likely to succumb to footguns than need the flexibility. I think some of that is a balancing act that hooks and especially useEffect are very low level "assembly language" in React and the impression I have is that they mostly were never entirely meant to be used to the extent of writing say 100% of one's business logic in these low level hooks and instead were always intended to be lego building blocks in "higher level" hooks. (Related in part to how in React you aren't likely to build entire components' VDOM by hand in JSON notation, you'd probably use JSX or TSX.) Right now the React community maybe isn't using or building enough "higher level" hooks because the low level hooks also seem to have created a decent "good enough" local maxima hill that "current wisdom" says to die on that hill ("just use hooks, you don't need redux") rather than search for a better mountain.

I think the Typescript wrappers in the article here are helpful. I think the article's reminder here is a useful one that just because you could do everything with raw useEffect doesn't mean you have to and that there are a number of good state management and service layer libraries that are still very useful in React post-hooks.
So, we're about a 25-50% memory increase off of being able to run GPT3 on a single machine?

Sounds doable in a generation or two.
I'd do exactly this if I were worried about losing connectivity
I haven't used R enough in the last 10 years to have an R-specific opinion. And to be honest it was more an unlearned statement on my part as it was an "ew, Excel" response and not thinking about the underlying workflow.

In the intervening time I've become a large advocate for the pattern of chained operators. So I'd imagine I'd enjoy piping in R. And if that means I'm emulating a common Excel workflow, that's fine. I won't have the childish response of "ew, Excel" :)
What's really concerning is if this turns out to be true, Okta has, at a minimum 26k (yes), customers right now. A simple enumeration of subdomains reveals this. I've put them here in a paste: https://ghostbin.com/K7tIA
You can ship to iOS with Java actually. That's the business model of Gluon:

https://gluonhq.com/

It's a combination of JavaFX, a custom controls library that implements Material Design and GraalVM native image. Whether you want a non-native UI toolkit on iOS is a separate matter, but it can be done technically.

In fact, you can ship JavaFX apps to the web too. It doesn't compile to megabytes of JS either - instead, the JavaFX app runs on the server and the UI is projected to divs and SVG elements on the fly. The browser provides native scrolling and text selection. If you have low latency to the server (e.g. same continent) it can work remarkably well. Check out https://www.jpro.one/ - the entire website is a JavaFX app.
https://twitter.com/eastdakota/status/1506160414106611712

They didn't want to get into the market (until now?) by the looks of things
Am I misunderstanding? UTF-16 can represent all Unicode characters, not just the BMP.
He updated the page to say basically "if you use a DisplayPort cable with the right connectors that's rated for the display resolution then the display part works".
The 'privacy vault' feature sounds interesting - do you have any more details how that might work?
CUDA and related software/libraries only work on Linux or Windows.
Surprisingly I am having the same symptoms. Like I can feel chest pain during cycling and hours after I am done. This was not the case earlier.

I haven't got it checked yet. I am gonna do that soon.