ThePhysicist

Wall heating, it's like floor heating, just on the wall.

I mean it's mostly about energy efficiency, a well insulated house is as easy to cool in summer as it is to heat in winter. Most heat pumps can also cool and new construction in most European countries like Germany is equipped with floor heating and central ventilation which in summer allows you to run around 18 degree Celsius hot water through the system to cool it, that yields around 20-40 Watt of cooling power per square meter, and that's often sufficient to keep things chilly. Mind you not American style 18 degree Celsius kind of chilly, but 20-25 degrees easily, which I think is quite nice. The bonus of this system is that it's mostly "radiative" cooling as the cold surface acts as an absorber of infrared radiation, I find it much more pleasant than having cold air blown into your face.

We equipped our founding era building with wall heating and will test out the heatpump based cooling next summer, if it's not enough I would consider installing a small AC unit, that's super easy as well.

Don't know what the article wants to say, there's no ban on AC anywhere in Europe and small units are quite affordable, you can get a single split unit from Mitsubishi for 500 € from Italy. The only nuisance is that installation is heavily regulated in Germany so they rip you off with insane cost. That's definitely a thing that needs to change in my opinion.

I mean I can deliver the same software in one month that I delivered in maybe 3 months before and for many things I don't need a dedicated frontend developer, designer or writer anymore. So for me it's the case!

Seems hard to believe, I mean I'm not an AI absolutist but as a programmer it allows me to automate simple things like writing small patches or config changes in a matter of minutes where before I would have invested hours, so hard to believe that it won't at least bump productivity up by 20-60 % overall, it's also tremendously better at finding relevant content and curating it than me so that's another time saver unrelated to programming but relevant for any type of knowledge work. Friends in research and medecine and law also tell me that AI has drastically accelerated their rate of processing and ingesting any type of information and helped them to automate aspects of their jobs. So not sure but negligible isn't the word I would use here.

Personally I feel a bit sad and annoyed sometimes, lots of folks I know that are working in some non technical roles e.g. lawyers in public departments or doctors in medecine come to me to show me their apps and tools and data science scripts they've written, and I have to admit their work looks totally respectable and they get it published on the app store. It can be a bit demoralizing as I feel like IT/software doesn't have any protected spaces for us engineers, whereas e.g. my friends in medecine or law feel fine as even though AI might come up with diagnoses or law expertise it won't be legally allowed to replace their function as there's a ton of red tape to ensue only certified lawyers and doctors can practice law or medecine. There's nothing like that in software engineering (at least in most fields) so in principle every "hack" can let their vibe coded data science results, software or script loose on the world. To a degree it feels quite disprespectful even. But it has always been like that I guess.

Not sure if I do anything wrong but Codex with Sol made such slow progress on my work, I iterated several days to do a redesign of my UI and it kept making small piecemeal changes then stopping and asking me for confirmation again and again even though I tried to get it to get bigger chunks done. Switched to Claude Code and had the redesign done in a short session within a day.

Maybe just the system prompt or my settings or the harness? Anyway, it seemed to me Codex was just deliberately being overcareful and wasting tons of tokens for a low-risk CSS / HTML refactoring with very minor breakage risk, while Claude got the job done immediately.

Would really like to know how their watermarking technique works, and if they can use it to store arbitrary information in the text (I assume they can if only in a limited way). I assume if the text is long enough they could add all kinds of metadata that would then be undetectable as the model that generated the text is the "cryptographic" key that encodes the data. I wonder if you can have another model run over the text and destroy the watermark. I predict an interesting cat and mouse game to develop.

Maybe those engineers that don't care about making their solution _good_ are actually the good engineers, have you ever thought about that??? There are exceptions where quality really matters but most software shops build CRUD web apps where it's not really a good characteristic to obsess over the cleanest and most elegant details, instead you need to get the stuff the customer wants done!

I for one tend to care less about the minutiae of solutions implemented by AI as long as it gets the job done, I do care about architecture and design decisions and correctness and I have ways to steer and verify these when working with LLMs but I couldn't care less about it writing "good" code. Bad engineers also produce better results with AI at least when they're working in established frameworks, AI doesn't really need a lot of high level architecture input when designing or building a web app with a common stack, so as long as you're not working on something that's completely novel I don't think it will make a strong difference.

