skysight-inc/HackerNews huggingface dataset:
>I dont remember anybody foreseeing that. Zero. Not one analyst. Ive only heard retrospective justifications for why it happened which any idiot can come up with.

It makes sense (in retrospect; I am certainly not an analyst who predicted this beforehand).

Right now, it is more or less impossible for any Russian to a) use the dollar to buy anything from outside Russia, and b) travel outside Russia to buy anything in the first place. That greatly reduces the demand for exchanging rubles for dollars, whether via official or unofficial means.

Consider Argentina, a country that for years has had its own serious economic issues. A huge skew between the official and black-market exchange rate for hard currency, such as in Argentina (the "dolar azul"), exists because a) there are capital controls but b) it's still possible to use those dollars/Euro/Swiss franc/whatever. Argentineans are free to use the US dollar to buy things, both inside and outside Argentina. This doesn't apply to Russians.

You wrote elsewhere:

>Im also really skeptical of the position that its an irrelevant economic indicator only when it goes in the opposite direction you expect it to. Everybody was saying the exact opposite when the ruble was plunging.

Agreed. It seems like Western analysts were completely wrong on both Russia's military strength versus Ukraine's, and the impact of Western sanctions on the Russian economy.
I wrote https://github.com/Freaky/zfsnapr a few months ago so I could finally have point-in-time consistent Borg backups with ZFS snapshots, without having the mess of teaching Borg where every .zfs directory was.

It recursively snapshots mounted pools, and recursively mounts snapshots of the mounted datasets into a target ready to point your backup tools at. I do so via a chroot so I didn't need to make any changes to my Borg setup - just to how I run it.
I hope this is not the end of it. There is a lot of research that could be brought to bear on understanding this, and a lot of researchers that would be very interested.

My guess is it boils down to something relatively trivial. 90% accuracy is not very good, it means there is some signal but there are also a lot of exceptions. The same way you can "predict" who is a criminal or gay or Democrat from a picture, there may be some loose stereotypes you can make that get you good enough correlation for an accuracy you can claim is good. But the model is not really learning a causal difference between the classes, it's more of a parlor trick. I'd love the opportunity to study how it works in this case.
I think you can both praise China's intentions and strategy while condemning some of their inhumane enforcement tactics. Zero-COVID is a great ideal, and far better than the USA's incoherent strategy. Different countries in the world tried tactics on the spectrum from human right violations(China) to enforced mandates (Aus, NZ?), to voluntary, unenforced, ignored mandates(USA). But nobody was actually very effective because we can't solve human nature's unwillingness to take collective action for everyone's benefit.
If anything, this drives home the point that debates are never about finding the truth. But what is the alternative? I don't know.
Unless when typing your password you deliberately use different fingers than you would when typing normally
Now you can order a third round of free test kits from COVIDTests.gov
Never said anything about approving your own prs nor bad actors. It’s just basic human psychology especially when money is involved and if you’re going to pretend it does not exist you got another thing coming
I have a couple basic android apps. Straight out of college I think they helped me get a job. They showed that I could build something of decent quality, even if it isn't fancy, from start to finish.
You are underestimating the reliability of modern servers by a lot (otherwise your EC2 instances or random VPS would randomly reboot way more often than they do since if the server crashes the VM is still gone).

Also failed PSUs or hard drives don't require downtime, since those are hot-swappable and redundant in servers.
If you want to optimize for (physical) hands-off operation you can even add an extra 1-2 hard drives that are configured as hot spare that the RAID (be it hardware, software or ZFS) will automatically use in case one of the active ones fails.

And the performance difference between dedicated hardware (be it dedicated server or your own) can be quite staggering compared to what you actually get from the cloud providers.
Collection of Sun Workstation boot logos
Previous discussion: https://news.ycombinator.com/item?id=31347478
Correct, but I-bonds cannot be cashed out in the first year, and households who can't afford to save more than $10k/year probably aren't interested in having their investment tied out for 1 year.

