skysight-inc/HackerNews huggingface dataset:
> having the ‘friction’ of defining a gRPC, GraphQL or REST endpoint is leading to more thoughtful API design

Make devs slower so they code smarter?

More friction is just that, it just frustrates devs it doesn't make them code better.

tRPC enables good teams to ship faster. Less friction means doing what the team was already going to do anyway, but faster.
Doom prophecies aside, I do think that some deflation protection in the form of US 10 year bonds (or longer, if you have the stomach for it) may be a wise idea. The 10 year yield hasn't been this high since before 2008, offering a decent upside should we get back to the low rate regime. Although of course if this is a 1960s or even 1970s replay then these bonds will cheapen to single digit cents on the dollar.

Chart for reference - always good to keep in mind the big picture: https://www.macrotrends.net/2016/10-year-treasury-bond-rate-...
That's why they call it Big Data
> how did they implemented it if you know?

It's relatively easy:

a variable:

CL-USER> foo

an operator with no arguments:

CL-USER> (foo)

an operator with one or more arguments:

CL-USER> foo 1

CL-USER> foo 1 2

CL-USER> foo 1 (+ 1 2) (+ 3 4)

and so on.

> Hemlock can use commands named more "english like"

That's like Emacs (called Zmacs) on the Lisp Machine does it. It does not use hyphens at all. I can't remember how the first Emacs, the TECO Emacs, did it.

M-x compile-changed-definitions-of-buffer

is then

M-x Compile Changed Definition Of Buffer

Basically instead of hyphens it uses spaces.

In LispWorks & Zmacs one enters the command M-x Replace String <return> and then the editor prompts for the arguments.
"""There have been 2,121 tests done since the first in July 1945, involving 2,476 nuclear devices. As of 1993, worldwide, 520 atmospheric nuclear explosions (including 8 underwater) have been conducted with a total yield of 545 megaton (Mt): 217 Mt from pure fission and 328 Mt from bombs using fusion, while the estimated number of underground nuclear tests conducted in the period from 1957 to 1992 is 1,352 explosions with a total yield of 90 Mt.[1]"""

- from opening paragraph of https://en.wikipedia.org/wiki/List_of_nuclear_weapons_tests

[1] https://doi.org/10.1007%2F978-3-662-03610-5_17
>when exactly are semantics (the meanings of things) not important?

arguing over meanings when we should understand the meanings tends to mean you're nitpicking instead of clarifying. There's clarification and then there's bike shedding.
It's not clear that we have technology from outside of earth. These statements are from a guy who has said that another guy told him about aliens.
Does anyone know how Mountpoint compares to s3fs-fuse in terms of performance and features?
It was a coincidence each time. The problem is that epidemic waves last a certain amount of time, and politicians tend to enact lockdown after a certain amount of delay because they want to be sure it's really going up and have to wait a few days for the announcements to propagate etc, and then you have to wait a short period before you expect any impact anyway. And then that's when the epidemic naturally goes into decline.

It's trivial to prove this because waves last roughly the same amount of time everywhere, so you can just compare places that went into lockdown with places that didn't and see what happens. The answer is that the waves are the same size and shape regardless of what governments do.

You can also do a regression analysis on "strictness indexes" and case counts, which also yields no correlation. There are such studies:

https://www.frontiersin.org/articles/10.3389/fpubh.2020.6043...

"Stringency of the measures settled to fight pandemia, including lockdown, did not appear to be linked with death rate"

https://thefatemperor.com/wp-content/uploads/2020/11/1.-LANC...

"Rapid border closures, full lockdowns, and wide-spread testing were not associated with COVID-19 mortality per million people"

But you don't need studies. The fact that Sweden didn't lock down and yet has some of the lowest COVID mortality in Europe is decisive. Claims about the effects and necessity of lockdowns were universal and made no exception for Sweden, so the existence of even a single counter-example disproves the theories.
Let’s just throw all this overly political AI stuff to the side. It sounds like what many people have been doing with good old fashioned linear regression for…decades…would severely upset you.

