skysight-inc/HackerNews huggingface dataset:
CJK native speakers can't read or write other "trivially derived" versions of Hanzi. I don't understand why this has to be reiterated ad infinitum.

We can't actually read Simplified Chinese as a native Japanese just like French speakers can't exactly read Cyrillic, only recognize some of it. Therefore those are different alphabet sets. Simple as that.

The "trivially derived different styles" justification assumes that to be false, that native users of all 3 major styles of Hanzi can write, at least read, the other two styles without issues. That is not true.

Итъс а реал проблем то бе cонстантлй пресентед wитҳ чараcтерс тҳат И жуст cанът реад он тҳе гроунд тҳат тҳейъре "саме".

I hope you don't get offended by the line before this, because that's "same" latin, isn't it?
There are plenty of better deals as long as you don’t limit yourself to big clouds and clouds with startup-esque landing pages frequently posted to HN. LowEndTalk may be the most well-known place for finding such deals.

(Not saying the typical cheap VPS on LowEndTalk has comparable PaaS features. Only responding to parent’s use case of a single cheap instance.)
And it is easier than AWS to deploy.
I thought we are in a place where people seem to express some sort of intelligence, and yet, reality always finds a way...
> A garbage collected relatively simple language that compiles into a statically linked binary but has a type system similar to rust, rest types etc.

Swift.
> and Voltaire responding with

Like a very long joke, which builds and builds and builds and builds, the punchline in the end arrives.

It's in the last sentence: "Yes, but you have to work for it". (I.e. he intended to stress an outer point.)
Unit tests and code review are the exception, not the rule.

One thing that has changed is that nowadays software is everywhere, cyberattacks as well, with corporations and goverments putting numbers into the dollars that get burned in developer salaries, fixing CVEs, rolling out updates, downtimes caused by bug fixes, insurance claims, insurance premiums, lawsuits, malfunction software which consultancies have to fix free of charge,.....
That and scrolljacking
"quickly find yourself wanting slightly more modern language features."

Use the tool that works for you.
> the underlying lib could change and suddenly throw a Runtime-Exception.

And what would you do in that case? Since this is a future change your existing code presumably wouldn't know what else to do but throw its own exception, so why not just let that one propagate?
Video game companies used to be like this. There was no community engagement, and the companies were essentially walled gardens. One day a feature (or even whole game!) would appear, and that would be the first you'd heard of it.
Extreme hike in energy prices was about four months before the war began.
It’s when EU decided to abandon long term gas contracts and turned to spot prices (~11.2021).
The war started in 02.2022.
Since northvolt is private, there is a lot less insight into what goes on there. However, I'm fairly sure that the CEO did sell some of his shares during one or more financing rounds, in order to create a little nest egg for himself.

On top of that I'd imagine that during the 8 years or so, he probably took out at least 200k EUR in salary, if not more, per year. So a few millions of dollars probably went to the CEO.
GraalJs is just a name. It was created by Oracle so they can use the trademark if they want to. I have no idea what you are talking about.

> Ryan has been outspoken about what he thinks he did wrong with Node and why he decided to make Deno

Yes, I explained that we disagree. Clearly he also feels he was wrong about Deno’s NPM choices since he reversed course and added NPM support. So Ryan agrees with me, I guess.

> If all these runtimes eat away enough at node’s share

WinterCG and other efforts are formalizing APIs that can be shared across runtimes. Which is great. Many of these APIs are at least informed by, if not outright standardized versions of, Node APIs. They are here to stay.
Oh Ef, might be time to check the prescription on my glasses again. I misread "piracy" as "privacy" in the headline. Apologies to Ars (but not Lars).

Still, are we able to have an honest conversation about one without closely examining the other?
What you want to say is that it will be made easier than it already is.
The edge SDKs do not parse and interpret data from the internet, they provide ingress/egress off the overlay. They authenticate and authorise to the controller and make outbound connections to the overlay network. This is why any app embedded with Ziti has no listening ports to host OS network, LAN, or WAN; they only listen to specific application calls across the overlay.

Now, you may say, "well, you have merely moved the listening port from the app to the overlay". Yes, true, not simple. Firstly overlay is written in Golang (thus memory safe). Secondly, if a vulnerability exists in the overlay network that would allow an attacker to bypass the security of the zero trust network, but what does that mean in practice? Well, to do this they would need to:

- bypass the mTLS requirement necessary to connect to the data plane (note, each hope is uses its own mTLS with its own, separate key).
- strong identity that authorizes them to connect to the remote service in question (or bypass the authentication layer the controller provides through exploits... note again, each app uses separate and distinct E2E encryption, routing, and keys)
- know what the remote service name is, allowing the data to target the correct service (not easy as OpenZiti provides its own private DNS that does not need to comply to TLDs, so it could literally be 'madeup.service.123')
- bypass whatever "application layer" security is also applied at the service (ssh, https, oauth, whatever)
- know how to negotiate the end to end encrypted tunnel to the 'far' identity

So yes, if they can do all that, then they'd definitely be able to attack that remote service. But I said "remote service", not "remote services". All that work and compromises and they only have access to 1 single service among hundreds, thousands, or potentially millions of services. Lateral movement is almost impossible. So the attacker would have to repeat each of the 5 steps for every service possible. Also, they don't know which company sits behind which OpenZiti fabric, so its pot luck if its even against the target they want to try and exploit.

Finally, we have developed a stateful firewall called 'ZitiFW' - https://github.com/netfoundry/zfw - which uses eBPF to look at the IP information of any incoming connections/packets to an Edge Router (Ziti's Policy Enforcement Point), if a connection/packet is received from an IP address which is not correlated to a known, bootstrapped endpoint to the overlay, the packet can be blackholed.
Looking at this another way, this case is a call-for-solicitor-general. Trump will pick John Sauer for SG because Sauer wrote a chapter of Project 2025.

A generation ago, the Contract with America arrived with Republican electoral gains. These manifestos are important because otherwise individual Republicans don’t have both the skills of governance and populist appeal.

It’s interesting that Project 2025 argues that its social points necessitate a more powerful executive. Like a Minister of Health rather than a supervisor of the department distributing advice on maybe improving medical regulations please.
Let me revise that: I’d be surprised if more than half of the trucks on the road have ever hauled anything.

> cybertruck can’t really haul things, it can’t really tow things, and it can’t be that fun to drive

This reminds me of people who complain about expensive garments being impractical.

That isn’t the point. They’re articles of fashion. Same as most trucks and sports cars. Cybertruck is outselling the F-150 Lightning. Consumers don’t care about hypothetical utility.
> if private cars are inevitable, I'd rather they be electric.

Thats the issue. The car industry has brainwashed everyone into thinking that owning an EV is the best option for the planet. It isnt. EVs are way more pollutant in creation and disposal. Emissions out of the exhaust pipe are one tiny part of the climate impact of a vehicle.

Replacing Petrol/Diesel with Hydrogen/Synthetic fuel is a much greener option overall.
A recent similar example was the Indian move in 2016 to demonetize the ₹500 and ₹1,000 notes with very little notice, which is in retrospect widely viewed to have been a disaster.

https://en.wikipedia.org/wiki/2016_Indian_banknote_demonetis...
I have a feeling piracy is way down from the heyday of the 2000s-2010s.
history keeps repeating, so often that there is no tragedy left, just farce

i give it 5 more years till hegel becomes popular. 10 more years till dialectical materialism and dictatorship of proletariat
With the current US Supreme Court, I wouldn't be that sure. And, depending on how they decide, it won't be just content disappearing because of excessive DMCA notices, your internet connection itself might be gone because someone didn't like what you downloaded (or watched) yesterday...
[meta]
Does anyone else color schema?
I found the blue links hard to read
with the dark background.

Or maybe the links are left to the default
for the browser to decide.

Either way I would prefer an easier to read color.
Feel free to take a look at any more complicated GoLang code (k8s, gorm, etc) and you'll see that the tool/library you're depending on requires a veritable rats nest of bad practices to work around the Go's inherent limitations.
Whether to provide Crimea with Starlink or not depends on who sits there. Similar reason why all Crimeans got under sanctions immediately after annexation. Not just Starlink but every other Western company respecting sanctions stopped doing business with Crimea. Same with Donetsk and Luhansk.

No one cares if it's "legally" Ukraine. People care about the "effectively".

Legally always depends on who you ask. Some will tell you that Taiwan is part of PRC for example. Maybe at least half of the world will. However Taiwan is not under sanctions because effectively it isn't under PRC.

> Indeed, it looks like you're shooting into the wind here

