Leimi

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.

Great to see such a tool not tied to a hosting formula, page views and everything.

I see the value in helping me (the dev) quickly setting up landing pages and including them in my existing website that I host where I want.

Super useful, great job.

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.

I guess we use our machines in different ways :)

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.

man, I was convinced this was 32gb max, great to hear!

I have the gen 2 which is the most annoying thinkpad I ever had, but well, it's still really great compared to other brands.

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.

yeah it's surprising, notebookcheck also has benchmarks and the results go in favor of amd.

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.

totally agree :)

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.

thinkpad x13, hp 835 g9, dell latitude… and if you go for a 14" laptop, connectivity is even better while still having a small device.

I'm not sure more than 4 ports is _extremely_ niche use case especially for a work device, but yeah I get that most people would be okay with it and I understand Framework's choice.

Sadly I feel like trackpoints are really end of life and I wouldn't be surprised if Lenovo ditched them entirely soon. It seems they keep it only to please the tiny but vocal minority of tinkerers that we are. But we mostly buy old, second hand thinkpads.

And as keyboards get thinner, trackpoints lose in quality. On linux it seems the software side is also not as good as before with libinput.

So I'd be really surprised if any one new on the market would go about making keyboards with trackpoints now.

This is starting to be a really interesting choice compared to sticking to thinkpads.

The dream would be to have 6 expansion cards in the laptop 13. 4 really is a bummer for a work laptop, it's definitely not enough for me… And while you can easily carry other expansion cards and switch at will, it's kinda like carrying adapters, you easily forget them.

> From someone used to the comforts of Linux, MacOS takes a huge amount of effort and expenditure to only get 20% of the way there.

You summed it up nicely!

Sadly even with all the apps like hammerspoon, tiling wms and others, there are lots of stuff you can't customize in the macOS environment.

Some workflows on a linux system can be totally different than what is possible on a mac. Even with apps like BetterTouchTool, Hammerspoon, Amethyst and others. Customizing window management, advanced keyboard shortcuts, general system behavior in mac is going against the tide. It kinda works, but never as good as you'd want because you can't really get rid of the default window manager and default global behavior.

Some window manager in linux are more like window manager frameworks, like AwesomeWM, that lets you customize its behavior via lua scripting. It's extremely powerful and allows you to get exactly the behavior you want.

But this part of linux is pretty niche stuff for sure though haha.

I wouldn't say I'm more productive thanks to this, but I'm way happier using a system I can set up so that it behaves how I want, instead of having to follow rules I don't agree with and can't change.

I'd agree with you if the argument was "full desktop setup" vs "just a laptop". I sometimes envy people who can spend all day using only their laptop. After a few hours bent to look at my 12 inch screen, my neck and back scream.

But when using a laptop with a dock, a big external monitor, external keyboard, mouse etc, I don't see the point in using a desktop machine anymore.

I'd agree on the upgrades and repair arguments.

From an ergonomic/setup side, of course using laptops doesn't prevent you from using a dock, with external monitors, external keyboard and all. In fact a docked laptop that you can pick up in seconds when needed is way easier to deal with than two machines.

About the cost, do like we nerds do: buy refurbished thinkpads. For most software dev, having the latest i9 is not necessary. Old thinkpad workstations are perfect as desktop replacement machines and are somewhat upgradeable. I'm sure this doesn't scale that much but small-scale companies can do this without any trouble. Worked perfectly in a previous company I worked for. People were actually pretty happy we didn't buy 2000€ new stuff while 700€ already-on-the-planet stuff was more than enough.

In the react world, valtio is a breath of fresh air as it removes almost all boilerplate code.

It's pretty simple. "they won't pay at all": would you want to add the feature if he paid you? Then tell him that.

Don't want the feature? Just say no, close the issue and move on. Especially if your project is MIT licensed, it's crystal clear in the license that very one thing: you don't owe anything to anyone :) You don't need to be nice, you don't need to explain. Life's too complicated to be upset about those things.

If the person keeps on insisting after that, you can block him from GitHub.

I feel like easy nesting shouldn't be included in CSS. The only few times it's actually useful and harmless to have nesting in Sass is when we want to do stuff like styling anchor's hover and focus styles at the same time. And this is already solved in CSS with :is() and :where().

Most of the time I see nesting used, it ends up either in a stylesheet that is less readable than without it, or in generating css classes that are way more specific than necessary.

It's not that it's such a boost in productivity, more a boost in comfort. You stop switching from mouse to keyboard all the time.

This seems like a good explaination!

Having the tab shown and having the accessibility tool working and consuming resource seems to be two different things.