skysight-inc/HackerNews huggingface dataset:
The Discord and AWS posts are both about GC vs no GC. The GC in Go prevented scaling the cache due to latency spikes. Rust doesn't have a GC and so the cache could be grown from x million to 8 million without increasing latency. The Discord post says just simply rewriting the service from Go to Rust increased performance in all metrics (but doesn't give numbers).

But Discord also made other changes during the rewrite - changing from hash table to B-tree, data structure layout optimizations, reducing memory copying, etc. And the graphs are with those changes included. So the Discord graphs aren't a pure Rust vs Go comparison. I guess I can agree with rsc that it's "misleading" to cite the graphs during a Rust vs. Go comparison.

But the headings of the Discord post imply the latency change for average response time from milliseconds to microseconds is purely due to increasing the cache size, which was only possible due to eliminating the GC spikes. So it is fair to include that as an issue in a Go 1.10 vs Rust comparison. rsc's opinion seems to be that Go 1.18 will fix the latency issue - I disagree, but the only way to tell is to redo the measurements.
I'm not sure if you misread my comment or I'm misreading yours.

The comment that broke the site guidelines was https://news.ycombinator.com/item?id=30443157, by assuming that the point of the OP was to convey "misleading health information" and then reacting to that.
> a simpler systems language, in contrast to Java.

I read this as saying the contrast between go and java is that the former is simpler. The confusion maybe comes about because "simpler" is a comparative adjective (as opposed to, eg, "simple", which is a descriptive adjective), and because there are up to two qualities being contrasted -- simplicity and "being a systems language".

Take it or leave it but I personally was a bit confused by the wording.
Everyone won't hit the upper margin of that; only those that are either exceptionally strong, experienced, or landing offers at multiple companies will. More generally though, the trick is to research and interview at multiple companies, and get the salary range established early (first call). Companies compete on talent heavily right now, so you can push the ranges by simply talking (not even interviewing) to enough companies, asking ranges, and selecting out the lower ones.
DDoS affecting Ukrainian sites, foreign ministry and state security service down
I've used both in production settings, a sympathetic perspective doesn't help :)
All-in-one development agency for custom software solutions.
I am the cofounder of https://Smartcar.com. The talking point being used to suggest that "it's not possible to comply because such a solution doesn't exist" is just completely false.

This is exactly what we've built at Smartcar over the past 5+ years. Thosuands of developers have built apps on our platform to let consumers access their own car data and bring it into the apps of their choice.
Has nothing to do with Intel’s problems
Indeed, why not? ;)

There may yet be something to Teilhard de Chardin's take on the Noosphere which exists in a matrix of consciousness that spans planets, solar systems, galaxies, galaxy clusters, and indeed universes!
Is 3.7-3.98 GHz range somehow particularly useful for mobile operators?
Huh, I remember seeing some of his videos about five years ago and wondering if he'd ever make it. Glad to see he's still going!
Vanced is awesome, except for the fact that they broke casting to my TV a while ago so I had to downgrade to an older version and hasn't updated for a while. Not sure if they fixed it now.

Also I tried to find something similar to put on my iPad and my god it's annoying. iOS allows you to sideload app if you have a dev cert (not too sure on the details) but you have to renew the cert every 7 days or so, so you need to keep a server app running in the network to automatically renew the cert for you.
As have I, heavily, and it did.
Traffic Engineers Can Finally Tame Stroads
35% would be bad yields with a 650mm^2 GPU.

These are likely only around 80-100mm^2 (likely because it’s impossible to find die size numbers for recent snapdragon processors — reviewers need to solve this).

Abysmal would be damning their process with faint praise. I wonder if Samsung is even turning a profit or just trying to offset losses.
I love Vanced! The only downside is that it's not able to avoid ads when casting to Chromecast.

SkyTube is a minimalistic Youtube Android client that can avoid ads when casting:
https://github.com/SkyTubeTeam/SkyTube

