skysight-inc/HackerNews huggingface dataset:
TGV doesn't make a profit by any normal accounting standards. As far as I know every line except Paris-Lyon has received large subsidies. The Bordeaux-Toulouse line requires a subsidy of 35 EUR per year per passenger for the next 50 years. Nor are tickets even cheap as a consequence. Supposedly it's cheaper to drive the moment you have at least two people in the car (I haven't checked that claim, probably there are routes where it's not true).

Rail in the UK requires subsidies. Once again you can play games with non-standard accounting, like by excluding the cost of track and stations, but those are the bulk of the costs. If rail subsidies were zeroed tomorrow every single railway in the UK would go bankrupt the day after. This is also true for the Tube which certainly isn't break even - where on earth did you read that? They were once able to cover daily operating costs from ticket fares, but Sadiq Khan put an end to that and now they can't even cover operational expenditure without subsidies from central government. Even back when they were able to balance the daily books they only achieved that by starving capital expenditure and not building up any kind of profit margin, meaning that any kind of upgrades or repairs have to come out of additional subsidies.

https://tfl.gov.uk/corporate/about-tfl/how-we-work/how-we-ar...

The Shinkansen has a long history of building unprofitable lines which led to JR's eventual "bankruptcy" in 1987, ending up 28 trillion yen in debt. After being semi-privatized they were given a lot more leeway to shut down their unprofitable lines, but even so, it's viable mostly due to the government ensuring they have access to nearly unlimited risk free and repayment-schedule free money (ZIRP).

Passenger railways are fundamentally not possible to run as ordinary free market companies. They were run that way once, but the railways were built out on the back of huge private sector investments in infrastructure. Governments the world over then nationalized them and redirected funds towards staff/union pay settlements or reducing ticket fares, cutting infrastructure spending to compensate. The result is a massive overhang of tech debt that now can't be paid off without unrealistically high ticket price rises.

British productivity is low because it has cheap labour due to effectively unlimited immigration. Companies invest in productivity improvements when labour becomes expensive, otherwise they don't bother, it's easier to just throw more people at a problem. None of that is really a secret, it just doesn't get talked about much because the British ruling classes don't like to criticize immigration lest they be called racist - however, this is a purely economic issue. Railways hardly matter for productivity and commuting may even harm it for many people, as evidenced by the popularity of working from home.
> Everyone I know who owns a Tesla loves it

Where do you live? In the bay area, I know a lot of Tesla owners, and 100% of them are absolutely sick of Elon's antics and are not considering another Tesla. (They also all are sick of the poor reliability and terrible service.)

Seriously. This is a virtually universal opinion in my experience, but, I wonder if it's different depending on the political alignment of your area. People may be starting to consider Teslas as political signaling.
Best Shopee Data Scraper – Extract Shopee Products, Search Data
Best Shopee Data Scraper - Scrapeless Shopee Scraper Use Case
You can check out the complete steps to use Shopee Scraper Tool to scrape Shopee data：
Step 1. Log in to Scrapeless

Step 2. Click Scraping API, then select Shopee to enter the Shopee scraping page.

Step 3. Drop down the Action list to select the data type to scrape, and you can customize the proxy region.

Step 4. Click Start Scraping to start scraping, and the scraping results will be displayed on the right.Scrapeless only charges for successful requests.
In China people might retire at 55 but there's no government pensions. People's children are their pension. Social welfare is not very great there.
MacPilot – Advanced macOS UI Automation Framework
It's a lot better place to live than the US though. And we don't need as much. Quality of life is not measured in terms of the amount of stuff you can buy. We don't have to be afraid of getting shot at school or being bankrupted because of an illness. We don't have to pay off our student loans for decades. Income equality is much higher (leading to more public safety and fairness). To many of us this matters more than money.

The US has different goals than we do. Europe has never been about maximum profit. Capitalism is a tool to support society, not the end goal.
Kotlin is interesting as a middle ground, but I still find it much less productive than Go for most tasks, and unsuitable for tasks where you'd reach for Rust.

In practice, Kotlin is extremely complicated, and you end up spending time being clever. There are 1000 ways to do things. Operator overloading. Proxies. Properties. Companion objects. Exceptions AND result types...

The build system (assuming you use Gradle) is tantamount to torture for anyone used to "go build".

The coroutines APIs feel simultaneously more complicated and yet more restrictive than Goroutines. More structured but less flexible and more effort to use.

Access control feels awkward. There's no way to make a type package-private -- it's file-private or available to the whole module. This leads to either a larger API surface than desired, or the inability to break up complexity into multiple files.

Kotlin/Native and Kotlin/JVM really are two different beasts too.

Kotlin/JVM is mature, but then you are running on the JVM, so that cuts out a whole class of use cases you might bust out Rust for.