Quite frankly, a S&P 500 index fund would serve them better than an I-bond, even during severe market drawdowns.
Load of my shoulders. As much as I hate to be beholden to Google, both my parents (in their 70s) use our gsuit account with custom domain and migrating them to a different service was … well, you know how it goes. The cost was a bit much.

So thanks Google.
Your logic is terrible. Your argument would only make sense if he didn't have an excuse for the previous sale, but he did.
There are good arguments for using either 0- or 1-based indices. As you should be aware, there are many languages on each side.

While preferring one over the other is perfectly fine, I question the intellectual honesty of anyone claiming incredulity about opposite choice.
The Chicago Neighborhood That Will Generate Its Own Energy
I was hoping 13.1 has wireguard. Cannot find it.
I thought I did? https://json5.org/

Parsing json as a human is unambiguous and simple.

Parsing yaml and toml is full of ambiguity and readability problems depending on where you're reading it.

The only people who think json is a bad format are the type of people that think semicolons are the problem. They're just not.
Awesome, how did you do that?

We use plenty of short-lived FreeBSD agents for our (AWS-hosted) CI builds, so a 2x speed up would be very welcome!
make sure you give Deno a test run too. I think it could be great for some applications already.

(Specifically cases where you want the project easy to jump into with almost no toolchain setup.)
Let's Encrypt is a CA. Their involvement with web cryptography begins and ends with signing certificates which are used for authentication -- they have no say over what cryptography actually gets used for a TLS connection.
The very first computer I used was a FreeBSD machine sitting in a small dark closet of my parents' house. Now that I'm all grown up, I run it on a Raspberry Pi and it makes me very very happy.

Such a joy to setup—so simple, so stable. Really happy to see that it keeps getting some love. :)
Actually, I think I answered my own question.

That tool is so good because it leverages the entire eco-system of IDE it is running in. The resulting merge panel is as powerful as any editor window in the IDE. It has code inspections, it detects missing imports, it does everything.

It might be the case that ripping the diff/merge tool out of the IDE would result in way inferior product than we get when we use it within the IDE.
I think the problem is that you included feelings in something that was clearly technical. The comparison they were making was 1/6th the spec. It was a technically inappropriate comparison. It could only support the claim that these features were removed to increase water resistance.

The comment I made doesn't require that I push, or be for against, some higher narrative that you seem to see me as having in my head. It's perfectly valid to criticize the technical merits of an individual comment. If you see that as weaselly, then tribalism has infected your mind.
I’d add Traefik to that list! Maybe not quite as simple to get up and running as Caddy with LE but still pretty smooth.
Leerob and co are fantastic :D
The feedback we got from the Vercel team while building the integration was invaluable :D

Also feel free to join our slack for more feedback :D
This reminds me of the Pixel Qi screens that promised cheaper notebooks with really long battery life (and was used in the OLPC.) Today's backlit e-ink screens do seem more promising, although the versatility of a computer using a slow refresh screen really hurts it.

For the right price it could be useful and find its niche.
Personally, if I get a small PR, I review it in about 30 seconds. If I get a giant PR, I review it in a matter of hours. You are usually aware that such things are coming; that's why people provide daily-ish status updates and that sort of thing.

I have also found that high review latency begets large code reviews. It's kind of a vicious feedback loop. If you always review PRs immediately, people are less afraid of splitting up their work, and PRs will become smaller. (It's hard to "stack" reviews, so people avoid it. That means that 3 PRs become 1 PR, so they can be mentally done with the task and start something brand new while waiting a week for your code review. The alternative is hoping that the bottom of your stack is approved without any requests to change anything, but what happens is that large changes are requested and the two floating PRs are now impossible to merge back in, or are irrelevant. If the bottom of the stack could be reviewed in an hour, then all that work wouldn't have been wasted, and it reinforces the good habit of doing 1 small thing at a time.)

I look at all of this as a systemic issue, and not a personal issue. The team needs to set an aggressive SLA, guided by what the engineer is expected to do while waiting for a review. Then engineers need to treat the objective seriously; code review is as important as any code you're writing. That's why you're part of a team, and aren't a 1 person army (which is a totally viable approach; I write a ton of code in my free time by myself, but I don't necessarily think that that's how I should behave at work.)