For those of you using Android TV, I highly recommend SmartTubeNext, a Youtube client with no ads, and includes SponsorBlock[1]:
https://github.com/yuliskov/SmartTubeNext

[1] https://sponsor.ajay.app
I remember watching Minority report again last year and being really surprised watching this scene!! I was like that looks like my research project but this movie is 20 years old???
Seems to be broken on iOS. Tap the button and a square appears, but nothing else.
True in broad, general sense.

But basically off the page as regards to the specific UX patterns under discussion in this thread.
> allows you to play videos in the background
This feature is why I use Vanced
Well snap. I was thinking about dipping my toe in this space.

If anyone wants to give me $6 Million, with 100% return in the event of my death, I'm all ears.
Totally fine. Note however that this isn't marketed as a place for anyones most private thoughts, it is right there in the announcement:

> unique collaboration system that is optimized for granular sharing between individuals rather than "all-in" sharing amongst teams or specific groups

Such applications has their place and for what you know I might be using them myself, but don't for a second believe that any web application with sharing possibilities are a place for anyones most private thoughts.

If you did think so until today, take my advice and clean up everything that can get you in hot water.

Someone funny once said: "what happens on the internet stays on the internet, forever". This is worth reminding oneselves about.

Edit: if one needs sync and security one can maybe use something like Joplin which supports encryption. I haven't verified neither the crypto nor the general codebase nor if it can autoupdate. I'm just saying it might be possible as an individual to sync sensitive data somewhat securely like people think they do with online services but if you are at a level where E2EE is necessary and where government agencies or basically (in my opinion) anything more than snooping kids or coworkers enters the picture, my advice is to forget about web applications.

To avoid doing what I despise when others do, when they basically say "if you don't do everything correct you can just give up": That does not mean you necessarily have to give up your current solution:

Just be realistic about what threat models it can hold up against.

Edit 2: (as said elsewhere) E2E-encryption is seriously nice and I can pay a premium for it even if I don't feel I need it. Just know what it helps against. And don't tell others that everything else is trash and unusable (but feel free to tell them what the risks are and how to protect oneselves).
Relax. Many people would call Docker/Kubernetes, and various types of databases like CockroachDB as systems. Lot of enterprises call large internal applications as "systems" There is no copyright on "systems programing" and it can be used only for OS kernels and such.
Go was definitely ahead of the curve on a few things.

I'd argue C# was there (or very very close). C# has had value types (and fine-grained memory layout) since the beginning, reified generics since .NET 2.0, and also (lesser-known fact) raw pointer support (inside `unsafe {}` blocks much like Rust's approach). This was all motivated by interoperability with native code (mostly Win32 or other C-like ABIs & COM).

In 2009, the concurrency paradigm in .NET was more like promises and not quite as slick as goroutines. async/await wasn't born until 2012.

It wasn't on your list, but I'll toss in another point that works in favor of your original claim. ;) The main C# project also wasn't TRULY multi-platform until 2014.
But this is a good thing not a bad thing. The mistake in that article is thinking that the existence of surprising edge cases means the whole design was a mistake. Its better to design for the 99% not the 1%. I don't want to live in Amos' perfectionist world.
> So, if app size is a problem, and over time, the problem is fixed by itself, why would you invest engineering resources into that ?

You are assuming apps won't scale larger over time. The old addage about software expanding to consume all available resources comes to mind. I remember thinking I'd never be able to fill my first 1 GB hard drive with software. And now it takes half that for the simplest things. As the bytes get cheaper we ration them less.
Cool tech. Still, I don't understand how one can wear millimeter wave radio transmitters so close to the brain and not be concerned.
What if the car is used to store valuable and illegal goods? And a big amount of them? Now you’re the target of both the criminals and the police.
> But what is the platform used for? Converting energy into human comfort, or just another layer of financial engineering?

This is essentially the "problem" at heart of all crypto "currencies". There is no real world use case that imparts human value, apart from its utility as a speculative vehicle to grow wealth.

