Not sure if I am a Typescript fan but I would most of the time choose Typescript over Javascript most of the time for frontend or backend NodeJs development.
I used to think the same. Coming from the Java world (might explain why I like it) colleagues convinced me that it would be better to use another runtime (JVM/CLR) than trying to use types on NodeJs (it was stupid). I used Typescript in the first versions it was painful, trying to find type definitions, writing my owns, etc. So I did not insist and moved to Javascript for NodeJs.
I rediscovered the language 1 year ago and uses it for some frontend (Vue) and backend (api gateway, lambda, mongoDB/dynamoDB)
Nowadays I very much like the language, union and intersection types make it very expressive and precise. Compilation (or translation) is a little slow but bearable, and it is nice to have a common language and tooling between the frontend and backend. Most of the libraries provide and maintain typescript definition files when they are not themselves written in Typescript.
Sometimes I think the language goes too far in the features, I had a look at the latest versions and was a little bit puzzled by the complexity. But even for small projects to larger ones, I definitely prefer statically typed languages (with type inference and even implicit ones) especially when time is limited to write tests and have a good test coverage.
I have been running Arch (Gnome/Wayland) on a Dell XPS13 9380 for more than 6 months now without any issue except the fingerprint reader not being recognized.
The Arch wiki page for the 9370 really helped, especially since initially the battery was draining on sleep, not after applying the recommendations.
I dock it on USB-C 3.1 dock. The display switches instantly.
The Gnome/Wayland fractional scaling is however not good, the image is blurry. I don't use it.
I have been using Arch from Windows/Ubuntu at home (I run Ubuntu in a VM at work) since the beginning of the year on 2 personal latpops Asus/Dell and didn't have any issue.
On the Asus Nvidia updates broke my Windows manager on Ubuntu it not happen with Arch.
The Arch install is a little bit more complex but you can do exactly what you want which was for me: use systemd boot instead of grub, and cipher only the home partition.
Once the setup is done, I did not have any issue, fiddling to be done.
For me where I lost time on Linux was when I tried to customize my desktop environment to my liking with i3/polybar/etc. Now I just run Gnome3 on Wayland, far from perfect but it is a good compromise TBH between setup ease/integrated UI components and features.
I had to renew my Asus home laptop last June running Windows/Linux. I hesitated between a Linux or MacOS MacBookPro but I finally decided to buy a Dell XPS 13 9380. It costed me 1500Euros (i7 8cores/16Gb/512GbNvme/1080p/Thunderbolt3/IntelGpu920). The MacbookPro with a better screen but inferior keyboard costed 2500Euros...
We'll see how long the Dell will last. I am bit worried about the battery.
Since then I run Arch with Gnome3/Wayland and everything just works including bluetooth/suspend/usbc dock/etc... except the following:
- the fingerprint scanner, there are no Linux driver (even for the Ubuntu version sold by Dell)
- Wayland fractional scaling does not really work, everything is blurry, so I don't use it. When my I am disconnected from the external monitor I just type a command to do text scaling...
- Battery life is still inferior compared to Windows, especially when I watch youtube videos (I don't use Firefox on Linux because of the lack of hardware acceleration)
Compared to MacOSX I find Linux better for development and Ops. All the tools just work, are up-to-date and can be installed from the command line (pacman with the user repositories > brew/cask).
For amateur video editing/photo editing, you now have plenty of choice (especially for video).
Of course Gnome3 is inferior in term of performance, stability and is less visually appealing.
The OS is a commodity nowadays. Well more and more. Many applications can be found for the 3 major OS.
That is why more and more OS vendors offer cloud services like backup/security/planning tied to the OS, well integrated and not opened.
Also more and more Microsoft/Apple/Google will integrate AI related services tied to your usage and what they know of you, so Linux will not be able to compete in that area.
I used to think the same. Coming from the Java world (might explain why I like it) colleagues convinced me that it would be better to use another runtime (JVM/CLR) than trying to use types on NodeJs (it was stupid). I used Typescript in the first versions it was painful, trying to find type definitions, writing my owns, etc. So I did not insist and moved to Javascript for NodeJs.
I rediscovered the language 1 year ago and uses it for some frontend (Vue) and backend (api gateway, lambda, mongoDB/dynamoDB) Nowadays I very much like the language, union and intersection types make it very expressive and precise. Compilation (or translation) is a little slow but bearable, and it is nice to have a common language and tooling between the frontend and backend. Most of the libraries provide and maintain typescript definition files when they are not themselves written in Typescript. Sometimes I think the language goes too far in the features, I had a look at the latest versions and was a little bit puzzled by the complexity. But even for small projects to larger ones, I definitely prefer statically typed languages (with type inference and even implicit ones) especially when time is limited to write tests and have a good test coverage.