I'd say the Chrome devtools are a tiny bit better, usually with more features or a bit better UX. But there are also things where I find Firefox devtools better. And the features missing are not a deal breaker for me.
Overall it's a pretty similar experience. Most difficult part is the habit changing of getting used to a different UI.
Kinda harsh to see it that way. You could remove the last four 4 sentences of the post and don't see it as an ad at all. The post does actually explain the most important part and the guy just tells us we can hire him if we need help.
- compare the tailwind example and yours, they don't have the same behavior. The tailwind one has a specific mobile menu for example. And that is just one example.
- sure, but since the tailwind page does more things, it's logical it has more code. Your base for comparison is production used code, sold to people. So of course it's polished, it must handle browser bugs and other things you might not expect in a quickly implemented alternative for a tech article. So I'm not surprised the code is bigger. That doesn't say at all that tailwind == more HTML tags :)
it's just CSS yes, with the focus on naming your classes depending on the content you style instead of their looks. "article-excerpt" instead of "bg-white padding-2 shadow rounded".
The article is interesting but really feels unfair sometimes, it doesn't help:
- The whole "amount of CSS" part is unfair when the Semantic CSS implementation isn't responsive at all, so of course it will be lighter, it does less.
- The part about the big number of HTML elements is a bit frustrating too; tailwind doesn't require you to use more HTML tags at all. It's totally possible to redo the Semantic CSS example with tailwind by not adding any HTML tags.
Besides that, it's still interesting to try and compare what is the best between big HTML (atomic, tailwind) vs big CSS (semantic).
Tailwind is not perfect, and sure, sometimes, you can get more performant code by writing it the semantic way. Sometimes.
But tailwind sure is a great way to easily write maintainable CSS in a team with different skill sets, producing really performant code by default, on large web apps.
I wonder how these "visual story telling" articles are created, they are really great.
Like, what tools do the authors have. Are the content authors super tech savvy or not. How much specific code must be created for each article. How long does everything take compared to a normal, mostly-text page. How many people work on one article. etc. Must be pretty interesting.
And I have a few use cases where 32 Gb is limiting. So I don't want to buy a brand new machine stuck at something that is, sometimes, already not ideal. And well, the usual next step is 64 Gb.
Sadly I think this is hopeless. The trackpoint is a thing of the past. Modern thinkpad trackpoints are notably not as good as the ones from 10 years ago anyway. I personally use it less and less on my p14s and surprisingly, it's not that annoying.
yeah I get the benefits. And yeah the "repair" argument I agree, good luck finding a bad stick :)
The real frustrating thing as for now in the real world is, there is an extremely low number of laptops with soldered ram that offers 64 GB. And the few that do, charge an absurd amount of money for it.
With socketed ram, I can:
- buy the cheapest built-in config of a laptop
- then buy the RAM I currently need on my own, often saving a few hundreds bucks just doing that
- then, in a few years, buy some new RAM again, when I need it, if I need it, instead of having to buy a whole new laptop.
That's how I went with thinkpads during 15 years. Now I have to pay 500$ more to be a bit future proof. If the manufacturer offers it. Double that if you want a mac.
So, still today, I'm 100% taking socketed ram instead of soldered one.
I'm curious how it's 50% more expensive than (new) thinkpads. Personally I'm looking for machines where there is at least 64gb soldered, or the possibility to upgrade later. In the thinkpad line that means basically only the X1 now for 13/14 inches laptops. And it's not cheaper than the framework.
I agree about the rest, a few things are not quite there yet, or maybe will never be. But on lots of things it is really refreshing.
Framework is really appealing as thinkpads get more and more soldered everywhere. And pricing is surprisingly ok, especially if you target 64gb of RAM and a big ssd that you buy on your own and install yourself. You can almost buy 3 amd framework with those specs for one macbook pro.
Only thing that I'm afraid of is the build quality of the chassis that doesn't really seem on par with premium thinkpads and other business laptops.
I'm still in love with my x201s, the x220 predecessor. It was 16:10 and could have a super high res of… 1440x900, a rare thing in such a small format for the time. These small thinkpads were solid as hell, packed with I/O. Perfect keyboard. You could set it with a 90Wh battery. For a 12" laptop. Haha. Screen quality, speakers, touchpad were all garbage but oh well. So much other stuff was perfect. Good times.
Overall it's a pretty similar experience. Most difficult part is the habit changing of getting used to a different UI.