When you’re doing prediction for the sake of prediction, the results speak for themselves. There is no inherent necessity for the indicators to be intuitive. There are certainly contexts in which it does matter, though. When accountability matters.

It’s, as you say, “basically just” doing exactly what it’s doing. It works exactly as well as it works. To argue that it’s good or bad based on some implementation detail is … kind of beside the point.
Oceans, marine fauna and marine flora are part of the biosphere.
https://sciter.com/
That's nice. Netflix does the same and actually beyond what I would expected. You can bring your own laptop (or desktop) or expense one from the company and install an off the shelf distro of your choice and after going through a browser based registration of your Netflix corp account, you can use it as your daily driver. All internal sites and tools work seamlessly.
i love nixos but flakes are not it
> The map of London (where I live) that I use to navigate on my phone is not in any sense the best map of London that has ever been created. It is definitely not an improvement on existing understanding, but it's a great improvement on not having a map.

But if the "map" is actually composed by a ML process parsing texts about London and arranging the place names based on proximity of mentions and cardinal direction references (this might be a fun exercise, might actually result in something that looks surprisingly like a map with the right data sources, and sufficient tuning, and absolutely won't have any real world use), people are going to ask why you trusted it.

To be fair to the authors of the original paper, their actual claims appear to fall some way short of the blog's insinuation that they were proposing that academics should actually use their model to decide to spend hundreds of hours of work replicating research papers (which would be the perfect example of misuse of ML). But what they've actually done is a very basic statistical ranking of possibly misclassified subfields without any ability to address systematic error.
The other thing they keep missing.

Where are the people with the skills to do this work? I wrote a whole post about it, but it is not like people with that knowledge exist in troves just waiting to be hired.

There are no path to learn this stuff either. Do we really expect every single company out there to build teams of sysadmin and operators from a non existing pool of talents?

It is easy to say that people can move to onprem, but orgs can barely hire the talents they need already. Sure let put even more pressure on a limited supply.
Try free clone of TC, Double Commander: https://doublecmd.sourceforge.io/
>Also, the founder appears to be of russian origin [0], which is completely untrustworthy to me.

what the fuck
> Similarly, don't make commitments unnecessarily. Instead of "I'll go downstairs and get your bear" maybe "I'll go downstairs and look for your bear." While with adults we understand that when a person says they'll do something they mean they'll put in a reasonable effort and may fail if the task is surprisingly difficult or if factors outside their control intervene, [...]

I'm not sure adults understand it either. Many times, I've seen managers calling out a team member for not delivering by the time that they told they would. So, I started to add a caveat to almost everything I say about the future: “I plan to [...]”.
I think this depends on what you’re doing. Working in software dev and using a lot of containers, anything other than Linux would be a PITA
The M1 is great, but I really dislike the limitation to 2 external displays unless you get the ultra model CPU.

I've just gotten really used to my portrait landscape landscape setup! And of course I'm an outlier so corporate IT won't buy me an ultra CPU version.

I guess that it's to force people to pay more, but it feels like such an arbitrary decision. Sure, restrict it to 2x6K displays, but I'm using 3x4K displays that the Intel MacBook Pro handles just fine.

Also, it's a real hassle trying to explain to angry developers about why their 4 year old ancient x86_64 arch docker containers won't work natively. (The containers crash under Rosetta emulation)

Compiling Emacs in 5 minutes vs 10 on Intel is really nice though!
This looks quite amazing at first glance but looking a bit deeper some elephant-in-the-room questions pop up:

1. Simple Gradient Descent is already linear in time w.r.t. # of parameters (but it is an iterative method). It seems to be missing from Table I too. This method requires waiting for equilibration, so could it be seen as another form of iterative method? If so, wouldn't the proper comparison be against known O(n) first-order iterative methods like GD as opposed to exact methods (O(n^3)) or pseudo-2nd-order iterative methods like CG (O(n^2))?

2. In 2.B.3 the paper says "Note that this includes a compilation step that scales as O(d2)". I think this needs some clarification. Is this saying that, in order to run this on actual hardware, there's a compilation step involved that is O(n^2)? Of course O notation says nothing about linear factors but wouldn't that contradict what's stated in Table I?
The Cloud Is Not Optional
wow llvmpipe looks like what i need. I still need to figure a way to lie to some other bits that probe the hardware but this is going to be helpful

But thanks exDM69, zamadatix, fayalalebrun
> Intentionally knee capping on-prem software feature wise

Or unavoidably. We have a SaaS product that's also available onprem - because we have some big enterprise customers who won't accept anything else - but there's a bunch of stuff we take advantage of in the cloud that we can't easily replicate in arbitrary onprem environments. So the onprem software ends up "kneecapped" just out of sheer pragmatism. There's not a single missing feature onprem that isn't because it would be too much effort to implement and support it.

> Stifle development of the on-prem product

Similar issue here. We have finite engineering resources, and onprem is a fraction of revenue.

> Force you to use some parts of their cloud services to make other things work

See first point.

> Poor documentation how to install/use/maintain the software on-prem or make it needlessly complex

See second point.

In short, many of the things you're saying are indeed disadvantages of onprem products today, but it's often not the result of some sort of "intentional kneecapping" or "dark patterns". In my direct experience, it has never been the result of that.
To answer your question about sorting an array: For an array of length n, where each element takes one of m possible values, there are n^m possible arrays. But there are only O(n^m/n!) possible sorted arrays, which could be crudely approximated as O(n^(m-n)). The decrease in information is proportional to the log of the ratio of the number of possible states before and after the computation, which is in this case log(n^n) = n log n. See another explanation here https://tildesites.bowdoin.edu/~ltoma/teaching/cs231/fall07/...
You are making very strong assertions, some of which I would like to question/temper/gently push back against.

I am part of a small startup, an SaaS product with 2 Million MAU. Our initial code was in Python and we absolutely struggled with it once we hit scale. Refactoring and adding features were really scary prospects.

The choice of picking Rust was taken after much soul searching and double guessing. We had even ported over one of the services to Golang before we switched to Rust. Most importantly, the choice to use Rust was not mine, it was that of another colleague of mine.

Rust turned out to be the best technical bet we ever took. Of course, since we were in fintech, there was a huge emphasis on correctness which was near impossible to get right in Python.

In Golang, we got the performance we wanted but it just had too many footguns that repeatedly came back to bite us. For context, we have a large number of very stateful and computationally intensive services running. There's a lot of concurrent mutations of shared data we had to deal with. Doing this in Golang was an absolute nightmare. Even after religiously using golangci-lint and fixing issues, we kept running into data race issues.

Rust has never given us these issues. I'd much much rather fight an overzealous compiler pointing out all my bugs at compile time rather than running into a nuanced race related Heisenbug that I need to debug in production, with millions of users' money on the line.

As for developer productivity, devs in our team are desperately pushing to port over _everything_ to Rust because of the peace of mind it gives them, pushing to production. People groan at the prospect of having to update some of the yet to be rewritten Golang code and riot when asked to deal with the legacy Python services.

There's one important caveat I'd like to add to anyone reading this and reaching for Rust. No one else in our team (including me) except one of my colleagues knew Rust when we set off to try Rust. However, we had a big advantage. That one person who had proposed the Rust refactoring had expert level of Rust knowledge.

Not all companies might have this luxury and his expertise may have been what ended up getting over all the initial humps that may have derailed us initially as everyone else was coming to grips with Rust.
I noticed this issue a few years ago looking for COTS or OS distributed schedule/process managers to replace a home grown solution to reduce some support risk.

Turns out in the two decades I’ve been in my industry everyone else has gone to ‘the cloud’, and the tooling has gone with it. Every product or project I looked at was skewed entirely toward physical host agnostic and/or single service reliability agnostic management.

So not only is in an issue with going back on prem, there’s entirely unserviced customers that cannot adopt the tooling given the direction it’s been developed.
Double Commander works natively on Linux with GTK2 and QT5 interfaces.
When it comes to blasphemy, logic does not apply ;)
They probably don't want to commit to it being undeveloped...
I found it so unusual. Sure enough they're reporting an ongoing DDoS attack.
Gameboy Leach
Everyone here talks up the cloud.

