Love Sublime and have used it since its inception long ago, however as the times changes with different built-in convenience tooling (such as AI), Zed has overtaken Sublime IMO. It's fast, has VIM mode, extensions, and takes away some of the hassle that you have to go through with ST.
I still use ST for basic editing, but for day-to-day, Zed is the go to, simply because it just helps me get my work done slightly faster.
The new docs are extremely annoying; if you're still running a legacy app, sometimes you get put into a doc for a feature you think exists, but then you realize it's not for the right version you're running.
Also the new app routers are very confusing. There are concepts of a layout, template, page, etc. While it's nice to have server rendering at this level, it's difficult to understand what is bubbling which direction, and when to use a layout vs a template. Sometimes after building something one way (eg using layout), you realize you actually need to build it using the other in order for specific features to work.
Old Next was great and simple- new Next has become increasingly frustrating and not so easy to adopt.
The crucial difference is keeping the address bar- this is where I think Arc is falling short. Maybe it's me, but I have an extremely difficult time reprogramming my expectations of where the address bar should be.
The NY Times is notoriously the worst at this. It's almost impossible to cancel without wasting a couple hours of your time. Interesting how I can subscribe with a click but can't cancel with one.
I’m trying to love GitHub Actions, however, when builds and tests randomly fail on custom runners when they’re configured the exact same and there’s no option to debug, it becomes painstakingly frustrating. We’ve tried most of the big CIs, Travis/CircleCI/codeship- and while GH Actions integrates nicely with GitHub itself, it’s a far less superior product compared to its peers.
There are better ways to gather feedback, even if your application is in beta. Most loyal customers will let you know what’s wrong and what features they’re most excited about- that honest feedback is far superior than telemetry data. You can even add a survey form after the application exits to try and maximize the feedback loop.
Totally understand you’re a new venture backed business, however, you most likely are targeting the wrong group of users by automatically sending data over the internet for “no reason”.
That's a ton of data being collected. I would rather much have this submitted during a crash, rather than opt-in/opt-out. I'd not want to use a terminal that has data collection that crosses the internet every time I use it.
Crazy how you need a tool that reads another tool to figure out how much you're spending for the original tool.
I'm sure there was a purpose for how the AWS console was originally built, but if someone spent this much time for an alternative, there's a clear problem in its original conception.
At this point, Darklang just seems like an over glorified side project. I cannot see any real business creating an entire backend system out of darklang- the learning curve, vendor lock-in, and volatility of the project is not worth the risk.
Developers hate these tools for a reason: they're the ones maintaining it after it's been deployed. The whole concept of "no-code website builder" ultimately goes back to "where is the code and how do we modify or integrate it with our current systems".
Maybe if it was marketed as a "fast prototyping" tool, I'd be more on board with the product.
I would argue that reset style sheets or normalizers should be part of your "minimal web dev" process, even if you roll your own version. There are so many browser nuances that these things fix so that you don't have to hack it later down the line.