Maybe designers think the same way about the AI generated web designs I have Claude Code do for me but to be honest I don't care, I just know that before this tool existed it would have taken me weeks or months to come up with a good design and I would have to rely on prefabricated UI libraries and stuff like that or pay a designer tens of thousands of USD to make one for me, now I can get a (for me and my customers) perfectly acceptable and professional design within a few hours. So maybe I'm also a bad designer that amplifies my bad design taste 10x in my company, but the fact is the stuff ships and makes money and the customer is happy! And I can tell you customers or users don't give a shit about how good your code is, they only care if the software works and does what they want!

I don't know, 12,000 USD a month is a steep price for having someone vibe code frontend features for me.

I don't know, I find AI still misses the mark so much for stuff that's not happening inside a well constrained framework with very specific guardrails and boundary conditions. Every time I have agents build something half complex that I would be easily able to pull off myself (albeit not at their pace) I always ask if everything is correct and working and I get a resounding "yes!", then I test it and it's essentially a steaming pile of garbage which I then tell the agent and after which it goes "you're absolutely right to push back, this isn't good at all!" as if it was clear from the beginning. I don't know if we'll achieve real intelligence soon with these things but what we have now isn't there yet. It's incredibly useful but I don't think you can replace a good programmer with it, you can make a good programmer into an excellent one though!

Same goes for writing, anyone who has written long complex texts with LLMs knows that a ton of editing is required to make it half decent.

When will we see the end of ads disguised as tech opinion pieces?

Which manufacturer was that?

Coming up with solutions isn't so difficult, getting everyone behind one is the hard part. Obviously easier if you're one of the two biggest AI companies in the (Western) world.

I think Valve is just going to kill Xbox in a couple of years. Basically Microsoft is planning to make the next Xbox an "ordinary" Windows computer with a different UI as well as vendor-locked hard- & software. So essentially you'll get a (maybe) slightly discounted small form-factor PC for the living room that only runs games from the Xbox store, which will be more expensive than the same games on Steam.

Now, everyone laughs about the "ridiculous" pricing of the Steam machine but once hardware prices come down they will make a second generation that will be an unlocked PC in the same form factor and probably just as powerful as the next-generation Xbox. They might even pass on some of their supply side bargaining power to the end user. Then you will have the choice between a fully locked down Windows PC that only plays Xbox games for 1,000 USD or a fully unlocked Steam machine that plays everything from the Steam, Epic, GOG store, can install regular games and even lets you do work on it, for probably around the same price. Built by a company that has the highest gamer trust of any company we know. Guess this will be a no-brainer for most folks! They have everything to pull this off as well, the brand, the trust, the gamers, the store, the platform, the money, the market power as well as experience with hardware. My take is that they wanted to pull this move already but the AI craze made that impossible so they are using the first-gen Steam machine to learn about the market, but I predict that once prices come down we'll see an announcement, they can time it to match the new console generation by Microsoft and Sony as well. The market should be in a great state by then as well, lots of folks were essentially priced out of the GPU market and NVIDIA won't even release a new generation of gaming cards anytime soon, so all those people that have the buying power but don't know where to put it would flock to a new Steam machine if it can deliver good performance for a reasonable price. And the thing is Valve will have the power to make sure studios optimize games for the Steam machine as well.

Really don't know what Microsoft is doing here, they turned one of the most profitable and beloved gaming platforms into something that seems to be in a death spiral, people are already speculating they might sell the whole thing off eventually.

There's this great blog post by Joel Spolsky from 2000 [1], where he essentially argues that controlling your environment makes you happy. He writes about his summer job in a bakery and how the dough mixers would be so unpredictable and how frustrating that was. I think AI agents are quite similar to a lot of folks, they change significantly with each major model update and even every day as the vendor tweaks the system prompts and settings, so you never feel "in control", it's more like pushing buttons on some blackbox and hoping the right stuff happens inside. Most people are unhappy about that as it takes away the mastery and craft aspect of software development and makes them managers of unpredictable AI tools. I certainly get this feeling even though I like AI in general, but having days where everything goes so well working with the agent and then days where nothing really seems to work and not knowing why is quite frustrating.

1: https://www.joelonsoftware.com/2000/04/10/controlling-your-e...