There is a very weak ecosystem for Kotlin/Native, and it's poorly documented. There are some scary bugs in the bug tracker.

You can't publish source-only libraries for Kotlin/Native either, so you need a complex CI setup to build binaries for every OS and arch under the sun. Or just don't publish libraries at all, which probably feeds in to the weak ecosystem...
In this context, all European countries including Finland were subject to rationing during the war; the question is about how to phase out both rationing and price controls without having a huge discontinuity at that moment.
I do miss several of the things you list, too, especially (safe) self-referential data structures. But Rust is a fantastic compromise solution if your number one priority is to match the performance (or rather, performance possibilities) of C and C++, and have memory safety while doing it. If your number one goal is to be able to write memory safe ideomatic code that is entirely comparable to those languages, and then add some functional programming and lots of quality of life stuff to that, then it's pretty sweet.

In other words: Don't think of it as rivalling the entry cost of Python or Java, or the expressiveness of Haskell or Scala. Try to think of it as a replacement for C++, with memory safety and piles of quality of life improvements. And then with a sprinkle of the other things on top.
I guess it's a matter of taste, for me reading the generics and big picture first is more important than the details. Maybe it's my programming skills, but my files start with some five or ten string manipulation utilities and helpers. I honestly do not even care about their implementation, a name would suffice. Which is why I also like `where` approach much more than `let ... in`: it allows you to read the general idea, postponing the details to later (if you want to go into them).

However, I agree on laziness, operators and point-free.
It's not just leftists. My Twitter feed had a large number of military experts in it since the start of the war against Ukraine. Almost all of them are posting on Bluesky now, and they're certainly not a leftwing group.

I think another interesting aspect is that Musk confirmed that tweets with links to external sources are penalized on Twitter. That would particularly hit the kind of people that make these platforms interesting to me because they also post longer content somewhere else.
Firefly sets January launch date for first lunar lander mission – SpaceNews
There's a _great_ book about that: https://en.wikipedia.org/wiki/My_Name_Is_Red

Helps understand how arts, religion, and power are intermingled. Made me question what we mean by "tradition" ; they always seemed fixed to a present observer, but are also the result of constant change.

Anyway, there's more to the book and it is really a great read (maybe more so if like me you know close to nothing about the Ottoman empire).

(and just to be clear: this book talks about what was admitted as acceptable art at a specific period in a specific region where Islam was the state religion, not commenting on the art in Islam as a whole as I would be incapable of doing so)
MacBook Pro M4 Pro Teardown: New Model, Same Repair Situation
> despite the fact that piracy is both inevitable and highly incentivized by the claimants

And also it doesn't harm sales: https://news.ycombinator.com/item?id=35701785, https://news.ycombinator.com/item?id=15309950
> What's closer to the truth? Tweets or real life conversations?

Why do you think either is close to the truth?
You can apparently lease a Cybertruck starting at $1000/month. That is definitely within range for someone on a 90k income, even if it is isn't the most financially smart thing you can do.
Yes, the solution he advocates is "we freeze your assets, allot you a certain basket of consumer goods, and take what we consider the appropriate price out of your frozen assets".

If you'd rather describe that as "communism" than "price controls", feel free.

The theme of the whole piece is that, if you don't allow people to pay more for things, then the price of those things won't rise, and that this is some sort of policy victory. It's a very stupid viewpoint; seeing prices fail to rise because you redenominated the currency means nothing. Seeing prices fail to rise because you prohibit that, on the other hand, doesn't mean nothing - instead, it means your economy is collapsing.
>I would probably feel offended if coding assistants were presented with a monkey in front of a computer

As a professional monkey in front of a computer, I feel offended.
The problem is that you can't hold a pointer to more than 64K of address space inside a 16-bit register.

x86 could have easily had an IP-relative addressing mode for data from the beginning (jumps and calls already had it), but to get a pointer you can pass around to use someplace else than the current instruction, it has to be either absolute, or relative to some other "base" register which stays constant. Like the segment registers.
>Recall is the industry-standard (and populace-understood) term for “this vehicle has a safety or reliability issue that must be resolved by the manufacturer.”

Exactly. But not just for vehicles or other durable goods. We see recalls of all sorts of food products[0] pretty regularly, and no one has to bring their carrots or ground beef back to the store/manufacturer to "remediate" the issue. Rather, you just throw it away.

And such activities are unfailingly called recalls.

[0] https://www.fda.gov/safety/recalls-market-withdrawals-safety...
Fun take.

I suggest countering it with a concept of "day reusability". You know, just as with rockets...
Seems to be the exhaustion that happens when you’ve built up waste products that need to be cleared by sleep.

But has anyone found success re-establishing that fresh mind without sleeping?