They’ve all drunk the kool aid and are cloud true believers.
> I know it’s to force people…

I’ve seen the longstanding understood technical explanation for this limitation. I can’t recall what it is now, but it seemed more than plausible at the time. Of course, ‘Apple bad’ is always going to be more viral. And, of course, you can take any hardware component and “just add…” it to max spec.
Yeah I already have a couple droplets at DigitalOcean. I just wanted to give Hetzner a try.
I think there is some miscommunication here. When I read I wanted to, that made me think that they knew about this before OP's problem. If they had made a warning post like warning - don't use render. It is a piece of poop, maybe OP would have saved a weekend.
Sounds like classic German customer service. You are wrong or have somehow used the service incorrectly until proven otherwise.
On the other hand, goroutines makes it very easy to write concurrent code. And the built-in checker for race conditions works well.

Async Rust, OTOH, can quickly become a horrible spaghetti mess that's virtually impossible to debug, and where common things such as cancellation are very challenging.

My networks servers written in Rust are unsafe.

I know they have dead locks, memory safety issues (due to usage or shared arrays and slabs to avoid allocations and work around the borrow checker), can be remotely DOS'd, leak memory (due to Rc, cycles or whatever), and have hacks to work around APIs that are not easy to use, just to make the borrow checker happy.
Doing simple things such as listening to multiple IP addresses can require a major refactor.

