royjacobs

Yes, this would have had the additional benefit that it was going to be pretty performant since having to do z-buffered perspective correct texture mapping wasn't cheap on PC's at the time and the game was already set up to not require any of that.

No, it didn't. It also didn't do any subpixel correction. Instead, there was a lot of tesselation happening to try and mask the texture warping somewhat but it was never really all that successful.

>The golden age of gaming ended somewhere in 2005-ish.

This kind of statement definitely requires a source.

>They are also less about the art, and more about the money.

There have never been more experimental and indie games released than now.

>Again, I find this sort of comment confusing.

Noted.

In what kind of world did you expect that "X is free for me" would imply that nobody is getting paid for anything regarding an IVF treatment? It clearly means that, _other than paying taxes like everyone else in the free world_ I do not have to pay for it.

This is at the same level as finding a free penny on the street and going "No, but hang on, _someone_ paid to mint this penny so I am extremely confused as to why you would say this penny is free?!"

I hope the other posts in this subthread have made things explicit enough for you, and perhaps you can use this discussion as a heuristic for parsing these kinds of statements in the future.

Sure, if for some reason you want to take the most absolute, most pedantic definition of the word 'free' and you are utterly confused by it meaning something else then, yes, it is not free.

I hope this clears things up for you.

Certainly. It's being paid for by the universal basic health care that our government provides. One of the reasons we pay taxes.

Unless you live in a country like The Netherlands, where the first three IVF procedures are, in fact, free. I won't disagree with you on the roller coaster of emotions, though.

How would you debug a program that you don't have source code access to? Or even a program that has a fairly long compile/link cycle?

At my company I've been a heavy promoter of Backstage and so far it's been a wonderful journey. The main thing to realize is that you can't just "deploy Backstage" and be done with it. Rather, you use it as a base and then customize it to fit your organisation. This is fundamentally different from other tooling in the same space, that requires you to change the way your organisation works to fit the tool.

Congratulations on reaching 1.0!

This has been posted a few times now, and while it definitely looks very cool I've not yet heard of people actually doing significant work with it (compared to other open source alternatives such as, say, Blender). Curious to hear about people's experiences with it.

"The number one problem Rust has now is that it’s overall not significantly better than C++"

This might be true for your specific use cases, but I've worked on reasonably large projects in both Rust and C++ and the fact that I don't have to chase various issues related to use-after-free, returning local variables, dealing with external libraries or general metaprogramming is definitely causing me to mark Rust as significantly better.

As always, if you're a C++ expert you'll bound to disagree, YMMV etc.

This is a pretty decent protocol. I've used it to add support for debugging a C64 application via VICE in my 6502 assembler MOS. [0]

The last time I did a deep dive into the protocol it was missing a few features like viewing memory (or, rather, I think it was in the protocol but not really useable in VS Code yet?) but it is a well thought-out protocol overall.

The only drawback is that the communication protocol is different from the one used by LSP, it would've been nice if this had been identical.

[0] https://mos.datatra.sh

I completely agree. I wrote a parser for my 6502 assembler and nom together with nom-locate allowed me to write a parser that could recover from errors, parse trivia, return detailed error messages with locations and make everything easily unit testable. The main drawback was that because it's a strongly typed parser combinator you can end up with some pretty inscrutable errors when you combine the parsers incorrectly.

Most modern music production is predicated on replicating analogue distortion and assorted non-linearities by digital means.

Maybe. It's not like the market for native graphical debugging tools is overflowing with options either, which is why I didn't understand OP's point that well.

Additionally, with some careful coding you can already run WASM+WebGPU applications both natively (e.g. via wgpu-rs) and in the browser, so you can pick and choose the best tooling depending on your use case, so ultimately I guess that's going to be the way forward.

Does this diminish the results of all browsers shipping decent WebGL 2.0 support, though?

Well, as I said I gave it a try very recently and had to abandon it due to wasm related crashes. I'll see if I can restart using it for normal browsing though.

That's odd. I'm running MacOS so perhaps the leak is in the OS layer somewhere.

Oh well. Looks like I'll just have to give Firefox another chance _again_ at some point :)

I used to use Firefox and I'd love to use it again on both desktop and mobile, but it's just so slow, memory-hungry and crashy compared to Chrome.

For example, I work on a wasm project in my spare time and it loads in a few seconds in Chrome. It does so, too, in Firefox, but just the first time. Reloading the page causes Firefox to leak a ton of memory and compiling my wasm suddenly takes dozens of seconds before crashing. And this is just a random anecdote, of course, but it's one of many over the years.

Won't this make leftpad-type scenarios even _more_ likely? What is the benefit?

One thing I don't understand about the JS ecosystem in general is the focus on minified size. This article does the same thing: preact is 6k or so whereas react is 36k.

This comparison seems entirely pointless when the first page load downloads multiple megabytes of assets and, additionally, a lot of users would have React in their browser cache anyway.

The Mac didn't even have memory protection before OSX iirc? I seem to recall that people would have to restart their Mac if something crashed, since it wouldn't be just the application that would crash - it would be the entire OS.

I would argue that every technology presentation he has done is, in fact, a masterclass on how to give technology presentations.

This isn't true. Spring Boot by itself brings in very little, you can however _add_ GRPC, JPA and JDBC support by adding a library and Spring Boot will even autoconfigure it for you.

It's an amazing film, and I adore the soundtrack.

These books were great. What especially captured my imagination were not just the drawings, but the fact that every listing would be prefaced by a print-out of a run of the game. This made it really easy to see what the program was about (entertaining enough by itself) but it would also allow me to map whatever the game was doing with the BASIC listing next to it. This was kind of like using a debugger to step through the program and it was a really neat way to learn about control flow and program structure.

Most photos seem to come from Utrecht, a large city in the center of The Netherlands that has been very busy purging cars from the city center in recent years.

Since you can reach the city very easily by public transport (and is very easy to traverse on foot or by bike) it is quite delightful to be in.

Up until the 1970s there were plans to add a freeway that would cut right through the city. Some of that infrastructure did get built (visible in the photos that now show a canal again) but thankfully they didn't demolish too many historic buildings along the way...

If you are interested in the ways that The Netherlands tries to keep its cities comfortable and reduce car-centricness (car-centricity?) I can recommend YouTube channel "Not Just Bikes".

This is another post in a series about SF2, it's not a duplicate.

Because they were manually drawing and designing the sheet layouts. If this was an automated process, as shown for the CPS-2 titles, then they could (and did) automate it.