Interesting point about "letting go". I hear that quite a lot, which I find surprising. In IT, when new technologies like cloud computing emerge people always need to adapt their workflows, and for some that is challenging e.g. going from manually maintained servers to virtual machines or containers that are just spun up and down on demand. Maybe it is similar with AI, we gain new capabilities along one dimension like speed of development and we lose some capabilities along the way e.g. manual control of quality. And of course there are large financial incentives here as well, maybe they are larger than we have ever seen before and the change also happens faster. Cloud computing took probably multiple decades to be fully adopted (I think AWS became available in 2006 and we still see large corporations migrating to the cloud from their on premise setups today, though the adoption curve is flattening), LLMs have significantly higher adoption after only around 2-3 years of them becoming "production-ready". So naturally people struggle with how to adopt them and we need to figure out where they make sense and where not. That said it's precisely an engineers' job to figure that out, people that just see the upsides of this technology seem quite naive to me.

I can see this struggle it in my organization as well, in the last year there was a big push to adopt AI everywhere and tons of initiatives to automate processes and produce code and text and other artefacts with LLMs. Now it seems the pendulum is swinging back a little as people see that all of the LLM generated stuff shows all of these subtle quality degradations, and people get tired of managing it as they are suddenly confronted with tons of additional information they need to manage.

Given that models are still evolving and becoming better at a rapid pace I think that we will solve most of these issues in the near future, but for now I don't think the age of hand crafted code is over yet.

I have been thinking about that machine code analogy before as well, I don't think it really holds. Machine code is written in an automated way but following mostly deterministic rules that have been crafted through decades of manual optimizations and testing. AI generated code has nowhere near this level of scrutiny, testing and optimization behind itself. The fault rate of compilers and optimizers is incredibly small (I can't find any numbers but it must be on the order of ppm or ppb), AI generated code has fault rates that are even in the best case on the order of 99-99.99 % maybe (i.e. between one error per hundred lines and one error per ten thousand lines in the best case), try building anything complex using such a fault rate without manual correction and review. It's impossible. I have done it, I dabbled with writing a compiler, a database and even a simple web framework from first principles. I didn't get far, even though I had good mental models of these things and I carefully wrote RFCs and documents for the LLM, specified test cases etc... If you're lucky it will regurgitate some existing code or follow documented guidelines, but when you're on new territory these models won't be able to produce anything good. I would really like to see a single example of someone vibe coding a high quality library or tool with LLMs, I haven't found anything and no one can point me to a complex codebase (say 10,000 lines or more) that was generated using high level prompts that looks decent and doesn't have multiple glaring issues that appear when looking at it in detail.

Oh for vibe coding small scripts it's great. Experience of people with AI can vary, I don't see what attitude has to do with this, at this point I have probably spent thousands of hours trying different strategies to leverage LLMs in my workflows both for code and other artefacts, so one cannot say that I'm not enthusiastic or open towards this technology, I want it to work for me. In some cases it works great and capabilities have increased a lot (the models I used two years ago seem so primitive by todays standards, I wonder how I could even have done work with them), but for me the tools still aren't good enough to be left writing products unsupervised. Maybe that is an attitude thing, but reading raw LLM generated text or code surfaces a lot of issues, and it requires heavy editing to make it meet the quality bar that I have. I'm not the only one seeing it like that. I could just throw that overboard and be happy, in the end I always make the LLM produce what I want, at least superficially, so like other people have suggested maybe I should just let go.

I get that people without this mental baggage will adopt LLMs more easily as they do not care about any of these and they are often not able to perceive quality. And maybe quality is something that doesn't even exist and doesn't matter much, in the end people don't care how the sausage is made and what is inside if it tastes good and nourishes them. It surprises me though how fast most "engineers" throw away their engineering principles when using these systems. So I could also say mean things like maybe these people weren't good engineers to begin with. I guess the divide is more between people that care about the underlying principles and quality of their work vs. people that care about being done and having the desired effect on the outside world through their work. For software that's more acceptable than in other engineering disciplines I guess, people won't get harmed (much) if your vibe coded SaaS app crashes or leaks your whole user database. Trust into vibe-coded software seems to be higher than I think is warranted though, which makes sense as the companies pour trillions of USD into marketing and getting people hooked on these systems. Feels a bit like the whole crypto bubble, LLM absolutists aren't that different from crypto bros in 2015 that were certain traditional finance was doomed and in five years our entire life would play out on the blockchain. I don't think it's entirely comparable though as LLMs have tons of real-world use cases. And I think it's not surprising that people have such strong opinions on them, there were similar discussions about Rust or frontend frameworks, seems in tech there are just types of people that discover something new and immediately think it will solve all of their issues and that anyone who has a different experience must be wrong, even though they are only seeing a tiny part of the whole problem space. So, glad people get value out of LLMs and I do too, but I don't get how one can use models and not see these quality issues.

