WJW · HackerTrans

22 saat öncediscuss

That's wild. According to the website of my local ambulance organisation, a full on ambulance ride with all medical supervision etc runs between 400 and 900 euros. Typically this would be reimbursed by the (mandatory in this country) health insurance. This is in a large city in western Europe, I would expect it's cheaper in places with lower cost of living.

EDIT: their own website states "If the ambulance only comes and stabilizes you on the spot but you don’t need to be transported, there are no costs." https://ambulanceamsterdam.nl/information-in-english/

WJW

7 gün öncediscuss

Do you mean Kramnik or Hans Niemann?

Kramnik ((ab)using his status as a former world champion) accused several other top level players to the point that one of them committed suicide.

Niemann allegedly cheated (In my personal opinion as a decently rated but certainly not elite chess player, he probably did cheat in this particular game, though proof was never given and probably never will) at a high level chess tournament and was ostracized by the chess community for a while. He has since rejoined and continues to play at a high level.

WJW

10 gün öncediscuss

It wouldn't have been true even if all young people in our generation would have had all the access to computers they would've liked. Most people just don't like tinkering with technology and that's fine!

The whole argument is pretty dumb anyway. Just try replacing "computers" with any other technology and you see how weird it starts sounding.

- "People use roads every day but almost nobody even knows how to make asphalt from scratch these days."

- "People use electricity every day but almost nobody even knows the basic equations for electric generators."

- "Children these days use refrigerators only as consumers, they don't even understand the differences between HCFC and A3 type refrigerants..."

Computer programmers despairing about how few children understand computers has strong vibes from https://xkcd.com/2501/ IMO.

WJW

10 gün öncediscuss

"Young people know all about computers" was never true either. It was maybe true for people like you and me, the type of people who now frequent places like HN. But for the vast majority of people, computers were never all that interesting.

WJW

10 gün öncediscuss

When I look around at my generation it's all too noticeable that most of them are barely capable of using a computer for more than watching youtube either. And both generations older and younger than mine have generated exceptional programmers.

Whatever dictates if people are capable of creative work with computers, year of birth does not seem to be it.

WJW

11 gün öncediscuss

No, that person is just the only one in his family who knows how computers work. There's plenty of people in generations both older and younger that know too, just apparently not his parents or his kids. Some of the most impressive assembly written today is by people younger than 20. It'll be fine.

WJW

11 gün öncediscuss

You could always have mixed rockets if you loaded them yourself, which wasn't ideal but not toooo much of a hassle. For me it was more that rocket platforms are dog slow to produce and can be shot up at only 50 platforms per rocket. Not too horrible in the endgame when you may have dozens of rocket platforms, but in the early to mid game it can really strain my rocket capacity sometimes.

I plan to have a slow but wide platform with lots of storage that just loops around between Nauvis and to hoover up as many metallic asteroids it can find, then turns them into space platforms. When it loops around to Nauvis, it ships off the platforms to any spaceship under construction that might need them.

WJW

11 gün öncediscuss

I don't think it'll be too hard; you can build infinite legendary iron from just a dozen or so foundries on Vulcanus. Legendary coal and stone are not much harder, and from legendary coal you get legendary plastic and then legendary steel and copper via the LDS shuffle. It's not quite as broken as the asteroid casinos and feels much more factorio-y IMO.

Avadii made a great guide about good ways to farm legendaries in 2.1: https://www.youtube.com/watch?v=ZuwBnOsULkc

WJW

11 gün öncediscuss

I'm especially stoked about space-to-space logistics. One of my first projects will be an in-orbit space platform factory, so that making a new space ship won't take a bazillion rocket launches just for the platforms.

WJW

14 gün öncediscuss

How does that change matters? If anything that makes it even worse. If not enough of your people can't be bothered to join the military even when an enemy army is invading, perhaps the country in question should draw the conclusion it's not viable as an independent nation.

WJW

14 gün öncediscuss

If the country doesn't have enough people to defend it, perhaps it's good and just that some other community gets to control the territory? A country isn't really anything except for its people, after all.

WJW

18 gün öncediscuss

Why do you think stablecoins cannot be taken away? There are already many cases where eg Tether got a court summons and handed over the contents of certain wallets to the local authorities.

WJW

18 gün öncediscuss

Not GP, but I think they mean usecases like limiting how many times any given IP address can access an API to a certain amount of calls per minute. For example, you might want to restrict login attempts to at most 10 per minute per IP to prevent people trying out lists of common passwords.

This is fairly easy to do if your apps runs on a single server, but many companies run multiple servers and load balance requests among them. Those servers need some sort of coordination mechanism to keep track of the rate limits and their current state. Redis has dedicated instructions these days to do this, and in the old days there were plethora of libraries that use embedded Lua scripts to do the same thing.

WJW

18 gün öncediscuss

Non-caching things I regularly see people do with Redis:

- Rate limits for API endpoints via the leaky bucket algorithm

- Feature flags and stats tracking

- Websocket pub/sub

- Background job queue

In general, lots of things that need to survive deploys (so they can't be in-memory in the app) and/or they need to be coordinated across multiple horizontally scaled servers and/or things that prefer to be in a data structure which is slightly awkward to stick in a database table.

WJW

21 gün öncediscuss

Oh don't worry, if history is any indication it shouldn't be much longer than 30-40 years from now. Basically 2 generations from the previous shift.

In the meantime, be the change you want to see! You don't have to be darker&grittier yourself just because the media ecosystem has decided that's where the current fashion is.

WJW

23 gün öncediscuss

Not GP, but after doing Crafting Interpreters I was kinda left with a gap in my knowledge regarding the conversion of an AST into native code. Also kinda missing was optimization passes over an AST. I somewhat understand the idea, but it would definitely be nice to have a more guided book/article for this.

Crafting Interpreters is definitely a recommended read, but it stops at Interpreters (fair enough, the book is thick enough). Crafting Compilers would need at least 4-5 extra chapters IMO.

WJW

geçen aydiscuss

Stick two of them together on the same axle then.

WJW

geçen aydiscuss

Eh. The only real things you need are:

- On startup processing begins at a known address, and you put the bootloader code over there. Hardware engineers can guarantee this for you.

- Every time you execute an assembly instruction, the program counter either explicitly jumps to a new location or else it just increments by 1. Hardware people can also make this happen as easily as implementing an adder.

Don't get me wrong, there are LOTS of layers between the hardware and most "useful" programs any of us will ever write. But all of them are pretty understandable. They're often not very complicated, just tedious.

WJW

geçen aydiscuss

Ehm no? Do it yourself if you want. I'm already happy.

WJW

geçen aydiscuss

Well the most basic redis replacement would be just a global hashmap to replace GET and SET, possibly with a background thread to periodically delete expired keys. But obviously that stops working as soon as you get a second node.

The entire value of redis IMO is that is ISN'T inside your normal application, but rather some shared storage that all nodes can use to coordinate and that survives deploys, but that provides more ergonomic data structures than SQL databases. Caches are only one type of such shared data, but things like feature flags, circuit breakers and rate limiters are also super common (and super useful).

comments