Fr0styMatt88

I nearly jumped out of my proverbial seat with joy when Casey talked about it being about where you draw your encapsulation boundaries. YES! THIS IS THE THING PEOPLE ARGUING ABOUT OOP NEVER SEEM TO ADDRESS DIRECTLY!

Honestly would love to see a Kay and Casey discussion about this very thing.

I find the discussions about real domain vs OOP objects to be a bit tangential, though still worth having. When constructing a program from objects, there’s a ton of objects that you create that have no real-world or domain analogs. After all, you’re writing a program by building little machines that do things. Your domain model likely doesn’t contain an EventBus or JsonDeserializer; that purely exists in the abstract ‘world’ of your software.

Here’s a thought: Conceptually, what would stop me from writing an ECS in Smalltalk? I can’t think of anything off the top of my head (whether I’d want to or not is a different question). Casey even hints at this.

This is probably the best Casey talk I’ve ever seen and one of the clearest definitions of ‘here is my problem with OOP’. I don’t agree with everything necessarily, but it’s the first time I’ve watched one of these and thought “yep they actually said the concrete thing that they disagree with”.

Great nostalgia trip, I wasn’t there at the time so for me it’s second-hand nostalgia but eh :)

https://youtu.be/ympjaibY6to

No specifically the question of how do you write maintainable code with generic multi-dispatch and highly dynamic languages.

I like Python, but I like static typing too because there’s just less to think about and when I have to learn a new codebase there’s a lot of assumptions I can lean on about how things work; this saves time.

I like the idea of Smalltalk and when you watch Alan Kay or Dan Ingalls talk about it, they make total sense and you have Pharo and Squeak to back it up as in “yes, you can build large systems with this idea”.

But I don’t think you could program Smalltalk and have it be maintainable without everything else the environment brings. Being inside the environment with your objects. The total different approach of sending a message an object doesn’t understand, then having the debugger pop up and then you just implementing that message right there. That’s just an utterly different workflow.

I like the idea in ‘late binding of all things’ and I think the approach of writing a DSL for your problem and then having to write far less code to solve your problem is great. But the objection is then always “okay but what about when someone else has to work with that code”.

I guess what I’m trying to say is, the more dynamic your language is, the more support you need from your tooling to ease the cognitive load while you program, simply because the state-space of things you can do is bigger and not being restricted by types, etc.

I’ve been doing the once-every-few-years deep dive into Smalltalk that I tend to do out of curiosity and this kind of question is one that always comes up for me. The answer there seems to be “the whole environment and philosophy is geared to work that way”; a dynamic language needs a lot of tooling support and interactivity.

One of the upcoming rumoured new Apple Vision Pro accessibility features will apparently be providing a magnified vision area.

Quest 3 has the passthrough API now that lets apps access the camera feeds as well. I’m eagerly awaiting Meta or a third-party to implement something similar.

There’s also other specialist devices for the vision impaired like myself, but as far as I know none of them give you magnified STEREO vision (although maybe the new eSight does, I’m not sure tbh).

There’s also bioptic glasses, but they’re chunky. Honestly give me glasses with micro-OLED displays like the viewfinder on the Sony DSLR cameras attached to a top-tier phone camera sensor and lens construction; my phone zooms in amazingly far yet is thinner than any bioptic or monocular I’ve ever seen.

I’ve looked into building this kind of thing a few times but I think it might be above the components I can get my hands on.

I immediately thought of the magnetic charging as well before getting to your second paragraph.

One other concern I’d have with wired charging in the car long-term is wear and tear on the USB port and the cable over time (also considering the cable is likely being left in a sometimes very hot car).

For me, Wolfenstein 3D planted the seed and then Doom sealed the deal. Not to mention I was a fan of Sierra games back in the day and the Amiga conversions of the 256-colour VGA games were trash (except KQ6 which I believe wasn’t done by Sierra themselves for the Amiga version). Which was a shame because arguably the Amiga had the best versions of the AGI games (better colour palettes, use of the Tandy 3-voice soundtrack as standard) and great 16-colour SCI conversions (use of sound samples from the MT-32 versions of the soundtracks as far as I can tell looking back).

I was introduced to those albums through this haunting Doom playthrough, highly recommend: https://youtu.be/MwgytHBu4sg

I mean we provided all the data that the AI was trained on, so there’s that.

What happens when all the AI models only have significant input from other AI models?

So much this, when you see Zuck or even Jensen Huang saying "software engineers won't be needed anymore" and being excited about it you get pissed off as a software engineer lol.

I feel like Microsoft's whole thing with Windows 11 has been "just force the users to do what we want them to do, we know better than they do" so it doesn't surprise me that 365 went the same way.

I'm saying this and I'm a person that's usually extremely enthusiastic about new tech, but I'm just burnt out on these companies trying to shove AI down our throats.

Had it been opt-in and gradual, I would be far more optimistic and enthusiastic. I guess my question is "why such a rush?". Even Apple rushed into it with something half-baked and unfinished.

Gotta leave this here for those that haven’t seen it :)

https://youtu.be/9kaIXkImCAM

I taught myself how to free-view stereo side-by-side images on my phone but after I did so I found that I would get strong stereo impressions involuntarily just looking at certain repeating patterns in normal circumstances like watching TV with side-by-side images or when looking at patterned wallpaper.