Maybe one point regarding quality, even for small scripts that I write using LLMs e.g. for data analysis I have to be very careful as they will often create subtle mistakes that ruin the whole analysis. Things that are not per se wrong as the script runs and produces the desired output (which the systems are optimized and trained for, i.e. they know how to create a script that works and kind of corresponds to the prompt), but in disciplines like data science where you need to think carefully about every step of an analysis LLMs are quite dangerous as they produce convincing looking results that seem correct at every stage but are completely wrong. The only way to get that right (in my experience) is to go really slowly testing each step individually with known good inputs and outputs, giving the LLM that as a harness to work in.

I have been looking at LLM produced artefacts for a while now especially in data science and there are very cases where the models actually produced something entirely correct, at least when it's more complex than averaging some numbers or other simple things. The same goes for writing, superficially it looks good but there are often subtle inconsistencies that the model just doesn't see and that are hard to spot. And again, some people will just look at that and think "that's fine!" because they just can't see the quality issues or they don't care about them, but that doesn't make these issues disappear...

Think about it statistically, the benchmarks say clearly these models produce correct code in maybe 90-95 % of cases for most complex questions. That sounds high but given that a real-world system can consist of e.g. 100 such individual components then even a 99 % correctness rate at the level of an individual component gives you only a 36 % correctness rate for the entire system! That's also true for papers, presentations and anything else. Again, most people won't even understand this, for them something that looks correct and works is good enough.

Yeah I have a lot of experience writing software. My code is written mainly in Golang, but I had models write different code in Javascript, Rust, Python, Shell and other languages already. I used a variety of frontier models over the last years, always the best available model at the time.

I prompt LLMs by writing design specs and iterate on them first, then let it implement them step by step, checking the results after each step. That works fine for simpler changes where I use the LLM to write code that I have mostly worked out in my head, it always goes wrong once I try to do that with larger features. I have tried a lot of different things like writing extensive RFCs and design docs for the whole codebase, building harnesses and evaluation loops to ensure we stick to specific paradigms in the codebases but the LLMs still deviate from that in sublte ways and spuriously introduce duplication, wrong abstractions or simple hacks. That said my codebases are quite complex, it's not run of the mill CRUD software, I suspect these LLMs would do much better on these. That's probably why other people report large success using AI based development, 90 % of apps out there are just plain RoR or Django backends, React or Next.js frontend or Android apps, and they are already built following strict cookie cutter recipes, LLMs have no trouble following these. My work is e.g. on novel parser generators, graph data persistence layers, format-preserving pseudonymization and personal information detection in unstructured data so there's really nothing that you can base the software design on apart from general principles, I suppose that is why the models struggle so much.

There was a discussion here explaining the attention mechanism of the larger models and why they are not good at using their full context length, that was quite enlightening to me as it explained a lot of the behavior I saw on more complex changes, so I think one mistake I made was to have too long conversations with too much context (even though "on paper" the context length was fine and well within limits of the given model), I guess I need more careful conversation management and in general reduce the level of abstraction I'm working at with an LLM. For me at least they're not yet good enough to work at the business or concept level of abstraction, but they are capable of speeding up delivery of finished architectural designs.

Maybe it's also a perception problem. A lot of people will just look at their AI generated software and check that it does what it's supposed to do on the happy path and they will be fine with that, calling it a day (and to be honest I did that too for projects with tight deadlines, though it feels irresponsible). Especially juniors or people without programming background don't care about how the code looks that the AI wrote, I only see these issues because I have 10+ years of experience working by hand in large codebases and I have developed a "taste" for what good code is supposed to look like for me. That might explain why people are feeling so radically different about LLMs, if you don't have all of that intrinsic baggage that senior level developers have amassed over their careers then AI generated code will always look good to you. And maybe they are right, could be that in 10 years no one looks at any code anymore and we just care about tests and making sure the behaviour is correct. To be honest I never looked at Assembly code in the last 10 years and I don't care how my compiler unrolls my loops (mostly) as it's a solved problem for me, maybe it will be similar with the higher level code, we just move the abstraction that we work at to a higher level. But I still feel that we don't have the right tools for working at this higher level yet.

