I hate to say it, but Windows is much more productive than MacOS for the usually tasks you perform on an OS (with GUI, both have CLIs, but I'm not talking about them). I'm using both at work all day long switching between them. When reflecting why, I think it comes down to windows management and the file explorer (vs finder).
Yes, quite an oversight ... as Vue has it all: Adoption, maturity, ecosystem, features, DX and speed (with upcoming Vapor mode even on par with Svelte and Solid).
It's quite an oversight of the author did not to include Vue. Vue has it all and is as of now in terms of DX, features, ecosystem and performance (with upcoming Vue Vapor mode basically the same as Solid and Vue) the best choice.
No OP, but I've also used Angular, React, Vue, Solid and Svelte in real world projects and my default choice is Vue, because it's on par with Solid and Svelte (and with Vue Vapor those three are basically the same) but with the larger ecosystem (vuerouter, vueuse, nuxt, nuxt-ui, primevue, nuxt-content, ...). I must also say that React was by far the most unpleasant and unproductive to use.
The most infuriating thing is that people still believe that you need isomorphic rendering (Next, Sveltekit, Nuxt) to have a fast, interactive and SEO friendly apps.
It can. DX is pretty much the same for backend and CLI stuff using VS Code on Mac, Linux and Windows. I'm working daily on C# backend and CLI stuff on a Mac (those are the dev machines at my employer). DX is on par with Go and Rust (at least dotnet CLI, LSP, Debugger, I can't speak for the profiler as I've never used it). I like the Rust tooling most, but dotnet CLI is not far behind.
Language and std lib wise, C# sits in the sweet spot.
Not a fan of apps like this, tbh. First, most of us need to learn proper diaphragmatic breathing, which is *not* belly breathing. Then just sit still without any "cosmic" sounds or timer-apps and bring awareness to the breath. Force nothing, just observe. Calmness and relaxation go hand in hand with letting go and surrender.
Hmmm, interesting. I used Datagrip for some years, now DBeaver (as I don't have a JB subscription anymore). Datagrip was and probably still is very powerful with top intellisense. Now I'm using DBeaver and it's very solid. Ok, I'm not spending my whole day in it, but when I need it, it does the job well.
>> all without ever leaving your favorite code editor
How do I install this on Neovim then? Is there a LSP? Or is this Microsoft proprietary? I wonder how much better without Copilot integration this is then the competition.
I'm using DBeaver CE currently. Does all I need (also for SQLite).
I'm using Linux (Ubuntu LTS is a no brainer) on my desktop for years. It enables me to just do the things I want or need to do with my computer. Windows is much more in our way than it's helping us just using our devices.
I have a very nice Microsoft Surface Pro running Windows 10. I refuse to update to Windows 11. Has anyone tried a Linux distribution on such a device? Which one would you recommend?
> IMO any system where taking a dependency is "easy" and there is no penalty for size or cost is going to eventually lead to a dependency problem.
Go and C# (.NET) are counterexamples. They both have great ecosystems and just as simple and effective package management as Rust or JS (Node). But neither Go or C# have issues with dependency hell like Rust or even more JavaScript, because they have exceptional std libs and even large frameworks like ASP.NET or EF Core.
A great std lib is obviously the solution. Some Rust defenders are talking it down by giving Python as counter example. But again, Go and C# are proving them wrong. A great std lib is a solution, but one that comes with huge efforts that can only be made by large organisations like Google (Go) or Microsoft (C#).
If you require to have an account to try the web search out (which you have all the right in the world, it's your service), tell us before we enter the service and type in our search. This comes around as sneaky. You should be clear upfront.
Yes, my experience as well. Last year I had to make a decision for the stack of a small app at work that needs a SPA (3D viewing large data sets using threejs and agGrid if anyone cares) and with long term stability as very high prio.
Long story short: I ended up choosing ASP.NET Core with Minimal APIs. The main reason was indeed EF Core as ORM, which I consider as one if not the best ORM. In the Node world there's so much promise (Prisma, Drizzle, ...) but also so much churn.
NextJS has a lot of significant drawbacks, that's why there's an ongoing debate (which is healthy):
- Cost
- Complexity
- Learning curve
- Scalability
- Frequent changes
- And surprisingly bad performance compared with the direct competitors
Nowadays, NextJS is rarely the best tool for the job. Next and React are sitting in the "never got fired for buying IBM" spot. It is a well earned position, as both had a huge innovational impact.
Do you need best in class loading and SEO with some interactivity later on? Astro with islands. Vitepress does something similar.
Do you need a scalable, cost efficient and robust stack and have moderate interactivity? Traditional SSR (RoR, Django, .NET MVC, whatever) with maybe some HTMX.
Do you have a highly interactive app? Fast SPA like Svelte, Solid or Vue.
Yes, pure old school SPAs have at least one additional roundtrip on the first visit of the site:
1. Fetch index.html
2. Fetch js, css and other assets
3. Load personalized data (json)
But usually step 1 and 2 are served from a cdn, so very fast. On subsequent requests, 1 and 2 are usually served from the browser cache, so extremely fast.
SSR is usually not faster. Most often slower. You can check yourself in your browser dev tools (network tab):