At the end of the day, after the excitement of having written a first version of these projects, I have a hard time understanding and fixing the remaining bugs, and eventually stop maintaining them.

The ecosystem is also unstable. Dealing with major changes, or crates that need to be replaced because of deprecation/abandon makes applications unsafe. "crap, after cargo upgrade, that doesn't compile any more. Let's randomly fiddle around so that it compiles again". The version with the new crates doesn't get tested as much as the previous one. If they behave differently, or if to get the behavior of function X, now one should call function Y because X now does something else, the application is not as safe as when originally written.

My network servers written in Go probably have plenty of bugs, but I can understand what's going on and fix them. I can dive into the code of the dependencies and of the standard library, follow and understand how things work under the hood. With Go's rich standard library, I also don't need to rely on a ton of dependencies, that will constantly be abandoned or introduce breaking API changes.

So I can stay focused on the application logic, and eventually, the Go servers are way safer from a practical perspective. And for something that must be maintained on the long term, Go also wins hands down.
"A previous BBC R&D white paper showed that UK audiences listen to 58 million hours annually via DTV radio. While these audiences concentrate on the audio, placeholder 'slates' for each station appear on screen. Not surprisingly, this makes TVs the most energy-inefficient 'radio' devices.

Market data also suggests that 3 million (11%) of the 27 million UK TV households own a FALD or OLED TV. As a'reactive' group of TV households, they would also gain from any LCGfx changes to DTV Radio, while the remaining 89% may also find smaller energy savings. Therefore, regardless of the screen type, any new LCGfx-style radio slates would have the potential to save energy in millions of DTV radio homes.

It's important to note here that the original DTV slates were designed in an era of mostly non-reactive TV screens, which reduced brightness by filtering an 'always-on' light. ..."
The problem I have with a lot of parenting advice is it's always written by someone with fewer than 30 kids.

Now I'm not saying you don't have a right to say anything until you have enough kids to fill a bus, far from it.

But the advice you get is always variations of the same. Try to be patient, try to be reasonable. If you need to make threats, have it escalate slowly. Follow through on consequences.