I'm about to throw away multiple months of LLM generated code for one of my side projects. I was really careful writing design specs and it wasn't even a new code base the LLM worked on, but still after several months of AI changes I feel my code degraded more and more into a subtle mess. Hard to explain, each individual change looked good and logical and on the surface the codebase looks fine, but looking at the whole picture everything is subtly wrong in multiple ways. The same goes for where I used AI for existing commercial code bases. I would love to have AI write production ready software for me, but it's just not there yet, there simply are things that good programmers and architects do that cannot be captured by the training loop of current generation LLMs.

I notice the same pattern when using LLMs to write longer text like reports or scientific papers, individually each section they write makes sense but overall the whole document feels off in a hard to describe way. I think it's where you can see the difference between human intelligence and whatever it is LLMs have, it's not the same thing. We are much slower and less able on the small scale but seems we can do some higher level reasoning that is still impossible for LLMs. That always becomes clear when you point an LLM at an obvious flaw it produced and it goes "You are absolutely right!" as if it's obvious in hindsight but when running multiple "Please look for issues" iterations it would never have spotted the issue by itself.

That said I think it will be absolutely fine writing a simple CRUD app for you e.g. using some popular JS framework, Tailwind for styling and a regular ORM, there's more than enough training data available for these things. But then again such software could be purchased before already e.g. as a SaaS template, I don't think LLMs are so revolutionary here, they just replace the template (but to be honest a good hand-written SaaS boilerplate is probably still better than a vibe coded one).

DigitalOcean simply does this at a later stage and will then just cut you off, Hetzner is doing it from the start. Their obligations aren't so different, they just approach this differently. It's the same thing with Stripe, it's cool that they just let you sign up and process transactions but at some point they will look at your business and if they don't like it they will just cut you off.

Also Hetzner really doesn't care much about individuals as far as I know, they mostly do business with other businesses and that's where the money is, their business is not designed to handle millions of individual users, DigitalOcean might also simply have a different strategy there.

Takes me back to when I was working on Josephson junctions (JJ) as a student, I-V curves were the first thing we did when characterizing a junction. JJ I-V curves were tricky due to the hysteresis they have in the underdamped regime, so we had some pretty involved stepping logic to ensure we get the curve with the required precision.

That said today everything is pretty much digital, you have Acqiris/Agilent 1 GHz ADCs and all the measurements are done in software, but I still remember using my old 20 MHz HMAG oscilloscope in XY mode with a triangle voltage generator to plot IV curves in real-time. Good old times!

Congrats Sonali, Nick, Dave & everyone else! I had an incredible time with you all in NY more than 10 years ago, it was so cool, and I'm still thinking of it very fondly. Spent my days hacking away in the space near Canal Street and the nights and weekends exploring NYC with other Recursers, visiting museums, parks and venturing out to buy cheap dumplings by the dozen. I was quite poor back then but I enjoyed my life so much, had a tiny room at the Kolping house on the Upper East Side which was very run down and tiny but also very cheap, basically just went there for sleeping and spent every other minute in the space and outside. No distractions, no possessions beyond my laptop, no responsibilities, simple but happy times. And then in 2021 I found my dream job at DuckDuckGo through RC, been working there for almost five years now! Thanks for everything and great to see it's still going strong!

Interesting that on one hand the valuation of these AI providers is based on the assumption that all code (and everything else producing digital artefacts) will be written using AI in the near future, on the other hand almost all popular open source projects fight to keep AI contributions out. Hard to reconcile.

Personally I'm also experiencing a bit of AI hangover after using it a lot in my own open-source projects. I find it's a bit like taking drugs (not that I have much experience with that) in the sense that in the moment I'm using these tools I feel great and powerful, writing features in a span of hours that would've taken me weeks to write by hand. But inevitably some time later I will look at the code and notice all the subtle cracks and inconsistencies the tool introduced, and despair a bit at the mess.

I now plan to use these tools less for extensive feature development and more for planning, debugging and narrow refactoring where I can put very strict guardrails on them. I'd still say it accelerates my work but not by a factor of 10, more like 1.5-3 (which is still a lot) given the care you need to ensure what is being built is actually good. For what I really like these tools is that I need less mental focus to do coding, but on the other hand I have this new kind of fatigue of being in a constant chat loop with a machine and trying to get it to do stuff based on natural language, never knowing how it will interpret what I write and wrote before. In that sense, these tools don't feel satisfying, it's like operating a machine where you try to push some buttons to get it to do something but the internal wiring changes all the time so you never know exactly what a given button combination will do and you have to figure it out by watching the machine and constantly adapting.

