neoberg

To your second question about the app size vs. framework/library sizes:

Frameworks and libraries provide generalised solutions to some common problems. In react and react-dom's case it's defining a ui in a declarative and more or less performant(wihtout making the dev think too much about it) way. The downside is; it includes lots of things your app doesn't need but other apps do.

The alternative is to roll your own but if your solution did all the things that the X framework did; then you'd end up with a similar size/complexity. You can build the features only needed by your app; but then I can't imagine the amount of engineering hours wasted for every apps custom framework.

And nowadays ~110kb is not that big of an application really. It might be really complex in terms of concepts and what it does but current day apps are a lot bigger than that in terms of size. So the size of frameworks doesn't make that much of a difference in most cases. For example the app I'm working on in my job has a total bundle size of ~15mb minified excluding any third party code. This is just the code written and being actively used by us. We don't serve it all at once and load as needed but still.

Yes retina display is 2x. But saying a display is 4k doesn't tell anything about its pixel density or scaling.

I look at the original commenters screenshot at 50% browser scaling but it's still blurry. I guess there is an element of image compression there.

On the other hand; from my own experience (I own linux, macos and windows pcs) on the same display Macos text rendering is much more sharper and pleasant to look at.

no I'm not using any zoom or extra scaling. It's the native scaling of mbp retina display. Screenshot is ~2 times bigger than what I actually see.

edit: your second screenshot looks very sharp and nice on my display.

Yeah that and many more convenience reasons are why people like me don't prefer to use linux on desktop. Also even if you have your setup, not being able to view hdr content at all on linux is a big turn off for me personally.

Off the top of my mind; mouse & trackpad, sound stack, bluetooth stack, hd/4k content streaming, no hdr at all, using multiple displays with different dpis... I tried every recommended driver&setting for mouse&trackpad. They are all terrible compared to Macos. The whole story of using multiple displays with xrandr, xinerama etc. is a joke. Agreed; you get a better experience with Wayland regarding that but then you lose the ability to do screenshare for the most part (without doing hacky stuff instead of doing work).

> When was the last time you used Linux

Yesterday and it was terrible.

> Never have I faced any issue that can't easily be solved. (If at all there were issues)

Good luck viewing hdr content.

There is always a way. But convenience is also important and time is valuable. So instead of just clicking on a title on Netflix, we should instal & maintain a server and search for content on torrents?

Yeah but is it really user's problem if a system requires lot's of knowledge to do computer stuff without breaking the system? I don't have the time neither want to learn the intricacies of an operating system to do my work.

It looks very bad tbh. This is how my comment looks on Mac for comparison. Uploading to imgur to test if there is compression in play here. https://i.imgur.com/hSirmx6.png

For work I use Macos because that is the only option I have for several reasons; and I also like it. For gaming and media consumption, there is no HDR support on Linux and there won't be in the foreseeable future. So, Windows there.

Lick your finger and then try. It usually helps.

Sweden is lucky that Erdogan is in power and he'll bend and do a 180 in a month max. If anyone else was in that position, this would never happen. This topic is probably the only thing that has this much mainstream support since Erdogan came to power.

not op but Java and C# are horrible, too.

So when it's stolen a thief can just switch it off?

Because real GUIs are designed to be useful.

Thank you. My day to day work involves sharing screen on calls a lot. While I know it's possible to some extent with pipewire, it is still too hacky and too much effort for a simple(from an end-user standpoint) task. Afaik it still doesn't work with Zoom at all. But I am in general excited about Wayland.

It was last summer. I bought one of the recommended laptops for running Linux just for the purpose of switching. It sucked hard.

(rant following so please don't read the rest if you don't like ranting about linux desktop)

I could probably live with trackpad not being great. But the sound stack, bluetooth stack, driving displays with different dpi (hidpi and non-hidpi) etc. are all terrible. Managing multiple displays (xrandr, xinerama etc.) even without the dpi difference is also just bad. If you like to tinker it's great but I just couldn't make the switch. It didn't give me the confidence that it will work when I need it. I tried all major distros and read almost the entirety of the arch wiki (it is so good). i3 is one of the things that would make me try again in the future. There is nothing like it on macos (some wms try but they always feel duct-taped). And systemd is good.

This. I don't care about ripped or dirty clothes since their function is to warm me and I don't see them when I wear them anyways.

But the most important thing with Apple trackpad is not the haptics imo. If Apple went back to regular buttons tomorrow I wouldn't care at all. The tracking itself is light years ahead of any competition. This is still one of the big things keeping me from using Linux (even on Macbooks). Tracking and scrolling is just unbearable. (Yes I tried that driver, the other library, the recommended macos like settings, custom settings... I spent a LONG time trying to have something decent. Nothing is even remotely close.)

I've been using React full time almost since its first release and I somewhat agree with the previous comment. While the choice of framework usually doesn't really restrict what can be done; it's often easier/harder to do specific things with a given framework.

For example; animations responding to user interactions are easier to do in frameworks with an OOP approach. It is generally more "different" in a declarative way. So most React apps simply don't have those. There are lots of small things like this that over time make React apps feel Reacty.

Yes. But the parent comment mentioned rallying. Group B was during 80s.

Because it makes the "story" more interesting? It's not an f1 documentary. It's a show based on f1. There is a difference.

Good old days where people dying was a part of the sport.

Yes but to try and experiment with those assets "in game", they'd need to use a PC.

I agree that hooks "can" be messy but in my experience they are quite useful and nice to maintain. That is if the code is written with maintainability in mind - which applies to any code really.

I've been working on a quite complex React codebase for 5 years now - it's not the biggest but still not so small. I was there on day 1. The team that works on it now full time is ~15 devs + 10-15 doing some minor stuff from time to time.

We've started using hooks about 1 year after they introduced them. Before we were very deep into redux and redux-saga. Now most of our codebase uses only hooks for most of the things we did with redux before - there are still some redux but most major parts are migrated to using hooks and contexts. It is probably the best decision we made after switching to TS. Most of our codebase is still very easy to maintain. Last year I went on a paternity leave for 6 months and I was pleasantly surprised how easy it was to adapt back.

Edit: forgot to write about Elm. I like elm a lot -even though I don't agree with how it's managed-. I even organized a local elm meetup :) But I think while it is very good in theory, it's not too easy to scale especially if you plan on hiring more devs. Also the way effects and data is completely separated from the view is not very ideal for bigger projects. You either end up having to touch too many files for a single feature or have incredibly big files.

Why tho? Cheating just takes away from the cheater's experience and doesn't affect anyone else. It's pretty much like any physical game. You can play (or cheat) it any way you like even though the game is designed to be played in a certain way.

Let's say you are developing a design application (think figma) which works in the browser. You don't want to lock the whole project just because someone needs to change a label somewhere. With CRDTs n people can open and edit the project at the same time and then push their changes and have them merged.

Very similar to git. When working with git, you don't lock the file or line you are working on.

Yes it's the same for us. He's 3 something now and his only interaction with screens is for calling the grandparents because they are at 2 days driving distance. We don't hide screens from him tho; I think that also contributes to him not being interested in screens too much.

I was talking mostly about the desktop space. My experience is from more or less the current generation of desktop OSes (GUIs as default etc.).

I agree with most of what you said.

> If I don't expose them to coding, how could I ever know they're interested or not?

About this one; programming nowadays is not some obscure niche thing that it's impossible to come by unless introduced by someone else. I started my programming career (being paid to do) when I was a teenager. There was no-one using computers around me let alone knowing what programming is to introduce it to me. I believe nowadays everyone in a somewhat developed or developing country will have the opportunity to choose whether to learn coding or not.