This works for most people, because if you have under 30 kids, you have a good chance of never getting a kid who is on the 1% level of difficulty (Rule of 1/3n).

In fact my first kid was normal in that sense. Ask him to do something, he does it eventually. Not too many issues. Patience and reason prevailed, I didn't even have to make a lot of threats before he just got it. At that point perhaps I should have written a book about parenting, because it was working great.

Second kid, no. It's not that the kid doesn't understand the trade: clean up first, then get read to. It's that the kid objects to the very idea that there's a deal. I'm being unreasonable in presenting this Faustian trade, no kid should be held prisoner until they unwillingly clean up after themselves! Consequences? Sure, try to hold to the things you said. No dinner, take away toys, stern voice, shouting.

Nothing helps. I can't be the only parent who has tried all the variations of "be reasonable". But that's also where the advice ends. I guess in programming we have the same problem: you've seemingly looked everywhere for the error, now you have no ideas left, but the problem is still there.
On Ubuntu this seems to be official (?) ppa: https://launchpad.net/~far2l-team/+archive/ubuntu/ppa Make sure "far2l-gui" is installed.

On ArchLinux there's package in AUR: https://aur.archlinux.org/packages/far2l-git (I maintain it).

Don't know details for other distros.
> I don't think the VCs are to blame at all

It's probably more reasonable to say "Not all the blame is on the VC". I've seen VCs, rich guys in their fifties with a lot of swagger, put unreasonable pressure on young padawan entrepreneurs to take more capital to grow faster than necessary. Then they over extended and it started failing apart. The entrepreneurs are ultimately responsible for taking the cash, but the power dynamic is such that the VCs surely deserve some blame for pressuring inexperienced entrepreneurs into biting off more than they could swallow.
And while you are fumbling around trying to learn the technology, the market is leaving you behind, you’re burning through resources and you’re not creating business value by either making the company money or saving the company money.
The example is not simply a compliment, it's an _objectifying_ comment. That's the issue.

Try giving a compliment that addresses the person as a human being with real experiences, thoughts, and accomplishments, rather than regarding the person as an object matching some abstract ideal. It's not a matter of ideology, just acting like a decent human being.
Joke apart, yes. ChatGPT can sometimes be more useful than rustc error messages.

However, the code you need it to explain have to be small and self-contained. When it's part of an actual project, preparing a proper prompt requires a bit of work.
Check Double Commander. It's a quite close multi platform clone.
I couldn't read it all because the number of GIFs started to make me nervous :(
I'm pretty sure thousands of years ago nobody in France was watching TV, flying in airplanes, even eating french fries.

People import culture all the time. Most dishes of the Italian cuisine involve tomatoes which weren't there before contact with the Americas. In India spicy food wasn't really same without chilli peppers!

Just be honest. It's not about culture, it's just that some people don't like other people that come from other lineages and appear different to us.

No matter how you adapt and fit in you'll always be unwelcome by some people, just because you shouldn't have come in the first place!

People rationalize around details all the times but ultimately it boils down to this: for some there is a double standard; you're either full-blood American, French, Italian, whatnot or you just should shut up and perhaps "we can put up with you, if you behave.". If an American, French, Italian commits crime in his country, well that unfortunate but ultimately "he's a good boy, who went astray".
In my experience small firms will struggle to hire excellent system engineers that can manage a bare metal setup, it's easier however to hire okay-ish SWE's that can design applications appropriate for cloud.
Why skilled immigration (usually) benefits both countries
Does Mark Spitbznagel run a hedge fund, perchance?

It’s never a surprise to hear bad news from people who make money from bad news.
> Also, the founder appears to be of russian origin [0]

It could be argued that he has more need of a reliable private chat than others, except maybe someone of chinese origin :)

> you can’t just take their phone number and check if they have a WhatsApp/Signal/etc account

So why the hell should I have to give away my phone number?

Edit: someone pointed out in a different comment thread that the company is registered in the UK. Considering the upcoming anti encryption legislation over there, maybe that's what should worry you.