"I feel uneasy about design patterns. On the one hand, my university class on design patterns revived my interest in programming. On the other hand, I find most patterns in the Gang of Four book to be irrelevant to my daily work; they solve problems that a choice of programming language or paradigm creates."
My relationship with design patterns changed when I stopped viewing them as prescriptive and started viewing them as descriptive.
Not just dirt cheap, the turn around time to manufacture was significantly lower. Sony had an existing CD manufacturing business and could produce runs of discs in the span of a week or so, whereas cartridges typically took months. That was already a huge plus to publishers since it meant they could respond more quickly if a game happened to be a runaway success. With cartridges they could end up undershooting, and losing sales, or overshooting and end up with expensive, excess inventory.
Then to top it all off, Sony had much lower licensing fees! So publishers got “free” margin to boot. The Playstation was a sweet deal for publishers.
Yea, people generally don't think about these things. People were genuinely surprised to find out that 70% of our expenses as a software business were... salaries. The next largest category? Rent. Everything else was effectively a rounding error.
I just bought a house this year, the previous owners lived in it for about 2 years from brand new. Thankfully it has an ethernet drop to every room upstairs, and in reasonable places on the main floor. Far better than the situation at the last place I lived in.
But annoyingly, it's all Cat5e! Sure, it's fine for gigabit, but now that I have proper networking equipment, I wish they'd have spent the extra few bucks and put in Cat6A or Cat7 so that I could get 10Gbps to my office from the rack in the basement...
I do wonder how much of an impact the PS5 and Xbox Series have on this though since they both have RDNA2 GPUs. Consoles tend to face higher optimization pressure, especially as the generation wears on. It might be why AMD has kept so competitive in gaming as of late.
Like, SBCL compiles and assembles directly to machine code, that's very much the Lisp way. But SBCL has a lot of C that's involved in getting the SBCL image running and interacting with the host.
It's more that it's easier to use C for two reasons. The first is that C is really popular and therefore pretty portable. It's a lingua franca. The other is that because the hosts are largely defined in C, it's easier to interact with. Of course, the host doesn't actually "speak C", it follows some form of ABI. But the reality is that implementing each ABI is non-trivial and you can avoid a lot of pain by just using the host's C compiler/linker/etc. that implements it for you.
I know. I've been spending a lot of time with CL, Scheme, and Clojure the past few years, and the ideal Lisp is some combination of them all. There are aspects of each that I miss in the others. CL has the nicest environment and development story (generally speaking). Scheme feels more refined in the small. And although they can be divisive, I really appreciate Clojure's data structure literals.
My understanding is that that's a non-trivial problem. You'd likely need some sort of AI system to do it, since the perception of colour isn't something that can be simply modelled.
Yep, it's saved me a lot of time on data transformation tasks. For instance, I wanted to convert the colors in Tailwind to CSS variables. I had the JSON listing all of the names and hex colors, I just needed to rewrite the names and convert the hex to base 10. A rather straightforward mapping, but I'd need to write the function for it. I just asked ChatGPT to give me the function. I read the function, it looked good. Boom, done in less than a minute. What's funny is that ChatGPT started spitting out the expected output of the function. And it was right! Perhaps surprising on the face of it, but really it's a simple pattern mapping.
I’ve been very happy with mine playing games of all vintages and development budgets. Just this weekend I was playing Far Cry 4 and The Division 2 quite smoothly.
My impression was more that he just wanted to do Star Trek but the studios were like "it'll be funny right???". And so he went along with it at first, but dropped it as time went on.
On a related note, I've been rewatching Enterprise and I didn't know Seth MacFarlane made 2 cameo appearances in the series! (In two different seasons too.)
It's easy to forget nearly 10 years on, but React came out when Backbone.js with mustache templates was rather common, and React was a LOT easier to manage. The other popular frameworks at the time were Ember and Angular 1, which were quite a bit larger/heavier. By comparison, React could be adopted in a much more incremental fashion. React was super easy to adopt (and it still is, but there's a lot more of an ecosystem around it now which makes it feel much more like a framework).
I used to have two otherwise identical displays, but it still does it for me now that all of my displays are different. Notably, I think this stuff happens more when you have 3+ monitors. I don't remember having as many issues with just two displays.
Interesting you say that about the Airpods. In my experience I've found that Airpods work extremely well so long as they're only paired with your Apple devices. Once I paired them to my PC I started having issues where they'd drop from my iPhone randomly in the middle of playback. After unpairing them from the PC altogether the problems went away.
Pretty much every thread on Tailwind will devolve into debates on CSS development/maintenance practices. My take is that Tailwind enables a style of CSS development more akin to using a dynamically typed language. It's really great for whipping things up and for one offs. And for so many tasks, that's all you need!
But of course, there are situations where it becomes unwieldy. I'd wager that a lot of the problems people have with Tailwind are more social in nature. Which are valid problems! It just means that you need some other solution for that. Analogously, many of the benefits of static typing are social in nature; notably in enforcing interfaces between teams. I suspect people are looking for a similar thing for CSS. But that doesn't invalidate the use cases where Tailwind is particularly handy.
It’s definitely context dependent. But I spent the last few years of my dad’s life not really speaking to him much, and when he died - suddenly at the age of 53 - I realized it had been for really petty reasons. The things I disagreed with him on blinded me to what really mattered: he was still my dad.
This year I sold my company, and as exciting as that has been, I wish I could have told him about it. :(
This is why I find prototype-based object systems so much more natural. Inevitably any dynamic object system ends up having to represent classes as objects, but that retroactively opens up a lot of mind-bending complexity. Prototypes on the other hand make far more sense in a dynamic context. You just create objects that you can clone and extend. Classes just become a design pattern. It also highlights that the interfaces of an object are more important than the class.