I am just trying to reduce you some confusion by explaining some basics. Starlink was not yet in Ukraine when Crimea was annexed and the world mostly sat and just watched it happen. Therefore the musk-man could not "cut out crimea". There's nothing to argue about. Just don't spread misinfo please, there's enough of it.
I think there's something missing from this analysis - YC companies might duplicate one another's products but that doesn't say anything at all about their target markets, route to market, product focus, etc.

As an example, my first startup was a requirements management app that, on paper at least, was a copy of IBM DOORS. Except DOORS is a massive enterprise app targeted at companies who are building a new airplane that has 250,000 technical requirements that need fully traceability, and my app was aimed at small businesses doing software projects with 1000 requirements. I was not competing with IBM; I was trying to apply the value of that app to much smaller projects (the end goal might have been to become a competitor one day but we failed long before then.)

You can't just say "These two products do the same thing so the companies are dupes." It's far more complicated than that.
My assembler days were 4 decades ago, but

"Everyone can read Go code and understand what happens."

There seems to be a difference between "easy to read" and "understand what happens" - or what happens on what level. The challenge is that there is a tradeoff between the two. Assembler is too low to understand what "really" happens, on the other hand Haskell for example with Monad stacks is again very easy to read + understand what happens "most of the time", but hard to understand all the abstracted away side effects.

In Haskell with

add 3 5

everything can happen beside what you see.

In assembler

ld a, 3
add a, 5

nothing happens except these two instructions.

The tradeoff is how much you want to be explicit, with the downside of creating too much noise, and how much you want to abstract away, with the downside of magic happening somewhere.
Single use book?
Yep. Europe is socialist, which makes it extremelt difficult to start successful tech-companies. Europes unicorns is far fewer than what are created in the US and China.

As long as europe continues to heavily regulate and tax its citizens in the best socialist tradition, it will continue its decline, to become a tourist playground in a generation or two, for the rest of the world.

I always advice young entrepreneurs to move outside europe to start their companies.

In its current form, europe is dead.
Warm pools are a supported feature in AWS on auto scaling groups. Works as you're describing (have a pool of instances in stopped state ready to use, only pay for EBS volume if relevant)
https://aws.amazon.com/blogs/compute/scaling-your-applicatio...
The proper definition will clearly mean the model, not the model instance.
Combatting hyper-inflation is unsustainable and ultimately symptomatic of a hypo-inflationary urge to short fiat with an epidermic poised at early warning signs.

Setelinleikkaus as a negative-feedback control mechanism to stop printing bak notes.
I always thought that stopped instances will cost money as well?!
America innovates, Europe regulates and China copies.

It was a parallel that in the EU we have regulations for things that there are no successful companies in the field and even if some companies will do AI in Europe, they will not be able to compete globally because they are chained by regulations. And with regulations that do not into account the economic realities, like the slow killing of the auto industry with the push for EVs even if very few people actually want them.
I think it is yes !

Malvina Reynolds - Little Boxes

https://www.youtube.com/watch?v=VUoXtddNPAM
It still doesn't sound right to me. Sure we can get adapted to the new meaning of the term as time goes on, but to me the term has strong implications to physically bring it back, and it is weird that people are claiming that it doesn't.

Surely this causes a lot of confusion at the very least people thinking those vehicles actually have to be brought back.
I don't think that's true. Most people are accustomed to there being many "recalls" for trifling matters which can be simply ignored until maybe the next time they bring the car into the shop. A typical conversation about recalls:

> "I changed your oil, and I also replaced one of your door seals because there was a recall for the rubber cracking in cold weather"

> "Oh, okay."

It doesn't colloquially imply that the manufacturer is going to come take your car due to some major issue.
> I'm surprised that rotating scanners are still used. It's been twenty years since Velodyne built their first one.

They're even older than that. SICK have been pointing laser range finders into spinning mirrors since about 1995 - albeit mostly for industrial safety systems which can be quite price-insensitive.

There's a few things to know about LIDAR to understand why spinning lasers make sense.

First of all, anything emitting a cone of light encounters "inverse square dropoff" - where moving twice as far away means you get a quarter of the light, per unit area. This is most visible with flash photography at night - but it also applies to LIDARs. And in an automotive application, ideally you want to be able to sense things 100m away. Illuminating a laser spot is much more practical than illuminating everything.

Secondly, whatever light source you use has to be eye-safe. And sure, IR has safety advantages over visible light here - but a light source bright enough to illuminate things at a 100m distance would be very hard to make safe, even with the advantages of IR. As a scanning laser never lingers in one point for long, it can safely be much more intense.

