dsego

My t480s is also very light as is the framework 13. I was actually surprised how heavy the m1 pro was when i got it, much heavier than the intel 13 before it, but more like the macbook from 2012.

I think there was a modifier key + click and drag to simulate a pinch, so at least some gestures can be simulated. But since one is developing for the mobile device, it makes sense to tether the device and send builds to test out on the target device itself.

I thought that they would basically replace macbooks with ipad pros. Sort of like microsoft surface, a tablet-laptop combo. Not sure what their plan is now.

Pretty useless, it's easy to simulate touches and gestures already.

How is it convenient? A pro workflow is not holding your arm with the finger up in the air trying to avoid accidental taps, when you can get a small 25 key akai midi controller for a 100 usd. And it's easy to carry around and comes with velocity-sensitive keys and pressure-sensitive pads.

Their marketing web page shows someone poking with their fingers at the virtual keyboard and it's so cringe. Who is going to use their laptop that way? For pro workflows? Pros have midi keyboards with pads and those are even not that expensive.

I agree, if it has too much friction it's more likely you will postpone it. Any option, either just a cloud backup tool or a spare HDD or SSD with CCC or TimeMachine is better than nothing. And you have to plan for the most likely case, e.g. spilling beer on the laptop vs the house burning down.

Why is antiquated?

I wanted subgrid a few years back. Imagine you need to show 3-4 pricing cards next to each other. It can't be a table, the cards have padding, an outline, shadow, etc. Inside they have rows of features. But some of the items aren't just a single line of text, they wrap around, and you need to have the heights of those inner rows align between the cards. It's not possible without a subgrid or some custom JS code.

Give it a more charitable reading. But I think there is truth to it, CSS was never that great with just describing what you want, it was always more like arcane spells and tricks you learn to achieve a specific goal. Historically just trying to center something or achieve equal spacing would send you down a deep rabbit hole of quirks, browser support, layout modes and so on.

Like Rust, CSS is a great language if you never ever have to actually look at it.

It failed because it married selectors to the content, so the CSS rules inevitably follow the document structure. You can avoid it by either using utility css, avoiding descendant selectors or using some methodology like BEM and use only classes to style elements. There are two types of separation here, same document that can be styled differently with a different stylesheet (think zen garden), but the other one is reusing the same look&feel across different web pages. These two goals are not always compatible. The other thing to consider is that maybe HTML itself is the presentation layer, data usually lives in a database or different file formats, JSON, CSV, excel spreadsheets. A lot of the aspects of laying out the content is trapped in how you structure the HTML, and no amount of CSS can change how the document is organized.

I don't know, sometimes I feel like I've been misled, I come back to the code that was generated, I find so many bad choices, claude never subtracts, it keeps piling on new code. Some minor things get declared as unbreakable rules, regardless of context. It memorizes the tiniest exception as some big decision and all new code follows those new rules it made up. Good luck cleaning up all the nonsense to all who just vibe coded their apps. It has to be steered constantly, if you care about understanding the code that is. The LLM will happily use gibberish variable names, long functions that mix responsibilities, inconsistent code style and so on. Give it a prompt to review the code over and over again, ten times in a row, it will always find something, that one race condition that wasn't handled, or it will warn about something that is clearly not important, but it won't realize that it showed rendering code into the core logic component. It can fix it once it's pointed out, it's good for refactoring and doing sweeping changes across the codebase, but it's better to be on top of things, because it can lose its way behind your back.

I'm very critical of myself and my family, she was the head of the house so to speak, and she was the one making decisions. She didn't want to see the doctor so in those few weeks we gave in, I think she was afraid of everything that followed, the prognosis wasn't good. Nothing in the slightest prepared us for this outcome, it was a total blind spot. It was very much in the wrong moment, many different life changing things all at once.