Maybe meditation can help?
The tricky part isn't money on a digital ledger. That's easy enough to handle with e.g. a one-off deposit tax (IIRC used as recently as the Euro crisis). There's no operational problem here, it just needs to be legislated to happen. Executing the operation properly might take a while (it's not something they'd have a process for), but banks must already have in place systems for e.g. freezing assets which could be used to buy time.

Bonds can just have a haircut on their nominal value, which is pretty much standard operation procedure during a financial bailout.

The real problem is deposits in foreign banks in foreign currencies. In the modern world by the time a country would be looking into this kind of a measure, a lot of the capital will have already fled. In this case the blocker is jurisdiction / sovereignty, not any kind of technical limitation.
The author clearly does not weigh in on the "whys" some things work in Go like they do.

So, adding an extra struct field results in the base value, and by design this should be used as a base default. The go proverb make base values useful goes hand in hand.

Obviously functions are not the same. And calling function with the wrong args is a compile time error. There is also CI check that check for this use case.

Overall this seems like a comparison to Rust, and its obvious they are not same same. Apples to Oranges.
If they'd drastically improved their tooling then yes.

But sadly it's not that easy to create a statically liked binary in swift. The last time i did it it also included the whole runtime, and the resulting "hello world" binary was 50mb large. Annoying at least.

For years I wished they got their stuff together, but at this point I'd be very suprised. They probably have too much technical dept already due to the support of XXX edge cases Apple need for iOS/MacOS development.
My theory is that open source was never intended to be based on free work.

Rather, it is an open collaboration between companies, which realize that it will lower their cost, while not being a competitive advantage for either party. It improves the profit margin for everyone.

What you're proposing is to convert Github into a small-business platform that sells "open source" software products, which is entirely different.
> People tend to forget that Golang was created on purpose for poor programmers.

The money shot....
PH-Sites, are that the new ToDo-List-Examples?
From the arguments I've read against this, I think not enough emphasis is being placed on the strongest one:

In the modern world online access is as necessary as water, power and phone service. No one would suggest forcing the power company to cut service to a customer over trivial civil law matters (which is what copyright is) that are completely unrelated to the company or the service it provides. No one should suggest cutting internet access either.

I guess ISPs in the US don't want to use that argument due to the regulatory implications (the common carrier classification thing)? But someone should be making that argument to the court.
Borland compilers and Clipper supported them directly.

Chapter 18, TP 3 and 7, to show its evolution

http://www.bitsavers.org/pdf/borland/turbo_pascal/Turbo_Pasc...

http://www.bitsavers.org/pdf/borland/turbo_pascal/Turbo_Pasc...

TC++, page 211

https://bitsavers.org/pdf/borland/turbo_c/Turbo_C++_Programm...

Clipper, section 7-18

https://archive.org/details/Clipper_Compiler_for_dBASE_III_a...
People are pedantic over this because they have a strong association from their past with this term and now it is being used unexpectedly. No matter how bad Tesla's issue might be, then maybe a different wording has to be used to highlight the issue. As right now it seems as if when the term is used it is almost intentionally made to seem as if the vehicle has to be physically transported back which would be a logistical and financial disaster. Sure, safety issues can be bad, but it is entirely different level of feasibility of physically recalling back all those vehicles. Why are people pretending it is not?

The whole issue is a spectrum of consequences. Right now it seems that the term used confusingly is always justified because the issue is binarily bad in the first place.
AI helps Indian e-commerce Meesho cut customer call costs by 75%
What many newer programming platforms (I deliberately don't say "language") got right, is that you can't design a language in a vacuum. If you design a language and leave the implementation open you'll iterate too slowly and eventually you'll grind to a halt or diverge in implementations.

A good programming platform has to consist of tooling which includes package managers, compilers, linters, etc. Ideally, in this orbit you would also have "Language Servers" or similar. At the very least, the compiler and language should be written with this in mind, e.g. written for the ground up to support incremental compilation and so on.

Go, C#, and Rust all have tooling-first and more importantly first-party tooling. The people who design the language MUST be able to iterate quickly with the people who make the compiler, who in turn should be able to walk down the hall and talk to the people who make the package manager, the package manager repository, and so on.
>I like the explicit error handling everywhere

Then you're doing yourself a disfavor by using Go. In other languages it would be even more explicit, mandatory, and automatically checked whether it's handled!
> to prove something to the compiler that is trivially known to be true

I don't think you've ever done any serious work with lifetimes. I've been a rust developer for a number of years, and I have never once encountered a situation where the rust compiler forces me to add annotations for something which is trivially true. Never.

What actually happens is 95% of the time I never have to add lifetime annotations anyway because the compiler infers the correct annotation from the lifetime elision rules. The remaining 1 in 20 instances is when the borrow checker yells at me, and literally every single time it is due to a latent logic bug in my code. For example, accessing memory after it's been freed, or using a container after it has been consumed. Stuff that C++ would call "undefined behavior" and are generally considered Very Bad Things by C++ developers as well.

It boggles my mind that you don't want the compiler to tell you that “you have a logic error here.”
In my ~2mio pop country, by the end of restrictions, we had (iirc) 5 people in the "below 35" age group what died 'with covid' (not necessarily because of it).

For comparison, that's way less than traffic deaths. Even way less than suicide rates in that age group (and we all know how bad the lockdowns were for many peoples' mental health).