Corporations will be quite happy with really simple features if they're packaged right. I'm selling software that mostly does things that a good programmer could whip up in a couple of days or weeks, but what cost me most of the development time wasn't the features but all the FUD around them e.g. SSO, multitenancy, audit logs, corporate design support, ... Most enterprise software could be replaced with simple scripts and command line tools if they had this enterprise layer. I'd wager tons of SaaS is just simple open-source software and libraries behind a management layer.

Noooo, my /22 IPv4 subnet allocation is my personal 401k, I need this money to retire.

It's quite easy to write a generic Maybe struct that performs most of the encapsulation that Rust's Maybe does i.e. allow unwrapping of the inner type through a function or handling the nil case through a switch like statement. I've never seen this in the wild which makes me think people don't care about it too much. And of course it's runtime based so no compile time guarantees, and just to preempt the expected replies I know it's not the same what Rust is capable off and Rust is of course a much much much much better language than Go.

Personally I do experiment with these things as it makes code more readable, it just seems adoption for generics and what you can do with them is still quite low in the broader community. That said I do not deal with null pointer exceptions much at all, and when I do it's often relatively simply to spot and fix, so for me it's not a large issue.

I think for mostly search-focused use case like the one presented here AI is great as you don't ask it to build stuff or invent new drugs, you just want to retrieve relevant documents with laser precision, and agents can do that.

I think right now I'm mostly disappointed with agents writing code as they always degrade the quality of the codebase after a while, and the same goes for writing in general which just requires a ton of editing and mostly just sounds good but doesn't have a lot of substance in the end. I think you can really tell that these systems are trained to just produce plausible streams of text, especially in longer artefacts you notice that locally the inner consistency of what they produce is great but globally it really falls apart, it's like seeing the limits of their "intelligence".

For search however I really like AI, it has improved information retrieval so much for me where before I had to think about which keywords to use and combine and which filters to apply, describing what I'm looking for in plain text and then having the AI find it for me feels magical. Recently I wanted to find an artist that I heard in some old episode of the KEXP runcast (a running podcast), and I didn't remember anything except that it was rap with a kind of monotone voice a fast beat and a strong accent. Googles' agent asked a few clarifying questions and after a few rounds it found the artist for me, Genesis Uwusu. That's why I think Google will win in the AI assisted search market, they just have the best integration between fast and reasonably "smart" agents and high quality search data. Claude or ChatGPT are too slow and don't have fast enough data retrieval it seems, using them for search feels quite sluggish in comparison.

Apple RAM prices always had quite a bit of margin though, I think they charged around 4x the going market rate per GB (that said you can't fully compare their RAM to a loose DIMM stick). I was planning to pick up a new Mac Studio this autumn, now I'll have to see if I can afford it, though I have been spending 1,000 USD on LLM subscriptions in some months so I guess even a 10,000 USD Studio Mac amortizes quite fast if it allows me to run coding models locally.

Everyone always wants to charge as much as they possibly can, and if SK Hynix would be the only manufacturer prices would be 10x of what they are today. Especially new incumbents will not ruin the market prices as they have the highest upfront cost and their calculation of entering the market is probably based on the high prices that can be achieved. In the long run, more competition is still good as everyone ramps up production to profit more from the high prices and at some point supply will outpace demand and prices will fall (assuming no cartel / price fixing is involved).

It's the ultimate power user desktop system, in my opinion it even dwarfs MacOS in terms of how you can customize it and how it looks. It left Windows in the dust a long time ago in terms of functionality and usability (not that this would be particularly hard given how Windows has been degrading over the last decade). Everything is super snappy, smooth, built-in apps like Konsole and Dolphin are super polished, Konsole runs circles around the MacOS terminal app.

Of course running Linux on modern hardware is still a bit fraught with errors, though it has been getting much better. I run a current gen Thinkpad X9 Aura and apart from the webcam which has fundamental driver issues on all Linux kernels everything runs really well, power efficiency is also great at around 10W, not as good as a MacBook (which I also use daily) but close enough for me, and I still prefer Linux over MacOS any day.