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.
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.
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.
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.
We were blindsided, her cancer was completely removed, but even though they suspected a metastatic cancer, histopathology determined grade 4 glial tumor, idh-1 negative, p16, GFAP positive, Ki-67 20-30%. She then developed oral thrush and had a cough, she was also feeling tired and sleepy, and had swollen ankles. Looking back, these were fairly obvious signs. But the surgeons never warned us about any of it, we attributed the swelling to dexametasone, coughing to her smoking habits, her frequent allergies and sinus problems. She was waiting for the molecular analysis of her tumor before starting treatment. Her state would at times improve completely, and her primary care physician dismissed her after seeing her throat, and the blood work was only done a few days later. By then her CRP was already through the roof. Only then was she admitted to the pulmonology department, and she never recovered, went into septic shock and died a week later. I would say that the first symptoms started maybe a few days before going to the doctor, and I suspect had we gone to the main ER in the next biggest city (where she did the operation), she would've gotten a throat swab and blood drawn at least. It's so sad, because it took only a week or two from diagnosis to her tumor being removed completely by skilled surgeons and she never got a chance to fight it. Croatian healthcare is also such that it's better to drive to the big city emergency hospital directly than to rely on your doctor or small local emergency, usually they are understaffed and just plain uninterested.
My mom removed her breast cancer in 2006. It never came back, no metastasis. She did however get a new separate grade 4 glial cancer this year and died within a month of the operation due to undiagnosed sepsis. She was immunocompromised and the medication she was on was hiding the signs of pneumonia. After they completely removed the brain tumor, she looked strong with only minor motor impairment, but she probably picked up the bacteria in hospital.
I remember that a lot of older folks had trouble understanding when to use a single click and when a double click. Clicking twice rapidly was also difficult for them, and they would consistently jerk the mouse and drag things around. Having every part of the interface in earlier windows draggable and reactive made this even more frustrating, since for them things would just disappear from the desktop.
I know from experience that Claude will be confident about something, but when I push back it will concede quickly. And it will happily overly complicate the code, come up with made up requirements or rules that it inferred but are completely bogus.
I could keep pace until about half a year ago. But it meant hands-on typing code for the full work day. Now with claude I can produce similar output in 1-2 hours, most of the time is spent on iterating and having the LLM review the code and fix it by itself and then me testing everything. There is more risk of letting the LLM make judgements and building the wrong thing and me having a smaller chance of discovering holes in the requirements because claude is happy to confidently make the wrong decisions.
I can compare this to my early days. At first I was using Visual Studio like everyone else and relying on auto-complete and built-in symbols to figure out how to make something, or I would just copy and paste examples from the internet, and then tweak until something works. But what actually made me understand what I was doing was switching from an IDE to a simple code editor. Because then I couldn't use auto-complete as a crutch, I had to actually read the documentation, understand how a library is structured, which methods are supported, what the parameters are. This helped me slow down, learn the concepts, instead of blindly throwing things at the problem and seeing what sticks. And I'm having a similar experience with the AI now, it's easier to just prompt continuously, feels productive, but then I find a bug or bad logic and trace it down to a prompt where the LLM made a mistake that I wasn't aware of, and this happens a lot. The solutions it provides are rarely optimal and it's easy to fool yourself that it handles everything.
I just moved into an apartment with ceiling fans made by an austrian manufacturer Globo, one with a broken lampshade, the other with a broken LED module. This was my interaction with them over email about spare parts:
> I have a few questions regarding your products and spare parts:
> - Would it be possible to order a replacement lampshade for this Globo fan and deliver it to [place], [country]? The model is Globo 0350/0351, I have attached a picture to describe the part I need.
> Unfortunately, no—that item is no longer in our product range.
>- Is it possible to order other spare parts, like LED modules for this or other models?
> Unfortunately, no
> - Separately, is the Elina model available with a shorter rod? The ceiling height in the room is approximately 2.6m.
Zed pretty much copied everything over from Sublime, so it's pretty much on par.
Sublime was one of the first editors to have an uncluttered UI without toolbars, but with advanced features, like multi-cursor editing and the command palette.
As a long time sublime users, it still feels superior as it gets lots of small details right, like for example when I do Cmd+P to search for files and scroll through the files it will show a preview, Zed doesn't show a preview until you actually select the file.
But what is the point of the background then? I mean, it seems like we're admitting that the design doesn't matter, then why keep up the ruse? Let's drop design, and keep just plain textual information. There is no substance to it, it's just performative, a simulacrum of design.
> Your phone always has a location lock and it’s super power efficient at getting it.
So why can't cameras do it? They are the same form factor, could be a feature to enable. My smart garmin instinct can track gps for a day, and it's a tiny sportswatch.