My visual system is pretty weird in general so I don’t know how common an experience this is with others. It’s not bothersome at all because I know what it is but it was a little startling the first few times.

A few years back I got a nice severance and took some time off, but looking back on it now I do regret not trying to get a job sooner. It would have been so nice just to have that money behind me in the bank while still bringing more in.

The other thing I found insanely wild was that if I looked at a repeating pattern and held still (like say a tiled floor or carpet), the image from my good eye would slowly start expanding over and filling in the big blind spot in my bad eye.

Also if lighting conditions were just right (mostly dim but bright enough to make out shapes like in the middle of the night with only some light coming through windows), my brain would ‘forget’ the other eye couldn’t see and it would look like I could see out of both eyes again. It was trippy as hell.

Yeah should have been more specific there — ‘people that have lost their sight’.

So one of the things I didn’t expect when I had a detached retina…. no darkness in that eye. The big flashing and swirling blob of light was there whether my eye was open or closed, day or night. I could look at it and identify shapes like when you look at clouds.

Many, if not I think most actually blind people don’t see blackness. I’ve read many stories about varying levels of visual ‘hallucinations’. In the absence of input the brain will come up with stuff (https://en.m.wikipedia.org/wiki/Visual_release_hallucination...).

Honestly gaming with either is feasible. HDR in general on the Linux desktop is just in an early phase. I think AMD is just better supported because it’s the hardware the Steam Deck runs on and the fact that AMD is way more open-source friendly.

I’ve seen people on Reddit report issues with both types of card, so it’s really just try it and see for your particular setup.

Just not if you’re interested in HDR and have an NVIDIA card :( (yep it’s improved heaps, I’m just impatiently waiting for the next new feature branch release past 560.35.02 that hopefully fixes colour desaturation in HDR).

Also, I’m really curious how Big Picture can be so broken on NVIDIA. It’s a webview driven by Chromium AFAIK, does general Chrome suffer the same?

In all seriousness though, everything else is pretty amazing. Proton is awesome.

This gets at something I’ve thought about a lot as a software dev.

Making a game engine is a very concrete task, in that you can map out the steps and many of them are well-defined.

On the other hand “make a good game” kinda isn’t. Which I think is a big reason why coders gravitate towards the “start making an engine” route and then fall down it :)

The developers I admire and look up to a lot are the artists that fell into programming. I think they’re the best when it comes to being a successful lone / indie dev for games. Everyone notices art, but you don’t notice programming unless it goes wrong or you know the tech behind what you’re looking at.

If you haven’t already, check if OpenRGB supports it.

I remember everyone saying that CDs were rated for 100 years but disc rot seemed to kill that idea.

The scarier thought I've had -- if a black hat had discovered this crash case, could it have been turned into a widely deployed code execution vulnerability?

Yeah it’s pretty awesome overall. I think the issues are from a few things on my end:

- I’ve upgraded through a few iterations starting with Plasma 6, so my dotfiles might be a bit wonky. I’m not using Home Manager so my dotfiles are stateful.

- Could be very particular to my dock setup as I have two docks + one of the clock widgets.

- Could be the particular wallpaper I’m using (it’s one of the dynamic ones that comes with KDE).

- It wouldn’t surprise me if it’s related to audio somehow as I have Bluetooth set-up for when I need it.

I’m sure it’ll settle soon enough :)

On latest NixOS unstable and KDE + Wayland is still a bit of a dumpster fire for me (3070 + latest NV drivers). In particular there’s a buffer wait bug in EGL that needs fixing on the Nvidia side that causes the Plasma UI to become unresponsive. Panels are also broken for me, with icons not showing.

Having said that, the latest is a pain on X11 right now as well, with frequent crashing of Plasma, which atleast restarts itself.

There’s a lot of bleeding on the bleeding edge right at this moment :)

I loved the Affinity Suite, but it’s such a shame that Linux isn’t supported or that it isn’t provided in a Wine-friendly distributable (a regular installer executable rather than a Windows App Store package).

For me it’s “I swear I feel like I’ve gotten the exact same TOTP code not that long ago!”.

What’s the actual likelihood of seeing the same TOTP code from different apps at different times?

What about those ones that get sent out in phone messages?

What do you mean by “not shipping on the choice you made to ship”? Do you have an example?

Really fascinating thoughts.

I think this is a great point. When looking at ‘best practices’ for constructing robust parametric models I keep thinking “this is so much like software engineering where the programming language is the CAD system” (as an aside, I’ve tried OpenSCAD but found the rendering UI waaay too slow even with simple stuff to be usable for me).

So as a model builder you end up trying to build these higher-level abstractions into your model, where the parameters are your top-level interface.

I think CAD is so much like programming in those ways, although I could just be biased since I’m a software engineer.

I was subscribed to Shapr3D and had been using their parametric beta before switching to Linux and even in that fillets would mess up what I could do with my models afterwards.

The impression I’ve gotten while learning FreeCAD is that making a CAD ‘just work’ is incredibly difficult and the commercial packages probably have a lot of very messy workarounds and heuristics in place to work like they do.

I will say that the FreeCAD weekly builds have made massive strides; I believe the toponaming fix is in the latest mainline weekly now and Ondsel have been contributing great work back from their branch as well.

I’ve been playing around with the weekly version and using the OpenDark theme. It looks pretty slick.

It seems like a really exciting time for open-source CAD (hopefully!).