Personally, I have Github's Slack notifications on, and almost always start the review as soon as I get the notification. I know that the person waiting for the review has no work to do other than to build on top of this foundation; the less they do without feedback, the better. (Plus, they want to get their code Out There, that's why they wrote it.) I don't think your organization has to be that aggressive, but I'd aim closer to "hard interrupt" than "within 1-2 business days". (No, I don't review PRs that come in at 7PM on Friday night. Those wait until Monday morning.)

The other metrics listed a few comments above are really a function of organizational policies. Make your releases easy, so you do them often. Make sure that your PMs know what users want, so you don't implement code and throw it away. Make sure that CI is fast, so there isn't a delay in pushing to production. And make sure your process is realistic. My team used to spend a lot of time manually testing stuff in staging before releasing to production. It never found any issues that the test suite didn't find, and we prefer the automated tests anyway, so eventually we just made every commit to master a deployment to production. Click the "merge" button and it's out to the users. No unusual number of surprise production outages, just a vastly reduced time from idea to being in the hands of the customer. (Code reviews ended up being the limiting factor. People really don't like doing them!)
I still prefer to use Julia, but this is a good summary of the problems that affect me personally as an experienced user (although I do like dynamic typing for most of the work I do).
Especially since you can’t even edit text directly in it. WinMerge is pretty much the only Windows app I miss now that I’m using MacOS full time.
The manufacturer downstream from Gore has a great repair service, but we've repaired GoreTex in the field with a GoreTex patch adhered with AquaSeal for larger tears and a drop of AquaSeal for pin-holes.

I agree that they could be doing a better job, as can we all.
I have never been as excited in a movie theater as when I heard that quote at 12.
This is not really accurate, it stores keys as securely as it is able to. Also the heap is not inherently insecure - it depends on other factors such as network isolation, user permissions, containers and other kernel protections.

Many things like https and ssh servers store secrets on the heap when they are in use.
I Spent a Day Without a Phone and It Didn’t Suck (2022)
Perón said a more radical version of this on camera[0]: "To friends, everything; to the enemy, not even justice"

"Al amigo, todo; al enemigo, ni justicia."

[0]: https://www.youtube.com/watch?v=WDh9M9aty4U
Maybe Tesla radar can't see any stationary objects, but others use radar for collision avoidance / auto braking and seem to do so also for stationary objects. It's harder to do from a signal processing view, but definitely not impossible.
Perhaps the keyboard could have an internal speaker that provides carefully crafted additional noise to make the keys sound more uniform (like each-other), or to sound more random (different each time).

However, if the counter-noise would get triggered first by a key press then it would not be able to mask the initial part of the key noise when the finger strikes the key surface before pressing it down.
Detection using a microphone would have the risk of false positives, so maybe a new key mechanism also including capacitive touch/proximity sensors would be needed.

And it would be ineffective against attacks that model key stroke patterns temporally.
it wouldn't have made it, as it ran off of electric power. It trailed a huge electrical cable. Which makes sense as it was operated by American Electric Power. You can visit the bucket at Miners' Memorial Park where it's on top of a hill ( which I have to visit to get cell service when I camp nearby). It's the size of a small house.
Your reasoning suggests the terms of the copyright license do apply when used as an internal tool (you'd be free to keep the code hidden otherwise) in which case preventing anyone from publishing any work derived from code under a copyleft license seems impossible. At the very least the GPL doesn't seem to allow you to create a derived work and require people to keep it secret even if it's just internal to the office (though I guess they could keep it secret willingly, I just see no way to legally compel them).

This seems different from something that's purely personal use. I don't think it makes much sense to force a program to show a notice its GPL licensed if you're the only one using it for instance. In fact that seems to run counter to the intent of free software.

It's possible that legal systems treat this situation differently, but I think it makes far more sense if you don't need an additional license to use stuff that's already published by the copyright holder until what you're doing starts to go beyond just personal use.
Huh, well I guess there goes my theory about the incentive. What a bummer. I would have thought that at least with search engine scraping, they would stop expending the effort once the results dried up.
Thanks for the unnecessary anxiety Google! I wish I could get back the wasted brain cycles spent contemplating how the fuck I was going to transition my family to something else.
I went to a Monster Jam show in ~2018, looks like they're still going: https://www.monsterjam.com/en-US/tickets
Boot Loader Changes

This section covers the boot loader, boot menu, and other boot-related changes.

Boot Loader Changes

UEFI boot is improved for amd64. The loader detects whether the loaded kernel can handle the in-place staging area (non-copying mode). The default is copy_staging auto. Auto-detection can be overridden, for example: with copy_staging enable, the loader will unconditionally copy the staging area to 2M, regardless of kernel capabilities. Also, the code to grow the staging area is more robust; for growth to occur, it’s no longer necessary to hand-tune and recompile the loader. (Sponsored by The FreeBSD Foundation)

boot1 and loader have been fixed on powerpc64le. 8a62b07bce7

Other Boot Changes

Performance improvements have been made to loader(8), nvme(4), random(4), rtsold(8), and x86 clock calibration, which collectively yield a significant speedup in system boot time. Configuration changes on the EC2 platform provide additional benefits, resulting in 13.1-RELEASE booting over twice as fast as 13.0-RELEASE. (Sponsored by https://www.patreon.com/cperciva)

EC2 images are now built by default to boot using UEFI instead of legacy BIOS. Note that UEFI is not supported by Xen-based EC2 instances or by "bare metal" EC2 instances. 65f22ccf8247 (Sponsored by https://www.patreon.com/cperciva)

Support was added for recording EC2 AMI Ids in the AWS Systems Manager Parameter Store. FreeBSD will be using the public prefix /aws/service/freebsd, resulting in parameter names which look like /aws/service/freebsd/amd64/base/ufs/13.1/RELEASE. 242d1c32e42c (Sponsored by https://www.patreon.com/cperciva)
Same. I recently moved to iOS and I found the Gmail app to be pretty buggy. Staring emails worked about 50% of the time, scrolling in HTML emails was very janky, clicking on a notification and reading an email didn't mark the email as read. This plus the Gsuite transition pushed me to Fastmail. I now use that plus the native iOS mail app and I have no complaints.
I was at an unpopular place yesterday sitting on the patio. The music was so damn annoying.

Regardless, I read an article that more or less describes that restaurants increase their revenue playing loud music.
If the majority want to exterminate a minority, sure. Democracy doesnt mean that they should be allowed.

If "whatever they want" means independence and self determination then yes, either you believe they should have it or you give democracy the middle finger.

Theres no middle ground there.

Some people think ukraine should be run from Moscow and fuck what anybody in ukraine thinks. Some people think crimea should be run from Kyiv and fuck what anybody in Crimea thinks. They both hate democracy.
> The alternatives are learning at the character level (way more complex

No, BPEs are more complex: you have a whole additional layer of preprocessing, with all sorts of strange and counterintuitive downstream effects and brand new ways to screw up (fun quiz question: everyone knows that BPEs use '
' tokens to denote document breaks; what does the string '
' encode to?). BPEs are reliably one of the ways that OA API users screw up, especially when trying to work with longer completions or context windows.

But a character is a character.

> and scales badly in memory/compute)

Actually very competitive: https://arxiv.org/abs/2105.13626#google (Especially if you account for all the time and effort and subtle bugs caused by BPEs.)
I spent longer times working in Turkey and really enjoyed the 40C :D
UST is down another 35% today, to 11 cents on the dollar.
Hmm, I already opted in to Google Workspace, even though I only use the account for personal use. I wonder if there will be an option to switch?
> 1. If you're off the grid, where are you going to get power to run this?

There are many sources of off-grid power. Solar, wind, hydro being the big three.

> 2. If there's no power grid or internet, you probably have much bigger problems than "how can I browse an offline copy of Wikipedia." Those problems would probably last longer than you want to schlep around and item like this.

s/Wikipedia/GIS
Transparency of the blockchain is only a temporary flaw. Better solutions exist (Monero, Zcash) or are being actively developed (Zk Rollups).
Something more like the dividend model would be interesting to me. I'd be willing to do some small scale funding like that.
If the dhcp server supports RFC2136, you can use that (isc-dhcp does). You could also run dnsmasq with dhcp+dns then put DHCP clients in their own zone and configure kittendns with that zone (NS dhcp.my.domain -> dnsmasq-ip)
I'm assuming "this domain" refers to scientific computing. My theory is that the typical scientist crunching data is just proficient enough to write specialized code for themselves but doesn't have time to develop a scalable, "professional" solution. Very large organizations tend to have capable internal systems but they may not make it into public view or they are too specific to their niche.

On the other hand you have premade, proprietary packages that can become quite popular (Matlab, JMP, etc.) for non-programmers, which dilutes the user base.

That leaves us with things like "R" (horrible, like you say) or Julia (eternally promising) or Python (stitch together low-level Fortran and C code). The latter solution is winning, it seems.
since facebook named their optimized php compiler "hip hop"

can we call this optimized ruby compiler "reggaton"

All jokes aside, they should get in contact with teh guys at gemstone software. I remember there was work on a highly optimized ruby vm called "maglev". I wonder whatever happened to that.
Tom Cruise wasn't in Red Dawn, as I recall - maybe thinking about Charlie Sheen (the discount Tom Cruise)? Yes, wheat harvest fails in Ukraine, coup in Mexico, NATO disbanded. Cuban paratroopers in the first wave if I recall correctly. Still a highly enjoyable movie - one of the best eighties adventure flicks.
Perhaps someone here can answer this, but why are wide-bandgap materials like SiC and GaN considered so promising for power applications but not more traditional semiconductor applications (CPUs, GPUs, SOCs, etc)? Seems like the ability to perform more efficiently and at higher power efficiency should be useful there too.

Is it just an issue of not being able to make crystals of the same defect-less purity that we've achieved for silicon? And is it a fundamental issue, or one that can be overcome by developing a similar level of expertise?
Is this actually broken in MSVC, or is it broken because Julia is using mingw and linking to an ancient version of libc on windows (which is intentionally left as-is for back-compat)?

(I genuinely don't know, but the linked issue mentioned mingw specifically)
Solution: get a keyboard loud enough that you make whatever mic is listening in clip because it's so loud.

If you can't get key switches loud enough, I made a little Emacs Lisp snippet that plays a tone on every keypress. Example is for macOS, but adaptation to *nix should be trivial. https://gist.github.com/ashton314/4ca20e6e040f07aef58a05f42d...
Can you save a version flag and support both until you write the migration logic? That way at least new users benefit
Really don't know but this page, for California corporations, seem to say that's one way.

https://www.sos.ca.gov/business-programs/business-entities/s...
Same boat, of course not. Google can take a hike.
Absolutely not. No social media company should take a set of user's private data and "open the data" (especially just because some blowhard is trying to find any reason to back out of a deal). Even without the "open" bit, they shouldn't be providing that data to a third party.
I would love to know this too. Should have waited it out...
Lots of things are being rewritten. Remember we just released a new neural network library the other day, SimpleChains.jl, and showed that it gave about a 10x speed improvement on modern CPUs with multithreading enabled vs Jax Equinox (and 22x when AVX-512 is enabled) for smaller neural network and matrix-vector types of cases (https://julialang.org/blog/2022/04/simple-chains/). Then there's Lux.jl fixing some major issues of Flux.jl (https://github.com/avik-pal/Lux.jl). Pretty much everything is switching to Enzyme which improves performance quite a bit over Zygote and allows for full mutation support (https://github.com/EnzymeAD/Enzyme.jl). So an entire machine learning stack is already seeing parts release.

Right now we're in a bit of an uncomfortable spot where we have to use Zygote for a few things and then Enzyme for everything else, but the custom rules system is rather close and that's the piece that's needed to make the full transition.