Every new DeFi application is a new layer to lock in current adapters who would've otherwise already cashed out. Crypto as a currency is a concept dead in the water because of the perverse incentives of finding every corner of arbitrage between non distinguishable (and frankly worthless) alt tokens/coins.

The entire world of crypto is nothing else but an experiment of how much one could financialize a fully non-regulated, intangible, and imaginary "good" based on nothing but greed.
Has the 3.07 BIOS update fixed the overnight drain issue? [1]

[1] https://community.frame.work/t/bios-3-07-windows-10-and-11-a...
Yeah, it's either a total fabrication or a great example of how to write up a true story that sounds like BS.
Unfortunately, that was the biggest problem with Anki’s DB. It was done by feel by a self-taught dev.

And now he has spent years trying to slowly undo the stuff he baked into it at the lowest levels.

It's fine to do stuff independently without knowing, but please seek feedback and advice on crucial design decisions.
The shame, lol. Your feedback is well deserved.
You do have more precise control over the memory layout of your data in Go. Because of the value types and support for using interior pointers to arrays. In that respect it's like C which is lowish level.
Isn't the word "fila" from Latin for "file, queue, rank" not from Arabic?
Intent doesn't communicate itself; the burden is on the commenter to disambiguate it.

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...

Intention also isn't enough when it comes to avoiding flamewars on the internet. What matters is the effect a post has on the thread, and in the case of a provocative one-liner like the GP, the effect is pretty predictable.

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...
https://github.com/akemin-dayo/AppSync
> If you’re not going to do that, there is no benefit to using a CDN. Just send all the traffic to your origin and run your own reverse proxy there.

You still get DoS protection.
Where are these reports of popular exchanges freezing customer accounts? I'm also genuinely curious, because I've never heard of them, and a cursory Google search isn't turning up much.

As for exchanging for Monero, there's starting to be the option of atomic swaps with Bitcoin. Alternatively, you could also try going through one of the various non-KYC automated swapping services.
Sure, this is the defence. Some basic questions that would be asked in any (ordinary) policy proposal conversation:

* What are the major problems with existing currency systems?

* Which of these specific problems does crypto solve?

* What problems does crypto create? Are these less serious than the existing ones?

* How well/reliably does crypto solve them?

* Who are the stakeholders that will determine crypto adoption?

* Which of these stakeholders would switch to crypto, and why?

* Why wouldn't they?

* If crypto sees no widespread adoption, is there any market value to it as an asset? What would this value be? Why?

Let me remind you: crypto is backed by a highly centralised companies largely controlled by early adopters who hold the vast amount of the crypto value within the system; their relative control can only increase overtime as the asset is deflationary. The entire economy is determined by the immutable blockchain, unless its forked to preserve the interests of those with massive holdings. The immutability of the blockchain makes fraud irreversible, unless the chain is forked -- so fraud is only reversible against high stakeholders. The chain is incredibly operationally expensive to run, centralising service control to a few companies, and incredibly slow. The whole economy is public, so once your identitity is known, you're entire economic life is visibile to everyone -- making blackmail, fraud, and "ruthless and abtiary credit checks" easy.

We know what a society based on a deflationary stake captured-early is like: its called feudalism.

Crypto is an anti-democractic economically illiterate project to create a feudal society in which power is proportional to holdings; and redress requires convincing the powerful to "fork the economy".

If it had any chance of success at all, it would be necessary immediately to organize a massive political project to ensure it was stopped. The reality is its just a group of fanatics engaged in a get-rich-quick scheme thinking that in the future where they are rich, they'll have the power (by design of the system)!

Thankfully it's genuinely silly and ineffective, and the only thing crypto has ever done is be sold to the next fool along. No one really needs to worry, within the decade crypto will have collapsed. I'd say 5 years, but of course, bernie madeoff ran his greater-fool scheme for 30.
I'm actually really hyped for this, I was thinking I would have to get the ultra-proprietary Varjo headsets to get a really good headset in 2022, but I'm really looking hard at the Tethered version and building my own RDNA2 based compute unit. I'd much rather give 2k to an open source project.
> What happens when 2 captured regulators collide?