The third thing to know is whatever light source you're using, you're in competition with the sun. Sometimes the sun is low in the sky and directly dazzling your sensors. Other times it's illuminating the same things you want to illuminate. This means you can't make up for a weak light source and inverse-square dropoff with clever signal processing.

And finally, the makers of these cars envisage a future where every single vehicle on the road is using this technology. So there's also a risk of the reflected returns of two different vehicles interfering with one another. Even rotating LIDAR can be vulnerable to it, but flash LIDAR is particularly vulnerable.

Meanwhile, automotive companies aren't scared of moving parts. A car has loads of spinning parts already; they have mastered the art of making spinning things that can keep spinning for thousands of hours.
Even less, the median household income is 80k: https://www.census.gov/library/publications/2024/demo/p60-28...
The one language feature that I miss in most languages is pattern matching. I wonder if there's any minimalistic language that implements pattern matching well?
I am but what can I do about it.
I'm not sure why you bring up Rust here, plenty of libs/languages use the Result pattern.

Your explanation of what bothers you with results seems to be focused on one specific way of handling the result, and not very clear on what the issue is exactly.

> what's the difference between your program and one with exceptions

Sometimes, in a language where performance matters, you want an error to be handled as an exception, there's nothing wrong with having that option.

In other languages (e.g. Elm), using the same Result pattern would not give you that option, and force you to resolve the failure without ending the program, because the language's design goals are different (i.e. avoiding in-browser app crash is more important than performance).

> syntactically noisy

Yeah setting up semantics to make users aware of the potential failure and giving them options to solve them requires some syntax.

In the context of a discussion about golang, which also requires a specific pattern of code to explicitly handle failures, I'm not sure what's your point here.

> full of footguns

I fail to see where there's a footgun here? Result forces you to acknowledge errors, which Go doesn't. That's the opposite of a footgun.
The way the current EC is set, fat chance of giving up regulating everything they can regulate.
Tesla offered wraps for a while. They've recently discontinued the option for the Cybertruck, although it is still available as an option for other models.

Of course, anyone can still get a third party wrap.
> MRV, go does not have tuples.

> MRVs mostly end up being worse tuples

I think you noticed yourself that you’re getting too hung up on terminology. Multiple return values are a half-hearted, non-reified version of tuples.
I see a lot of people say this about exceptions, and I don't have that problem. The exception bubbles up the stack until something catches it. Ok it's a different code path, but it's a very simple one (straight up). So you either catch the exception nearby and do something specific with it, or it bubbles up to a generic "I'm sorry there was a problem please try again later" handler.

Honestly makes me wonder what I'm missing. Maybe it's because I don't deal with state much? Do the problems start to mount up when you get into writing transaction locks, rollbacks etc? But I don't see why you wouldn't have the same problems with Go's mechanism.

Hoping to gain enlightenment here.

[copied from a comment below]: They are just horrific gotos that any library can invoke against your code. They are pretty much never, ever handled correctly. And nearly always, after an exception is “handled”, the application is actually in an unknown state and cannot be reasoned about.

Maybe this is it? I prefer a "fail early and often" approach, and I tend to validate my data before I perform operations on it. I don't want to attempt recovery, I want to spew log messages and quit.
These are fully equivalent in outcome, though often not low-level implementation. You can use try...catch (called panic...recover in Go) to pack a normal and abnormal return case into the equivalent of a Result<> type. Or just pass an abnormal Result<> back to the caller to manually unwind a single "layer" of the call stack.
Rust: Tools (early access edition)
If you use hourly billed machines...Sounds like the world most expensive semaphore :-)
That should not be an issue, unless the code is written in notepad.
As for interfaces, a better approach is to return struct and accept interface in your functions wherever it is possible.
> With this attack, only Google is in control. Not the user, not even the website owner, but an ad company.

You, as a website owner, can opt out via: https://docs.google.com/forms/d/1h9I0TbN-H_1e85CqXYb1ng7rQfg...

> What would you think if I randomly injected my own promotional content in your HN comments in a way that's indistinguishable from your own writing?

Through what vector, the Unofficial Hacker News for iOS app that you maintain? Because that's the correct analogy here.

Also stating 'promotional content' is being disingenuous to the type of Google content states it will surface through these links, see my other comment on this thread.

I'm not in support of what Google is doing but I think we should be fair in our assessment and especially in our presentation of our assessment to others.