We also had a 20yo girl die because of vaccine-induced clots. She got vaccinated, because she had to (couldn't use public transport without either a vaccine or getting tested every 48 hours, and there was no testing location near her to get tested).

Let's not mention all the other promises.

We took out a good year of schooling and socializing for the whole generation of kids, with empty promises of "when we get vaccines, you won't be able to infect grandma".
I like Go, but after writing/reading so much Go code, I get nightmares from `if err != nil` demons punching me in the face. There were so many nice suggestions made to fix this, but there are some extremely conservative and extremely loud-spoken community members who killed all the proposals with vitriolic feedback. Now, the Go team has given up the battle for improving error handling since they are psychologically afraid of these folks.

Every Go developer survey has results where the community overwhelmingly votes to improve error handling, but a few extremists have derailed all progress.
The '?' operator is the opposite of a footgun. The whole point of it is to be very explicit that the function call can potentially fail, in which case the error is propagated back to the caller. You can always choose to do something different by using Rust's extensive facilities for handling "Result" types instead of, or in addition to, using '?'.
Fascinating piece of financial history I hadn't heard about. Imagine your government telling you to literally take scissors to your money, it's like a weird mix between arts & crafts hour and monetary policy. Though I suppose we're already halfway there with our modern central banks, just without the satisfying snip-snip sounds.

The Finnish experiment failing because people just deposited their cash in banks first is a classic example of Goodhart's Law in action. Or as I like to call it, "If you tell people you're going to cut their money in half, they'll find a way to keep it whole."

What's really interesting is Belgium's more successful approach, they went full scorched earth on 2/3 of their money supply and somehow managed to pull off an economic miracle. Makes our current inflation-fighting tools look rather tame in comparison. "Sorry, best we can do is nudge interest rates up a quarter point at a time.
Air travel is taxed not subsidized. As far as I know there are no subsidies to the airline industry, unless you get into very ideological arguments by claiming the US military is a form of subsidy to anything that depends on fossil fuels. Double checking Wikipedia confirms this. After a huge page listing all the taxes, there's one unsourced paragraph claiming that "some" governments subsidise air travel with a "who?" dispute filed against the claim:

https://en.wikipedia.org/wiki/Aviation_taxation_and_subsidie...

Road travel is usually profitable for the government as fuel taxes cover more than the costs of building and maintaining the roads. Drivers end up subsidizing rail in every country that I know of. It's possible EV cars will start to change this.

US passenger rail is nationalized. Amtrak is majority owned by the federal government, for example.
>I don't understand why people get so passionate about programming languages. They are tools.

Because when you're a professional programmer, tools are a huge part of what you do and how you do it, same like a race driver would need to be passionate about cars.

It's just that for an e.g. carpenter, tools are more or less standadized and simple enough to evaluate.

If saws and hammers and routers had as much variety as programming language tooling, and were as multi-faceted to evalute, carpenters would be absolutely obsessed with using the good ones - even more so than they already are.
Rust is also not the same as C, and therefore shall not be compared to it. Crabs to Cats.

Of course they are not same; that's why we want to compare them in the first place: were they the same, there'd be no need to compare them at all. Since, you know, they would be same and have no differences.
Preventing Python "Sandbox" Escape?
I'm using python's exec(code, globals, locals)

I disable __builtins__ so no imports, exec, eval, open, etc. inside that context

but it seems you can still always do object.__subclasses__() and find every system method (eg. open())

it can't be overwritten but looking at the interpreter code is seems like it's possible to hack a workaround for this specific case.

are there other known ways to escape exec()?
Just in case this has to be said: the reason this hasn't been a problem in the past is because you could solve this problem by picking a team and completely breaking support for the others.

With rapidly improving single-image i18n in OS and apps, "breaking support for the others" slowly became non-ideal or hardly viable solution, and the problem surfaced.
sorry but this makes no sense: if you infrange a US law, but you neither are a US resident or citizen, or you never even been there, why this law should apply to you?

perhaps nz is indeed a US protectorate if it allows this
Torille! https://www.urbandictionary.com/define.php?term=Torille%21