When moneyed interests compete it becomes the same as their being no moneyed interests

An average case outcome

Not obvious what would happen here though, just a general reality that mostly undermines the “rich shadow organization controlling everything” idea
I see no amount of evidence will convince you that China is ok with Russia invading Ukraine. Your thesis about China and international norms is clearly false and your beliefs about China’s position is not supported by the facts.

My contention that Russia has China’s blessing is correct. It’s ok to admit when you are wrong.
That's great. Fortunately for my sanity, I've decided not to take on the burden of caring about being "good" in all things.
"I had my car stolen 3 times"

I'm curious: does the above make you think the car will be stolen again pretty soon? If so, does that cause you ongoing stress?
While this should have been better studied before the spectrum was allocated, it's not really the fault of the FCC.

These radar altimeters have very wide front-ends, as as a result are highly susceptible to out-of-band emissions. The radars are allocated from 4.2 to 4.4 GHz, so the bottom edge of the radar altimeter band is 200 MHz above the top end of the 5G band in question (3.98 GHz).

The fact that these radar altimeters are susceptible to out-of-band interference that is literally further away in the spectrum than the width of their entire allocation is IMO an engineering failure. Yes, spectrum management (rightfully) tends to err on the side of not forcing the incumbents to make modifications to existing systems. However, better filtering would resolve this issue and it is shocking that the engineers who designed them didn't foresee that other services would eventually be allocated in adjacent bands. Avionics is often NRE dominated, they couldn't have sprung for a cavity filter? Or if that was too expensive, designed more headroom in the LNA before saturation and filtered the out of band signal with a crystal or SAW filter at IF? Rejecting out of band that far away is not rocket science.

I don't think it's unreasonable in this case to temporarily suspend the rollout and give the aviation industry a deadline to fix its radars, but it should only be temporary. Any other radio service would be told to take a hike if it keeled over due to out of band interference that far away.
He also just put CloudFlare on the front page of HN yet again, so, he's just paid them handsomely in PR.
If solar and wind were scaled to provide the same kWh as everything else does right now (solar and wind providing all power involved in the mining and repair of the machines used to build solar and wind), would they still be more effective than non-renewables? Or is a combination of renewables and non-renewables the most efficient?
C# is an interesting case. You can only use pointers in unsafe C# code, so you could argue that unsafe C# code is as low-level as Go or even lower (which I actually think you'll find many supporters for), but unsafe C# is different from normal C# and is outside the purview of everyday C# code (whereas again pointers in Go are absolutely pedestrian).

RE threading, green threads though are coming (back!) to Java as well with Loom, but I consider that more of a library/runtime thing than a language thing (as is the case with Loom). A hypothetical Go library could expose system threads and have an API for manipulating them, it just wouldn't be first-class in the same way goroutines are. But this is similar to how having async-await in C# doesn't negate the fact that you can use direct system threads from the standard library.
I honestly think the best way of accomplishing performance is constraints. Constraints allow you to nip performance problems in the bud, they will show you exactly where the performance problems are without guesswork. This makes them much easier to fix than doing it after the fact. If your staging environment is a raspberry pi, I can almost guarantee you will not have performance problems on your production machine.

Also, with proper encapsulation, readability problems aren't that bad. With a clearly defined and well designed interface, you can always just do a new take on the implementation. I often produce fairly messy code when I prototype something, but since I keep interfaces in mind, it's almost never more than hour or two to clean up into something readable.
Yes and no. Many other countries are using C-Band, but often under slightly different conditions. Some countries licensed frequencies that stop significantly farther away from the spectrum used by radio altimeters. Some countries have mandated lower power levels for C-Band. Some countries have created larger exclusion areas around all airports (rather than the smaller, temporary exclusion areas around some airports in the US). Some countries have mandated a downward tilt for C-Band antenna panels (nationwide or in areas around airports) so that the transmissions aren't going go up as much (but a downward tilt also limits the transmission range which is bad for wireless carriers).

