Ooo the Apple Store has the 14" I want for in-store pickup today... I will have the 16" and the 14" today and have to decide which one to keep π
Expect lots of pictures!
π€€
Donβt have the new 16β but hereβs my 2019 16β next to the new 14β.
When I got the 16β originally it felt like an aircraft carrier but this 14β does feel like a little baby computer now π
Overall the design is beautiful in person, it feels extremely pro and industrial.
The simpler shape makes the previous gen feel like it was trying to hard to be βcoolβ or something.
New 16" is here, here it is next to the new 14":
Here's new 16" on left, and my 2019 16" on the right:
Hereβs both new MacBook Pros and an M1 MacBook Air for comparison.
Hereβs how the 13β and 16β look in my setup in practice, docked as a second display.
Most days I donβt even unplug my laptop, which is making me lean towards 16ββ¦
14β whoops, not 13β π€¦π»ββοΈ
I still haven't had a chance to set either computer up to actually use it, but even with both machines in hand I still can't decide which size I prefer π
Pros for 16" π
π₯ Bigger secondary screen
π Better battery life
β‘οΈ Less chance of thermal throttling
βοΈ More screen space when working only on laptop/traveling
π Better speakers
Pros for 14" π
π More comfortable on couch/in bed, where I literally never use it
16" looks like the obvious choice on paper but man I am struggling to resist the cool factor of having a smaller laptop again. The 12" MacBook still holds a special place in my heart for example, even though there is literally no practical benefit for my lifestyle π
I think I'm leaning 16" because I know I'll appreciate the extra workspace when we're on vacation as a family. But there's a little devil on my shoulder that I know is gonna call me a coward for doing it π
The problem with this decision process is that if Apple made a 20" laptop, that would technically be better on paper too. So there has to be some limit where the size is just too annoying to lug around. Just can't decide if the 16" is at that threshold.
Hereβs an interesting tidbit though β because of the increased pixel density on these new machines, the 14β actually has slightly *more* workspace than my 2019 16β.
So if Iβm happy with my current 16β, I should be happy with the new 14β.
But look at all the extra space on the new 16β!
Hereβs what I actually look like in front of each size. My wife says I look ridiculous with the 14β, and like Iβm working inside a doll house π
I think the winner is the 16" π
Better on paper in every important way, and my biggest concern was just looking like a goofus carrying around a giant aircraft carrier of a computer.
I never stopped to think the 14" makes me look like a fat guy in a little coat instead π
Have been using 16" all day, I literally can't get the fans to turn on. Largest Figma file I have + running my CamLink 4K in Photobooth + screensharing in Tuple at the same time, computer is just like "lol nice try".
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
What's the actual best floor planning tool I can play around with for redoing my office? Hard to find the good stuff, this whole category is SEO'd into oblivion π
Here's where I got with Homestyler which was pretty quick and easy to play with... Wish I could come up with a good way to make it work with the desk in the middle but this doesn't seem terrible.
Hmm maybe this could work, desk not in the true middle but only need access from one side anyways...
Just not sure where to set up the ol' Rocket League station π
Is there any way with CSS grid to say "all rows should have size 'auto', except the last one which should be '1fr'" while relying on implicit rows?
I want every row as short as possible, with the last row taking up the rest of the space, but with an unknown number of rows π€
The image above is the outcome I want, but I don't want to have to use `grid-template-rows: auto auto 1fr`, because that breaks if I need another row. Any way to do it without knowing the number of rows?
Put another way, it's easy to make the first row different than the rest:
grid-template-rows: 1fr;
grid-auto-rows: auto;
But how can you make the _last_ row different than the rest?
Building really great stuff takes a lot more time, attention, and focus than is really possible to understand up front.
It's hard but I've had to learn to say no to even my own best ideas if they mean spinning another plate, or I eventually resent them for getting in the way.
If you want to do a lot of things, focus on things that can be finished.
Write a book, record an album, organize an event, produce a video, give a talk β you can build a rich catalog of work if you are deliberate about doing things that can actually be *done*.
But if you want to do things that can't really be finished (like software), I think the right way to be ambitious is to focus on one thing and make it great.
The sacrifice of saying no to a few fun ideas is not as bad as the sacrifice of never feeling awesome about your work.
It's a set of extensions for REAPER (DAW software) for editing live drum performances super efficiently + a bunch of other productivity helpers.
Although I'd been programming in some capacity since I was 10-11 and had good exposure to basic concepts like variables, loops, etc., I had no idea that "software design" was a concept, and it never even occurred to me that code could have "quality" π
I just had a bunch of feature ideas and had been messing around with some Python scripts, when Tim (the author of the bigger project) saw potential in me, took me under his wing in IRC, taught me C++, and created this stupid `Adam.cpp` file for me to go nuts in β€οΈ
π€ What's the best way to structure your classes and markup when building UIs with Tailwind CSS?
Here are some of the rules I follow to build things that are consistent, easy to understand, and straightforward to componentize π
Sort classes generally from the outside in (in terms of the box model) putting things that affect layout before things that don't, while also trying to group related classes.
This lets you see the things that are going to have the biggest impact quickly.
βοΈThis is a bit of an art, but hoping to automate in the near future!
I've been working on nailing the recommended class order a bit lately β check out my list so far on GitHub:
Maintaining open-source is brutal, and feeling obligated to acknowledge, review, and respond to every attempt to contribute is a huge burden to carry.
When I saw this tweet from @dhh the other day I couldn't help but s/email/open source contribution/, but it makes me feel horribly guilty to suggest that anyone should feel anything but grateful for unsolicited free work from contributors.
But the reality is even though folks are generally trying to help by contributing, those contributions still cost the maintainer more than they cost the contributor, in terms of time to review, stress worrying about making time to review, and long term maintenance.