I think one of the big things in the US is that anything that makes C-Band harder to work with makes it hard for 2 of the 3 wireless carriers to compete. T-Mobile has a lot of 2.5GHz spectrum that it has been using to launch high-speed 5G services. Verizon and AT&T had been waiting for their C-Band spectrum to be usable to launch their high-speed 5G services. In Europe, if all carriers are facing the same restrictions, it's a level playing field. In the US, if Verizon and AT&T face restrictions that T-Mobile doesn't face (for most of its spectrum since it's 2.5GHz and not C-Band), that doesn't offer a level playing field.

I think it's also more contentious in the US because we have a much more suburban and rural population. Transmission distance is really important in the US because people expect to get modern services even in low-density areas. Verizon built its business on the idea that you should expect excellent wireless coverage even in places that have virtually no people.

I think another part of it is that the FAA is often very cautious and it seems like they didn't coordinate well with the FCC in voicing their concerns early on enough.

The FAA does have a web page on C-Band (https://www.faa.gov/5g) which is their official stance on the subject. They cite "Lower power levels, antennas adjusted to reduce potential interference to flights, different placement of antennas relative to airfields , and frequencies with a different proximity to frequencies used by aviation equipment" as reasons why the C-Band situation in the US is different from that in other countries. Is the FAA being too cautious? Maybe.

Ultimately, no one wants their business plans disrupted. Airlines don't want to see issues that delay landings. Verizon and AT&T don't want to see things that delay their ability to provide fast 5G service.
So what kind of settlement do we anticipate as compensation to Verizon and AT&T for allowing them to bid and purchase spectrum and then not allowing them to capture value from that spectrum, post-purchase? Seems like a slam dunk for a hefty payout of some kind.
Show HN: Flatsauce – Database with Decoupled Storage and Compute
Hi HN, this is Soheil (https://flatsauce.com). Flatsauce is a cloud database service that separates storage from compute while horizontally scaling your database cluster. Think of it as a Postgres read/write cluster with several nodes except that all the nodes in Flatsauce share the same storage. Flatsauce intelligently routes data between the nodes and incorporates a file locking mechanism to ensure there is no data corruption.

In traditional read/write replication scenarios usually a write instance is the source of truth. First data is written to the write server then the data is copied to all the read nodes. When more read nodes are needed to run long-running queries the storage needs to be copied for each node.

Flatsauce reduces the cost to run a database cluster by eliminating the need to duplicate the data storage every time a new node is added to the cluster.
Cloudflare is not at that stage yet, but for a global Internet MiTM there are a hundred different ways to lock user in.
Usually resulting in a Windows computer being powned before patches could even be applied: https://it.slashdot.org/story/04/08/17/1347214/survival-time...

Note: The graph url is dead.
NewPipe can do that as well.
Also good luck if you need to cross-compile. The Go toolchain for that is seamless, Graal’s is non-existent (because it is fundamentally incompatible with the way native image compilation works).
You could just hire someone for repossession (aka “repo”)
>Golang is anemic when it comes to modeling ability and expressiveness. I have come across so many code sections where having something like sealed classes and pattern matching or switch expressions would have made code so much readable and safer.

But there is a tradeoff. Every complex feature you add has a continuous cost applied to every reader, in that they have to become expert with the new feature. C++ is a great example of the failure mode here, and even Java has too many features such that using many of them will confuse most of my coworkers. Having few features means that the code is more accessible, and you can spend your cognitive load on the genuine complexity of your problem rather than fiddling with language knobs.
Pretty sure it's Lego: https://www.lego.com/en-us/product/bucket-wheel-excavator-42...